I like the idea of a [partial] convention, though let's formalize it up top and use consistently throughout. Can we define what "partial" means: "commits occasionally with a reduced depth of knowledge of the component's codebase"? Should we also have (interested)? E.g., I am *interested* in VFS, particularly VFS3, but I have never committed any code to that component as yet. Do we care to capture that in any way for this exercise?
Matt On Tue, Oct 15, 2013 at 1:05 PM, <s...@apache.org> wrote: > Author: sebb > Date: Tue Oct 15 18:05:01 2013 > New Revision: 1532460 > > URL: http://svn.apache.org/r1532460 > Log: (empty) > > Modified: > commons/trunks-proper/CHALLENGE.txt > > Modified: commons/trunks-proper/CHALLENGE.txt > URL: > http://svn.apache.org/viewvc/commons/trunks-proper/CHALLENGE.txt?rev=1532460&r1=1532459&r2=1532460&view=diff > > ============================================================================== > --- commons/trunks-proper/CHALLENGE.txt (original) > +++ commons/trunks-proper/CHALLENGE.txt Tue Oct 15 18:05:01 2013 > @@ -11,12 +11,12 @@ betwixt= > bsf= > chain=britter > cli= > -codec= > +codec=sebb > collections=mbenson,britter > -compress=bodewig > +compress=bodewig,sebb > configuration= > -csv=adrianc*,britter > -daemon= > +csv=adrianc*,britter,sebb > +daemon=sebb[partial] > dbcp=psteitz > dbutils= > digester= > @@ -27,18 +27,18 @@ exec= > fileupload= > functor=kinow,mbenson > imaging= > -io=joehni > +io=joehni,sebb > jci= > jcs= > jelly=polx,kinow > -jexl= > +jexl=sebb > jxpath=mbenson > -lang=bayard,joehni,mbenson,britter > +lang=bayard,joehni,mbenson,britter,sebb > launcher= > logging= > -math=psteitz,erans,luc > +math=psteitz,erans,luc,[sebb] > modeler= > -net= > +net=sebb > ognl= > pool=psteitz > primitives= > > >
