The reasons may be various - maybe they don't want to encourage centralizing components from the comunity - its just like an "anti-globalization" attitude.

Maybe they are simply busy implementing Tapestry 4 in addition to their job...

This new component repository should be created as a component library (or libraries). Maybe in the future some components can go to the official tapestry distribution. But first (before even a specification or well defined goals are available) you should think about it as a separate project, with only a few number of supporter developers. Nowadays developers are maybe prejudiced when someone talks about a new SF project because there are so many dead/slowly developed ones. I think a project has to show some real value to gain attention/contributions.

I have a sourceforge project I could use for that - and will register a gmane list as soon as I hear from you (Hugo, Juan, Todd and others), so we can move on to difining goals...

What is this project? (Wouldn't it be better to register a new one than use an existing one?)

It would be good to create a project with a mailing list at SF as soon as possible because this thread does not tightly belong to tapestry-users (just like tacos has its own list).

Please announce it on tapestry-users when it is ready, and let's transfer this discussion to there.

Br,
Norbi


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to