Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Number RFCs by order of proposal

Open
#23 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start by reviewing the RFC files, especially those in the accepted/ folder, and identify each proposal's order from the repository history. Rename RFC files with a zero-padded number at the beginning, then verify that accepted/ is ordered by proposal and that references such as RFC 001 are unambiguous.

Written by the indexing model from the issue text.

Description

Assign each RFC a number in order of when it was proposed that is put as the beginning of the file name e.g. 000-rfc-process.md.

  • Users will be able to tell what order RFCs were proposed in
  • Users will be able to reference individual RFCs more easily (e.g. "go look at RFC 001")
  • RFCs will be ordered in the accepted/ folder by order of proposal
  • RFCs which change the RFC process can be more clear (e.g. "RFCs after 001 MUST...")
Dominant language
No language data
Stars
73
Forks
23
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/rfcs

All issues in bytecodealliance/rfcs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.