I would prefer two real centers. For licensing reasons, much code can not be hosted at Apache. In addition, my big concern is "dump-and-run" code (which we've even seen with Tapestry committers in the past). We don't want to be responsible for more code than we can support.
On Wed, Jun 22, 2011 at 9:30 AM, Lenny Primak <lpri...@hope.nyc.ny.us> wrote: > I agree with Taha here. > > I think Tapestry needs THE one place to put contributing modules. > 'Put it on GitHub' isn't good enough. > > One of the guys who works for me came from microsoft world, > and he constantly complains that everything is very hard to find. > I am teaching him the 'right' unix way of doing things but I am starting > to feel his pain when it comes to finding tapestry contributing components. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
