| |
@@ -1,4 +1,4 @@
|
| |
- = Code of Conduct reponse policy
|
| |
+ = Fedora Council Policies
|
| |
|
| |
[NOTE]
|
| |
====
|
| |
@@ -9,6 +9,13 @@
|
| |
|
| |
====
|
| |
|
| |
+ == Code of Conduct response policy
|
| |
Once a ticket notifying us of a code of conduct issue has been filed, the Council will respond with an initial contact message within one week. That will come with a request for response, and further action will come within a week of the Council's initial response.
|
| |
|
| |
(Fedora Council IRC meeting, 2018-05-23)
|
| |
+
|
| |
+ == Policy Change policy
|
| |
+
|
| |
+
|
| |
+ Proposed changes to Fedora Council policies must be publicly announced on the https://lists.fedoraproject.org/admin/lists/council-discuss.lists.fedoraproject.org/[council-discuss mailing list] and in a https://communityblog.fedoraproject.org/[Fedora Community Blog] post in order to get feedback from the community.
|
| |
+ After a minimum of two calendar weeks, the Council may vote on the proposed change using the *full consensus* voting model. After approval, the change is reflected on the https://docs.fedoraproject.org/en-US/council/policies/[Council policies page].
|
| |
We don't have a good policy for changing our policies. That seems like a bug we should fix.