Skip to content

Conversation

@garlick
Copy link
Member

@garlick garlick commented Dec 10, 2025

@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.

@github-actions
Copy link

⚠️ linkcheck failed with status code 2

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.
@github-actions
Copy link

⚠️ linkcheck failed with status code 2

Copy link
Contributor

@grondo grondo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. One suggestion and a couple questions inline.

spec_48.rst Outdated
the flux-framework organization:

Administrator
A person with the GitHub administrator access to the organization and all its
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

spec_48.rst Outdated
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, sorry, "free range" was a bit silly.

I think Collaborator was just another name for contributor. Will fix.

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.
Problem: collaborator and contributor are used interchangeably
in this RFC.

Use contributor.
@garlick
Copy link
Member Author

garlick commented Dec 10, 2025

Fixed those things and will set MWP.

@mergify mergify bot added the queued label Dec 10, 2025
@mergify mergify bot merged commit af05fab into flux-framework:master Dec 10, 2025
7 checks passed
@mergify
Copy link
Contributor

mergify bot commented Dec 10, 2025

Merge Queue Status

✅ The pull request has been merged at 5034048

This pull request spent 6 seconds in the queue, with no time running CI.
The checks were run in-place.

Required conditions to merge
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:flux-rfc
    • check-neutral = docs/readthedocs.org:flux-rfc
    • check-skipped = docs/readthedocs.org:flux-rfc
  • any of [🛡 GitHub branch protection]:
    • check-success = make check
    • check-neutral = make check
    • check-skipped = make check
  • any of [🛡 GitHub branch protection]:
    • check-success = validate commits
    • check-neutral = validate commits
    • check-skipped = validate commits

@mergify mergify bot removed the queued label Dec 10, 2025
@github-actions
Copy link

⚠️ linkcheck failed with status code 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants