> we could share MLs and also SVN (Sandbox > would be nice, not?) MLs are fine, b/c one would need to change address later, and searching for pre-graduation threads is more easily.
For SVN I don't see a benefit. The repos can be moved with less effort once component is graduated. I would like to avoid to get something into the sandbox which is not cleared from legal perspective. What, if OGNL fails in the incubator and we just forget to remove the code from the sandbox? If its in the incubator part, it is like a tag saying:"beware" I would be +1 on user/dev ML but leave SVN in incubator Is there a need to create a pmc ML for OGNL to discuss incubation related matters? Cheers > What Incubator PMCs think about it? > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <flame...@gmail.com> wrote: >> Below is a thread from the Commons Dev list in which I'm recommending >> that OGNL use the commons dev mailing list and that the svn >> permissions allow the ognl committers and the commons committers to >> have read write access. >> >> http://commons.markmail.org/thread/ku3ouuilpiicb5is >> >> Is this a concern for anyone? >> >> OGNL's target is to graduate into Commons rather than to TLP, so >> making it act like a TLP seems destined to cause problems. >> >> Hen >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
