Bounty Poll Results
I understand the importance of having the blocking alpha bugs squashed, but at the same time realize that there are really only a few core Haiku developers that can solve these problems, and I'm not so sure they're receptive to bounties. They have enough to worry about on their plates, and I'm sure these bugs will get solved eventually; when they have time.
Now might be a good time to also mention the third most popular bounty based on the votes. A flash port. This bounty already exists, and has a healthy pool of ~$425
Regarding a wireless bounty, Ithamar and Fredrik Holmqvist were looking into wireless, and Urias McCollough reported on Haiku's website that Ithamar "would like to work on porting FreeBSD's wireless stack where Fredrik Holmqvist left off".
I personally emailed Ithamar to ask if he's consider a wireless bounty and he replied in a thread at Haikuware:
"I've had a closer look at wireless, and I personally feel we shouldn't push for this at this time. There's a lot to be done for it to work properly, and I guess we'd like to have it supported in a more fundemental way then just a 'simple' recompile from BSD (which would make it part of the FreeBSD compatiblity layer)".
However, I told him I'd run a poll and he said:
"I'm not turning a wireless bounty down. Let's see what the community says, and if the Alpha items don't get enough backing, we'll take another look".
So there you have it. Personally, I think this is a huge project, and $750 just doesn't cut it. If we could get some of the 58 people that voted for the wireless bounty to contribute some money towards this bounty and raise it to $2000-3000 maybe it will get a better second look...
I am going to contact the contributors to the Macbook bounty and ask if they'd like a refund, if not, the money will be transferred into a wireless bounty that should be opened by this Friday. Please contribute!
Thanks again for all the input and voting!
Top Downloads in 90 Days
Free Heroes of Might and Magic II
ICH AC97 Driver
BeOS 5 PE Max Edition
Wifi driver for Intel WiFi Link 1000/5000/6000 Series
VLC Media Player
Kadu 0.6.5.3
gnash-bzr-r1a1-x86-gcc4-2009-12-13.zipLatest Hardware
Search Files
Newest Files
Feb 8 |
SimCar |
| Feb 8 |
Qt-App Installer - GCC4 |
| Feb 8 |
Qt-App Installer - GCC2 |
| Feb 7 |
LottoGen |
| Feb 5 |
Arora |
| Feb 5 |
KOffice for Haiku |
| Feb 4 |
Synthetic Package Manager |
| Feb 4 |
C-Dogs SDL |
| Feb 4 |
QuickLaunch |
| Feb 4 |
QuickLaunch(gcc2) |
| Feb 3 |
QueryWatcher |
| Feb 1 |
BeSly Tutorial Editor |
| Jan 30 |
yab starter Script |
| Jan 30 |
Get Haiku Bin Tools |
| Jan 29 |
SDLGameLibraries GCC4 |
| Jan 28 |
Wormux 0.9.0 |
| Jan 24 |
){kind=icon}
MacFile Server for Haiku |
| Jan 22 |
Arora 0.10.2 |
| Jan 22 |
PhotoGrabber 2.2 R114 gcc4 |
| Jan 21 |
Be_Canny_or_be_a_Donkey |
Comments
May I suggest to post on the dev mailing list, asking if anyone of the core devs is willing and able to take the Alpha-Blocker bounty, take a break from his day job for two weeks to squash the last big bugs?
At least to me, it would make more sense to spend the $750 now to get an alpha in a few weeks than trying to raise $3000 over next months to maybe get wireless support next year (which maybe could come without a bounty should more devs work together instead of one paid man alone).
If really nobody is interested or can’t take the time out, you can always come back for the wireless bounty. But I think it’s worth a try.
It’s a bit awkward with the poll being over, but I understood it as more of an opinion gauge than a poll to definitely determine the next bounty. Anyway, all just IMHO…
Quote:
I think it's perfectly logical. Since Ithamar would probably be the only developer that *might* have taken on the wireless bounty, and he already stated his preference is the alpha bugs bounty. $750 should be enough for a paid work week to look at these bugs.
Care to initiate the dev-thread?
Whether it be discussed on the mailing list or as a possible future bounty.
It should be something along the lines of:
$x for resolving issue #K ,
$y for issue #L,
and so on.
This would break the entire list into separate smaller bounties,
which should be an easier goal for a particular dev to attain.
Plus, multiple devs would be able to work on multiple tasks.
Mmadia's suggestion may be a good one. However, consider that we only have a small budget. That there are still alpha blockers indicates that they are hard to solve. So it may really be an issue of lack of time due to a paying day job. Offering $50-$100 per bug wouldn't help in that situation as it's not "motivation-limited".
Anyway, let's see what those devs have to say.
RSS feed for comments to this post.