nervosnetwork / nervosnetwork/rfcs
Trace RFC Number Allocation
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 271
- Forks
- 158
- PR merge metrics
- No merged PRs in 30d
Description
This issue trace RFC number allocation to avoid conflicts.
If you want to submit an RFC, please leave a comment here to reserve an RFC number first.
NumberPR
-
40#290 -
41#335 -
42#343 -
43#349 -
44#370 -
45#375 -
46Rejected -
47Available -
48#416 -
49#419 -
50#418 -
51#417 -
52#428 -
53#442 -
54#451 55Available Since Here
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the RFC allocation checklist in issue #246 and the referenced pull request numbers. Check which entries are reserved, completed, rejected, or available, then ensure the table reflects the current allocation state. Done means the checklist accurately shows the status of each listed RFC number.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100