-
Notifications
You must be signed in to change notification settings - Fork 95
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
[SC Vote Required] Expansion of GH wishlist channel scope #313
Conversation
Create new resolution in proposals related to the expansion of GitHub wishlist channel scope and change of name for SC to cast their vote Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
abstain |
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
This would be pointless. It's not a channel for "I wish that this service, or some service, offered something", it's a channel that GitHub were listening to. If GitLab wanted a channel, that could be setup, and the same for any other service. |
/vote |
Vote created@justaugustus has called for a vote on The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for |
To @hyandell's point and to explain my That said, a few questions we should try to answer as follow-ups:
|
I would appreciate to have a copy of the conversation which is referenced in the resolution either in this issue or in the resolution itself for context. Currently, I feel don't have enough context - also based on the fact that I was not a member of this channel up until now.
I agree with this. |
I agree with Stephen's comment - expanding the channel purpose diminishes value. As far as (Q2) I want to ensure that this does not signify an open invitation for all vendors to seek channels. GitHub holds a prominent position in open source and is a key platform for community participation. GitLab as well. Where do we draw the line for vendors? |
Vote statusSo far Summary
Binding votes (4)
|
Vote statusSo far Summary
Binding votes (4)
|
abstain and agree with Stephen's comment. |
There is already a vote in progress in this pull request @anajsana. Please wait until it is closed before creating a new one. |
/check-vote |
Vote statusSo far Summary
Binding votes (5)
|
Since 4 votes in favor are needed to pass the threshold (51%) and there are only 2 people who haven’t voted, it is impossible to reach the threshold of 4 votes in favor with only 2 remaining votes. This resolution will be declined and GH wishlist will keep as it is |
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.
Approving the update to the content (to reflect Steering's vote to decline) and canceling the vote.
/cancel-vote
I am sorry I missed this vote and will be more diligent to keep up on requests in the future. |
Vote statusSo far Summary
Binding votes (5)
|
Vote closedThe vote did not pass.
Summary
Binding votes (5)
|
Create new resolution in proposals folder related to the expansion of GitHub wishlist channel scope and change of name for SC to cast their vote
Instructions:
Steering Committee Members should cast their vote by making edits on the line where their name appears. If needed, members can leave comments regarding their final vote in the Rationale section by adding their initials. As an alternative, members can leave a comment with their vote on this PR conversation page, and @anajsana will update the document accordingly.