public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Thu, 18 Aug 2011 01:25:38 +0000	[thread overview]
Message-ID: <4E4C6A12.8@gentoo.org> (raw)
In-Reply-To: <4E488238.4070004@gentoo.org>

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

On 15-08-2011 02:19, Samuli Suominen wrote:
> On 08/14/2011 10:01 PM, Mike Frysinger wrote:
>> this has come up multiple times in the past as a concern, but in
>> practice has never been an issue.
> 
> constant problem with devrel bugs lately, with people having such 
> powers, acting as if they didn't need to listen to other anymore 
> (including members from his own team)

I understand you may not agree with all or some of DevRel decisions and
I don't think we've ever claimed all decisions are reached by an
unanimous vote, but all DevRel members are addressed when an issue is
brought up to a vote and all are expected to vote and express their opinion.
All members are trusted and expected to make up their own mind in a
reasonable manner, hearing the case and giving a chance for parties to
explain themselves and or present their arguments. This doesn't mean
individual members should have no background on an issue and or a prior
opinion, only that they need to keep an open mind and take into account
latest developments, nor that they will have to change their opinion to
satisfy anyone else's desires.
Since the decision and the cast of votes are being published in the
conclusion of the issues, the wider community has access to some
information that should help form an opinion on how DevRel is working.

>> if members feel like there's going to be a conflict from 
>> themselves, they can recuse themselves. this has happened once or
>> twice.  i dont see any value in laying out red tape for an issue
>> that has never caused a problem.
> 
> in developer relation bugs, the accused should also be allowed to
> recuse such double members; as
> 
> "i'm not saying this as devrel member but..." "i'm not saying this as
> council member but..."
> 
> is constantly being used as weapon by selected people, making the
> whole process of devrel unfair when other members get semi ignored

When a Gentoo developer that is both a DevRel member and is serving a
term in Council acts in a bug, clearing in what role he/she is
intervening should only help clarify his intervention - I don't see how
that can be "used as a weapon".
If there is any doubt about any comments I may have made in the last
year and in which I expressed in which role I made the comment, let me
make it clear that the intention was just to clarify in which role I was
intervening - there were no "second intentions" in such comments.

- -- 
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOTGoSAAoJEC8ZTXQF1qEP6YMP/35nidLLhLgS/EnfyQYPT03y
+UOq4MltTugdqqxmUiWztOQW3K54C7LWEQUlT4hEvND2Jvr6WMmO+dawjtzXuphm
0TKV/k+h42W32PznUm5ncItB04wCpmWNZF4MD/021FlHO/Nrn2VlfzQGXeiCK8Cm
y/ViKvhkP+UVpHjO/EUevlQHfoC2mtXX1+EM7wV2ie3TxNaK46K4XeLB5bmGEMlg
biNXeErEms88xg7vbcwPH/BRyOccpGWZF6FhnGl1wXw/5HsSHQGSph14NXkmKJN3
vEZsJ85fAeCwH3H223aDWKXEnbuDfgEo/pbVwf+P0IoJ4JjH4nEEUCMI2ad1nyF1
0je63oIS6gqcAj8FOLSA54hRF9IoTYq1Mc3RQ0kdxhjsIwehQNiVdIbe2ifGSZyG
VeUL1x28A6zquJl+e7eQ/0FkC3XV/u4NUo0g/m6pOvd1hD5EcsXk8PNWwJrs/Z+g
hzKmfXq9IUGNRAA9ToUMgBlgN/ucg094tWRz4RgUTft0M+kTGrAN9PFj60oBCscE
WG7ZnvQrWum+R+PNsDhq22sdMBVhr6iZh8cr1X4S9TDCtjsEYHKiCAiAA5Z+dkO4
wO7kJcfOv1Zb32TCojF6jbaBndQpZ+B6XGR6h4fJJHBbsLgFvBtWTRUKADMB+9Np
b1M6E1N1OPyjvzLv4Xlz
=+1GC
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2011-08-18  1:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 11:12 [gentoo-project] Should DevRel members be in Council? Markos Chandras
2011-08-14 11:25 ` Rich Freeman
2011-08-14 14:42   ` Roy Bamford
2011-08-14 14:52     ` Rich Freeman
2011-08-14 16:24       ` Roy Bamford
2011-08-18  0:46       ` Jorge Manuel B. S. Vicetto
2011-08-14 19:01     ` Mike Frysinger
2011-08-14 11:27 ` Fabian Groffen
2011-08-14 11:31   ` Markos Chandras
2011-08-14 11:50     ` Rich Freeman
2011-08-14 11:38 ` Rich Freeman
2011-08-14 12:19 ` Thomas Sachau
2011-08-14 12:26   ` Markos Chandras
2011-08-14 13:14     ` Thomas Sachau
2011-08-14 13:42       ` Markos Chandras
2011-08-14 14:05         ` Petteri Räty
2011-08-14 14:11           ` Markos Chandras
2011-08-14 14:42             ` Petteri Räty
2011-08-14 19:01 ` Mike Frysinger
2011-08-15  2:19   ` Samuli Suominen
2011-08-15  2:46     ` Rich Freeman
2011-08-18  1:25     ` Jorge Manuel B. S. Vicetto [this message]
2011-08-16 18:28 ` William Hubbs
2011-08-16 19:17   ` Rich Freeman
2011-08-16 20:46     ` Donnie Berkholz
2011-08-17  2:46       ` Mike Frysinger
2011-08-16 19:32   ` Roy Bamford
2011-08-18  1:09 ` Jorge Manuel B. S. Vicetto

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=4E4C6A12.8@gentoo.org \
    --to=jmbsvicetto@gentoo.org \
    --cc=gentoo-project@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