With more teams adopting the Starter Pack, we should have some form of guidance for contributors. Our current development practices are very opaque for anyone who isn't a regular contributor to our tooling.
We currently have a placeholder how-to guide that describes the mechanics of a contribution. On top of this, the proposed guide should set clear expectations on which changes belong in the Starter pack, how they'll be evaluated, and when they'll be released.
This is more of a detail, but I think it would be ideal if this came in the form of a top-level CONTRIBUTING.md file. I feel this is more discoverable when you have the repo open, and it can still be rendered in the RTD docs (albeit without full MyST syntax).
With more teams adopting the Starter Pack, we should have some form of guidance for contributors. Our current development practices are very opaque for anyone who isn't a regular contributor to our tooling.
We currently have a placeholder how-to guide that describes the mechanics of a contribution. On top of this, the proposed guide should set clear expectations on which changes belong in the Starter pack, how they'll be evaluated, and when they'll be released.
This is more of a detail, but I think it would be ideal if this came in the form of a top-level CONTRIBUTING.md file. I feel this is more discoverable when you have the repo open, and it can still be rendered in the RTD docs (albeit without full MyST syntax).