Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] second set of amendments to voting policy

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Jeremy Blosser <jblosser-smgl AT firinn.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] second set of amendments to voting policy
  • Date: Sun, 9 Jul 2006 23:08:48 -0500

On Jul 09, Andrew Stitt [afrayedknot AT thefrayedknot.armory.com] wrote:
> On Sun, Jul 09, 2006 at 09:03:28PM +0200, Andra?? ruskie Levstik wrote:
> > Jeremy Blosser wrote :
> >
> > >
> > > - Change the inactivity limit for general developers from one year to
> > > six
> > > This was supposed to get changed before the initial proposal based on
> > > feedback from various people, but didn't get changed. Changing this
> > > now
> > > may be controversial but I'm putting it out there anyway so we can
> > > discuss it.
> >
> > Personaly I think it would be ok to leave it at 1 year. We do have
> > contributors
> >
> > that make very few commits/year.
> >
>
> As I understand the wording:
> "General Developers -- are automatically *** nominated and seconded for
> a removal vote *** after one year of inactivity (defined as no committed
> changes to any part of the project's source code or documentation
> repositories)."
>
> ***'s added for emphasis.
>
> The developer is not actually removed until we vote on it. In the cases
> where we want to keep people in the team we can chose to not remove
> their developer status. For example because they told us they would be
> busy with RL for an extended period of time. I think this is more intended
> to safeguard against people signing up and making a couple commits then
> disappearing. I dont think committing a version bump once every 6 months
> is asking much.

You're right on the intent but for completeness I'll note that these
automatic "removal" votes are sort of more "keep" votes in that the default
action is to go ahead and remove them. A majority has to vote to keep them
for them to stay.

The whole original idea was that someone who was a lead and went inactive
would get dropped from lead to general developer after 6 months, then
dropped out entirely after 6 more months. So a year total for leads and 6
months for general devs. The way it is right now it's a year for leads and
18 months for general devs.

Attachment: pgpdisRy2DrGt.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page