Vincent Massol wrote: > >> -----Original Message----- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: jeudi 12 janvier 2006 13:56 >> To: Mojo Developers >> Subject: [mojo-dev] Bringing plugins to Apache Maven >> >> Some of the plugins that wound up in mojo seem better suited to the main >> Apache project due to a) originally coming from there b) having the core >> libraries located there c) being essential to the day to day use of the >> project. >> >> These are the ones I'm thinking of: >> - build helper >> - jxr report (jxr) >> - surefire report (surefire) >> - changes/jira/announcement report (issue stuff in sandbox) >> - changelog report (scm) >> >> What do others think? > > I think that moving them to Apache is risking to have less committers work > on them as lots of mojos committers won't have access to their sources > anymore. Does your plan include voting all the mojo committers active on > them as apache committers?
I absolutely think anyone that has contributed significantly (and can continue to do so) should become a Maven plugins committer. On these, I think there is only one or two people and they've been around a long time. That still theoretically reduces the number of people, but since we haven't seen it much in practice then I don't think its a problem. The worst case is someone contributing patches for a while. > Personally I think the more open we make contributions to the plugins the > better it is (remember our issue with maintaining Maven 1 plugins). I'd > prefer seeing more plugins move from the direction apache -> mojo. I also > think that having 2 places for plugins is not that good and thus I'd rather > have everything on mojos with apache committers on Maven core doing > oversight. I don't want to move Apache > mojo. That would mean that Maven doesn't operate *at all* without the mojo project, which is not good. Given we must have separation, I see it as this: Plugins at Apache: Essential to almost everyone's normal use of Maven, or if it has relationships with other Maven code, or is "strategically important" (say, Maven decides we want to build .Net stuff, so we take in C# work even if we don't currently have a tonne of users). Plugins at Mojo: Project oriented, but can't be housed in the project. Or can't be at Apache due to more restrictive licensing. People at Apache: Committed to the Maven project. Showing interested in several plugins/codebases. Active on the lists. Able to pick up other things from time to time to keep plugins going. People at Codehaus: Plugin focused. Delivering their own stuff. Hopefully helping out other mojo-ers and getting interested in other plugins and Maven core stuff. Likely place to discover new Apache committers. All just IMO. Maybe worth a separate thread on [EMAIL PROTECTED] - Brett
