Jack-- I don't think it's so much an Apache "convention" as it is just a way to sandbox some prototyping, experimentation, group think, or revolutionary changes. A sandbox might be populated with a branch of code -- it just uses the "sandbox" moniker to denote that it's not a real, supported branch. And, the username just scopes it to a particular owner of the stuff beneath the directory.
My take is that it's a little early for a sandbox :) given that the build doesn't quite work yet (at least locally for me -- haven't dug in on that yet), but ultimately, they're useful things for collaborative and distributed projects. My $0.02... Eddie On 1/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Sebastien wrote: > > > I don't think that this will confuse people if we make clear that > everything > > understands that the tree under the sandbox directory is for prototypes, > > experiments, and under-construction stuff. I just took a look at other > > Apache projects, axis2, synapse and beehive, and they seem use a sandbox > (or > > scratch) directory in a similar way, but that doesn't necessarily mean > that > > it's the "right" thing to do... > > To the group at large, what's wrong with using branches with good names? > Just > curious how this particular Apache convention of sandboxes got started > (and I > realize that you are looking for pointers to that info as well). > > -- > Jack Unrue > [EMAIL PROTECTED] > >
