[openbeos] Re: Bounties
- From: "Brian Verre" <bverre@xxxxxxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Tue, 17 Jul 2007 16:48:23 -0500
I support this bounty idea (don't have much time to help in other ways ATM).
I'll put forward US$50 each on #3,#6 and on #7 by Friday @ haikuware. Also,
maybe we should have a Java bounty (given there is someone picking that up
again).
I would like to offer this as well: I have a bunch of custom EFI code (two
working bootloaders, not elilo) that was gathered for an AppleTV project, and
some good documentation. Some of this code is not online anymore, and I had to
track down the authors to get copies. Semthex from the OSX scene could help you
with EFI too, btw. Good guy, capable hacker. The project licensing is fairly
open if I remember, if anyone would like copies email me at bverre@xxxxxxxxx
<mailto:bverre@xxxxxxxxx> . One is the last SVN code from that XP on Mac bounty
that won for a little over $10k.
Thanks Karl!
________________________________
From: openbeos-bounce@xxxxxxxxxxxxx on behalf of Karl vom Dorff
Sent: Tue 7/17/2007 4:01 PM
To: openbeos@xxxxxxxxxxxxx
Subject: [openbeos] Bounties
Dear all,
As you may know, I have come to the decision to resurrect a bounty project. I
believe that Haiku is far from where it was the last time we tried this; if you
recall, Haiku didn't even have a website back then! Some may have seen the
project as a failure, while in the end, I believe everyone came out happy since
the proceeds were donated to Haiku.
A while back I held a poll asking users where they'd like to see a renewed
bounty project - At Haiku or Haikuware. Surprisingly, 60% voted in favour of
having it at Haikuware. I had mixed feelings about this and then gave a weeks
notice to every registered user at Haikuware (of which there are a few Haiku
devs) to have a discussion about a bounty project. I also gave another email to
remind everyone 15 minutes before the discussion. I was a little upset not to
get any input from anyone directly related in the active development of Haiku,
but as a couple of people said in the discussion, Haiku shouldn't have to worry
about bounties, and a third party should help with that.
It took some contemplating on my part, but with that discussion, the lack of
turnout, and the results of the poll, I've decided that I would host the
project at Haikuware. I realize this may not be ideal for some, but I can't
please everyone. Even Axel commented that Haiku would get a bounty system with
or without me, and that it was just a matter of time. And that's fine, but
until then, I'd like to ask for Haiku's support with what we have, and that
will be a fully functional bounty system at Haikuware within the next couple of
days (I just have to work out some of the rules and guidelines). I'm pleased to
announce that we will team up with OSDrawer.net <http://osdrawer.net/> to host
any of the bounty projects.
What I'm asking for, is for developers with a thorough knowledge of Haiku
identify some 'show stopping' parts of Haiku that are missing for the R1
release. I've identified these areas (not all are R1 material), but would like
to hear first hand from Haiku devs what they feel is needed:
1) Hardware/driver management and database program (as described in the news
<http://www.haikuware.com/index.php?option=com_content&task=view&id=38&Itemid=1>
). An implementation similar to that of the hardware database program on the
Kubuntu <http://www.kubuntu.com/download.php> and Ubuntu
<http://www.ubuntu.com/getubuntu/download> LiveCDs would be ideal.
2) A simple CD burning application with support for Data/Audio/Disc Images
3) NDIS Wrapper <http://ndiswrapper.sourceforge.net/joomla/>
4) LIRC <http://www.lirc.org/> port (Project started
<http://bebits.com/app/3860> on BeOS)
5) CUPS <http://www.cups.org/> port
6) Webkit port.
7) EFI module (boot EFI motherboards)
8) Haiku Drive Setup
9) Haiku Bootman
10) Intel, Via and Nvidia SATA drivers (port Syllable's FreeBSD drivers?)
I am open to criticism about the project, but, try to keep things on a
constructive level please!
Regards,
Karl
Other related posts:
