| 1 |
musikc 08/02/02 14:32:03 |
| 2 |
|
| 3 |
Modified: policy.xml |
| 4 |
Log: |
| 5 |
Update Developer Relations conflict resolution policy |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.18 xml/htdocs/proj/en/devrel/policy.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/policy.xml?rev=1.18&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/policy.xml?rev=1.18&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/policy.xml?r1=1.17&r2=1.18 |
| 13 |
|
| 14 |
Index: policy.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/policy.xml,v |
| 17 |
retrieving revision 1.17 |
| 18 |
retrieving revision 1.18 |
| 19 |
diff -u -r1.17 -r1.18 |
| 20 |
--- policy.xml 23 May 2007 16:23:46 -0000 1.17 |
| 21 |
+++ policy.xml 2 Feb 2008 14:32:02 -0000 1.18 |
| 22 |
@@ -7,8 +7,8 @@ |
| 23 |
|
| 24 |
<abstract>Developer Relations Policy Guide</abstract> |
| 25 |
|
| 26 |
-<version>1.1.2</version> |
| 27 |
-<date>2006-08-27</date> |
| 28 |
+<version>1.1.3</version> |
| 29 |
+<date>2008-02-02</date> |
| 30 |
|
| 31 |
<chapter> |
| 32 |
<title>Conflict resolution policy</title> |
| 33 |
@@ -18,13 +18,12 @@ |
| 34 |
<body> |
| 35 |
|
| 36 |
<p> |
| 37 |
-While conflicts serious enough to require developer relations |
| 38 |
-involvement are rare, it's inevitable that developers will clash to |
| 39 |
-varying degrees. It's essential that the developer relations team find |
| 40 |
-fair and impartial resolutions to inter-developer problems. Although |
| 41 |
-all situations differ and exercising good judgment is necessary, these |
| 42 |
-guidelines are intended to define the most acceptable course of |
| 43 |
-action. |
| 44 |
+While conflicts serious enough to require Developer Relations involvement are |
| 45 |
+rare, it's inevitable that developers will clash to varying degrees. It's |
| 46 |
+essential that the Developer Relations team find fair and impartial resolutions |
| 47 |
+to inter-developer problems. Although all situations differ and exercising |
| 48 |
+good judgment is necessary, these guidelines are intended to define the most |
| 49 |
+acceptable course of action. |
| 50 |
</p> |
| 51 |
|
| 52 |
</body> |
| 53 |
@@ -35,38 +34,42 @@ |
| 54 |
<body> |
| 55 |
|
| 56 |
<p> |
| 57 |
-Developer relations should only be involved in a conflict when other |
| 58 |
-attempts to solve the issue have failed. Developers should attempt |
| 59 |
-polite discussion relating to the matter at hand to resolve conflict |
| 60 |
-between themselves. Developers within a single top level project |
| 61 |
-(TLP) engaged in conflict may wish to consult with the TLP |
| 62 |
-manager. Although TLP managers are not necessarily qualified to |
| 63 |
-resolve personal disputes, technical issues resulting in conflict can |
| 64 |
-often be resolved within the TLP without Developer Relations |
| 65 |
-involvement. Developer relations becomes involved when the above methods |
| 66 |
-have failed. Any member of the Developer Relations Conflicts Resolution |
| 67 |
-Subproject may work with the conflicting parties to resolve the conflict; |
| 68 |
-the Developer Relations member who takes this role should make clear that |
| 69 |
-he or she is taking control of the conflict in order to prevent miscommunication. |
| 70 |
-This does not mean that the Developer Relations member in control may not |
| 71 |
-ask others for assistance. |
| 72 |
+Developer Relations should only be involved in a conflict when other attempts |
| 73 |
+to solve the issue have failed. Developers are encouraged to try to resolve the |
| 74 |
+issue amongst themselves in a civil manner. Developers within a project |
| 75 |
+engaged in a personal conflict may wish to consult with the project lead. |
| 76 |
+Although leads are not necessarily qualified to resolve personal disputes, |
| 77 |
+technical issues resulting in conflict can often be resolved within the project |
| 78 |
+without Developer Relations involvement. |
| 79 |
</p> |
| 80 |
|
| 81 |
<p> |
| 82 |
-Issues not necessarily related to personal conflict, such as |
| 83 |
-intentional or repeated policy breaches, malicious or abrasive |
| 84 |
-behavior to users or developers, or similar developer-specific |
| 85 |
-behavioral problems should be brought directly to Developer Relations |
| 86 |
-via <mail link="devrel@g.o">devrel@g.o</mail>. These |
| 87 |
-should be dealt with on a case-by-case basis by Developer Relations |
| 88 |
-and may require disciplinary action. |
| 89 |
-</p> |
| 90 |
- |
| 91 |
-<p> |
| 92 |
-Any complaint which the parties are not able to resolve themselves |
| 93 |
-using the resources described above is assigned to the Conflict |
| 94 |
-Resolution subproject for resolution. This process is described in |
| 95 |
-'Disciplinary Action and Resolution'. |
| 96 |
+Developer Relations becomes involved when the above two methods have failed. To |
| 97 |
+involve Developer Relations in your issue please send an email to |
| 98 |
+<mail>devrel@g.o</mail> or open a Bug and assign it to Developer |
| 99 |
+Relations; either is acceptable. Please note that opening a bug is not |
| 100 |
+necessary for mediation, however the developer may open a bug if he/she wishes |
| 101 |
+to do so; opening a bug is mandatory if mediation efforts fail. Developer |
| 102 |
+Relations includes a team of developers who work with the conflicting parties |
| 103 |
+to resolve the conflict, these members are deemed mediators; the Developer |
| 104 |
+Relations Mediator who takes this role should make clear that he or she is |
| 105 |
+taking control of the conflict in order to prevent miscommunication. This does |
| 106 |
+not mean that the Developer Relations Mediator in control may not ask others |
| 107 |
+for assistance, nor that they should make a decision for the involved parties. |
| 108 |
+The purpose of the Mediator is to assist in mediating discussion to aid in a |
| 109 |
+mutually agreed upon resolution. If all attempts at mediation fail, the issue |
| 110 |
+is escalated and a decision will be made by majority vote of Developer |
| 111 |
+Relations members; this process is detailed in the Policy and Process sections |
| 112 |
+below. |
| 113 |
+</p> |
| 114 |
+ |
| 115 |
+<p> |
| 116 |
+Issues not necessarily related to personal conflict, such as intentional or |
| 117 |
+repeated policy breaches, malicious or abrasive behavior to users or |
| 118 |
+developers, or similar developer-specific behavioral problems should be brought |
| 119 |
+directly to Developer Relations via <mail>devrel@g.o</mail> or via a |
| 120 |
+Bug. These issues may bypass mediation and immediately be escalated to a vote |
| 121 |
+by Developer Relations for the appropriate course of disciplinary action. |
| 122 |
</p> |
| 123 |
|
| 124 |
</body> |
| 125 |
@@ -77,159 +80,167 @@ |
| 126 |
<title>Disciplinary action and resolution</title> |
| 127 |
|
| 128 |
<section> |
| 129 |
-<title>Introduction</title> |
| 130 |
+<title>What Action May be Taken</title> |
| 131 |
<body> |
| 132 |
|
| 133 |
<p> |
| 134 |
-Disciplinary action must be decided on a case-by-case basis by the |
| 135 |
-Developer Relations lead(s). For the majority of situations requiring |
| 136 |
-disciplinary action, a warning is enough to correct future |
| 137 |
-behavior. If behavior does not improve, a probationary period with |
| 138 |
-revoked access to Gentoo infrastructure of two weeks to one month is |
| 139 |
-appropriate. If upon restoration of access negative behavior |
| 140 |
-re-occurs, removal from the project will be necessary. In extreme |
| 141 |
-cases, suspension or removal may be necessary upon a single |
| 142 |
-offense. Except in critical situations where immediate action is |
| 143 |
-required, such disciplinary action is determined by members of the |
| 144 |
-Conflict Resolution subproject. |
| 145 |
-</p> |
| 146 |
- |
| 147 |
-<p> |
| 148 |
-Upon removing a developer, the gentoo-core mailing list should be |
| 149 |
-notified. Additionally, the Developer Relations team are informed |
| 150 |
-of the issues that led to removing or suspending a developer, and |
| 151 |
-this information is stored on a bug. Developers who are removed |
| 152 |
-from the project may not reapply for developer status without the |
| 153 |
-approval of the Developer Relations lead(s). |
| 154 |
+Disciplinary action must be decided on a case-by-case basis by Developer |
| 155 |
+Relations. For the majority of situations requiring disciplinary action, a |
| 156 |
+warning is enough to correct future behavior. If behavior does not improve, a |
| 157 |
+probationary period with revoked access to Gentoo infrastructure of two weeks |
| 158 |
+to one month is appropriate. If upon restoration of access negative behavior |
| 159 |
+re-occurs, removal from the project will be necessary. In extreme cases, |
| 160 |
+suspension or removal may be necessary upon a single offense. Except in |
| 161 |
+critical situations where immediate action is required, such disciplinary |
| 162 |
+action is determined by members of the Developer Relations project. If the |
| 163 |
+issue is deemed critical, the developer in question may have his or her access |
| 164 |
+suspended while a vote takes place; the critical nature of an escalation may be |
| 165 |
+determined by the Developer Relations Lead or Infrastructure, for |
| 166 |
+security-related issues, that which would endanger Gentoo, or our reputation. |
| 167 |
+An issue that is deemed critical does not need further justification in |
| 168 |
+addition to stating which of the above situations it falls under. |
| 169 |
+</p> |
| 170 |
+ |
| 171 |
+<p> |
| 172 |
+Upon removing a developer, the gentoo-core mailing list should be notified. |
| 173 |
+Additionally, the entire Developer Relations team is informed via email of the |
| 174 |
+issues that led to removing or suspending a developer, and this information is |
| 175 |
+stored on the bug. Developers who are removed from the project may not reapply |
| 176 |
+for developer status without the approval of the Developer Relations lead(s). |
| 177 |
</p> |
| 178 |
|
| 179 |
</body> |
| 180 |
</section> |
| 181 |
|
| 182 |
<section> |
| 183 |
-<title>Conflict Resolution Subproject</title> |
| 184 |
+<title>The Policy for Resolution of Conflicts</title> |
| 185 |
<body> |
| 186 |
|
| 187 |
<p> |
| 188 |
-Developer Relations has established a Conflict Resolution subproject |
| 189 |
-for resolving disputes covered by this policy. This group consists of |
| 190 |
-one Developer Relations member as a strategic lead, four active Gentoo |
| 191 |
-developers who serve as a conflict resolution board, and alternates as |
| 192 |
-determined by the lead. The lead is chosen by the active Developer |
| 193 |
-Relations members, and the lead is responsible for selecting board |
| 194 |
-members and any alternates. Developer Relations approves or rejects |
| 195 |
-the lead's choices. |
| 196 |
+What kind of disputes should be escalated? |
| 197 |
</p> |
| 198 |
|
| 199 |
+<ul> |
| 200 |
+<li>A dispute involving Code of Conduct, or similarly themed violations, |
| 201 |
+involving two or more developers.</li> |
| 202 |
+<li>A developer whose behavior is believed to be a negative influence for the |
| 203 |
+Gentoo community. This includes any inappropriate action conducted by a |
| 204 |
+developer.</li> |
| 205 |
+<li>Any other conflicts of a non technical nature involving two or more |
| 206 |
+developers.</li> |
| 207 |
+</ul> |
| 208 |
+ |
| 209 |
<p> |
| 210 |
-The lead of the Conflict Resolution subproject is primarily a |
| 211 |
-strategic contact between the board and the Developer Relations lead(s), |
| 212 |
-and as such, has no voting role in determining the resolution of any |
| 213 |
-conflict unless needed to break a tie. However, the lead should be |
| 214 |
-involved in any conflict referred to this subproject, and must be |
| 215 |
-available to provide guidance, advice, or assistance if needed. The |
| 216 |
-lead is also charged with the tasks of ensuring all subproject members |
| 217 |
-are in fact active participants, that all members are eligible to |
| 218 |
-serve, that the subproject works to establish any necessary internal |
| 219 |
-procedures, and for similar administrative actions necessary for |
| 220 |
-proper functioning of the board. |
| 221 |
+Any conflicts that are purely technical should be addressed to either QA or |
| 222 |
+Council. If a technical issue is turned into a personal issue, it would then be |
| 223 |
+applicable. |
| 224 |
+Please note, any conflict where a developer wishes to report a user should be |
| 225 |
+escalated to User Relations. |
| 226 |
</p> |
| 227 |
|
| 228 |
-</body> |
| 229 |
-</section> |
| 230 |
- |
| 231 |
-<section> |
| 232 |
-<title>Conflict Resolution Policy</title> |
| 233 |
-<body> |
| 234 |
- |
| 235 |
<p> |
| 236 |
-Once a complaint is sent to the Conflict Resolution subproject, the |
| 237 |
-board assumes responsibility for coordinating all aspects of the |
| 238 |
-complaint. The board must act in accordance with the following |
| 239 |
-guidelines: |
| 240 |
+Once a complaint is sent to Developer Relations, the team assumes |
| 241 |
+responsibility for coordinating all aspects of the complaint. The team must act |
| 242 |
+in accordance with the following guidelines: |
| 243 |
</p> |
| 244 |
|
| 245 |
<p> |
| 246 |
-Disputes between developers are first assigned to a member of the |
| 247 |
-Developer Relations Conflict Resolutions Subproject for mediation. |
| 248 |
-This step may be omitted only upon unanimous agreement among the |
| 249 |
-the board members, and only if no such subproject member has already |
| 250 |
-attempted mediation as described above. |
| 251 |
+Mediation efforts are not intended to be transparent to the developer |
| 252 |
+community. Developer Relations respects the privacy of the developers whom we |
| 253 |
+work with; accordingly there can and will be mediation efforts made without |
| 254 |
+being made public knowledge to the rest of the developer community. Regardless |
| 255 |
+of private or public knowledge mediation, all mediation efforts will be |
| 256 |
+confined to a window of 4 weeks. If mediation has not proven successful by this |
| 257 |
+time, regardless of reason, the issue will be escalated to Developer Relations |
| 258 |
+for a vote. |
| 259 |
</p> |
| 260 |
|
| 261 |
<p> |
| 262 |
-Complaints that do not require mediation per se (such as repeat QA |
| 263 |
-problems) are dealt with exclusively by the board. Problems for |
| 264 |
-which mediation has been unsuccessful are also returned to the board |
| 265 |
-for resolution. |
| 266 |
+Disputes between developers are first assigned to a member of the Developer |
| 267 |
+Relations team for mediation. This step may be omitted only upon unanimous |
| 268 |
+agreement among the mediation members, and only if no such member has already |
| 269 |
+attempted mediation as described above. A bug is not required for mediation; |
| 270 |
+however a bug is required if mediation efforts have failed or are not |
| 271 |
+applicable. |
| 272 |
</p> |
| 273 |
|
| 274 |
<p> |
| 275 |
-In either case, once a complaint reaches the board for final |
| 276 |
-resolution, the board should act upon the complaint in a timely |
| 277 |
-manner. Although it is impossible to establish absolute time limits, |
| 278 |
-unnecessary delays are not acceptable. It is up to the board members |
| 279 |
-themselves to establish communications among themselves. IRC is the |
| 280 |
-preferred communications medium, but e-mail is an acceptable |
| 281 |
-alternative if IRC proves to be impossible. |
| 282 |
+Complaints that do not require mediation per se are dealt with exclusively by a |
| 283 |
+vote of the Developer Relations team. Problems for which mediation has been |
| 284 |
+unsuccessful are also escalated to a vote of the Developer Relations team. |
| 285 |
</p> |
| 286 |
|
| 287 |
<p> |
| 288 |
-No matter how the board chooses to carry on its business, all official |
| 289 |
-proceedings including board meetings and voting sessions must be made |
| 290 |
-public. However, discussions with parties involved in a complaint held |
| 291 |
-for the purpose of mediation may be kept private at the request either |
| 292 |
-of the parties or of the board members meeting with the parties. The |
| 293 |
-subproject lead is responsible for releasing (the public) logs or |
| 294 |
-e-mails to the devrel mail alias and for maintaining an archive of all |
| 295 |
-public documents. In the case of private discussions, a summary of the |
| 296 |
-non-sensitive parts of the discussion should be provided. |
| 297 |
+In either case, once a complaint reaches the need for a vote the parties |
| 298 |
+involved in the escalation and the mediator are given three days to supply |
| 299 |
+Developer Relations with information on the matter. While information exchange |
| 300 |
+cannot be forced, it does not indicate the matter is dropped, nor the vote |
| 301 |
+cancelled, if any party does not provide information within three days. After |
| 302 |
+the third day, the Developer Relations team is given two weeks to vote on the |
| 303 |
+matter. The two week period allows members of Developer Relations to ask |
| 304 |
+questions to either party as applicable. The Mediator to the issue is not |
| 305 |
+excluded from voting. The Developer Relations Lead may only cast a vote if a |
| 306 |
+tie-break is needed. |
| 307 |
</p> |
| 308 |
|
| 309 |
</body> |
| 310 |
</section> |
| 311 |
|
| 312 |
<section> |
| 313 |
-<title>Resolution and Appeal</title> |
| 314 |
+<title>The Process for the Resolution Conflicts</title> |
| 315 |
<body> |
| 316 |
|
| 317 |
<p> |
| 318 |
-Once the board members determine they have enough information to reach |
| 319 |
-a conclusion, they meet to make a final determination of the |
| 320 |
-appropriate resolution of the complaint. The subproject lead does not |
| 321 |
-vote in determining this final resolution unless needed to break a |
| 322 |
-tie. |
| 323 |
+Developer Relations includes a team of Mediators dedicated to resolving |
| 324 |
+disputes covered by this policy. Should such mediation fail, Developer |
| 325 |
+Relations will vote to resolve the issue. The information regarding the issue |
| 326 |
+will be presented by each involved party as well as the Mediator involved, if |
| 327 |
+applicable. |
| 328 |
</p> |
| 329 |
|
| 330 |
<p> |
| 331 |
-Any party to a dispute resolved by the board may appeal the resolution |
| 332 |
-to the Developer Relations lead(s). No other developer may appeal. |
| 333 |
+Each party is given three days to present information on the issue, at the end |
| 334 |
+of the third day the team will review the information regarding the issue and |
| 335 |
+vote on a resolution. The team will decide which information presented is valid |
| 336 |
+for the current case and disregard information which is deemed invalid or not |
| 337 |
+applicable to the current case. |
| 338 |
</p> |
| 339 |
|
| 340 |
<p> |
| 341 |
-In case of an appeal, the Developer Relations lead(s) must take one of two |
| 342 |
-actions. They may deny the appeal and refer it to the Council for final |
| 343 |
-resolution. |
| 344 |
+All members of Developer Relations have one vote to determine the appropriate |
| 345 |
+disciplinary action; all votes must be received within 14 days. For the voting |
| 346 |
+to be valid it requires a simple majority of all Developer Relations members to |
| 347 |
+vote in a particular direction. |
| 348 |
</p> |
| 349 |
|
| 350 |
<p> |
| 351 |
-Or, they may accept the appeal. If they accept the appeal, the lead(s) |
| 352 |
-must immediately post the appeal to the devrel mail alias for vote on |
| 353 |
-the appeal by all of Developer Relations. Developer Relations members |
| 354 |
-then have three days in which to vote to accept or deny the appeal. |
| 355 |
+To illustrate this, if there are currently 12 members in the Developer |
| 356 |
+Relations project then at least 7 members must vote in a particular direction. |
| 357 |
+This does not mean that all 12 members must vote, just that the majority of the |
| 358 |
+team must vote in a one direction, making it unnecessary for the remaining 5 |
| 359 |
+members to vote as they would have already been over ruled by the majority |
| 360 |
+vote. If the vote is split 50/50, the Developer Relations Lead will cast the |
| 361 |
+deciding vote. |
| 362 |
</p> |
| 363 |
|
| 364 |
+</body> |
| 365 |
+</section> |
| 366 |
+ |
| 367 |
+<section> |
| 368 |
+<title>Resolution and Appeal</title> |
| 369 |
+<body> |
| 370 |
+ |
| 371 |
<p> |
| 372 |
-If a majority of those who vote agree with the appeal, then the appeal |
| 373 |
-is successful. In this case, the judgment of the board is modified as |
| 374 |
-requested in the appeal. |
| 375 |
+Any party to a dispute resolved by the Developer Relations team may appeal the |
| 376 |
+resolution to Council. No other developer may appeal. |
| 377 |
</p> |
| 378 |
|
| 379 |
<p> |
| 380 |
-If Developer Relations votes to deny the appeal, then the judgment of |
| 381 |
-the board is accepted unmodified. The outcome of such a vote may be |
| 382 |
-appealed to the Council for resolution, but again only parties affected |
| 383 |
-by the resolution are allowed to appeal. |
| 384 |
+Council may decide to override the Developer Relations decision, this decision |
| 385 |
+would be reached by majority vote within Council, in which case the Council |
| 386 |
+decision would be respected and adhered. Repeat offenses for the same action |
| 387 |
+would be treated as such, resulting in review of possible disciplinary actions |
| 388 |
+at the discretion of Developer Relations with the appeal process being the same. |
| 389 |
</p> |
| 390 |
|
| 391 |
</body> |
| 392 |
@@ -240,43 +251,23 @@ |
| 393 |
<body> |
| 394 |
|
| 395 |
<p> |
| 396 |
-No member of Developer Relations may participate in more than one step |
| 397 |
-in the attempt to resolve a conflict. Specifically, anyone who attempts |
| 398 |
-to mediate or otherwise resolve a conflict early in the process is barred |
| 399 |
-from taking part in later stages (such as serving on any required dispute |
| 400 |
-resolution board). |
| 401 |
-</p> |
| 402 |
- |
| 403 |
-<p> |
| 404 |
-In particular, if a party to a dispute is also a member of Developer |
| 405 |
-Relations, that person may have no role in the dispute resolution process |
| 406 |
-except as a party. If that Developer Relations member also has a specific |
| 407 |
-role in the resolution process (such as Developer Relations lead or Conflict |
| 408 |
-Resolutions sublead), then that person must immediately inform Developer |
| 409 |
-Relations of the conflict and ask Developer Relations to select an alternate |
| 410 |
-to act in his or her place for this dispute. |
| 411 |
-</p> |
| 412 |
- |
| 413 |
-<p> |
| 414 |
-For any complaint sent to the Conflict Resolution subproject, the |
| 415 |
-Developer Relations lead(s) and the subproject lead should speak with |
| 416 |
-each board member to determine any conflict of interest issues. Board |
| 417 |
-members having a conflict of interest in any particular dispute may |
| 418 |
-not participate in the resolution of that dispute. They should be |
| 419 |
-replaced by an alternate chosen by the subproject lead. Whether the |
| 420 |
-alternate becomes a permanent board member or whether the member |
| 421 |
-rotated out is brought back at the end of the dispute is left to the |
| 422 |
-discretion of the subproject lead. |
| 423 |
+If a party to a dispute is also a member of Developer Relations, that person |
| 424 |
+may have no role in the dispute resolution process except as a party; |
| 425 |
+forfeiting their vote if a Developer Relations vote is held. It is the |
| 426 |
+responsibility of that person to immediately inform Developer Relations of the |
| 427 |
+conflict. The only way a conflict of interest is applicable is when a person |
| 428 |
+involved in the mediation/resolution process is also involved in the conflict. |
| 429 |
+As developers, we are entrusted to make decisions in the best interest of |
| 430 |
+Gentoo and set aside personal interest for the best interest of Gentoo as a |
| 431 |
+whole. |
| 432 |
</p> |
| 433 |
|
| 434 |
<p> |
| 435 |
-Complaints raised about any member of the Conflict Resolution |
| 436 |
-subproject may be raised to the Developer Relations lead(s) or at |
| 437 |
-Developer Relations meetings for discussion at any time. Under extreme |
| 438 |
-circumstances, Developer Relations as a whole may vote to remove |
| 439 |
-members from the conflict resolution subproject. Also, board members |
| 440 |
-may be replaced at the subproject lead's discretion with an |
| 441 |
-explanation to Developer Relations. |
| 442 |
+Complaints raised about any member of Developer Relations may be raised to the |
| 443 |
+Developer Relations lead(s) or to Developer Relations via |
| 444 |
+<mail>devrel@g.o</mail> for discussion at any time; a meeting may be |
| 445 |
+called to discuss the matter further, up to and including to vote to remove |
| 446 |
+members. |
| 447 |
</p> |
| 448 |
|
| 449 |
</body> |
| 450 |
|
| 451 |
|
| 452 |
|
| 453 |
-- |
| 454 |
gentoo-commits@l.g.o mailing list |
Archives