1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 15-08-2011 02:19, Samuli Suominen wrote: |
5 |
> On 08/14/2011 10:01 PM, Mike Frysinger wrote: |
6 |
>> this has come up multiple times in the past as a concern, but in |
7 |
>> practice has never been an issue. |
8 |
> |
9 |
> constant problem with devrel bugs lately, with people having such |
10 |
> powers, acting as if they didn't need to listen to other anymore |
11 |
> (including members from his own team) |
12 |
|
13 |
I understand you may not agree with all or some of DevRel decisions and |
14 |
I don't think we've ever claimed all decisions are reached by an |
15 |
unanimous vote, but all DevRel members are addressed when an issue is |
16 |
brought up to a vote and all are expected to vote and express their opinion. |
17 |
All members are trusted and expected to make up their own mind in a |
18 |
reasonable manner, hearing the case and giving a chance for parties to |
19 |
explain themselves and or present their arguments. This doesn't mean |
20 |
individual members should have no background on an issue and or a prior |
21 |
opinion, only that they need to keep an open mind and take into account |
22 |
latest developments, nor that they will have to change their opinion to |
23 |
satisfy anyone else's desires. |
24 |
Since the decision and the cast of votes are being published in the |
25 |
conclusion of the issues, the wider community has access to some |
26 |
information that should help form an opinion on how DevRel is working. |
27 |
|
28 |
>> if members feel like there's going to be a conflict from |
29 |
>> themselves, they can recuse themselves. this has happened once or |
30 |
>> twice. i dont see any value in laying out red tape for an issue |
31 |
>> that has never caused a problem. |
32 |
> |
33 |
> in developer relation bugs, the accused should also be allowed to |
34 |
> recuse such double members; as |
35 |
> |
36 |
> "i'm not saying this as devrel member but..." "i'm not saying this as |
37 |
> council member but..." |
38 |
> |
39 |
> is constantly being used as weapon by selected people, making the |
40 |
> whole process of devrel unfair when other members get semi ignored |
41 |
|
42 |
When a Gentoo developer that is both a DevRel member and is serving a |
43 |
term in Council acts in a bug, clearing in what role he/she is |
44 |
intervening should only help clarify his intervention - I don't see how |
45 |
that can be "used as a weapon". |
46 |
If there is any doubt about any comments I may have made in the last |
47 |
year and in which I expressed in which role I made the comment, let me |
48 |
make it clear that the intention was just to clarify in which role I was |
49 |
intervening - there were no "second intentions" in such comments. |
50 |
|
51 |
- -- |
52 |
Regards, |
53 |
|
54 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
55 |
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng |
56 |
-----BEGIN PGP SIGNATURE----- |
57 |
Version: GnuPG v2.0.18 (GNU/Linux) |
58 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
59 |
|
60 |
iQIcBAEBAgAGBQJOTGoSAAoJEC8ZTXQF1qEP6YMP/35nidLLhLgS/EnfyQYPT03y |
61 |
+UOq4MltTugdqqxmUiWztOQW3K54C7LWEQUlT4hEvND2Jvr6WMmO+dawjtzXuphm |
62 |
0TKV/k+h42W32PznUm5ncItB04wCpmWNZF4MD/021FlHO/Nrn2VlfzQGXeiCK8Cm |
63 |
y/ViKvhkP+UVpHjO/EUevlQHfoC2mtXX1+EM7wV2ie3TxNaK46K4XeLB5bmGEMlg |
64 |
biNXeErEms88xg7vbcwPH/BRyOccpGWZF6FhnGl1wXw/5HsSHQGSph14NXkmKJN3 |
65 |
vEZsJ85fAeCwH3H223aDWKXEnbuDfgEo/pbVwf+P0IoJ4JjH4nEEUCMI2ad1nyF1 |
66 |
0je63oIS6gqcAj8FOLSA54hRF9IoTYq1Mc3RQ0kdxhjsIwehQNiVdIbe2ifGSZyG |
67 |
VeUL1x28A6zquJl+e7eQ/0FkC3XV/u4NUo0g/m6pOvd1hD5EcsXk8PNWwJrs/Z+g |
68 |
hzKmfXq9IUGNRAA9ToUMgBlgN/ucg094tWRz4RgUTft0M+kTGrAN9PFj60oBCscE |
69 |
WG7ZnvQrWum+R+PNsDhq22sdMBVhr6iZh8cr1X4S9TDCtjsEYHKiCAiAA5Z+dkO4 |
70 |
wO7kJcfOv1Zb32TCojF6jbaBndQpZ+B6XGR6h4fJJHBbsLgFvBtWTRUKADMB+9Np |
71 |
b1M6E1N1OPyjvzLv4Xlz |
72 |
=+1GC |
73 |
-----END PGP SIGNATURE----- |