Sure, go for it ! Since there are some samples already, this shouldn't be difficult to figure out for most others. Just leave the trickiest to the team it belongs to. I checked the sample codes in the be mirrors, but if someone has something I missed in source form, no need to redo it, jut put it in the CVS and/or mail me. En réponse à Ryan Leavengood <mrcode@xxxxxxxxx>: > Most of these seem like they would be perfect for "newbies", similar to > the > Preferences Team. In fact, these seems like they belong in the > Preference > Team since it is already doing some of the other miscellanous apps in > R5. > > I'm a member of the Preferences Team myself and have so far been > "bootstrapping": reading the BeBook, reviewing C/C++ (I'm a Java > programmer > with minimal C/C++ experience), and getting a Be machine set up. > Seeing > this list of /bin apps has reinvigorated me since they are all nice, > small > projects that can be completed fairly easily without being a Be guru. > Maybe > some of the current non-contributors like myself can get started by > coding > up some of these. Seems like there are plenty to go around... > > Ryan > > ----- Original Message ----- > From: "François Revol" <revol@xxxxxxx> > To: <openbeos@xxxxxxxxxxxxx> > Sent: Thursday, April 25, 2002 1:31 PM > Subject: [openbeos] Re: commands in /bin > > > > 2 ways: > > - each binary belongs to a kit so each team make binaries that goes > with, > > and teamless bins are made by a new team, > > or > > - we have a dedicated team fir command line apps. (but some bins need > team > > specific infos) > > > > Anyway, I got a prio replacement, and I'll put the renice I coded > also. > > > > table: > http://clapcrest.free.fr/revol/beos/openbeos_bin_commands.html > > (shell script rulz) > > > > I'll complete the table anyway... > > > > François > > >