Consider adding a section for risk assessment to the RFC template

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Locate the RFC template referenced by this issue and read the discussion linked from #1 for the intended risk-assessment concern. Add a section that asks proposals to describe potential problems and weigh their severity, then verify the template presents this guidance clearly.

Written by the indexing model from the issue text.

Description

Over in #1, @ggreif highlighted that the RFC template doesn't include a section on risk assessment:

Should a proposal address some pain point, at the cost of potentially introducing other problems, one needs to elaborate the latter, and weigh in on their severity. One could argue that this belongs into the discussion of the proposal, but that thread is not a document.

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.