As this is unusual for the incubating project, it might be eductive for the future poddling to describe why the incubator wants normaly to to have the project under /incubator/ and why this rational is not applicable to subversion.
Don't misunderstand me, I think it is good to have such exception for subversion. But I know by experience that is extremely frustrating for a podling to have to move 2 times. Having exceptions that applies to other will probably make the incubation even more frustrating for some project if the rational of such exceptions is not cristal clear and well documented. Gilles Scokart 2009/11/12 Greg Stein <[email protected]> > It looks like we might be moving the code repository over on > Sunday(!). Thus, my query about source code placement has a finite > window for further discussion :-) > > Over the past two days, it sounds like nobody has any particular > object to the svn code being loaded directly to /subversion. (yes, it > is still under purview of the IPMC) > > Is there any further discussion or concerns before we pull the trigger? > > fwiw, the software grant should arrive tmw, and ICLAs are being > recorded as we speak. > > Thanks, > -g > > On Tue, Nov 10, 2009 at 14:27, Greg Stein <[email protected]> wrote: > > There are two other issues to discuss for the Subversion podling: > > > > * moving the mailing lists directly to @subversion.apache.org > > * placing the source code at /subversion/ rather than > /incubator/subversion/ > > > > We are hoping to minimize overall disruption to the community with a > > move to incubator space, then a move to apache space. > > > > Cheers, > > -g > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
