rfc43: update roles section #485
Open
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
|
|
Problem: the governance doc discussed "the project", which could be confusing since "the project" is really a github organization that contains several github projects, that may have different maintainers. Add a sentence to the Project Governance intro to make this explicit.
Problem: maintainers are mentioned outside the Roles section, and administrators are not defined. Since we are distinguishing between individual project Maintainers and the framework Administrators, be explicit about that in the Roles section.
|
|
grondo
approved these changes
Dec 10, 2025
Contributor
grondo
left a comment
grondo
left a comment
There was a problem hiding this comment.
This looks good to me. One suggestion and a couple questions inline.
| the flux-framework organization: | ||
|
|
||
| Administrator | ||
| A person with the GitHub administrator access to the organization and all its |
Contributor
There was a problem hiding this comment.
Suggested change
| A person with the GitHub administrator access to the organization and all its | |
| A person with GitHub administrator access to the organization and all its |
Comment on lines
+54
to
+57
| Contributor | ||
| A person who wishes to provide a patch. This person may be added to the | ||
| GitHub project without commit access, or they may be "free range" | ||
| contributors without special access. |
Contributor
There was a problem hiding this comment.
Should Collaborator also be defined here (or actually below)? (It is used later in the document) I think there was already a discussion around the term "collaborator" but I don't remember the resolution.
I'm actually not sure what "free range" contributor means here, does that just mean they are contributing issues or pull requests from their own forks without special access? (maybe just say that?)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@grondo, @trws, and I had a chat today about this and wanted to add Administrator as a new role in the gov doc. This would be the people who are able to add/remove projects from the flux-framework organization and do other "root" like tasks within it.
This defines the new role and tries to distinguish between "the project" which is really the organization, and the individual projects within it which follow the rules, but may have different maintainers for example. (They also may have different policies for development, within the constraints of RFC 1).
Anyway, @trws or @grondo please make sure I captured what we discussed.
p.s. I also added a README.md for the organization that lists me, @grondo, and @trws as the administrators and this doc links to that page.