Add-on to previous msg: Each branch is required to have a status doc and a todo doc and any committer is allowed to red flag a branch if they feel it is out of date, fubarred, etc. One flag would not prevent commits, but a certain number of flags should prevent commits until thos flags are taken away. Also a hall of shame listing the ten developers with the most flags. Be nice to have a bravo list as well, each committer can give a bravo to a developer and a hall of fame lists top ten. If this was done it might be a good idea to model after the duke dollars program.
----- Original Message ----- From: "Bill Barnhill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 22, 2000 8:07 PM Subject: Re: "Libaries" of task defs > This is a radical idea and would take work to get right, but here it > is for feedback: > > Allow any developer to commit, but each developer is on their own > branch until they become a commiter. Then they are allowed to commit > to the committer branch. This branch would be a kind of mainline R&D > branch and committers could merge in worthy code from the other > developer branches as each saw fit. The project committee would > maintain the main release branch and merge in items from the committer > branch, tagging all the files with a release number and packaging a > release about twice a month (as Cathedral/Bazaar says release early > and often). This committee branch would always have only working code > so the head revisions for that branch would always bootstrap and work > as far as basic functionality goes. > > ----- Original Message ----- > From: "Jason Sando" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, May 22, 2000 3:05 PM > Subject: RE: "Libaries" of task defs > > > > <cut> > > > >I have posted a request for a Ant Tasks Repository, but there > > > >were no responses. > > </cut> > > > > and more: > > > > <cut> > > > as a person > > > who has contributed a Taskdef that went nowhere ... > > </cut> > > > > There's a whole bunch of people trying to help grow this project, > doing lots > > of work that's getting ignored. Anybody plan to update the TODO, > README, or > > spec/core.html documents anytime soon? Or possibly add a STATUS > doc? I > > think it would really help reduce frustration ... > > > > Thanks, > > > > -j > > > > > > >
