-
Notifications
You must be signed in to change notification settings - Fork 747
New provisions for what Core WG vs other WGs do #3894
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
Conversation
Example new working groups and purviews:
|
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.
I agree with this generally.
I would still like to see some brief statement about conflict resolution and/or escalation procedures for when there is a contribution to subsystems under purview of multiple working groups, or working groups propose contributions that are in conflict on a technical or conceptual level.
doc/wg/README.md
Outdated
organizations, physical distance, timezones, and engagement. It has | ||
also grown large in scope. This has resulted in strain on maintainers | ||
to regularly keep up with contributions while ensuring quality and | ||
important global policies like safety and security. It has also | ||
resulted in contributors' work going unaddressed for long periods of | ||
time. |
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.
I think this text is helpful in this PR description, but the goal is for this to become incorrect, which makes it awkward to add to the README. I think either we don't need it or it could be phrased as what we want to avoid, rather than what is currently happening.
doc/wg/README.md
Outdated
However, working groups are encouraged to avoid consensus-based | ||
decision making as quickly as possible and establish appropriate |
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.
I'm not sure what this is supposed to imply exactly. WGs are supposed to not converge to a consensus?
doc/wg/README.md
Outdated
its own rules for deciding how to accept contributions as well as how | ||
to establish and disband working groups. | ||
|
||
The Core Working Group's duties are: |
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.
Specifying these here is in conflict with the core WG charter.
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.
OK, you're right. I'll move these to doc/wg/core/README.md
@lschuermann, done. I think I addressed @bradjc's comments as well. |
Pull Request Overview
This pull request codifies the high-level responsibilities of the Core
WG relative to other working groups as originally proposed
here
and discussed on the Core WG 2024-03-01.
TODO or Help Wanted
Copy editing suggestion welcome
Documentation Updated
/docs
, or no updates are required.Formatting
make prepush
.