| 1 |
musikc 08/04/27 16:33:01 |
| 2 |
|
| 3 |
Modified: policy.xml |
| 4 |
Log: |
| 5 |
Revision |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.19 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.19&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/policy.xml?rev=1.19&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/policy.xml?r1=1.18&r2=1.19 |
| 13 |
|
| 14 |
Index: policy.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/policy.xml,v |
| 17 |
retrieving revision 1.18 |
| 18 |
retrieving revision 1.19 |
| 19 |
diff -u -r1.18 -r1.19 |
| 20 |
--- policy.xml 2 Feb 2008 14:32:02 -0000 1.18 |
| 21 |
+++ policy.xml 27 Apr 2008 16:33:01 -0000 1.19 |
| 22 |
@@ -7,8 +7,8 @@ |
| 23 |
|
| 24 |
<abstract>Developer Relations Policy Guide</abstract> |
| 25 |
|
| 26 |
-<version>1.1.3</version> |
| 27 |
-<date>2008-02-02</date> |
| 28 |
+<version>1.1.4</version> |
| 29 |
+<date>2008-04-26</date> |
| 30 |
|
| 31 |
<chapter> |
| 32 |
<title>Conflict resolution policy</title> |
| 33 |
@@ -94,11 +94,16 @@ |
| 34 |
critical situations where immediate action is required, such disciplinary |
| 35 |
action is determined by members of the Developer Relations project. If the |
| 36 |
issue is deemed critical, the developer in question may have his or her access |
| 37 |
-suspended while a vote takes place; the critical nature of an escalation may be |
| 38 |
-determined by the Developer Relations Lead or Infrastructure, for |
| 39 |
-security-related issues, that which would endanger Gentoo, or our reputation. |
| 40 |
-An issue that is deemed critical does not need further justification in |
| 41 |
-addition to stating which of the above situations it falls under. |
| 42 |
+suspended while a vote takes place. In such situations, the Developer Relations |
| 43 |
+lead may act without a vote of the remaining Developer Relations team; this |
| 44 |
+power is granted by Council. In the event of such a case, process for |
| 45 |
+the resolution of the conflict may be bypassed altogether, a decision may be |
| 46 |
+made, and any disputes would then be raised to Council per the below appeal |
| 47 |
+process. The critical nature of an escalation may be determined by the |
| 48 |
+Developer Relations Lead or Infrastructure, for security-related issues, that |
| 49 |
+which would endanger Gentoo, or our reputation. An issue that is deemed |
| 50 |
+critical does not need further justification in addition to stating which of |
| 51 |
+the above situations it falls under. |
| 52 |
</p> |
| 53 |
|
| 54 |
<p> |
| 55 |
@@ -231,7 +236,7 @@ |
| 56 |
<body> |
| 57 |
|
| 58 |
<p> |
| 59 |
-Any party to a dispute resolved by the Developer Relations team may appeal the |
| 60 |
+Any party to a dispute resolved by Developer Relations may appeal the |
| 61 |
resolution to Council. No other developer may appeal. |
| 62 |
</p> |
| 63 |
|
| 64 |
|
| 65 |
|
| 66 |
|
| 67 |
-- |
| 68 |
gentoo-commits@l.g.o mailing list |
Archives