1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 17-06-2010 00:00, Sebastian Pipping wrote: |
5 |
> Hello! |
6 |
> |
7 |
> |
8 |
> yngwin's devaway message still reads |
9 |
> |
10 |
> "inactive, pending resolution of devrel issue". |
11 |
> |
12 |
> yngwin retired. I woudn't go as far as saying that his case made him |
13 |
> retire but I definitely say that _DevRel failed on his case_. |
14 |
> I believe I had enough insight to be able to say. |
15 |
|
16 |
Sebastian, |
17 |
|
18 |
not being in the Developer Relations team means you don't have a |
19 |
complete picture about what happened. |
20 |
|
21 |
> I would like to propose these fundamental changes to DevRel: |
22 |
> |
23 |
> 1) Make the list of subscribers to the devrel alias public |
24 |
> |
25 |
> Idea: If you share private information you have a right |
26 |
> to know with whom you share. |
27 |
|
28 |
I don't know what gave you the idea that the list of the Developer |
29 |
Relations project members is private. |
30 |
You can check the alias members directly by running "grep devrel |
31 |
/var/mail/master.aliases" on woodpecker and you can check the project |
32 |
members at http://www.gentoo.org/proj/en/devrel/ |
33 |
|
34 |
> 2) Clearly split DevRel into groups for recruiting and conflict |
35 |
> resolution with distinct aliases. |
36 |
|
37 |
There are subgroups in the DevRel team, including recruiters and |
38 |
undertakers, and there are specific aliases for those - recruiters and |
39 |
retirement. The conflict resolution is handled through the devrel alias |
40 |
as the Ombudsman project was dissolved 1 or 2 years ago. |
41 |
You can check the membership to the subgroups in the DevRel page. |
42 |
|
43 |
> 3) Let Gentoo developers vote on who's in the conflict resolution |
44 |
> team just like we do with the council. |
45 |
|
46 |
AFAIK this never happened before and in my opinion choosing conflict |
47 |
resolution members by "popularity" is a very bad idea. |
48 |
|
49 |
> 4) Disallow membership with both the conflict resolution group |
50 |
> and the council at the same time (as the council is where issues |
51 |
> with devrel are taken to). |
52 |
|
53 |
The reason the elections page clearly identifies members of devrel is to |
54 |
alert developers to possible conflicts. |
55 |
To clarify your above statement, I read it as being about the fact that |
56 |
disciplinary actions of DevRel can be appealed to the Council. If it |
57 |
were meant globally, I'd have to note that whenever you cannot reach an |
58 |
agreement with any project or their lead, you'll have to "appeal" to the |
59 |
council. |
60 |
|
61 |
> Idea: From insight on cases of DevRel versus members of RevRel |
62 |
> I can tell this dossn't work well. I suppose that |
63 |
> Council against Council-DevRel doesn't work better. |
64 |
> |
65 |
> Problem: Both betelgeuse and jmbsvicetto are DevRel members |
66 |
> nominated for the upcoming council election. |
67 |
> As I am also nominated proposing such rule could be |
68 |
> understood aiming at decreasing their chances on the |
69 |
> council and increasing mine as a result. However, as I |
70 |
> propose to start over with a developer voted conflict |
71 |
> resolution team this is not the case. The only |
72 |
> implication is that if they make it to the council |
73 |
> they cannot be elected for the conflict resolution team. |
74 |
|
75 |
My response to your email has nothing to do with the above and to make |
76 |
it crystal clear, this is my personal opinion and doesn't represent the |
77 |
global view of the DevRel team or any other team I am a member of. |
78 |
|
79 |
> DevRel is one of the most important things in Gentoo - we dependend on |
80 |
> that working well. If you care about this please make yourself heard. |
81 |
> |
82 |
> Thanks, |
83 |
> |
84 |
> |
85 |
> |
86 |
> Sebastian |
87 |
|
88 |
- -- |
89 |
Regards, |
90 |
|
91 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
92 |
Gentoo- forums / Userrel / Devrel / KDE / Elections |
93 |
-----BEGIN PGP SIGNATURE----- |
94 |
Version: GnuPG v2.0.15 (GNU/Linux) |
95 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
96 |
|
97 |
iQIcBAEBAgAGBQJMGW1pAAoJEC8ZTXQF1qEP4bAQAL1da+zyT//dvMdmv4cxaTth |
98 |
DzU5R0/NYOFnqlRKSUuRoSu63mPyL9XshAUZsdzY71qhYYtCzdhbqbIDNV84C5fm |
99 |
vdOTmV0dQyEbqvV0jI6rrsevyvuQ0g40IjuMFH8kkXmpD982OFAb22l3BZWE5Evh |
100 |
sk+LYnRWuzXLsptsJj2gumvsf7MrjdpwYmU65W6kJutKYovB9otrqwea75yGObnA |
101 |
/21TmNOm8UAYIFHndxu7iC93yy2obMxbPy/XLuKAavsr5kU/kyJGIsRq8oWnrBwN |
102 |
pX2lmyDIPdSM41k+HZtM0Rs4kCYW1WgMT8Ntq6I4dvHdL1WlHiIGrDWal1hGhHhM |
103 |
smh1Exrjk8FJ4hjjD6O99VSa1JY7AVurGbPHOOaQxAIhb/tKqrdaQxG9bypTQhqD |
104 |
uV2QmeSilv0cSxyTtUxmISIb3z2+Xez+lD/ZPmmPnmhaEhieudR7X/K3lXQVk1GF |
105 |
lBY11QjNmJ4zubIyty2edHDuxT0wvNFdDNH9gv6nxmPEZmjn6ApNfB3/lu+QWkQM |
106 |
4WHINu+eXGyAzkLKxcpOgNOFw5IJyHsz3OBhs8y7YXSWNbZrIrkbnW7zrx0hkGOV |
107 |
kv1L25u6rVCdvLZvRvYMRnhh+AkxLdIfqDcc7H5cQDvRveWVLM5yRf2071XiZjWE |
108 |
c5S8QMNGCcAVo/60fL5S |
109 |
=1QFB |
110 |
-----END PGP SIGNATURE----- |