FreeLists / openbeos / [openbeos] Re: status update and task list update.

[Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx>]

You are right, this hasn't been done by some of the teams. I just read 
through them all and some are very up to date, but others aren't. 

Here are some potential areas that need help:
Kernel - I hate to beat this drum too hard, since an influx of people new to 
kernel development can harm more than help, but this is the big one. IF you 
are comfortable working on this level of code and are a self-starter, talk to 
Axel.

Networking - we have very little going on in networking lately. This stuff is 
mostly done; it is kernel code, too, though, so please be careful. :-)

BFS - if you are a QA type or just want to find bugs for Axel, d/l BFS, make 
a BFS test partition or test file and beat this thing until it breaks. Script 
how it breaks. Send it to Axel with a "haha" message. :-)

Preferences - there are still a bunch of these to write. I have ported a 
whole bunch which will go into CVS today (I hope), but there are still a 
whole lot that need to be done. This is quick one-off action if you have a 
few days but don't want to make a long term commitment.





On 2004-03-01 at 05:01:45 [-0500], Chira, Valentin wrote:
> Hi, you guys said that soon somone will update the status list and the task
> list. this was a couple of months before. If somone wants to give a helfull
> hand it doesn't know exactly what is done and what he could do. Maybe a more
> up-to-date task list can bring more developers. Another question is about
> the development/testing process. how are you guys doing this? Lets say I
> would like to help how can I? Is there a document that describes how could
> one start doing things?
> 
> regards,
>  Valentin