public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] 2009 Council Elections
Date: Sun, 28 Jun 2009 16:40:00 +0100	[thread overview]
Message-ID: <1246203606.3656.1@NeddySeagoon> (raw)
In-Reply-To: <1246179604.19613.155.camel@localhost> (from dev-zero@gentoo.org on Sun Jun 28 10:00:04 2009)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2009.06.28 10:00, Tiziano Müller wrote:
> Am Freitag, den 26.06.2009, 07:15 -0600 schrieb Denis Dupeyron:
> > On Fri, Jun 26, 2009 at 6:46 AM, Ben de Groot<yngwin@gentoo.org>
> wrote:
> > > To appoint as proxy for a council meeting someone who has been
> booted
> > > from Gentoo is a clear lapse of judgement, and would in my eyes
> > > disqualify the involved council member from functioning in that
> position.
> > 
> > As Petteri noted it's not obvious that GLEP39 disallows choosing a
> > non-dev as proxy for a council meeting. I haven't talked to 
> Tiziano,
> > and I don't know what he had in mind when he chose ciaranm as his
> > proxy, but I'd be ready to believe part of it was that he wanted to
> > experiment.
> Well, it was surely not an experiment to see whether someone must be 
> a
> dev or not to be a proxy. Based on GLEP 39 it was fairly clear to me
> this must not be the case and I at least expected the council to
> accept
> him (or any other non-dev) at least for that meeting.
> 
[snip]
> -- 
> Tiziano Müller
> Gentoo Linux Developer, Council Member
> Areas of responsibility:
>   Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor
> E-Mail   : dev-zero@gentoo.org
> GnuPG FP : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30
> 

Its my opinion that the concept of proxies in council meetings is 
fatally flawed.  

1. The brief (if any) that the proxy is given by the council member 
being proxied is never made public. 

2. Its never clear if the proxy is voting as instructed by the council 
member or as they see fit at the time.

What if an entire meeting and therefore any votes were staffed by 
entirely by non gentoo developer proxies?
Unlikely, but perfectly possible under GLEP39. Would Gentoo feel bound 
by decisions that such a meeting reached?

Oh. Don't talk about 'common sense' GLEP39 does not mention it, so it 
doesn't count ... and its much rarer than you may think.

Lastly, as a trustee and partly legally responsible for decisions made 
on behalf of Gentoo, I am uneasy with the concept of non developers 
making those decisions. Now reread my 'what if' above with that 
liability in mind.

Note: Other trustees may have a different view of the world

- -- 
Regards,

Roy Bamford
(NeddySeagoon) a member of
gentoo-ops
forum-mods
treecleaners
trustees
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEARECAAYFAkpHjtYACgkQTE4/y7nJvavn9gCgt5tw0IaT8GRdh2w0nY+RskZF
H2YAoMgphYWUOp4bVMl8TWp0Qy1nTzjI
=aR8L
-----END PGP SIGNATURE-----




  reply	other threads:[~2009-06-28 15:40 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 15:48 [gentoo-dev] 2009 Council Elections Doug Goldstein
2009-06-24 17:37 ` Denis Dupeyron
2009-06-24 21:31   ` Tobias Scherbaum
2009-06-25 19:00 ` Wulf C. Krueger
2009-06-25 19:50   ` Nirbheek Chauhan
2009-06-25 19:57     ` Ciaran McCreesh
2009-06-26  1:13       ` Andrew D Kirch
2009-06-26  6:30         ` Benny Pedersen
2009-06-29  3:53           ` Andrew D Kirch
2009-06-26  6:34       ` Nirbheek Chauhan
2009-06-26  6:58         ` Petteri Räty
2009-06-29  3:56           ` Andrew D Kirch
2009-06-29  4:21             ` Jorge Manuel B. S. Vicetto
2009-06-26 11:55         ` Ciaran McCreesh
2009-06-29  3:48           ` Andrew D Kirch
2009-06-25 20:50     ` Alistair Bush
2009-06-26  0:47       ` [gentoo-dev] " Duncan
2009-06-26  6:43       ` [gentoo-dev] " Nirbheek Chauhan
2009-06-26  6:49       ` Jeroen Roovers
2009-06-26 12:46   ` Ben de Groot
2009-06-26 13:15     ` Denis Dupeyron
2009-06-26 13:51       ` Joe Peterson
2009-06-28  9:00       ` Tiziano Müller
2009-06-28 15:40         ` Roy Bamford [this message]
2009-06-28 16:05           ` Nirbheek Chauhan
2009-06-28 16:57             ` Tiziano Müller
2009-06-28 16:53           ` Tiziano Müller
2009-06-28 22:14           ` Ferris McCormick
2009-06-28 22:53             ` Roy Bamford
2009-06-28 23:12               ` Dale
2009-06-29  0:09                 ` [gentoo-dev] " Duncan
2009-06-29  0:45                   ` Dale
2009-06-29 11:55                     ` Duncan
2009-06-29 12:32                 ` [gentoo-dev] " Ferris McCormick
2009-06-29 22:40                   ` Mart Raudsepp
2009-06-29 12:19               ` Ferris McCormick
2009-06-28 23:42             ` [gentoo-dev] " Duncan
2009-06-26 14:50     ` [gentoo-dev] " Alistair Bush
2009-06-28 18:38       ` George Prowse
2009-06-26 15:23     ` Ferris McCormick
2009-06-26 15:41     ` Richard Freeman
2009-06-26 17:34       ` Jim Ramsay
2009-06-28  9:30       ` Zhang Le
2009-06-28 18:31   ` George Prowse
2009-06-28 18:46     ` Ciaran McCreesh
2009-06-28 19:46       ` George Prowse
2009-06-28 19:58         ` Ciaran McCreesh
2009-06-28 21:09           ` George Prowse
2009-06-28 21:45         ` Tiziano Müller

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=1246203606.3656.1@NeddySeagoon \
    --to=neddyseagoon@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