Versions Compared

Old Version 3

changes.mady.by.user Olamide Kolawole

Saved on

compared with

New Version 4

changes.mady.by.user Olamide Kolawole

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Fork the official RFC repo at https://github.com/folio-org/rfcs . This is usually only needed once for any number of RFCs to be submitted.
  2. Create a file in the text directory at the top of the forked repo. It should follow the template defined here.
    • Ensure that the file is named appropriately, taking note of the sequence numbers of existing RFCs.
  3. Make edits to the file as needed for the RFC.
  4. Commit edits and push changes to the forked repo.
  5. In the forked repo on GitHub, create a PR comparing the branch where edited file is located to the master branch of the official RFC repo.
    • Ensure the name of the pull request has the name of the RFC phase at the beginning. e.g. "[DRAFT REVIEW] Java 17" or "DRAFT REVIEW | Java 17"
  6. When the interactions on the pull requests are complete there are two options based on the current status of the RFC:
    1. There are still other phases left in the RFC process: close Close the pull request and start from step Step 3 from in this guide.
    2. The RFC is at the last phase: The pull request will be merged by a maintainer of the official RFC repo. The RFC should be at its end with no other actions necessary.