Do you have any additional reasons that those given by Vincent? Did my answers to those help? For that matter, Vincent, did they help you?
It is only about 3 or 4 in favour at the moment, so its more of a trickle than a flow :) - Brett Trygve Laugstøl wrote: > On Thu, 2006-01-12 at 15:02 +0100, 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? >> >> 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 agree with Vincent here, I'd rather move stuff from Apache to Mojo > than the other way around. > >> That said, I'll go with the flow. > > Me too :) > > -- > Trygve >
