This page lists the most common questions related to the RFC process. If you want to know more, just send us a message via our contact page.
Do I need a GitHub or an OpenReview.net account to contribute to an RFC?
Yes, you will need a GitHub account if you would like to contribute directly to the text of an RFC, to discuss issues or to comment on pull requests. If you would like to comment on a review candidate on OpenReview.net you will need an account on OpenReview.net. Both tools serve to make attributions of content and comments from individual persons possible and to help to ensure scientific standards for the drafting and review process.
I have an idea for an RFC. What do I do?
Please contact the RFC Editorial Committee with your idea. They will assist you with the creation an initial draft version of the idea, if it is deemed to be suitable and feasible.
I would like to fix some errors in an RFC draft. How do I do that?
The easiest way is for you to sign in to your GitHub account, create a fork of the main RFC repository into your own account, fix the error in your forked version of the document, commit it into your repository and open a pull request outlining your changes to the main RFC repository. It will then be visible, can be reviewed and then eventually merged into the main draft document if the changes are accepted by the reviewers.
I have worked on a draft document myself and would like to preview the final PDF document to see how it would look. How can I do this?
If you follow the official contribution process by forking the main RFC repository, anything you push to the
master branch in your own repository will be automatically converted into a PDF document by triggering a GitHub action. You can access the ZIP file with the compiled draft documents in the GitHub job details page in the action section.
How do I see which drafts are currently available for contributions or release candidates open for review?
You can see the current plan of work in the
README file of the main RFC repository.