promotion is basically a beauty contest.
there are a number of issues which usually effect how people vote but they are a fluid. here are some issues which (IMHO) effect the voting:
* evidence of compliance with the commons charter. this means having the right documents in place (a PROPOSAL, a STATUS and so on). it also means auditing your dependencies and ensuring compliance with general apache rules. the PROPOSAL needs to be fall within the scope of the commons charter.
* the scope of the PROPOSAL. (in keeping with the charter) tightly scoped PROPOSALs are preferable.
* the health of the development community. fellow committers need to be persuaded that users will be supported and the code pushed forward by the listed committers. this is a major issue since there's only a limited amount of energy amongst the commons committers and no one wants to have to support a component whose committers have gone AWAL.
- robert
On Tuesday, March 18, 2003, at 10:54 PM, [EMAIL PROTECTED] wrote:
Okay, I thought that was how it worked, but I couldn't remember. I think
that configuration is in okay shape, and some work I am doing with Turbine
means that having a released version would be nice. What is required to
promote something? I have seen other things promoted, but I can't find the
doc on "what is required to promote soemthing from sandbox."
Eric Pugh
-----Original Message----- From: Rodney Waldhoff [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2003 5:53 PM To: Jakarta Commons Developers List Subject: Re: [configuration] Should we update the current version?
On Tue, 18 Mar 2003 [EMAIL PROTECTED] wrote:
what is required to cut a release of a sandbox component?
Promotion to commons "proper". We shouldn't be releasing stuff from the sandbox, indeed our guidelines expressly prohibit it.
--------------------------------------------------------------------- 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]
