Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
211 lines (141 loc) · 10.1 KB

CONTRIBUTING.md

File metadata and controls

211 lines (141 loc) · 10.1 KB
Raw

Contributing to the coding guidelines

Table of Contents

Contribution Workflow

Here's a diagram of the overall process:

flowchart TD
  Start(["Start"]) --> Idea["Coding Guideline Idea"]
  Idea --> Zulip[/"(Optional)<br>0: Contributor brings <br> to discuss on Zulip"/]
  Zulip --> CreateIssue{{"1: Contributor creates <br> issue"}}
  CreateIssue --> Issue["Coding Guideline Issue"]

  S2{{"2: reStructuredText <br> generated as comment <br> on issue"}} --> Issue
  Issue --> S2

  S3{{"3: Review started by subcommittee member in <= 14 days <br><br> Contributor updates accordingly"}} --> Issue
  Issue --> S3

  Issue --> S4{{"4: Contributor creates a PR using the reStructuredText generated for them on issue"}} --> PR["Coding Guideline<br>Pull Request"]

  S5{{"5: <br> 5.1 PR review started by subcommittee member in <= 14 days <br><br> 5.2 Contributor discusses on PR with members and updates"}} --> PR
  PR --> S5

  PR --> S6{{"(Optional) <br> 6: Contributor applies feedback to issue"}} --> Issue
  Issue --> S7{{"(Optional)<br> 7: Contributor applies updated reStructuredText to Pull request"}} --> PR
  PR --> S8{{"8: Subcommittee member <br> approves & queues;<br>merges to main"}} --> Main[[main]]
  Main --> End(["9: End"])
Loading

Note on Chapter Layout

The Safety Critical Rust Coding guidelines has the same chapter layout as the Ferrocene Language Specification (FLS). If you would like to contribute a new guideline, find a section from the FLS that interests you, then write a guideline in the corresponding chapter of these coding guidelines.

0) (Optional) Bring the idea up for discussion

Have an idea for a coding guideline? Want to discuss it?

If you want to discuss the feasibility of a guideline or discuss it with others to ensure it's not too similar an existing guideline, drop by the Safety-Critical Rust Consortium's Zulip stream and open a new topic.

1) Submit coding guideline issue

To add a new coding guideline, open a coding guideline issue.

1.1) Finding the FLS ID

Note that the FLS ID should be filled according to the FLS paragraph ID for which the guideline is covering. One way to go about finding this is to inspect the page using your web browser. You'll be looking for something like:

<p><span class="spec-paragraph-id" id="fls_4rhjpdu4zfqj">4.1:1</span>

You would then pull fls_4rhjpdu4zfqj to place in the FLS ID field.

2) Guideline Generated as a Comment

A GitHub Action will fire, adding a comment to your newly created issue with the contents of the coding guideline prepared written out correctly in reStructuredText.

Note that if you later update the body of the coding guideline issue this will fire the GitHub Action again and update the original comment with the new contents converted to reStructuredText.

3) Create a Draft with a Member

Within 14 days of your submission, a member of the Coding Guidelines Subcommittee should give you a first review. You'll work with them (and other members) to flesh out the concept and ensure the guideline is well prepared for a Pull Request.

4) Create the PR

Note

Here's a list of recommended prerequisites that shall be fulfilled before turning an issue into a PR:

  • The new rule isn't already covered by another rule
    • OR, in case there is(are) already another rule(s),
    • The existing rule(s) need(s) to be linked to the new rule,
    • AND the new rule needs to link to the existing rule(s).
  • All sections contain some content
  • Content written may be incomplete, but must not be incorrect
  • 🧪 Code Example Test Results section shows all example code compiles

As soon as these prerequisites are fulfilled, the draft shall be marked as PR-ready by a subcommittee member, by labeling the issue with sign-off: create pr. This denotes that you should create a Pull Request with your Guideline. Further discussion about the amount and correctness of its content shall then be done on the Pull Request itself.

The contents of the PR should be based on the bot comment containing the generated RST form of your guideline, as seen in Step 2. The comment has the exact file content you'll need.

In order to ensure your guideline appears when rendering the document, reference the generated comment from Step 2. All the steps necessary should appear below the headings 📁 Target Location and 🗂️ Update Chapter Index.

Make sure to include this command in the body of your PR, where xyz is the number of the issue you opened in Step 1:

closes #xyz

This will ensure issue #xyz is closed when your Pull Request gets merged.

5) Iterate on Feedback

5.1) Member Begins Review

The generated Pull Request may attract additional feedback or simply be an easier place to suggest targeted edits.

As the contributor of the coding guideline and opener of the issue, you'll respond to comments, discuss, all the normal things on the pull request.

5.2) Update the PR Based on Feedback

If you agree with the suggested changes, you've got two options:

6) Contributor Applies Feedback on Issue

(Optional, if not comfortable with reStructured Text from 5.2) Update the PR Based on Feedback)

The contributor edits the body of the issue summary, reflecting suggestions and then saves it. You will then momentarily see a new comment added to the issue containing the updated guideline content written in reStructured Text.

7) Contributor Applies Regenerated Guideline to PR

(Optional, if not comfortable with reStructured Text from 5.2) Update the PR Based on Feedback)

The contributor then copy + pastes the contents of the guideline from 6) Contributor Applies Feedback on Issue and overwrites the contents of their feature branch, so that the feedback is reflected into the Pull Request.

8) Your Guideline gets merged

Once the coding guideline contents have passed review, a subcommittee member will approve the pull request, and put it on the merge queue to be merged.

You just contributed a coding guideline!

That's it!

Writing a guideline locally (less typical, not recommended)

While it is possible to create guidelines locally, we encourage contributors to make use of the process described above since it handles some of the fiddly details for you as a guideline writer.

Guideline template

We have a script ./generate_guideline_templates.py which assumes you're using uv that can be run to generate the template for a guideline with properly randomized IDs.

You can the copy and paste this guideline from the command line into the correct chapter.

Before You Begin Contributing

Licenses

There is no Contributor License Agreement to sign to contribute this project. Your contribution will be covered by the license(s) granted for this repository, commonly MIT, Apache, and/or CC-BY, but could be a different license. In other words, your contribution will be licensed to the Foundation and all downstream users under those licenses. You can read more in the Foundation's intellectual property policy.

Code of Conduct

Please review and adhere to the code of conduct before contributing any pull requests.

Contribution Process

All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.

Issues

Do you just want to file an issue for the project? Please do so in GitHub under the Issues tab.