On Tue, 7 Mar 2006, Simon Kitching wrote:
On Mon, 2006-03-06 at 22:42 -0500, Henri Yandell wrote:
To that end, I'd like to propose that Commons Sandbox and Taglibs Sandbox
merge into Jakarta Sandbox - servicing all of Jakarta - though I imagine
it would mostly be the component groupings.
Thoughts?
I presume that a "commons committer" would have commit access to both
old commons and Language Components? Having a separate commit list would
set the barrier to high for movement between the groups. Actually, the
proposed "jakarta-wide" commit access would be even better.
I'm assuming the latter, yeah.
I'm presuming we need to have a vote on the SVN one soon, there's not
really been a lot discussion-wise there other than +1 and -1s.
We're seen as a bit vote-happy - if there's consensus on something just do
it, don't worry about the vote; but I don't think well get unaminous
consensus on any of these issues.
Regarding sandboxes, the issue is really where the commit mails will go.
An experimental project that hopes to be promoted to community X really
should have its commit messages go to the mailing list for that
community. Other than that, what *is* a "sandbox" exactly?
The sandbox is somewhere where existing Jakarta committers can start up
new components - and any ASF committer can then join in.
How it would work depends on which direction we go.
I'd like to see us consider Jakarta a large bag of components with
groupings to ease communication - but not form a subhierarchy. Components
would either be in one grouping only, or many groupings - depending on
whether we wanted to try the more interesting yet trickier latter option.
In that case, the sandbox is quite simple - the same thing it is for
Commons. Once something leaves the sandbox its groupings and communication
lines would be determined. Commit emails would goto the [EMAIL PROTECTED] list.
Another option is to use groupings as the new subprojects.
In that case the sandbox becomes a bit more of an incubator, maybe with
commit emails going back to the subprojects - or we lessen it so that the
new subproject groupings can start things up internally and they would
come to the sandbox when they wanted to engender cross-Jakarta activity,
with commit emails going to [EMAIL PROTECTED] probably.
I'm obviously not much of a salesman for the latter.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
