[openbeos] Re: The neglected parts of OpenBeOS

  • From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Wed, 02 Oct 2002 08:10:44 -0400

MIDI is one, if you are interested. ;-)
There are others, if anyone else is interested.

One of the best things that we have ever done is to move to a more task 
oriented way of doing things. Anyone can pick a task off of a team's list, let 
the team lead know, and do it. Most of the work is fairly independent of other 
work, so you probably won't be holding your team up. The only real demand that 
working on OBOS should place on you is a short email to the team lead once a 
week that gives them a clue where you are. This might sound overly corporate. 
Really, the only point to this is to show them that you are still around and to 
allow them to see possible problems in the "schedule" (i.e. nothing has been 
done on BFoo for 4 months). 

So, everyone, grab a task. Many hands make light work...

<Your local neighborhood recruiter>

>Hi all,
>In the latest newsletter, Michael Phipps writes:
>"Whether this is paying code bounties or paying someone to write
>code, I am not sure. But this could facilitate some of the areas t
>hat are not moving."
>My question to you all is, what exactly are these "areas that are
>not moving"? As a long-time BeOS developer, I am interested in
>contributing to OpenBeOS, but so far the tasks seem boring
>(recreating command line apps or preferences apps doesn't really
>captivate me) or interesting but too fast-paced for me (I have a
>company to run, and spare time is limited).
>But I would like to contribute, and writing code is what I do best.
>So if there are any neglected parts that need attention, then I'd
>like to take a look at them to see if they interest me, and whether
>I can fit them into my own schedule. And it's okay if the task is
>hard, because I do like a challenge ;-)
>Matthijs Hollemans
>All Your Software

Other related posts: