Re: [E-devel] For code owners and contributers

2003-02-14 Thread Ibukun Olumuyiwa
On Fri 14 Feb 2003, Ben Martin wrote: *snip* > Maybe we can add a list of which projects should get the new love, so > that folks dont start hacking on something like ebits1 etc? This way > they know what is for hacking and that those projects need love no > matter how many names are attached. Gim

Re: [E-devel] For code owners and contributers

2003-02-14 Thread Ben Rockwood
>> technically cvs does this for us :) > > Well, that was partially my point. But now that I think about it: > > - No, cvs only tracks who changes what. We need to encourage commit > comments that say what the change does functionally. > - I'd suggest not using the ChangeLog files on pre 1.0

Re: [E-devel] For code owners and contributers

2003-02-14 Thread Valdis . Kletnieks
On Fri, 14 Feb 2003 06:37:12 EST, Kevin Brosius <[EMAIL PROTECTED]> said: > - I'd suggest not using the ChangeLog files on pre 1.0 apps/libs and > sticking to it. For packages that are stable, then a ChangeLog should This implies that we force something to go to 1.0 when there's enough usage

Re: [E-devel] For code owners and contributers

2003-02-14 Thread Kevin Brosius
"Carsten Haitzler (The Rasterman)" wrote: > > > On Thu, 13 Feb 2003 17:19:26 -0500 Kevin Brosius <[EMAIL PROTECTED]> babbled: > > > Ben Rockwood wrote: > > > > > > > > (snip) > > >been noted in the AUTHORS files of each project and the ChangeLog of > > > > Well, one of the points of doing ne

Re: [E-devel] For code owners and contributers

2003-02-14 Thread The Rasterman
On Thu, 13 Feb 2003 17:19:26 -0500 Kevin Brosius <[EMAIL PROTECTED]> babbled: > Ben Rockwood wrote: > > > > > (snip) > >been noted in the AUTHORS files of each project and the ChangeLog of > > Well, one of the points of doing new/early development in cvs is that > you don't maintain a chang

Re: [E-devel] For code owners and contributers

2003-02-13 Thread The Rasterman
On 14 Feb 2003 12:10:40 +1000 Ben Martin <[EMAIL PROTECTED]> babbled: > On Fri, 2003-02-14 at 08:35, Carsten Haitzler wrote: > > > > > 1. collect all names from AUTHORS files. list all of them. (this will assume > > the step of making sure they are up-to-date has been done) i REPEAT it is > > th

Re: [E-devel] For code owners and contributers

2003-02-13 Thread Ben Martin
On Fri, 2003-02-14 at 08:35, Carsten Haitzler wrote: > > 1. collect all names from AUTHORS files. list all of them. (this will assume the > step of making sure they are up-to-date has been done) i REPEAT it is the > responsibility of the contributors to make sure their patches include patches to

Re: [E-devel] For code owners and contributers

2003-02-13 Thread Ben Rockwood
Agreed In which case you might wanna just put a reference to SF's CVS Web, which can act as a ChangeLog. Since most projects aren't GPL I don't think we're stuck with all the Changelog requirements. benr. > Ben Rockwood wrote: >> >> > (snip) >>been noted in the AUTHORS files of each pro

Re: [E-devel] For code owners and contributers

2003-02-13 Thread The Rasterman
On Thu, 13 Feb 2003 13:19:09 -0800 (PST) "Ben Rockwood" <[EMAIL PROTECTED]> babbled: > > Hello All. > > I'm planning a complete re-vamp of the team page soon to remove all the > old non-active people from that page. The hope is to encourage new > people to join the effort who may look at

Re: [E-devel] For code owners and contributers

2003-02-13 Thread Kevin Brosius
Ben Rockwood wrote: > > (snip) >been noted in the AUTHORS files of each project and the ChangeLog of Well, one of the points of doing new/early development in cvs is that you don't maintain a changelog... -- Kevin --- This SF.NET email