On Sun, Mar 01, 2015 at 12:14:19AM -0800, Dan Tran wrote:
> Apache process may send some new potential committers away :)
> 
> +1 for Github, but stay together under on umbrella of org.code.mojo
> groupId.

+1

The concern with moving to Github is their lack of mailing lists, but I guess a 
Google group is the best choice these days.

> 
> -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
> >
> >
> >

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to