+1 On 1 November 2010 21:35, Dennis Lundberg <[email protected]> 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 [email protected] and [email protected] 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: [email protected] > For additional commands, e-mail: [email protected] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
