I feel a bit like Eric which is why I've not answered to the vote so far (I'm still unsure whether it's a good idea or not).
Some points: - I see the ML merge as a good way to talk about m2 and dispel the urban legends that have started to accumulate around it. - I agree that an official statement of information on M2 is necessary at this stage as m2 is getting visibility quickly. It should contain answers to FAQs such as: - what should current users of m1 do? Should they migrate to m2? When (maybe separate OSS projects from business projects)? How? - what commitment is there from the Maven development team to continue supporting Maven 1? For how long? - a rough date when M2 will be considered equivalent in functionality to m1 (i.e. roughly same number of plugins which do the same thing - isofunctionality) - support for m1 plugins and Jelly in general - rough planning for m2. First alpha, first beta, planned 1.0 and their contents I know this FAQ list makes Maven sound like it's a commercial product... However I do think Open Source nowadays have to be managed like commercial products because more and more people rely on it and establish business decisions on it. I think we owe it to our users to make the strategy and direction as transparent as possible. Thus, I do think we need to put these M2 FAQ answers visibility on the Maven web site. Once this done, I think merging the 2 lists will be a good thing. I'm happy to help if I can. What do you think? -Vincent > -----Original Message----- > From: Eric Pugh [mailto:[EMAIL PROTECTED] > Sent: mardi 5 avril 2005 17:33 > To: Maven Developers List > Subject: Re: [vote] bring m2-dev back to [email protected] > > +0 > > I think we need to address somewhere what M2 is. I talk to new people > all the time, and when they hear Maven2, they get nervous.. They > start wondering why learn M1 if M2 is coming down the pike.. And, for > early adopters, they need to know that M2 isn't baked the way M1 is, > and that things may break or take digging in. > > M2 is more then just a complete rewrite of M1, and that M2 won't > replace M1 in one fell swoop is something that we need to communicate. > Rather, the backporting of components out of M2 like wagon or scm, are > things that M1 users can really benefit from (I know I am excited about > them!), and having discussion about them on [email protected] will > really help. > > I hope it doesn't devolve to where every subject line starts with [M1] > or [M2].. > > Eric > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
