public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matti Bickel <mabi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy regarding the inactive members
Date: Sun, 11 Apr 2010 16:04:57 +0200	[thread overview]
Message-ID: <4BC1D709.2020503@gentoo.org> (raw)
In-Reply-To: <201004111616.41414.hwoarang@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2769 bytes --]

/me puts on his asbestos underwear

Markos Chandras wrote:
> So the attendance to council meetings  is enough to prove that a member is 
> active? 0_o

Yes. Anything else is just too hard to measure, imo. If you notice a
council member acting w/o knowing what the heck is going on, then vote
him down next election.

> place on the mailing list. Because I really doubt that *all* council members 
> are reading the mailing list in daily basis so they get to know everything 
> that is going on to Gentoo.

This is impossible. Council should follow -council and debate points
pushed onto their agenda via -dev. At least that's my understanding.

> The only council
> members who look active to me are Petteri and Denis.

While I applaud Denis and Petteri for taking a stand on the pit that
-dev is, I doubt council members should be required to participate here.
They can vote on an issue without discussing their opinion first, based
on their technical/social experience (which is what I voted them in for,
in the first place)

> A council member is inactive when:
> 
> 1) He is inactive in critical discussions ( such as the whole Phoenix 
> discussion ) for a certain period of time

Please, no. Or we start to get -council/-dev threads about why a certain
thread here is not considered critical by half of the council when they
don't reply. If you can't put a number on it, please don't make it a
hard requirement.

> 2) Fails to accomplish his role by supervising the Gentoo projects.

This isn't even in their domain. I would complain *loud* about any
council member interfering with projects unless it's an inter-project
issue. The council is meant for arbitration and vision, not for
commanding devs.

> Remember we have plenty of Gentoo projects nearly dead and there is
> no way for us to participate since contacting the project leaders is
> a no-go.

Huh? That's what I did with php. Chtekk was most helpful, and because
he's no longer active (wish him all the best!), nobody stopped me from
updating the projects pages to reflect that (after speaking to the team,
of course!)

Rather than relying on the council for whatever "leadership" you want,
please just DO something that scratches YOUR itch. I'm aware our current
technical/social infrastructure is not up to par on handling large scale
contributions by hundreds of users/non-devs. I realize there's this
impression that every time you have an idea there's a mob of people
stoning your idea to death. I have however observed that the more mature
(read: the more implemented code) your idea is, the smaller the stones.
And if your idea is good enough, others might use their stones for
building instead of mud-slinging.

Just my 2cent.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2010-04-11 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 13:16 [gentoo-dev] Policy regarding the inactive members Markos Chandras
2010-04-11 13:50 ` [gentoo-dev] Re: [gentoo-council] " Markos Chandras
2010-04-11 13:59 ` [gentoo-dev] " Tony "Chainsaw" Vroon
2010-04-11 14:04 ` Matti Bickel [this message]
2010-04-11 15:17   ` Zeerak Mustafa Waseem
2010-04-11 16:12     ` Matti Bickel
2010-04-11 15:27   ` [gentoo-dev] " Duncan
2010-04-11 15:01 ` [gentoo-dev] Re: [gentoo-council] " Denis Dupeyron
2010-04-11 15:02 ` [gentoo-dev] " Roy Bamford
2010-04-11 19:17 ` Jorge Manuel B. S. Vicetto
2010-04-11 20:09 ` Rémi Cardona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BC1D709.2020503@gentoo.org \
    --to=mabi@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox