| 1 |
Sent to devrel@ before realizing it was rather more appropriate here, my |
| 2 |
bad. Forwarding. |
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
Today's devrel meeting confirmed the pending conflict resolution RFC |
| 7 |
(http://dev.gentoo.org/~avenj/Devrel_ConflictResRoadmap), thus it's time |
| 8 |
to determine member selection. Attached are my thoughts on the subject |
| 9 |
for discussion. |
| 10 |
|
| 11 |
|
| 12 |
|
| 13 |
RFC |
| 14 |
Selecting/removing conflict resolution subproject members |
| 15 |
|
| 16 |
- Initial member selection |
| 17 |
The initial conflict resolution lead should be chosen via a short |
| 18 |
nomination period & voting. The lead should then compose a list of four |
| 19 |
primary board members. Once the list is presented to devrel for review, |
| 20 |
objections may be raised and the final list will be voted on. |
| 21 |
|
| 22 |
- Conflict of interest rotation |
| 23 |
|
| 24 |
For each complaint filed, devrel leads & conflict resolution lead |
| 25 |
are expected to speak with board members to examine any conflict of |
| 26 |
interest issues. Members determined to have a conflict of interest |
| 27 |
should be rotated out and replacements chosen for the interim. At the |
| 28 |
conflict resolution lead's discretion, members rotated out may be |
| 29 |
brought back on or remain in reserve after the pending action is |
| 30 |
complete. |
| 31 |
|
| 32 |
- Complaints & removal |
| 33 |
Complaints raised about conflict resolution members may be raised |
| 34 |
to leads or at devrel meetings for discussion at any time. Devrel-wide |
| 35 |
votes may be taken to remove members from the project under extreme |
| 36 |
circumstances. Members may also be removed at the subproject lead's |
| 37 |
discretion with an explanation to devrel. |
| 38 |
|
| 39 |
-- |
| 40 |
Jon Portnoy |
| 41 |
avenj/irc.freenode.net |
| 42 |
-- |
| 43 |
gentoo-devrel@g.o mailing list |
Archives