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

[OSPO Associate] Request - CURIOSS #370

Open
anajsana opened this issue Jan 15, 2025 · 7 comments
Open

[OSPO Associate] Request - CURIOSS #370

anajsana opened this issue Jan 15, 2025 · 7 comments

Comments

@anajsana
Copy link
Member

The issue was submitted to the OSPO landscape by CURIOSS to become OSPO Associates. check the information here: todogroup/ospolandscape#226

@anajsana
Copy link
Member Author

/vote

Copy link

git-vote bot commented Jan 15, 2025

Vote created

@anajsana has called for a vote on [OSPO Associate] Request - CURIOSS (#370).

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.

@claredillon
Copy link

Thanks so much @anajsana - just for my context, is the expectation in this process that all steering group members generally vote either way - or is there a risk not enough of the potential voting panel engage to have a valid output?

@anajsana
Copy link
Member Author

Thanks so much @anajsana - just for my context, is the expectation in this process that all steering group members generally vote either way - or is there a risk not enough of the potential voting panel engage to have a valid output?

The vote will pass if at least 51% of the users with binding votes vote In favor. If the deadline of teh 28 days to vote expires and the poll doesn't reach the minimum votes. We can restart the poll to ensure all SC members vote in time.

However, SC members are already being notified and I have set up reminders weekly in the SC TODO slack channel to make sure they cast their votes on time 🙂

Copy link

git-vote bot commented Jan 22, 2025

Vote status

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

Summary

In favor Against Abstain Not voted
1 0 0 6

Binding votes (1)

User Vote Timestamp
gkunz In favor 2025-01-15 14:02:38.0 +00:00:00
@justaugustus Pending
@lhawthorn Pending
@annania Pending
@ashleywolf Pending
@BrittanyIstenes Pending
@nikpete Pending

Non-binding votes (1)

User Vote Timestamp
natalisucks In favor 2025-01-22 3:27:34.0 +00:00:00

@anajsana
Copy link
Member Author

/check-vote

Copy link

git-vote bot commented Jan 23, 2025

Vote status

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

Summary

In favor Against Abstain Not voted
2 0 0 5

Binding votes (2)

User Vote Timestamp
gkunz In favor 2025-01-15 14:02:38.0 +00:00:00
natalisucks In favor 2025-01-22 3:27:34.0 +00:00:00
@justaugustus Pending
@annania Pending
@ashleywolf Pending
@BrittanyIstenes Pending
@nikpete Pending

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

No branches or pull requests

9 participants