There's a few discussions here, so on each point: Arnaud: +1 to Arnaud (welcome!) HOWEVER: my understanding is that 3 x +1 is not enough to jump in - aren't we required to wait 24 hours so those on the other side of the planet have a chance to -1? (Not that this is necessary in this case, I just notice it happening lately :)
Maven-plugins committers: +1 to separate maven-plugins committers HOWEVER, I don't think maintenance of one plugin is enough, they need to be interested in helping out in several areas. I think we should move out fringe plugins, not just keep maven-core plugins. We should keep maven-plugins as the ones most used by our core users (somewhat more than 10, especially considering the reports) and build a set of developers willing to look after them. At the moment we have myself, dion, Emmanuel and Vincent doing this. We can hopefully add Arnaud to this list. We need to ask who else here wants to be involved in this in the Maven 1.x timeframe, and reassess when future releases start happening. From this list, we need someone to volunteer for every plugin. Anything left over gets marked as dead and we need to document it as such so that we can manage user's expectations. If it is needed, hopefully the umbrella project will own it (such as has happened with cactus, statcvs and so on), or someone will put their hand up to join the sourceforge project and take it over there. Let's get this in motion now. I'll release a bunch of them for RC3, but from there I only want the plugin lead doing so, and on a timeframe that suits the plugin, not the distribution. Other stuff: - yes, you can put an alternative remote repository in project.properties for your plugin, and your plugin dependencies get pulled from there. This is really helpful. - I don't remember, I think there was something, but its early :) Cheers, Brett > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 20 April 2004 8:28 AM > To: Maven Developers List > Subject: RE: [Vote] Arnaud Heritier as a committer > > > On Mon, 2004-04-19 at 18:18, Fabrizio Giustina wrote: > > > There's nothign stopping you from putting your own stuff in any > > web-enabled location and pointing any build you want at > that location. > > > > I know, and I already do that... but you still need to ask > people to > > add your new repository location > > (http://maven-validator.sourceforge.net/) while the upload > request is > > waiting. And I don't really like to create an unofficial maven > > repository on the sourceforge web servers (I don't even know if sf > > policies allow this...) > > Why do you need people to add anything? It appears to be in > your project.properties file so what do your users have to add? > > > Starting maven 2 with a brand new set of plugins (with a > brand new set > > of bugs) is scaring... this really makes me want to stay > with maven 1 > > forever... > > That's the fantastic part about having a choice, you don't > ever have to use maven2 if you don't like. Maven 1 isn't > going to pulled from face of the planet. > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://maven.apache.org > > happiness is like a butterfly: the more you chase it, the > more it will elude you, but if you turn your attention to > other things, it will come and sit softly on your shoulder ... > > -- Thoreau > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
