Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lightweight RFC Process #286

Closed
5 of 18 tasks
lidel opened this issue Jun 7, 2022 · 0 comments · Fixed by #289
Closed
5 of 18 tasks

Lightweight RFC Process #286

lidel opened this issue Jun 7, 2022 · 0 comments · Fixed by #289
Assignees
Labels
effort/weeks Estimated to take multiple weeks kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up status/in-progress In progress

Comments

@lidel
Copy link
Member

lidel commented Jun 7, 2022

The aim here is to create a convention-driven process that enables IPFS community
to propose changes to existing specs or even propose new ones.

Guiding principles

  • no new tooling
    • reuse markdown, git, and existing github PR review process for user auth / reputation etc
  • convention over byzantine process
    • proposing RFC should have low cognitive overhead, allowing us to focus on specs
    • one should be able to create a valid RFC without reading about the process: just looking at past RFCs, and then copying a template and opening a PR with their proposal should be good enough

TODO

Prior art

@lidel lidel added status/in-progress In progress P1 High: Likely tackled by core team if no one steps up kind/maintenance Work required to avoid breaking changes or harm to project's status quo effort/weeks Estimated to take multiple weeks labels Jun 7, 2022
@lidel lidel self-assigned this Jun 7, 2022
This was referenced Jun 7, 2022
@lidel lidel closed this as completed in #289 Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/weeks Estimated to take multiple weeks kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up status/in-progress In progress
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants
@lidel and others