Skip to content
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

Merged
merged 5 commits into from
Jun 4, 2024

Conversation

anajsana
Copy link
Member

@anajsana anajsana commented Feb 20, 2024

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.

- Annania Melaku - decline
- Ashley Wolf - abstain
- Brittany Istenes - absent
- Georg Kunz - abstain
- Leslie Hawthorn - absent
- Nik Peters - abstain
- Stephen Augustus - decline

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]>
@anajsana anajsana requested a review from a team as a code owner February 20, 2024 09:11
@anajsana anajsana requested review from annania, gkunz and BrittanyIstenes and removed request for a team February 20, 2024 09:11
@anajsana anajsana added Logistics / Documentation Resolutions Actions to be considered by the Steering Committee and removed Logistics / Documentation labels Feb 20, 2024
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
@ashleywolf
Copy link
Member

abstain

Signed-off-by: Ana Jimenez Santamaria <[email protected]>
@hyandell
Copy link
Member

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.

@justaugustus
Copy link
Member

/vote

Copy link

git-vote bot commented May 19, 2024

Vote created

@justaugustus has called for a vote on [SC Vote Required] Expansion of GH wishlist channel scope (#313).

The members of the following teams have binding votes:

Team
@todogroup/gitvote-steering

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor Against Abstain
👍 👎 👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 28days. It will pass if at least 51% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.

@justaugustus
Copy link
Member

To @hyandell's point and to explain my against vote, I believe that the channel exists to provide a focused forum for GitHub employees to be able to review. The value is diminished when you generalize the channel purpose.

That said, a few questions we should try to answer as follow-ups:

  1. Is this providing value to the Hubbers that have access to the channel?
  2. What is the scope of vendors allowed to ask for this type of forum within the TODO Group?

@gkunz
Copy link
Contributor

gkunz commented May 21, 2024

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.

That said, a few questions we should try to answer as follow-ups:
1. Is this providing value to the Hubbers that have access to the channel?
2. What is the scope of vendors allowed to ask for this type of forum within the TODO Group?

I agree with this.

@annania
Copy link
Member

annania commented May 21, 2024

To @hyandell's point and to explain my against vote, I believe that the channel exists to provide a focused forum for GitHub employees to be able to review. The value is diminished when you generalize the channel purpose.

That said, a few questions we should try to answer as follow-ups:

  1. Is this providing value to the Hubbers that have access to the channel?
  2. What is the scope of vendors allowed to ask for this type of forum within the TODO Group?

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?

Copy link

git-vote bot commented May 26, 2024

Vote status

So far 0.00% of the users with binding vote are in favor (passing threshold: 51%).

Summary

In favor Against Abstain Not voted
0 2 2 3

Binding votes (4)

User Vote Timestamp
annania Against 2024-05-21 15:07:33.0 +00:00:00
gkunz Abstain 2024-05-21 14:37:49.0 +00:00:00
ashleywolf Abstain 2024-05-20 16:47:53.0 +00:00:00
justaugustus Against 2024-05-19 5:05:19.0 +00:00:00
@lhawthorn Pending
@BrittanyIstenes Pending
@nikpete Pending

Copy link

git-vote bot commented Jun 2, 2024

Vote status

So far 0.00% of the users with binding vote are in favor (passing threshold: 51%).

Summary

In favor Against Abstain Not voted
0 2 2 3

Binding votes (4)

User Vote Timestamp
ashleywolf Abstain 2024-05-20 16:47:53.0 +00:00:00
annania Against 2024-05-21 15:07:33.0 +00:00:00
justaugustus Against 2024-05-19 5:05:19.0 +00:00:00
gkunz Abstain 2024-05-21 14:37:49.0 +00:00:00
@lhawthorn Pending
@BrittanyIstenes Pending
@nikpete Pending

@nikpete
Copy link

nikpete commented Jun 4, 2024

abstain and agree with Stephen's comment.

Copy link

git-vote bot commented Jun 4, 2024

There is already a vote in progress in this pull request @anajsana.

Please wait until it is closed before creating a new one.

@anajsana
Copy link
Member Author

anajsana commented Jun 4, 2024

/check-vote

Copy link

git-vote bot commented Jun 4, 2024

Vote status

So far 0.00% of the users with binding vote are in favor (passing threshold: 51%).

Summary

In favor Against Abstain Not voted
0 2 3 2

Binding votes (5)

User Vote Timestamp
justaugustus Against 2024-05-19 5:05:19.0 +00:00:00
gkunz Abstain 2024-05-21 14:37:49.0 +00:00:00
annania Against 2024-05-21 15:07:33.0 +00:00:00
ashleywolf Abstain 2024-05-20 16:47:53.0 +00:00:00
nikpete Abstain 2024-06-04 9:27:18.0 +00:00:00
@lhawthorn Pending
@BrittanyIstenes Pending

@anajsana
Copy link
Member Author

anajsana commented Jun 4, 2024

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

@anajsana anajsana merged commit 5a08b10 into main Jun 4, 2024
Copy link
Member

@justaugustus justaugustus left a 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

@lhawthorn
Copy link

I am sorry I missed this vote and will be more diligent to keep up on requests in the future.

Copy link

git-vote bot commented Jun 11, 2024

Vote status

So far 0.00% of the users with binding vote are in favor (passing threshold: 51%).

Summary

In favor Against Abstain Not voted
0 2 3 2

Binding votes (5)

User Vote Timestamp
justaugustus Against 2024-05-19 5:05:19.0 +00:00:00
nikpete Abstain 2024-06-04 9:27:18.0 +00:00:00
ashleywolf Abstain 2024-05-20 16:47:53.0 +00:00:00
gkunz Abstain 2024-05-21 14:37:49.0 +00:00:00
annania Against 2024-05-21 15:07:33.0 +00:00:00
@lhawthorn Pending
@BrittanyIstenes Pending

Copy link

git-vote bot commented Jun 16, 2024

Vote closed

The vote did not pass.

0.00% of the users with binding vote were in favor (passing threshold: 51%).

Summary

In favor Against Abstain Not voted
0 2 3 2

Binding votes (5)

User Vote Timestamp
@nikpete Abstain 2024-06-04 9:27:18.0 +00:00:00
@annania Against 2024-05-21 15:07:33.0 +00:00:00
@gkunz Abstain 2024-05-21 14:37:49.0 +00:00:00
@ashleywolf Abstain 2024-05-20 16:47:53.0 +00:00:00
@justaugustus Against 2024-05-19 5:05:19.0 +00:00:00

@git-vote git-vote bot removed the vote open label Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gitvote Resolutions Actions to be considered by the Steering Committee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants