But at the same time there's been a lot of +ve talk for having a general commons list which allows components to become aware of each other. Without it projects would vanish away into their own receptacles.
So we need both? Top level mail list for general things [this list?] and then a bottom level one per component. And then one per category [language/functionality/colour-hair]? Hen On Thu, 24 Oct 2002, Andrew C. Oliver wrote: > Yeah... J-C is a PAIN because of this. Its impracticle to build a > community with all the other communities talking over you. > > Stephen Colebourne wrote: > > >----- Original Message ----- > >From: "Justin Erenkrantz" <[EMAIL PROTECTED]> > > > > > >>As we have discussed before, I believe we are going to stick with a > >>single email list for all of commons. If/when a particular group > >>takes over the mailing list, someone could suggest a new mailing list > >>to be created. (I'd say majority of the participants on the list get > >>to decide if the new list should be created.) > >> > >>I prefer that we evolve the infrastructure rather than hash out an > >>infrastructure from the beginning. -- justin > >> > >> > > > >Please, noooo ;-) > > > >The j-c commons mailing list is already very, very busy. A reorg of this > >nature is the time to think about breaking that down into smaller lists. if > >done correctly, the committers on the mailing lists naturally fall out to be > >those that should have access to that part of the CVS, very much like j-c > >current (pretty successful) model, but with more controls. > > > >The exception comes if two languages share a mailing list. In that case CVS > >commit priveledges should probably be separated by language. > > > >Stephen > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
