Define a process for resolving disagreements among stakeholders for the RFC process

Open
#6 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start by reading issue #1 and the linked comment from @joshtriplett to understand the unresolved RFC conflict concern. Define and document a process for resolving stakeholder disagreements before an RFC remains in limbo; the work is done when the process is agreed and recorded for future RFCs.

Written by the indexing model from the issue text.

Description

Over in #1, @joshtriplett highlighted that we haven't yet defined a process for resolving conflicts that might otherwise leave RFCs in limbo indefinitely. We shouldn't put this off for too long, and instead aim to have it in place before the first such case occurs.

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.