One of the reasons not moving to ASF is to keep the "process" much simpler/lightweighter. At least that's how I've seen it so far. The threshold to start a new plugin here at Mojos has been very small.
But I guess that could be changed. Maybe we could introduce something like the sandbox over att Apache Maven? Or are we talking about starting Apache Mojos? /Anders On Mon, Mar 2, 2015 at 9:37 AM, Dan Tran <dant...@gmail.com> wrote: > is MIT license compatible with ASF license? Mojo has a few MIT ones > > > -D > > On Mon, Mar 2, 2015 at 12:26 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> My vote is move to github. >> >> Mojo exists to hold those plugins that have licenses that are not >> compatible with being hosted in Apache. >> >> I would say we should move all compatible plugins/components to ASF and >> leave the license entangled plugins at mojo. >> >> Github issues is fine from my perspective. Not sure about an import >> process but if somebody has tooling the maven PMC may be able to run said >> tooling against the JIRA dump to get the issues migrated. >> >> Wiki content is a different issue. I suspect manual curation may be a >> better option there >> >> >> On Sunday, March 1, 2015, Dan Tran <dant...@gmail.com> wrote: >> >>> Apache process may send some new potential committers away :) >>> >>> +1 for Github, but stay together under on umbrella of org.code.mojo >>> groupId. >>> >>> -D >>> >>> btw, i found this https://github.com/codehaus-plexus >>> >>> so we may something similar like that? >>> >>> >>> >>> On Sat, Feb 28, 2015 at 11:26 PM, Tony Chemit <che...@codelutin.com> >>> wrote: >>> >>>> On Fri, 27 Feb 2015 12:51:18 +0100 >>>> Lennart Jörelid <lennart.jore...@gmail.com> wrote: >>>> >>>> > I second the opinions for moving to GitHub (or Bitbucket) instead of >>>> > remaining in SVN. >>>> > If doing so, I suggest we reuse as much as possible of the GitHub >>>> > infrastructure - Wiki, Issue Tracker, Mailing lists etc. >>>> > If we are already bound for some major migrations, let's make the >>>> best of >>>> > them - and a Distributed version control system is a productivity >>>> boost. >>>> > >>>> > Also - is there really a point to maintain a particular GroupID (i.e. >>>> > org.codehaus). >>>> > I belive we could/should move Mojo's development efforts into the >>>> Apache >>>> > umbrella (why have 2 sources of normative plugins - apache and >>>> codehaus) to >>>> > simplify for users. >>>> >>>> I really like this idea to *merge* mojo projets with maven plugins one >>>> or something at apache house. >>>> >>>> I guess there is some legal issue about it ? or not ? >>>> >>>> >>>> >>>> -- >>>> Tony Chemit >>>> -------------------- >>>> tél: +33 (0) 2 40 50 29 28 >>>> http://www.codelutin.com >>>> email: che...@codelutin.com >>>> twitter: https://twitter.com/tchemit >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >> >> -- >> Sent from my phone >> > >
