RFCs for changes to Star Haven
1 1 0

Clone this repository

https://tangled.org/starhaven.dev/rfcs https://tangled.org/did:plc:tjgdahiw3u2djgnigyqeummg/rfcs
git@knot.starhaven.dev:starhaven.dev/rfcs git@knot.starhaven.dev:did:plc:tjgdahiw3u2djgnigyqeummg/rfcs

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz
README.md

Star Haven RFCs#

The "RFC" (request for comments) process provides a way to propose and discuss substantial changes to Star Haven repos before implementing them. Think of it as collaborative planning.

When you need an RFC#

Some changes are "substantial", and we ask that these be put through a bit of a design process first. This includes:

  • Major architectural decisions (new services, new databases, etc.)
  • New features that affect multiple components / are cross-repo

Many changes, including bug fixes, documentation improvements, and minor UI tweaks, can be implemented and reviewed via the normal pull request workflow without an RFC.

Process#

  • Fork this repository.
  • Clone your fork locally.
  • Copy 0000-template.md to text/0000-my-feature.md.
  • Fill in the RFC file.
  • Commit on a branch and push it.
  • Submit a pull request..
  • Post it in Discord so we can discuss it.
  • Once the open questions have been discussed and solved, edit the RFC file and push.
  • The PR will be merged once it the RFC is accepted.