-
Notifications
You must be signed in to change notification settings - Fork 234
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
Combine Steering and TO Committees #1587
base: main
Are you sure you want to change the base?
Conversation
…establishing process for future 1-election-per-year schedule.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -236,20 +244,20 @@ found in the [elections folder](./elections). | |||
|
|||
### Limitations on Company Representation | |||
|
|||
No more than two seats may be held by employees of the same organization (or | |||
conglomerate, in the case of companies owning each other). Additionally, each | |||
No more than two contributing seats may be held by employees of the same organization |
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.
Do we need to limit the selected seats too? Otherwise one company could in theory hold 4/7 seats (two contributing seats and the two selected seats)?
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.
Good question -- this would be done with the consent of the 2 other contributing seats and the end-user seat. I'm willing to add this restriction, but I'm also thinking of times that we've approved an exception to these rules for the TOC, so I'm wondering if we want to hem ourselves in.
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.
Maybe just an overall limit of < 50% seats per organization? (so 2 or 3 depending) I'd love for it to be lower, but also dealing with the current reality.
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 don't think we need these limits anymore and should drop them and reintroduce them later when we have more vendors actively participating in the project.
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.
@dprotaso The problem with removing the limits is that if a malicious vendor ended up with a majority of seats (which could happen if not enough other people run), then there would be no way to reintroduce the limits because the vendor could always vote against reintroducing them, since this is the decision-making body that would make that change.
The challenge with governance is that we need to anticipate the worst case scenarios and prevent them from happening.
Changes
This is based on #1549 (comment), but I've adjusted the Steering-appointed ("selected") seats to be optional and 1-year terms rather than 2-year terms with staggered appointment. I don't feel strongly about this, but it seemed to provide more flexibility.
Relates to #1549