Bob Harner has already something called a module registry. I think it should be adopted by Tapestry documentation project. No need to create anything new here.
Also, even though github is 'in' right now, not everything is on github. lots of projects are hosted on google code, sourceforge, etc. Forcing or pseudo-forcing (i.e. if you are not on github you are not in the registry) isn't a good idea. On Oct 9, 2013, at 8:42 AM, Thiago H de Paula Figueiredo wrote: > On Wed, 09 Oct 2013 07:50:21 -0300, Barry Books <[email protected]> wrote: > >> I think there needs to be some repository of 3rd party modules > > Agreed. There's http://tapestry.apache.org/third-party-modules.html, linked > on the documentation page. It may not be ideal, but at least that's a start. > >> and I don't think >> the apache site is the place for that. I've been thinking about creating a >> github project and using that as a way to document what's available. If you >> have a 3rd party module you could be a contributor and I think it would be >> pretty easy to create one place to go for info, create bug reports etc. >> I think this could be one step to more cooperation. > > I like the idea. I have some ideas about the distributed configuration JIRA > you posted that would make it easier to implement the project above. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
