Re: plugin project leads
Jason van Zyl wrote: People will always come and go but some people are willing to steward a particular plugin. If there ends up not being those people then that's fine. But I would hope some people care enough. They can always work with the group of interested people and person who wants to steward will most likely shift over time. If someone wants to take charge and apply patches and do releases and assign themselves the lead then they should go for it. I don't see it as an ownership thing, I see it as a stewardship thing. I don't think its a care factor, its just that it goes off the radar. Especially when one steward gets 10+ plugins and has other things to do as it is. I think regular reporting, giving anyone the opportunity to volunteer, is a better alternative here. Irrespective of that I agree that some form of review should be done. All the information required for the view we should be able to glean from the stock of information we have. Release dates can be picked off (if not easily now, then we can make it easier using the repo manager), issues closed for releases, stagnant issues or whatever else. +1 Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin project leads
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: mercredi 28 décembre 2005 14:35 To: Maven Developers List Subject: Re: plugin project leads Jason van Zyl wrote: People will always come and go but some people are willing to steward a particular plugin. If there ends up not being those people then that's fine. But I would hope some people care enough. They can always work with the group of interested people and person who wants to steward will most likely shift over time. If someone wants to take charge and apply patches and do releases and assign themselves the lead then they should go for it. I don't see it as an ownership thing, I see it as a stewardship thing. I don't think its a care factor, its just that it goes off the radar. Especially when one steward gets 10+ plugins and has other things to do as it is. I think regular reporting, giving anyone the opportunity to volunteer, is a better alternative here. I dont think it's an or thing. As Jason has said it's an and: both needs to be done. IMO there's a need for a plugin lead. Preferably this is the person who has a good history of the plugin and who can provide explanations/directions for contributors, possibly review and apply patches, etc. It doesn't mean he's the only committer on the plugin of course. The pb we had with m1 was not the problem of having leads. It was more the fact that they need to change and we didn't control well enough when leads were still written as leads but actually not leading any more (i.e. they were on other stuff). I think having leads is a good thing. It also provides additional visibility for those accepting to be leads and that's usually a good tradeoff. Irrespective of that I agree that some form of review should be done. All the information required for the view we should be able to glean from the stock of information we have. Release dates can be picked off (if not easily now, then we can make it easier using the repo manager), issues closed for releases, stagnant issues or whatever else. +1 +1 -Vincent ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin project leads
I think we still have a lot to do on these projects. 1) turn off assign to lead by default. This doesn't fit with our process and is the cause of all your mail. Personally, I won't be signing up to be a plugin lead. I don't think that idea worked the last two or three times we tried it. 2) I'm not sure the workflow/issue template/etc are correct for the plugins. They should match MNG. can any of this be automated? - Brett Jason van Zyl wrote: Hi, Can anyone who is taking charge of an m2 plugin assign themselves as the lead please. I will do the couple that I know but if folks can go in and set themselves as lead where appropriate that would really cut down on the mail I'm getting :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin project leads
Brett Porter wrote: I think we still have a lot to do on these projects. 1) turn off assign to lead by default. This doesn't fit with our process and is the cause of all your mail. Personally, I won't be signing up to be a plugin lead. I don't think that idea worked the last two or three times we tried it. Why do you think that is? Vincent and Stephane signed up pretty quickly for their respective plug-ins. Someone needs to be the steward for a plug-in, maybe we need to flip over the lead more often or something. I agree that it shouldn't assign by default, the default project setup goes to the lead. 2) I'm not sure the workflow/issue template/etc are correct for the plugins. They should match MNG. Vincent pointed out that they are not when I set them up. can any of this be automated? I think both can be updated automatically. I'll try it later on tonight. - Brett Jason van Zyl wrote: Hi, Can anyone who is taking charge of an m2 plugin assign themselves as the lead please. I will do the couple that I know but if folks can go in and set themselves as lead where appropriate that would really cut down on the mail I'm getting :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin project leads
Brett Porter wrote: I think we still have a lot to do on these projects. 1) turn off assign to lead by default. This doesn't fit with our process and is the cause of all your mail. Personally, I won't be signing up to be a plugin lead. I don't think that idea worked the last two or three times we tried it. 2) I'm not sure the workflow/issue template/etc are correct for the plugins. They should match MNG. can any of this be automated? Automated. 1) and 2) done. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
