#54 Add a Policy Change Policy
Merged 2 months ago by bcotton. Opened 3 months ago by bcotton.

Add a Policy Change Policy
Ben Cotton • 3 months ago  

@@ -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.

Per AsciiDoc Recommended Practices, they suggest writing one sentence per line. It makes it easier to compare diffs in changes to written documents. Normally I think this is a nitpick, but since this is a policy document, it might help to follow this convention for easier review of changes in the future.

I saw this ticket from the Community Blog post. I wanted to give a big :thumbsup: for this policy change. This adds better transparency and visibility into understanding how changes and decisions are made that involve the wider community.

Per AsciiDoc Recommended Practices, they suggest writing one sentence per line. It makes it easier to compare diffs in changes to written documents. Normally I think this is a nitpick, but since this is a policy document, it might help to follow this convention for easier review of changes in the future.

+1

rebased onto 582b297

3 months ago

Thanks for the review, @jflory7 . I corrected the two issues you pointed out.

The community blog is available via HTTPS, so please adjust the URL.

rebased onto 6970369

3 months ago

Pull-Request has been merged by bcotton

2 months ago
Metadata