Re: [vote] Next steps for Archetype

2007-05-25 Thread Brett Porter
On 25/05/2007, at 11:44 PM, Jason van Zyl wrote: If you have specific objections about the code from your review of it, please let's hear them. [...] I see you put these in JIRA too. Thanks. If I fix something or add something on trunk now, I need to make sure it still exists in the

Re: [vote] Next steps for Archetype

2007-05-25 Thread Jason van Zyl
On 23 May 07, at 7:02 PM 23 May 07, Brett Porter wrote: If I fix something or add something on trunk now, I need to make sure it still exists in the future code. That's the double work, and it's a disincentive to do anything. Just for sake of providing a sanity check. No one has commit

Re: [vote] Next steps for Archetype

2007-05-25 Thread Jason van Zyl
On 23 May 07, at 7:02 PM 23 May 07, Brett Porter wrote: On 24/05/2007, at 2:53 AM, Jason van Zyl wrote: I've only ever vetoed code I as working on that someone interfered with and didn't ask. I've not ever vetoed against the majority on project decisions. It's Raphael's decision really, an

RE: mojo (was: [vote] Next steps for Archetype)

2007-05-23 Thread Brian E. Fox
>But this vote is about where the active development of the code will >continue. And I have to disagree on Mojo, even if it is temporary. I'll agree it's temporary in my mind. >The Maven PMC has no oversight over the project, nor any authority. >The code at mojo is not covered under any of Ap

Re: [vote] Next steps for Archetype

2007-05-23 Thread Brett Porter
On 24/05/2007, at 2:53 AM, Jason van Zyl wrote: I've only ever vetoed code I as working on that someone interfered with and didn't ask. I've not ever vetoed against the majority on project decisions. It's Raphael's decision really, and my only point is that people should accept when they un

Re: mojo (was: [vote] Next steps for Archetype)

2007-05-23 Thread Brett Porter
Separating this discussion from the vote. On 24/05/2007, at 2:53 AM, Jason van Zyl wrote: I don't consider working on Archetype at Mojo unacceptable. Raphaël is welcome to work on it there, of course. But this vote is about where the active development of the code will continue. And I have

RE: [vote] Next steps for Archetype

2007-05-23 Thread Brian E. Fox
7;re waiting for a patch to be applied, otherwise you risk having patches that contain other unapplied patched code. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 8:13 AM To: Maven Developers List Subject: [vote] Next steps for Archetype Hi,

Re: [vote] Next steps for Archetype

2007-05-23 Thread Jason van Zyl
On 23 May 07, at 10:52 AM 23 May 07, Brett Porter wrote: Ok, probably needs a little clarity - I'll try and keep it brief as it is a vote. Firstly, we're not diametrically opposed on when to make people committers, as I've tried to point out elsewhere, though we do disagree. But that's n

Re: [vote] Next steps for Archetype

2007-05-23 Thread Milos Kleint
+1 I've tried to create 2 archetypes for netbeans based apps (placed at mojo.codehaus.org svn) and it works like a charm as opposed to the current archetype in trunk. Milos On 5/23/07, John Casey <[EMAIL PROTECTED]> wrote: +1 On 5/23/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > > +1 > > Mark

Re: [vote] Next steps for Archetype

2007-05-23 Thread Raphaël Piéroni
Short answers inlined Raphaël 2007/5/23, Brett Porter <[EMAIL PROTECTED]>: Ok, probably needs a little clarity - I'll try and keep it brief as it is a vote. Firstly, we're not diametrically opposed on when to make people committers, as I've tried to point out elsewhere, though we do disagree.

Re: [vote] Next steps for Archetype

2007-05-23 Thread Brett Porter
Ok, probably needs a little clarity - I'll try and keep it brief as it is a vote. Firstly, we're not diametrically opposed on when to make people committers, as I've tried to point out elsewhere, though we do disagree. But that's not really the issue here, so I won't go into it any furthe

Re: [vote] Next steps for Archetype

2007-05-23 Thread Jason van Zyl
On 23 May 07, at 8:28 AM 23 May 07, Raphaël Piéroni wrote: +1 (But it don't really count :-)) You are the one that counts the most. I disagree with Brett about moving this code over here right now because I don't think you're ready, though I do see that you have the potential to be a goo

Re: [vote] Next steps for Archetype

2007-05-23 Thread John Casey
+1 On 5/23/07, Mark Hobson <[EMAIL PROTECTED]> wrote: +1 Mark On 23/05/07, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > We need to figure out where we go next with Archetype. Raphaël has > been doing a good job adding features and patiently listening to my > feedback/nagging. It appears

Re: [vote] Next steps for Archetype

2007-05-23 Thread Mark Hobson
+1 Mark On 23/05/07, Brett Porter <[EMAIL PROTECTED]> wrote: Hi, We need to figure out where we go next with Archetype. Raphaël has been doing a good job adding features and patiently listening to my feedback/nagging. It appears to me that it is very close to being as good as what we had befor

Re: [vote] Next steps for Archetype

2007-05-23 Thread Raphaël Piéroni
+1 (But it don't really count :-)) Raphaël 2007/5/23, Brett Porter <[EMAIL PROTECTED]>: Hi, We need to figure out where we go next with Archetype. Raphaël has been doing a good job adding features and patiently listening to my feedback/nagging. It appears to me that it is very close to being

[vote] Next steps for Archetype

2007-05-23 Thread Brett Porter
Hi, We need to figure out where we go next with Archetype. Raphaël has been doing a good job adding features and patiently listening to my feedback/nagging. It appears to me that it is very close to being as good as what we had before (though still a long list of things to do before 1.0).