merging from a differently named branch for some reason. (#117)

* proposal for RFC process

* Update README.md

fixing typo

Co-authored-by: Pavel Kirienko <[email protected]>

* Update README.md

fixing wording

Co-authored-by: Pavel Kirienko <[email protected]>

* changes per discussion on PR

* Fix typo

Co-authored-by: Pavel Kirienko <[email protected]>

* Update README.md

Co-authored-by: Pavel Kirienko <[email protected]>

* Fix CI configuration

Configure the workflow to run on pull requests OR when pushed to specific branches

Co-authored-by: Pavel Kirienko <[email protected]>

Author: thirtytwobits

.github/workflows/build.yml

@@ -1,12 +1,13 @@
 # A workflow to create the Cyphal Specification PDF
 
 name: CI
-on: push
+on: [ push, pull_request ]
 
 jobs:
   build:
     runs-on: ubuntu-latest
     name: Build PDF file using LaTeX
+    if: github.event_name == 'pull_request' || contains(github.ref, '/master') || contains(github.ref, '/dev')
 
     steps:
     # Checks-out the repository under $GITHUB_WORKSPACE

README.md

@@ -8,6 +8,19 @@ The sources of the Cyphal specification and other related documents are containe
 When cloning this repository, don't forget to initialize the Git submodules:
 `git submodule update --init --recursive`.
 
+## Governance
+
+The Cyphal specification is community-managed and completely open. Anyone can propose changes but only Cyphal maintainers may commit changes to this repository where the contents of the HEAD revision of the primary branch constitutes the latest version of the specification in-effect.
+
+### Request For Comments (RFC) Process
+
+Changes to the specification shall use the following, community-driven RFC process:
+
+1. An RFC is posted on the [OpenCyphal forum's specification section](https://forum.opencyphal.org/c/dev/spec/15) with the details of the proposed change. The title of this post should start with "RFC: " to indicate it is the start of a proposed change to the specification.
+2. RFCs will remain on the forum for at least 10 days to ensure interested parties have time to discover and review them.
+3. After some discussion and review by the community, the RFC is either accepted or rejected by at least one OpenCyphal maintainer.
+4. Once accepted the RFC is implemented in the specification as a pull-request and is considered adopted once the PR has been merged.
+
 ## Editing guide
 
 ### Style