The crust
project is an OPENISH Open Source Project
Individuals making significant and valuable contributions are given commit-access to a project to contribute as they see fit. A project is more like an open wiki than a standard guarded open source project.
There are a few basic ground-rules for contributors (including the maintainer(s) of the project):
- No
--force
pushes or modifying the master branch history in any way. If you need to rebase, ensure you do it in your own repo. - Non-master branches, prefixed with a short name moniker (e.g. zik/my-feature) must be used for ongoing work.
- All modifications must be made in pull-request to solicit feedback from other contributors.
- A pull-request must not be merged until CI has finished successfully.
- Contributors should adhere to the substrate House Coding Style.
A PR needs to be reviewed and approved by project maintainers unless:
- it does not alter any logic (e.g. comments, dependencies, docs), then it may be tagged
A5-insubstantial
and merged by its author once CI is complete. - hotfix with no large change to logic, then it may be merged after a non-author contributor has approved the review once CI is complete.
A-*
Pull request. ONE REQUIRED.P-*
Priority. ONE REQUIRED.
- Please tag each PR with 1
A
andP
label at the minumum. - PRs that break the external API must be tagged with
A2-breakapi
. - PRs that change the FRAME or consensus of running system with
A0-breakconsensus
. - PRs that change the client or any other logic which may lead to hard fork must be tagged with
A1-maybeforked
. - PRs should be labeled with priority via the
P0-P2
.
Please label issues with the following labels:
I-*
Issue severity and type. EXACTLY ONE REQUIRED.P-*
Priority. AT MOST ONE ALLOWED.