I will never ever use a piece of software distributed like that.
Could You explain why not?
I can't speak for Hoodoo, but I wouldn't, neither. For me, personally, it creates a blackmail-y feeling. I guess for the more general community, it also brings back memories of similar things in the past that didn't work out too well.
Also, specifically for ports, there is an unease at taking what is mostly someone elses work and "holding it hostage" for money. This would be frowned upon quite strongly from an FOSS perspective - Enough so that I imagine that if you started out doing something like this, some other talented coder (I.e. not me - This is not me doing veiled threats) would negate it by doing a parallel port in the "grace time". Since I'm not able to write well enough for me to understand myself today (Have a fever and a big fat head cold. My brain is two sizes too big for my skull), I'll give an example of what I mean:
You: "I have now ported MegaAPP 3000, and those who want it now can donate $4 - I will release it to everyone in four weeks time!"
One week later:
SomeoneElse: "I've now ported MegaAPP 3000. Get it as usual from the Repo"
In short, I imagine it will leave you with a bad reputation and your donators with a feeling of having been ripped off.
Really, in the end, I think there are a few unmovable principles of this hobby:
* It is a hobby, not a work. You will not be making noticable amounts of money out of this. Not even, I think, enough to pay for good standard hosting.
* Donations comes from many users. Many users come from quality of software
and ease of getting hold of.
As it is, the standard way to get the pandora software fix is by the Repo. Not putting your ports on the repo is an extra complication for the users. Not putting it on one of the other, less-used places (archive/app store) makes it even more complicated. Fiddling about with several classes of users (paid/not paid) and thinking about whether to donate now or wait till later is more complication. At every step of complicating, you will lose potential users (and thereby potential donors) who just can't be arsed to figure out how to jump the hoops. You'd need a real killer app to pull people past those barriers, and as the reference to Zod above goes to show, even that doesn't help, sometimes.
In the end, you have the problem/question: "I'd like to have a lot of users of my ported apps donate a little to me, so that the apps themselves at least pay for the hosting for them", more or less. And it is very hard to avoid the conclusion that "Well, sonny, put them on the Repo. That way, you will get the most users, the donation infrastructure is built-in, and the hosting is free. Problem solved
and disappeared, at the same time".
Now, I have no idea about what the problem is between you and the Repo. There has been some similar incidents earlier, where some devs have publicly stated that they do not wish their work to appear on the app store, for instance, in reponse to something Craig has said or done. It is a good thing to have principles and ideals to stand by
but there is also a cost associated by holding on to a principle in face of the easy solution (this is a general observation). In this case, the decision to not use the obvious way to host and distribute your work will cost you in users (and donations) and in hosting. It is the price to pay for your conviction, and I'd imagine the solution is to think about whether the conviction is worth the cost.
End Apology: I've a headache and my breathing apparatus is full of goo. I do not quite feel at home in english today (whether on the reading or writing side, I can't tell). I'm trying, in the above, to be helpful. If it comes across as fingerpointing, or if I stepped on someones toes, blame my cold, not me