<snip>
Great... does it still make sense to use the sandbox at all?
definitely :)
i could say that it is part of the jakarta commons rules (everything goes through the sandbox) and so it's got to be done but this rule is part of the reason why the commons has been successful and so i'd rather view the positives.
the sandbox means that new components can be started in CVS with the minimum of fuss and bureaucracy and gets the chance to build a community from day one (without wasting time on arguments). new committers are not allowed for sandbox components and releases are also not allowed but it's recommended that the component gets a website up and linked from the other components as soon as possible. it's probably a good idea to add something into the news on the jakarta home page (this is very well read and indexed) and add something into the newsletter.
once the component has refactored itself (to comply with the ASF, jakarta and jakarta-commons structures), built a community and is ready to create a full release (even if it's a 0.1 rather than a 1.0) then it's time to propose a promotion vote. sometimes at this stage, the consensus may be that a component would be better as a jakarta sub-project rather than a jakarta-commons component and if this is the case, jakarta-commons will recommend to the jakarta pmc that the sandbox component be elected to sub-project status.
usually this process takes a long time but it can also happen very quickly.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
