Change Suggestion and Resolution Process - OCFL/spec GitHub Wiki

Editorial collaboration takes place primarily in this repository on GitHub. When changes for revision are submitted, they must adhere to the following criteria:

  1. There should be a Github issue that explains the reason for the change and serves as a platform for discussion. Discussion regarding smaller, primarily word level, changes may take place directly on a pull request in the comments or as line notes.
  2. The Editorial Group will review tickets and talk through them in the bi-weekly meeting. Tickets will be assigned to individuals in the meeting who will then be responsible for making changes.
  3. The changes must be made in a branch and submitted as a pull request.
  4. The submitted pull request must reference the associated Github issue.
  5. Changes on the branch should be squashed into one commit, with a reasonable commit message, and one parent commit that is the latest revision. Multiple commits are allowed when they are logical, but this should generally be avoided as it usually indicates that there are too many changes happening on one branch.
  6. When one or more editors feel that a pull request is ready for final consideration, they must label the pull request as "Ready for Review".
  7. Once a pull request is labelled "Ready for Review", the editors have 72 hours to provide feedback or indicate approval or ambivalence.
  8. If necessary, the pull request may be labelled as "More Time Needed".
  9. A pull request may be merged when all editors have responded with 👍/+1, or after 72 hours have passed and a majority of editors have responded with 👍/+1, and no editors have responded with 👎/-1.
  10. Minor updates, such as those that affect only whitespace, grammar, and typo fixes may be merged when a majority of editors have responded with 👍/+1, and no editors have responded with 👎/-1, without waiting for 72 hours.