Steven Noels wrote:
Sam Ruby wrote:
Merge or diverge. Having community boundaries distinct from PMC
boundaries is not sustainable.
And what about Commons and Commons-Sandbox? One can imagine these as the
refugee camps for smallish subprojects, without the 'community' to go
toplevel.
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/
http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/
might contain a lot of subprojects which doesn't fit your criteria
sizewise. Should these all be put back to incubator stage? Or do they
share a common 'Commons' community?
I understand your point that a single PMC overlooking a lot of scattered
projects doesn't scale. Still, I believe some of these smallish
subprojects can share a common spirit, without sharing the developers
community. Merging all of these will make them less visible to the
outside world IMHO - meaning developers can meet, merge or exchange, but
to prospective users it will all be one big sinkhole.
IIUC this is to gently nudge them to go top-level with their own PMC.
If they want visibility, they need take also the responsibilities.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
