-
Notifications
You must be signed in to change notification settings - Fork 16
Changes to eligibility framework and member process #47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or 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
- Currently includes unspecific references to the “ethos of decentralization,” a list of general characteristics that contributions should have, and descriptions of possible exceptions - Over the course of the Pilot, it became clear that the eligibility and the process for changing it should be better defined - see the DVT discussions - this PR adds explicit projects and research areas which maintain and progress the core protocol
- a rewrite of the Proposing and Discussing New Members section. The rewrite will better align with these more explicit Qualifications - Instead of proposing new members and new projects at the same time, the new process splits them into two distinct proposal types: “Members” and “Projects”
delete list of teams to align with new qualifications around projects or research areas
small typos
language tweaks, more example projects
rolfyone
reviewed
Jul 2, 2023
|
one minor point for discussion but I think overall this looks really good. |
potuz
reviewed
Jul 2, 2023
Co-authored-by: Danno Ferrin <[email protected]>
Co-authored-by: Danno Ferrin <[email protected]>
- Consensus work - Cryptography - Mechanism design - Resource pricing
shemnon
approved these changes
Jul 5, 2023
cheeky-gorilla
approved these changes
Jul 5, 2023
Contributor
cheeky-gorilla
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few minor fixes for doc 4 but other than that looks good to me.
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
Co-authored-by: cheeky-gorilla <[email protected]>
realbigsean
approved these changes
Jul 6, 2023
macfarla
reviewed
Jul 12, 2023
philknows
approved these changes
Jul 12, 2023
Co-authored-by: Sally MacFarlane <[email protected]>
Co-authored-by: Sally MacFarlane <[email protected]>
potuz
approved these changes
Jul 13, 2023
skylenet
approved these changes
Jul 14, 2023
gumb0
reviewed
Jul 18, 2023
gumb0
approved these changes
Jul 18, 2023
adiasg
approved these changes
Jul 18, 2023
Co-authored-by: Andrei Maiboroda <[email protected]>
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.
A proposal to make the Guild eligibility framework more explicit for existing and prospective members, as well as aligning the member process to match.
I've requested review from the people who engaged in the DVT discussion - looking for feedback on the concept of "projects vs members" generally, as well as the specific projects linked and any I missed.
This PR includes: