Ingo Weinhold wrote:
On 2012-05-25 at 01:09:22 [+0200], Sean Collins <smc.collins@xxxxxxxxxxx> wrote: I am not familiar with European workplace hours either -- AFAIK they vary -- for Germany it's typically 40 h/week, so about 160 h/month (averaging in public holidays). But I believe the previous contracts had been for a fixed number of hours anyway, so it doesn't really matter how many hours per week or month one works.I understand if your more a contract worker how that could be. contract employement is extremly uncommon in the states for the most part.
One of the problems is that even estimating how much time reaching a goal takes gets the more complicated the larger the task. Furthermore something like "finish up Haiku into a usable state" is extremely fuzzy. Even if you define a fixed set of tickets that this task encompasses, it would contain a good deal of bugs that may be hard to reproduce and track down.Well, I think defining to the donors what needs completion, a list of tickets, issues and missing functionality, incomplete functionality and what it would take "rough estimation here" to get haiku to at least Beta, would be a very useful thing. Obviously bug hunting generally takes more time then feature additions. At least thats been my observations of software development.
The should probably best be answered by Haiku, Inc., but anyway ...
I've never felt comfortable posting to that list. Honestly because I don't really have much to add to it. It'd be arguable to say I add anything of value to this list. but I do like to monitor it to stay in the loop.
The issue is the level of funding, if there is more $$$$ on the plate, more work can be accomplished.So far, at least for contracts, I believe every contract proposal has been accepted and funded.
I don't know which milestone you refer to, but e.g. the work on WebPositive has certainly resulted in tangible results. The work on package management isn't included in the main repository yet (and won't be until it is more or less done), but there has been quite a bit of progress (you can check out the branch and test a fully packaged system). All other contracts have resulted in significant progress es well.I'd not argue the point about webpositive. Would you give a realistic estimate of the cost to finish the package management ? You are a pretty seasoned professional, I would think you have a good idea in relative time "weeks" what it would take to complete the task. Lets put a dollar amount on it and get it done.
To my knowledge all contracts save Michael's recent one (who had to step back due to health/personal issues AFAIK) have been completed. Most of them have been documented by blog posts.Well, one must ask "/please mind you I am not criticizing Micheal's work, it solved several issues for me/" what exactly did Haiku's donor base get for this investment ?Ultimately the users are willing to make the investment, but if you read the forums, and you pay attention to press about haiku and even in other FOSS communitys, you can see fustration, disapointment and a attitude out there that haiku is the duke Nukem forever of FOSS Operating systems. I can understand how that attitude could emerge. Haiku could be all the things that Linux has fialed to be, and it seems pretty stable, and the drivers keep getting better, and the stability is pretty good. so it seems like Haiku is in perpetual feature creep hell.
Eventually, the racecar must go down the racetrack, and eventually, everybody ships a product.
but the users view all donations as investments, and I think they are seriously starting to question if this is a good thing to do ? Is haiku a good investment ?
Please don't take these as criticisms, I am simply trying to represent the view point of the donorsCriticism is fine. If there are (perceived) communication issues, they should be addressed.CU, Ingo
Theres nothing perceived about it, the users see no time line to ship code.
Sean
