You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2010/11/01 22:35:14 UTC
[PROPOSAL] Create a retirement plan for plugins
Hi
Given the discussions about retiring plugin I feel strongly that we need
to have a plan for doing so. There are bound to be differing opinions
about this, so see this as a starting point for discussions. When we get
to the point that we agree on the general process, I'll turn this
discussion into a document and put into our site.
1. Propose a vote on the dev-list to retire a plugin. The vote should be
open for the standard 72 hours to allow people to voice their opinions.
Perhaps also send this to the users-list?
2. Decide how to retire the plugin (don't know whether this should be a
vote or not, or perhaps incorporated into 1.). There are multiple
scenarios available. Two have been suggested in the other threads:
2.1 Move to retired area in svn
2.2 Move to mojo.codehaus.org
please add more possible actions here
3. Make one final release of the plugin before it goes away. This allows
us to make a clean break. The final release should have the site changed
so that SCM URLs are changed or removed to reflect the decision made
under 2. If the plugin is moved elsewhere a prominent notice should be
placed on the front page of the plugin's site.
To respond to the inevitable "why bother" responses I hereby volunteer
to do all those releases, if no one else steps up.
4. Announce the fact that the plugin has been retired/moved/whatever on
the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
they should do if they would like to help with the continued development
of the plugin at some other place.
Opinions, comments are welcome
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
And I capture what votes I've seen so far.
https://cwiki.apache.org/confluence/display/MAVEN/Proposal+of+plugins+to+retire
And we can just use that as a record.
On Nov 1, 2010, at 10:57 PM, Dennis Lundberg wrote:
> On 2010-11-01 22:38, Jason van Zyl wrote:
>> Can you put this in Confluence.
>
> Sure, I'll just wait for some feedback first, then I'll summarize it in
> Confluence. Once the wrinkles are ironed out I'll move it to the site.
>
>> I think we should include the addition of plugins as well ... as that's how we got here in the first place. New plugins, if we ever add anymore, should require the same rigor going in.
>
> Do you mean that we should describe how high the bar is for new plugins
> to enter?
>
>>
>> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>>
>>> Hi
>>>
>>> Given the discussions about retiring plugin I feel strongly that we need
>>> to have a plan for doing so. There are bound to be differing opinions
>>> about this, so see this as a starting point for discussions. When we get
>>> to the point that we agree on the general process, I'll turn this
>>> discussion into a document and put into our site.
>>>
>>>
>>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>>> open for the standard 72 hours to allow people to voice their opinions.
>>> Perhaps also send this to the users-list?
>>>
>>>
>>> 2. Decide how to retire the plugin (don't know whether this should be a
>>> vote or not, or perhaps incorporated into 1.). There are multiple
>>> scenarios available. Two have been suggested in the other threads:
>>>
>>> 2.1 Move to retired area in svn
>>>
>>> 2.2 Move to mojo.codehaus.org
>>>
>>> please add more possible actions here
>>>
>>>
>>> 3. Make one final release of the plugin before it goes away. This allows
>>> us to make a clean break. The final release should have the site changed
>>> so that SCM URLs are changed or removed to reflect the decision made
>>> under 2. If the plugin is moved elsewhere a prominent notice should be
>>> placed on the front page of the plugin's site.
>>>
>>> To respond to the inevitable "why bother" responses I hereby volunteer
>>> to do all those releases, if no one else steps up.
>>>
>>>
>>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>>> they should do if they would like to help with the continued development
>>> of the plugin at some other place.
>>>
>>>
>>>
>>> Opinions, comments are welcome
>>>
>>> --
>>> Dennis Lundberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> In short, man creates for himself a new religion of a rational
>> and technical order to justify his work and to be justified in it.
>>
>> -- Jacques Ellul, The Technological Society
>>
>>
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
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
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
I prefer to comment in Confluence where it can be captured:
https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins
I added a bit about creation as well.
On Nov 1, 2010, at 10:57 PM, Dennis Lundberg wrote:
> On 2010-11-01 22:38, Jason van Zyl wrote:
>> Can you put this in Confluence.
>
> Sure, I'll just wait for some feedback first, then I'll summarize it in
> Confluence. Once the wrinkles are ironed out I'll move it to the site.
>
>> I think we should include the addition of plugins as well ... as that's how we got here in the first place. New plugins, if we ever add anymore, should require the same rigor going in.
>
> Do you mean that we should describe how high the bar is for new plugins
> to enter?
>
>>
>> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>>
>>> Hi
>>>
>>> Given the discussions about retiring plugin I feel strongly that we need
>>> to have a plan for doing so. There are bound to be differing opinions
>>> about this, so see this as a starting point for discussions. When we get
>>> to the point that we agree on the general process, I'll turn this
>>> discussion into a document and put into our site.
>>>
>>>
>>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>>> open for the standard 72 hours to allow people to voice their opinions.
>>> Perhaps also send this to the users-list?
>>>
>>>
>>> 2. Decide how to retire the plugin (don't know whether this should be a
>>> vote or not, or perhaps incorporated into 1.). There are multiple
>>> scenarios available. Two have been suggested in the other threads:
>>>
>>> 2.1 Move to retired area in svn
>>>
>>> 2.2 Move to mojo.codehaus.org
>>>
>>> please add more possible actions here
>>>
>>>
>>> 3. Make one final release of the plugin before it goes away. This allows
>>> us to make a clean break. The final release should have the site changed
>>> so that SCM URLs are changed or removed to reflect the decision made
>>> under 2. If the plugin is moved elsewhere a prominent notice should be
>>> placed on the front page of the plugin's site.
>>>
>>> To respond to the inevitable "why bother" responses I hereby volunteer
>>> to do all those releases, if no one else steps up.
>>>
>>>
>>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>>> they should do if they would like to help with the continued development
>>> of the plugin at some other place.
>>>
>>>
>>>
>>> Opinions, comments are welcome
>>>
>>> --
>>> Dennis Lundberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> In short, man creates for himself a new religion of a rational
>> and technical order to justify his work and to be justified in it.
>>
>> -- Jacques Ellul, The Technological Society
>>
>>
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.
-- Eric Hoffer, Reflections on the Human Condition
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 1, 2010, at 10:57 PM, Dennis Lundberg wrote:
> On 2010-11-01 22:38, Jason van Zyl wrote:
>> Can you put this in Confluence.
>
> Sure, I'll just wait for some feedback first, then I'll summarize it in
> Confluence. Once the wrinkles are ironed out I'll move it to the site.
>
>> I think we should include the addition of plugins as well ... as that's how we got here in the first place. New plugins, if we ever add anymore, should require the same rigor going in.
>
> Do you mean that we should describe how high the bar is for new plugins
> to enter?
>
Yes, that we should be loathe to add new ones given how we have supported what's here.
>>
>> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>>
>>> Hi
>>>
>>> Given the discussions about retiring plugin I feel strongly that we need
>>> to have a plan for doing so. There are bound to be differing opinions
>>> about this, so see this as a starting point for discussions. When we get
>>> to the point that we agree on the general process, I'll turn this
>>> discussion into a document and put into our site.
>>>
>>>
>>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>>> open for the standard 72 hours to allow people to voice their opinions.
>>> Perhaps also send this to the users-list?
>>>
>>>
>>> 2. Decide how to retire the plugin (don't know whether this should be a
>>> vote or not, or perhaps incorporated into 1.). There are multiple
>>> scenarios available. Two have been suggested in the other threads:
>>>
>>> 2.1 Move to retired area in svn
>>>
>>> 2.2 Move to mojo.codehaus.org
>>>
>>> please add more possible actions here
>>>
>>>
>>> 3. Make one final release of the plugin before it goes away. This allows
>>> us to make a clean break. The final release should have the site changed
>>> so that SCM URLs are changed or removed to reflect the decision made
>>> under 2. If the plugin is moved elsewhere a prominent notice should be
>>> placed on the front page of the plugin's site.
>>>
>>> To respond to the inevitable "why bother" responses I hereby volunteer
>>> to do all those releases, if no one else steps up.
>>>
>>>
>>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>>> they should do if they would like to help with the continued development
>>> of the plugin at some other place.
>>>
>>>
>>>
>>> Opinions, comments are welcome
>>>
>>> --
>>> Dennis Lundberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> In short, man creates for himself a new religion of a rational
>> and technical order to justify his work and to be justified in it.
>>
>> -- Jacques Ellul, The Technological Society
>>
>>
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-11-01 22:38, Jason van Zyl wrote:
> Can you put this in Confluence.
Sure, I'll just wait for some feedback first, then I'll summarize it in
Confluence. Once the wrinkles are ironed out I'll move it to the site.
> I think we should include the addition of plugins as well ... as that's how we got here in the first place. New plugins, if we ever add anymore, should require the same rigor going in.
Do you mean that we should describe how high the bar is for new plugins
to enter?
>
> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>
>> Hi
>>
>> Given the discussions about retiring plugin I feel strongly that we need
>> to have a plan for doing so. There are bound to be differing opinions
>> about this, so see this as a starting point for discussions. When we get
>> to the point that we agree on the general process, I'll turn this
>> discussion into a document and put into our site.
>>
>>
>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>> open for the standard 72 hours to allow people to voice their opinions.
>> Perhaps also send this to the users-list?
>>
>>
>> 2. Decide how to retire the plugin (don't know whether this should be a
>> vote or not, or perhaps incorporated into 1.). There are multiple
>> scenarios available. Two have been suggested in the other threads:
>>
>> 2.1 Move to retired area in svn
>>
>> 2.2 Move to mojo.codehaus.org
>>
>> please add more possible actions here
>>
>>
>> 3. Make one final release of the plugin before it goes away. This allows
>> us to make a clean break. The final release should have the site changed
>> so that SCM URLs are changed or removed to reflect the decision made
>> under 2. If the plugin is moved elsewhere a prominent notice should be
>> placed on the front page of the plugin's site.
>>
>> To respond to the inevitable "why bother" responses I hereby volunteer
>> to do all those releases, if no one else steps up.
>>
>>
>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>> they should do if they would like to help with the continued development
>> of the plugin at some other place.
>>
>>
>>
>> Opinions, comments are welcome
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>
> -- Jacques Ellul, The Technological Society
>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
Can you put this in Confluence. I think we should include the addition of plugins as well ... as that's how we got here in the first place. New plugins, if we ever add anymore, should require the same rigor going in.
On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
> Hi
>
> Given the discussions about retiring plugin I feel strongly that we need
> to have a plan for doing so. There are bound to be differing opinions
> about this, so see this as a starting point for discussions. When we get
> to the point that we agree on the general process, I'll turn this
> discussion into a document and put into our site.
>
>
> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
> open for the standard 72 hours to allow people to voice their opinions.
> Perhaps also send this to the users-list?
>
>
> 2. Decide how to retire the plugin (don't know whether this should be a
> vote or not, or perhaps incorporated into 1.). There are multiple
> scenarios available. Two have been suggested in the other threads:
>
> 2.1 Move to retired area in svn
>
> 2.2 Move to mojo.codehaus.org
>
> please add more possible actions here
>
>
> 3. Make one final release of the plugin before it goes away. This allows
> us to make a clean break. The final release should have the site changed
> so that SCM URLs are changed or removed to reflect the decision made
> under 2. If the plugin is moved elsewhere a prominent notice should be
> placed on the front page of the plugin's site.
>
> To respond to the inevitable "why bother" responses I hereby volunteer
> to do all those releases, if no one else steps up.
>
>
> 4. Announce the fact that the plugin has been retired/moved/whatever on
> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
> they should do if they would like to help with the continued development
> of the plugin at some other place.
>
>
>
> Opinions, comments are welcome
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-11-02 00:46, Jason van Zyl wrote:
> Do you want a different process and proposal process for restructuring? Like I've proposed for the site plugin?
Such a process isn't easy to put down in words, as one proposal might
look very different from another.
However the propose, discuss, vote, release, do changes, announce should
work in those cases to.
>
> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>
>> Hi
>>
>> Given the discussions about retiring plugin I feel strongly that we need
>> to have a plan for doing so. There are bound to be differing opinions
>> about this, so see this as a starting point for discussions. When we get
>> to the point that we agree on the general process, I'll turn this
>> discussion into a document and put into our site.
>>
>>
>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>> open for the standard 72 hours to allow people to voice their opinions.
>> Perhaps also send this to the users-list?
>>
>>
>> 2. Decide how to retire the plugin (don't know whether this should be a
>> vote or not, or perhaps incorporated into 1.). There are multiple
>> scenarios available. Two have been suggested in the other threads:
>>
>> 2.1 Move to retired area in svn
>>
>> 2.2 Move to mojo.codehaus.org
>>
>> please add more possible actions here
>>
>>
>> 3. Make one final release of the plugin before it goes away. This allows
>> us to make a clean break. The final release should have the site changed
>> so that SCM URLs are changed or removed to reflect the decision made
>> under 2. If the plugin is moved elsewhere a prominent notice should be
>> placed on the front page of the plugin's site.
>>
>> To respond to the inevitable "why bother" responses I hereby volunteer
>> to do all those releases, if no one else steps up.
>>
>>
>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>> they should do if they would like to help with the continued development
>> of the plugin at some other place.
>>
>>
>>
>> Opinions, comments are welcome
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
>
> -- Paul Graham
>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
Do you want a different process and proposal process for restructuring? Like I've proposed for the site plugin?
On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
> Hi
>
> Given the discussions about retiring plugin I feel strongly that we need
> to have a plan for doing so. There are bound to be differing opinions
> about this, so see this as a starting point for discussions. When we get
> to the point that we agree on the general process, I'll turn this
> discussion into a document and put into our site.
>
>
> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
> open for the standard 72 hours to allow people to voice their opinions.
> Perhaps also send this to the users-list?
>
>
> 2. Decide how to retire the plugin (don't know whether this should be a
> vote or not, or perhaps incorporated into 1.). There are multiple
> scenarios available. Two have been suggested in the other threads:
>
> 2.1 Move to retired area in svn
>
> 2.2 Move to mojo.codehaus.org
>
> please add more possible actions here
>
>
> 3. Make one final release of the plugin before it goes away. This allows
> us to make a clean break. The final release should have the site changed
> so that SCM URLs are changed or removed to reflect the decision made
> under 2. If the plugin is moved elsewhere a prominent notice should be
> placed on the front page of the plugin's site.
>
> To respond to the inevitable "why bother" responses I hereby volunteer
> to do all those releases, if no one else steps up.
>
>
> 4. Announce the fact that the plugin has been retired/moved/whatever on
> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
> they should do if they would like to help with the continued development
> of the plugin at some other place.
>
>
>
> Opinions, comments are welcome
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Stephen Connolly <st...@gmail.com>.
On 2 November 2010 13:03, Jason van Zyl <ja...@maven.org> wrote:
>
> On Nov 2, 2010, at 1:33 PM, Stephen Connolly wrote:
>
> Nothing does ever happen. That's empirically evident at least here.
>
> But I'm fine having a vote, we certainly can't do less so there's no harm.
>
I await the [VOTE] thread with excitement
-Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 2, 2010, at 1:33 PM, Stephen Connolly wrote:
> On 2 November 2010 12:08, Jason van Zyl <ja...@maven.org> wrote:
>>
>> On Nov 2, 2010, at 12:20 PM, Stephen Connolly wrote:
>>
>>> I think we should have a separate discussion on what our SLA with the
>>> Maven users should be / can be.
>>>
>>
>> I think following the Eclipse process is wise. We're not going to come up with anything better. They have delivered consistently for 10 years on schedule. We're open source but all of our users are enterprises and businesses. Thus all of our contributions are going to come from these people and there is an expectation of a release process and social contracts that I believe Eclipse has gotten right.
>>
>
> Call a vote, let's see what happens
>
> I am not opposed to the eclipse process, but rather than saying, oh
> nothing ever happens at apache, call a vote and lets see what happens,
Nothing does ever happen. That's empirically evident at least here.
But I'm fine having a vote, we certainly can't do less so there's no harm.
> OK?
>
> -Stephen
>
>>> Once we decide on our initial SLA (we can always increase our SLA
>>> afterwards) then we decide what we can keep in agreement with that
>>> SLA.
>>>
>>> as for punishment, there is no point in punishment without hope of
>>> redemption. We would need a mechanism whereby the -1's who fail to
>>> step up and maintain their favourite plugins can recover their vote...
>>> and all that needs to be defined before we think about punishment
>>>
>>> -Stephen
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Stephen Connolly <st...@gmail.com>.
On 2 November 2010 12:08, Jason van Zyl <ja...@maven.org> wrote:
>
> On Nov 2, 2010, at 12:20 PM, Stephen Connolly wrote:
>
>> I think we should have a separate discussion on what our SLA with the
>> Maven users should be / can be.
>>
>
> I think following the Eclipse process is wise. We're not going to come up with anything better. They have delivered consistently for 10 years on schedule. We're open source but all of our users are enterprises and businesses. Thus all of our contributions are going to come from these people and there is an expectation of a release process and social contracts that I believe Eclipse has gotten right.
>
Call a vote, let's see what happens
I am not opposed to the eclipse process, but rather than saying, oh
nothing ever happens at apache, call a vote and lets see what happens,
OK?
-Stephen
>> Once we decide on our initial SLA (we can always increase our SLA
>> afterwards) then we decide what we can keep in agreement with that
>> SLA.
>>
>> as for punishment, there is no point in punishment without hope of
>> redemption. We would need a mechanism whereby the -1's who fail to
>> step up and maintain their favourite plugins can recover their vote...
>> and all that needs to be defined before we think about punishment
>>
>> -Stephen
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 2, 2010, at 12:20 PM, Stephen Connolly wrote:
> On 2 November 2010 10:50, Jason van Zyl <ja...@maven.org> wrote:
>>
>> On Nov 2, 2010, at 11:47 AM, Jason van Zyl wrote:
>>
>>>
>>> On Nov 2, 2010, at 11:38 AM, Stephen Connolly wrote:
>>>
>>>> On 2 November 2010 10:10, Jason van Zyl <ja...@maven.org> wrote:
>>>>>
>>>>>
>>>>> That's perfectly reasonable, people who object commit to signing up to maintain the plugin. I think it's also fair to say if someone does this and then doesn't follow through loses the right to vote again to save a plugin a plugin from retirement. There should be consequences to objecting and then doing little or nothing.
>>>>>
>>>>
>>>> If we are going to hae consequences then we need to be very clear up
>>>> front what the commitment is that somebody is signing up to.
>>>>
>>>> If we say that the commitment associated with a -1 is:
>>>>
>>>> * At least one release per year
>>>>
>>>
>>> Not good enough. I think the model Eclipse has is reasonable where there is a release everywhere 6 weeks where a release does not have to happen unless there are regressions introduced in the last cycle. At a bare minimum the regressions need to be dealt with. I would rather have 10 plugins where we can accomplish this then 40 that no one pays attention to.
>>
>> Sorry, jetlag and no sleep for a while.
>>
>> A release cycle of every six weeks
>> - If there are regressions those at a bare minimum must be addressed
>> - A best effort to process patches
>> - A best effort to process improvements
>>
>> Regressions simply cannot be left floating around. i don't think anyone can disagree with that.
>>
>
> I was not saying what our SLA should be. I was just trying to
> illustrate what should be in our SLA and what I see as being an
> absolute minimum SLA for a community driven project.
>
> I do think we need to have an SLA, and the minimum for a community
> driven project should be one release per year... and I don't think
> that is what the minimum SLA for Maven should be BTW.
>
> I think we should have a separate discussion on what our SLA with the
> Maven users should be / can be.
>
I think following the Eclipse process is wise. We're not going to come up with anything better. They have delivered consistently for 10 years on schedule. We're open source but all of our users are enterprises and businesses. Thus all of our contributions are going to come from these people and there is an expectation of a release process and social contracts that I believe Eclipse has gotten right.
> Once we decide on our initial SLA (we can always increase our SLA
> afterwards) then we decide what we can keep in agreement with that
> SLA.
>
> as for punishment, there is no point in punishment without hope of
> redemption. We would need a mechanism whereby the -1's who fail to
> step up and maintain their favourite plugins can recover their vote...
> and all that needs to be defined before we think about punishment
>
> -Stephen
>
>>>
>>>> * JIRA which includes a patch with integration tests remains open
>>>> for more than two releases
>>>>
>>>
>>> Remains open, or doesn't remain open for more then two release cycles?
>>>
>>>> Then that is fine... somebody saying -1 knows up front what they are
>>>> committing to... but we cannot set the bar after the -1 vote.
>>>>
>>>
>>> Why not? Release slated for every 6 weeks to account for bug fixes and at a minimum regressions.
>>>
>>>> Similarly I think the committment should be the committment that we as
>>>> Apache Maven Committers are giving in terms of an SLA for the Apache
>>>> Maven hosted plugins... so that frames the vote for removal being we
>>>> cannot meet the commitment of our SLA with the community
>>>>
>>>
>>> For core lifecycle plugins I think we have to follow the 6 week cycle and Eclipse has been doing this for years and it works for them, and their users are pretty happy. Regressions in lifecycle related plugins like the niggly thing in the WAR plugin just can't linger.
>>>
>>> For heavily used plugins we should try and do the same. Once a year when regressions exist we simply can't do. That's just wrong.
>>>
>>> For site and other plugins I will follow the policy other people set forward.
>>>
>>>> -Stephen
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> A language that doesn’t affect the way you think about programming is not worth knowing.
>>>
>>> -— Alan Perlis
>>>
>>>
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> People develop abstractions by generalizing from concrete examples.
>> Every attempt to determine the correct abstraction on paper without
>> actually developing a running system is doomed to failure. No one
>> is that smart. A framework is a resuable design, so you develop it by
>> looking at the things it is supposed to be a design of. The more examples
>> you look at, the more general your framework will be.
>>
>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Stephen Connolly <st...@gmail.com>.
On 2 November 2010 10:50, Jason van Zyl <ja...@maven.org> wrote:
>
> On Nov 2, 2010, at 11:47 AM, Jason van Zyl wrote:
>
>>
>> On Nov 2, 2010, at 11:38 AM, Stephen Connolly wrote:
>>
>>> On 2 November 2010 10:10, Jason van Zyl <ja...@maven.org> wrote:
>>>>
>>>>
>>>> That's perfectly reasonable, people who object commit to signing up to maintain the plugin. I think it's also fair to say if someone does this and then doesn't follow through loses the right to vote again to save a plugin a plugin from retirement. There should be consequences to objecting and then doing little or nothing.
>>>>
>>>
>>> If we are going to hae consequences then we need to be very clear up
>>> front what the commitment is that somebody is signing up to.
>>>
>>> If we say that the commitment associated with a -1 is:
>>>
>>> * At least one release per year
>>>
>>
>> Not good enough. I think the model Eclipse has is reasonable where there is a release everywhere 6 weeks where a release does not have to happen unless there are regressions introduced in the last cycle. At a bare minimum the regressions need to be dealt with. I would rather have 10 plugins where we can accomplish this then 40 that no one pays attention to.
>
> Sorry, jetlag and no sleep for a while.
>
> A release cycle of every six weeks
> - If there are regressions those at a bare minimum must be addressed
> - A best effort to process patches
> - A best effort to process improvements
>
> Regressions simply cannot be left floating around. i don't think anyone can disagree with that.
>
I was not saying what our SLA should be. I was just trying to
illustrate what should be in our SLA and what I see as being an
absolute minimum SLA for a community driven project.
I do think we need to have an SLA, and the minimum for a community
driven project should be one release per year... and I don't think
that is what the minimum SLA for Maven should be BTW.
I think we should have a separate discussion on what our SLA with the
Maven users should be / can be.
Once we decide on our initial SLA (we can always increase our SLA
afterwards) then we decide what we can keep in agreement with that
SLA.
as for punishment, there is no point in punishment without hope of
redemption. We would need a mechanism whereby the -1's who fail to
step up and maintain their favourite plugins can recover their vote...
and all that needs to be defined before we think about punishment
-Stephen
>>
>>> * JIRA which includes a patch with integration tests remains open
>>> for more than two releases
>>>
>>
>> Remains open, or doesn't remain open for more then two release cycles?
>>
>>> Then that is fine... somebody saying -1 knows up front what they are
>>> committing to... but we cannot set the bar after the -1 vote.
>>>
>>
>> Why not? Release slated for every 6 weeks to account for bug fixes and at a minimum regressions.
>>
>>> Similarly I think the committment should be the committment that we as
>>> Apache Maven Committers are giving in terms of an SLA for the Apache
>>> Maven hosted plugins... so that frames the vote for removal being we
>>> cannot meet the commitment of our SLA with the community
>>>
>>
>> For core lifecycle plugins I think we have to follow the 6 week cycle and Eclipse has been doing this for years and it works for them, and their users are pretty happy. Regressions in lifecycle related plugins like the niggly thing in the WAR plugin just can't linger.
>>
>> For heavily used plugins we should try and do the same. Once a year when regressions exist we simply can't do. That's just wrong.
>>
>> For site and other plugins I will follow the policy other people set forward.
>>
>>> -Stephen
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> A language that doesn’t affect the way you think about programming is not worth knowing.
>>
>> -— Alan Perlis
>>
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
>
> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 2, 2010, at 11:47 AM, Jason van Zyl wrote:
>
> On Nov 2, 2010, at 11:38 AM, Stephen Connolly wrote:
>
>> On 2 November 2010 10:10, Jason van Zyl <ja...@maven.org> wrote:
>>>
>>>
>>> That's perfectly reasonable, people who object commit to signing up to maintain the plugin. I think it's also fair to say if someone does this and then doesn't follow through loses the right to vote again to save a plugin a plugin from retirement. There should be consequences to objecting and then doing little or nothing.
>>>
>>
>> If we are going to hae consequences then we need to be very clear up
>> front what the commitment is that somebody is signing up to.
>>
>> If we say that the commitment associated with a -1 is:
>>
>> * At least one release per year
>>
>
> Not good enough. I think the model Eclipse has is reasonable where there is a release everywhere 6 weeks where a release does not have to happen unless there are regressions introduced in the last cycle. At a bare minimum the regressions need to be dealt with. I would rather have 10 plugins where we can accomplish this then 40 that no one pays attention to.
Sorry, jetlag and no sleep for a while.
A release cycle of every six weeks
- If there are regressions those at a bare minimum must be addressed
- A best effort to process patches
- A best effort to process improvements
Regressions simply cannot be left floating around. i don't think anyone can disagree with that.
>
>> * JIRA which includes a patch with integration tests remains open
>> for more than two releases
>>
>
> Remains open, or doesn't remain open for more then two release cycles?
>
>> Then that is fine... somebody saying -1 knows up front what they are
>> committing to... but we cannot set the bar after the -1 vote.
>>
>
> Why not? Release slated for every 6 weeks to account for bug fixes and at a minimum regressions.
>
>> Similarly I think the committment should be the committment that we as
>> Apache Maven Committers are giving in terms of an SLA for the Apache
>> Maven hosted plugins... so that frames the vote for removal being we
>> cannot meet the commitment of our SLA with the community
>>
>
> For core lifecycle plugins I think we have to follow the 6 week cycle and Eclipse has been doing this for years and it works for them, and their users are pretty happy. Regressions in lifecycle related plugins like the niggly thing in the WAR plugin just can't linger.
>
> For heavily used plugins we should try and do the same. Once a year when regressions exist we simply can't do. That's just wrong.
>
> For site and other plugins I will follow the policy other people set forward.
>
>> -Stephen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> A language that doesn’t affect the way you think about programming is not worth knowing.
>
> -— Alan Perlis
>
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 2, 2010, at 11:38 AM, Stephen Connolly wrote:
> On 2 November 2010 10:10, Jason van Zyl <ja...@maven.org> wrote:
>>
>>
>> That's perfectly reasonable, people who object commit to signing up to maintain the plugin. I think it's also fair to say if someone does this and then doesn't follow through loses the right to vote again to save a plugin a plugin from retirement. There should be consequences to objecting and then doing little or nothing.
>>
>
> If we are going to hae consequences then we need to be very clear up
> front what the commitment is that somebody is signing up to.
>
> If we say that the commitment associated with a -1 is:
>
> * At least one release per year
>
Not good enough. I think the model Eclipse has is reasonable where there is a release everywhere 6 weeks where a release does not have to happen unless there are regressions introduced in the last cycle. At a bare minimum the regressions need to be dealt with. I would rather have 10 plugins where we can accomplish this then 40 that no one pays attention to.
> * JIRA which includes a patch with integration tests remains open
> for more than two releases
>
Remains open, or doesn't remain open for more then two release cycles?
> Then that is fine... somebody saying -1 knows up front what they are
> committing to... but we cannot set the bar after the -1 vote.
>
Why not? Release slated for every 6 weeks to account for bug fixes and at a minimum regressions.
> Similarly I think the committment should be the committment that we as
> Apache Maven Committers are giving in terms of an SLA for the Apache
> Maven hosted plugins... so that frames the vote for removal being we
> cannot meet the commitment of our SLA with the community
>
For core lifecycle plugins I think we have to follow the 6 week cycle and Eclipse has been doing this for years and it works for them, and their users are pretty happy. Regressions in lifecycle related plugins like the niggly thing in the WAR plugin just can't linger.
For heavily used plugins we should try and do the same. Once a year when regressions exist we simply can't do. That's just wrong.
For site and other plugins I will follow the policy other people set forward.
> -Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A language that doesn’t affect the way you think about programming is not worth knowing.
-— Alan Perlis
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Stephen Connolly <st...@gmail.com>.
On 2 November 2010 10:10, Jason van Zyl <ja...@maven.org> wrote:
>
>
> That's perfectly reasonable, people who object commit to signing up to maintain the plugin. I think it's also fair to say if someone does this and then doesn't follow through loses the right to vote again to save a plugin a plugin from retirement. There should be consequences to objecting and then doing little or nothing.
>
If we are going to hae consequences then we need to be very clear up
front what the commitment is that somebody is signing up to.
If we say that the commitment associated with a -1 is:
* At least one release per year
* JIRA which includes a patch with integration tests remains open
for more than two releases
Then that is fine... somebody saying -1 knows up front what they are
committing to... but we cannot set the bar after the -1 vote.
Similarly I think the committment should be the committment that we as
Apache Maven Committers are giving in terms of an SLA for the Apache
Maven hosted plugins... so that frames the vote for removal being we
cannot meet the commitment of our SLA with the community
-Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 2, 2010, at 8:17 AM, Dennis Lundberg wrote:
> On 2010-11-02 00:10, Jason van Zyl wrote:
>>
>> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>>
>>> Hi
>>>
>>> Given the discussions about retiring plugin I feel strongly that we need
>>> to have a plan for doing so. There are bound to be differing opinions
>>> about this, so see this as a starting point for discussions. When we get
>>> to the point that we agree on the general process, I'll turn this
>>> discussion into a document and put into our site.
>>>
>>>
>>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>>> open for the standard 72 hours to allow people to voice their opinions.
>>> Perhaps also send this to the users-list?
>>>
>>
>> What kind of vote. 3 +1s, no -1s. Majority of the PMC? Like a technical vote that can be vetoed or a release vote that cannot. Please be more clear here.
>
> I haven't decided yet. But if a vote fails, then anyone who voted -1
> should be willing to support and maintain that plugin.
>
That's perfectly reasonable, people who object commit to signing up to maintain the plugin. I think it's also fair to say if someone does this and then doesn't follow through loses the right to vote again to save a plugin a plugin from retirement. There should be consequences to objecting and then doing little or nothing.
>>>
>>> 2. Decide how to retire the plugin (don't know whether this should be a
>>> vote or not, or perhaps incorporated into 1.). There are multiple
>>> scenarios available. Two have been suggested in the other threads:
>>>
>>> 2.1 Move to retired area in svn
>>>
>>
>> Just retire it and let people take the code as they like. Once it's retired it's open season. Let folks who might want to work on it organize themselves as they like.
>
> If we don't care what happens to a retired plugin then that is the way
> to go, but I think we should put a little more effort into it.
>
>>
>>> 2.2 Move to mojo.codehaus.org
>>>
>>> please add more possible actions here
>>>
>>>
>>> 3. Make one final release of the plugin before it goes away. This allows
>>> us to make a clean break. The final release should have the site changed
>>> so that SCM URLs are changed or removed to reflect the decision made
>>> under 2.
>>
>> You're not going to know. I would just say it's retired. When and if someone takes up the torch we can point the site at that. In the interim saying it's retired I think is fine.
>
> Removing the SCM report is probably the best way to go.
>
>>> If the plugin is moved elsewhere a prominent notice should be
>>> placed on the front page of the plugin's site.
>>>
>>> To respond to the inevitable "why bother" responses I hereby volunteer
>>> to do all those releases, if no one else steps up.
>>>
>>
>> I don't think you have to be a martyr. How about the person who proposes the retirement do the final release. If you want to do the cleanup work, you have to do all of it.
>
> Jason, you need to understand that this is not about me - it's about
> caring for our users. We should not leave things (plugins in this case)
> in an unfinished state, no matter what.
>
> If someone wants to take over a retired plugin they shouldn't have to
> start with reviewing the difference between the last release and trunk,
> changes that someone else has already reviewed and committed.
>
>
>>>
>>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>>> they should do if they would like to help with the continued development
>>> of the plugin at some other place.
>>>
>>
>> Make sense.
>>
>>>
>>>
>>> Opinions, comments are welcome
>>>
>>> --
>>> Dennis Lundberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> To do two things at once is to do neither.
>>
>> -—Publilius Syrus, Roman slave, first century B.C.
>>
>>
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-11-02 00:10, Jason van Zyl wrote:
>
> On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
>
>> Hi
>>
>> Given the discussions about retiring plugin I feel strongly that we need
>> to have a plan for doing so. There are bound to be differing opinions
>> about this, so see this as a starting point for discussions. When we get
>> to the point that we agree on the general process, I'll turn this
>> discussion into a document and put into our site.
>>
>>
>> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
>> open for the standard 72 hours to allow people to voice their opinions.
>> Perhaps also send this to the users-list?
>>
>
> What kind of vote. 3 +1s, no -1s. Majority of the PMC? Like a technical vote that can be vetoed or a release vote that cannot. Please be more clear here.
I haven't decided yet. But if a vote fails, then anyone who voted -1
should be willing to support and maintain that plugin.
>>
>> 2. Decide how to retire the plugin (don't know whether this should be a
>> vote or not, or perhaps incorporated into 1.). There are multiple
>> scenarios available. Two have been suggested in the other threads:
>>
>> 2.1 Move to retired area in svn
>>
>
> Just retire it and let people take the code as they like. Once it's retired it's open season. Let folks who might want to work on it organize themselves as they like.
If we don't care what happens to a retired plugin then that is the way
to go, but I think we should put a little more effort into it.
>
>> 2.2 Move to mojo.codehaus.org
>>
>> please add more possible actions here
>>
>>
>> 3. Make one final release of the plugin before it goes away. This allows
>> us to make a clean break. The final release should have the site changed
>> so that SCM URLs are changed or removed to reflect the decision made
>> under 2.
>
> You're not going to know. I would just say it's retired. When and if someone takes up the torch we can point the site at that. In the interim saying it's retired I think is fine.
Removing the SCM report is probably the best way to go.
>> If the plugin is moved elsewhere a prominent notice should be
>> placed on the front page of the plugin's site.
>>
>> To respond to the inevitable "why bother" responses I hereby volunteer
>> to do all those releases, if no one else steps up.
>>
>
> I don't think you have to be a martyr. How about the person who proposes the retirement do the final release. If you want to do the cleanup work, you have to do all of it.
Jason, you need to understand that this is not about me - it's about
caring for our users. We should not leave things (plugins in this case)
in an unfinished state, no matter what.
If someone wants to take over a retired plugin they shouldn't have to
start with reviewing the difference between the last release and trunk,
changes that someone else has already reviewed and committed.
>>
>> 4. Announce the fact that the plugin has been retired/moved/whatever on
>> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
>> they should do if they would like to help with the continued development
>> of the plugin at some other place.
>>
>
> Make sense.
>
>>
>>
>> Opinions, comments are welcome
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> To do two things at once is to do neither.
>
> -—Publilius Syrus, Roman slave, first century B.C.
>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Jason van Zyl <ja...@maven.org>.
On Nov 1, 2010, at 10:35 PM, Dennis Lundberg wrote:
> Hi
>
> Given the discussions about retiring plugin I feel strongly that we need
> to have a plan for doing so. There are bound to be differing opinions
> about this, so see this as a starting point for discussions. When we get
> to the point that we agree on the general process, I'll turn this
> discussion into a document and put into our site.
>
>
> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
> open for the standard 72 hours to allow people to voice their opinions.
> Perhaps also send this to the users-list?
>
What kind of vote. 3 +1s, no -1s. Majority of the PMC? Like a technical vote that can be vetoed or a release vote that cannot. Please be more clear here.
>
> 2. Decide how to retire the plugin (don't know whether this should be a
> vote or not, or perhaps incorporated into 1.). There are multiple
> scenarios available. Two have been suggested in the other threads:
>
> 2.1 Move to retired area in svn
>
Just retire it and let people take the code as they like. Once it's retired it's open season. Let folks who might want to work on it organize themselves as they like.
> 2.2 Move to mojo.codehaus.org
>
> please add more possible actions here
>
>
> 3. Make one final release of the plugin before it goes away. This allows
> us to make a clean break. The final release should have the site changed
> so that SCM URLs are changed or removed to reflect the decision made
> under 2.
You're not going to know. I would just say it's retired. When and if someone takes up the torch we can point the site at that. In the interim saying it's retired I think is fine.
> If the plugin is moved elsewhere a prominent notice should be
> placed on the front page of the plugin's site.
>
> To respond to the inevitable "why bother" responses I hereby volunteer
> to do all those releases, if no one else steps up.
>
I don't think you have to be a martyr. How about the person who proposes the retirement do the final release. If you want to do the cleanup work, you have to do all of it.
>
> 4. Announce the fact that the plugin has been retired/moved/whatever on
> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
> they should do if they would like to help with the continued development
> of the plugin at some other place.
>
Make sense.
>
>
> Opinions, comments are welcome
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
To do two things at once is to do neither.
-—Publilius Syrus, Roman slave, first century B.C.
Re: [PROPOSAL] Create a retirement plan for plugins
Posted by Stephen Connolly <st...@gmail.com>.
+1
On 1 November 2010 21:35, Dennis Lundberg <de...@apache.org> wrote:
> Hi
>
> Given the discussions about retiring plugin I feel strongly that we need
> to have a plan for doing so. There are bound to be differing opinions
> about this, so see this as a starting point for discussions. When we get
> to the point that we agree on the general process, I'll turn this
> discussion into a document and put into our site.
>
>
> 1. Propose a vote on the dev-list to retire a plugin. The vote should be
> open for the standard 72 hours to allow people to voice their opinions.
> Perhaps also send this to the users-list?
>
>
> 2. Decide how to retire the plugin (don't know whether this should be a
> vote or not, or perhaps incorporated into 1.). There are multiple
> scenarios available. Two have been suggested in the other threads:
>
> 2.1 Move to retired area in svn
>
> 2.2 Move to mojo.codehaus.org
>
> please add more possible actions here
>
>
> 3. Make one final release of the plugin before it goes away. This allows
> us to make a clean break. The final release should have the site changed
> so that SCM URLs are changed or removed to reflect the decision made
> under 2. If the plugin is moved elsewhere a prominent notice should be
> placed on the front page of the plugin's site.
>
> To respond to the inevitable "why bother" responses I hereby volunteer
> to do all those releases, if no one else steps up.
>
>
> 4. Announce the fact that the plugin has been retired/moved/whatever on
> the announce@m.a.o and users@m.a.o mailing lists. Explain to people what
> they should do if they would like to help with the continued development
> of the plugin at some other place.
>
>
>
> Opinions, comments are welcome
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org