Draft: Defining clear rules regarding merging a PR #678
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial clean up
Draft Spec Committee
Co-authored-by: caso <matteocasonato@protonmail.com>
Update Committee
Add Kamil
Quadrivium instead of Soramitsu
|
Per my comment here, it seems like this may be a good opportunity to deploy the Polkadot Fellowship. |
|
The idea behind introducing the Spec Committee, in addition to the technical fellowship:
That said, I'm happy also to move the spec to the fellowship and to discuss or help fellowship members with the transition. |
|
Any additional comments here? Given the response here, I would like to at least give it a try and see if this leads to more/better contributions to the spec. |
bhargavbh
approved these changes
Sep 4, 2023
Add myself, as requested
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given that we now have separated the website repo and the spec repo, it might make sense to define clear rules regarding who decided what should be merged and what shouldn't. Therefore I quickly came up with a Spec Committee and potentially we can also integrate some additional rules (e.g., the spec needs to be based on research and/or existing implementations). My main goals here are: