Hello, we should stick to having one mailing list. If a component becomes so specialized that the PMC fails to follow what is going on (like what happend with CM), it is time to move that component out of commons. Having separat mailing lists will only make things worse, IMHO.
Benedikt Jochen Wiedmann <jochen.wiedm...@gmail.com> schrieb am Fr., 24. Juni 2016 um 16:58 Uhr: > On Fri, Jun 24, 2016 at 3:58 PM, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > > > Well, it sort of works for the incubator. They are constantly having > discussions about how to do it better. And yes, it could work for us if all > the subprojects have to follow the incubator rules, such as filling > quarterly reports with the Commons PMC to be included in the board report, > insuring that each sub-project has a strong enough community to keep moving > forward (which implies shepherds/mentors to monitor those communities), > etc. Do you really want to go that far? > > Not necessarily. My intention is to demonstrate, that some kind of > compromise *is possible*, and might even be beneficial for us all. > > > Jochen > > -- > The next time you hear: "Don't reinvent the wheel!" > > > http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
