A Carbyne Stack Enhancement Proposal (CSEP) is a way to propose, communicate and coordinate on new efforts for the Carbyne Stack project. The CSEP process is intended to provide a consistent and controlled path for changes to Carbyne Stack (such as new features) so that all stakeholders can be confident about the direction of the project.
- Promote an idea within the community, in particular onboard the maintainers, by pitching at the Carbyne Stack community meeting. Do this early to avoid any waste of effort in case your idea is rejected and to make sure that you give all stakeholders a chance to comment on and possibly join the effort. No need to have a proposal with all bells and whistles attached at this stage.
- In case your proposal is well received, fill in the
CSEP template with all the required information and
create an issue to track the implementation of the proposal. Note that the
issue will go through the regular triage process and gets assigned a
priority. CSEPs should be developed in the public whenever possible as a
shared document in this folder. The name of the file should follow the
pattern
NNNN-short-title.mdwhereNNNNis the zero prefixed issue number used to track the implementation of the CSEP from above.
The CSEP process is heavily inspired by IETF RFCs, Kubernetes KEPs and Rust RFCs.