incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodney Waldhoff <>
Subject Re: [PROPOSAL] Apache Incubator Sandbox
Date Tue, 14 Jan 2003 00:37:14 GMT
Not that it invalidates this proposal, but for the record, the
Jakarta-Commons Sandbox has not expanded in scope.
jakarta-commons-sandbox was never intended to only house projects whose
eventual home is jakarta-commons, but rather as a place for
cross-jakarta-subproject collaboration:

"(1.5.1) the sandbox

"The subproject will host a CVS repository available to all Jakarta
committers as a workplace for new packages or other projects. Before
release to the public, code or documentation developed here must be
sponsored by a Jakarta subproject. The sponsoring subproject(s) will
distribute the code or documentation along with the rest of their


"Should other Jakarta subprojects move their utility packages to the

"They are welcome to do so. If they would like to experiment with
refactoring a package outside their own CVS tree, they can setup shop in
the Commons sandbox. Any Jakarta committer is entitled to write access to
this CVS repository upon request. They could then decide to propose the
package to the Commons, and thereby become committers to the Commons, or
to move it back to their own CVS [...]"


"Why not just enroll all the Jakarta committers in the Commons?


"We do have an open-door policy for the sandbox CVS
(jakarta-commons-sandbox). Any Jakarta committer is entitled to write
access to the sandbox upon request, no vote required, no questions asked.
Just subscribe to [commons-dev@jakarta], and request authorization."


On Mon, 13 Jan 2003, Nicola Ken Barozzi wrote:

> Many projects have a sandbox where developers can try new things related
> to the project. But developers still want to have a place where to
> experiment new things, not necessarily tied with the scope of a project
> they're in.
> Current lack of such a space has lead to
>   1 - Projects keep creating new things and expanding scope
>       For example, Maven, a project build tool, is a sub-project of
>       Turbine, that is a sub-project of Jakarta...
>   2 - Projects need to try new things
>       For example Avalon has projects like EOB and Jesktop that were
>       not created under Avalon because are built *on* Avalon, not
>       for Avalon. Do committers have to go to Sourceforge to do these
>       things?
>   3 - Jakarta Commons Sandbox has an expanded scope
>       Jakarta Commons Sandbox is now filling this role because
>       projects that not necessarily will fit in the Commons Charter
>       get started there. There is an evident need for it from what
>       I see.
> A need to make new projects but a need for project consistency create
> IMHO embarassement in developers, that some times decide to put stuff in
> Commons Sandbox, some in Sourceforge, some inside existing projects.
> I would propose that the Incubator creates a "subproject" to enable
> experiments of code by Apache Committers in a SVN repository. Incubator
> Sandbox would be the place where anybody @ Apache can start coding
> together and share a space.
> Thoughts?
> --
> Nicola Ken Barozzi         
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message