On 11/27/07, Ted Husted <[EMAIL PROTECTED]> wrote: > On Nov 27, 2007 4:21 AM, Philip Luppens <[EMAIL PROTECTED]> wrote: > > By this 'commons' project, do you mean that (some of) these projects > > should become consolidated (thus giving up their own googlecode page) > > ? Or would it just be a listing with news and information (=plugin > > registry), and a global maven repository (Tom's project) ? > > I'd say "could" instead of "should", but yes, everyone in the commons > project would share the one GoogleCode repository, and, by extension, > we'd all have write access to all the code. > > > > > On a side note: what could be useful would be an overview of all > > plugin developers and their contact details, so that when a new > > project gets started, they can be added and/or contacted when > > required. It could be nice to get an idea of who's interested in > > helping out developing/maintaining plugins. > > One effect of a commons would be that the members list would also be a > list of some of hte people who have been working on Struts 2 plugins. > Another effect would be there would be less need to contact someone, > since everyone in that project would have access to the code, in case > something needs to be done.
Sounds ok to me. If people want to keep the control over their plugins, they can just keep their own project page and repository like we're doing now. What would be the name ? struts2-plugins ? struts2-commons ? struts2-extra ? What would happen with the maven repository ? Should it be kept as a seperate project, or also consolidated into the new project ? I can imagine there being plugins that are not in the central repository, so maybe standalone would be better (even if only to have limited access control). - Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
