[openbeos] Re: Reporting for duty

> Well, after a bit of difficulty in running BeOS on too-advanced 
> hardware,
> I've borrowed a hard drive and network card from some generous 
> friends and
> am up and running with BeOS R5. (Specifically the nicely put together
> "BeOS Developer Edition" available on BeBits).

Firstly download a new compiler - the one in dev ed is fairly badly 
broken IIRC. Either just get the R5 Developer Tools from the R5 PE page 
at BeBits, or download the GeekGadgets package from BeBits that also 
contains a working compiler.

> Now, somebody who wanted to jump in and lend a hand .. what would 
> they do
> about that? I'm not a kernel wizard, but I like to think I'm a pretty 
> fast
> learner (I've read and understood the Xinu book, if that counts for
> anything and have patched FreeBSD in small ways before, nothing 
> major).
> Are there any groups in need of extra hands/eyes? Should I just 
> attach
> myself to a group and find out what they need done?

I think accepted practice is just to pick an area you're interested in, 
find out what needs doing (look at the team page on the website, but 
email the relevant mailing list too as some of the team pages are out 
of date), and then get some code written. I think there's an entry in 
the FAQ about how to get involved.

Simon

Other related posts: