On Thu, Oct 24, 2002 at 10:32:52PM -0000, [EMAIL PROTECTED] wrote: > gstein 2002/10/24 15:32:51 > > Modified: . STATUS > Log: > hey! our first candidate! > ... > + o APR's serf project has voted itself to move into Commons. > ...
I think this is premature, we need a few more things first, like a mission to start. Once we have a mission I will write a proposal for an "HTTP Utilities" component that will exist under the Commons project. This component will be the logical community around various projects, like Serf, and possibly HttpClient and even APREQ. This component would be limited to the creation of reusable libraries (and possibly support utilities) that help us reach our goal, and would not be limited by language or other implementation feature. I'm trying to come up with a good way so that this component could self-organize into a managing committee and a contributor community. The managing committee (not necessarily a PMC) would be reposible for identifying and promoting committers, making recommendations to the Commons PMC about new projects within the scope of the HTTP Utilities Component, and so forth. Community members would share development lists, while committers would share CVS access and voting privileges (subject to the normal ASF voting rules). How does this sound so far? If you don't like the word "component", feel free to suggest a replacement. So far I like the organization structure of this proposal, but I would welcome any refinement or constructive criticism of it. Also, I'd like to come up with a snazzy name instead of the default "Apache Commons HTTP Utilities Component". :) -aaron
