-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Proposal for Admin Rights for CoC Main Committee on Slack #1227
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
/vote |
Vote created@Mayaleeeee 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 |
Hi @Mayaleeeee, since you are not a TSC Member, you cannot start or stop voting. Please read more about voting process |
/check-vote |
Vote statusSo far Summary
Binding votes (1)
|
/check-vote |
Votes can only be checked once a day. |
/check-vote |
Vote statusSo far Summary
Binding votes (12)
|
User | Vote | Timestamp |
---|---|---|
iambami | In favor | 2024-05-29 8:33:34.0 +00:00:00 |
/check-vote |
Vote statusSo far Summary
Binding votes (12)
|
User | Vote | Timestamp |
---|---|---|
iambami | In favor | 2024-05-29 8:33:34.0 +00:00:00 |
Vote statusSo far Summary
Binding votes (18)
|
User | Vote | Timestamp |
---|---|---|
iambami | In favor | 2024-05-29 8:33:34.0 +00:00:00 |
/check-vote |
Vote statusSo far Summary
Binding votes (19)
|
User | Vote | Timestamp |
---|---|---|
iambami | In favor | 2024-05-29 8:33:34.0 +00:00:00 |
/check-vote |
Votes can only be checked once a day. |
Vote closedThe vote passed! 🎉
Summary
Binding votes (28)
|
User | Vote | Timestamp |
---|---|---|
@iambami | In favor | 2024-05-29 8:33:34.0 +00:00:00 |
@Mayaleeeee the vote passed. Please reach out to @thulieblack to cleanup the admin rights in Slack. Except of Thulie and me, and code of conduct committee nobody else should be admin I guess |
@aayushmau5 did we have a solution to add |
/check-vote |
To make other voter's lives easier, clicking this link will take you back to the relevant comment in this PR ...where they need TSC members to vote by selecting the emoji that represents their vote |
Didn't this vote end? 😕 |
Admin rights granted to the full-time members @smoya, @Mayaleeeee, and @AceTheCreator. Use them wisely 😉😉 |
I guess this issue can be closed now, right? |
yes |
As our community grows, we must uphold our Code of Conduct (CoC) to maintain a safe, respectful, and inclusive environment. To achieve this, we propose granting admin rights on our Slack workspace to the main members of the CoC committee.
Why We Need Admin Rights:
Maintaining a Safe Environment: Admin rights will enable us to issue warnings and temporarily or permanently ban users who violate the Code of Conduct, ensuring that our community remains a welcoming space for everyone.
Removing Inappropriate Content: We need the ability to promptly remove inappropriate or harmful content to prevent disruption and protect our members.
Managing Discussions: Admin rights will help us manage and moderate discussions effectively, ensuring adherence to community guidelines.
How We Intend to Use Admin Rights:
Issuing Warnings: We will issue warnings to users who violate the Code of Conduct as an initial step to address inappropriate behaviour.
Temporary Bans: When necessary, we will issue temporary bans to users who continue to violate the Code of Conduct, allowing time for reflection.
Permanent Bans: To protect the community, we will issue permanent bans in severe cases or for repeated violations.
Granting admin rights to the CoC committee is not intended to threaten or intimidate anyone. Our primary goal is maintaining a positive and inclusive environment for all community members. These rights will be exercised with care, transparency, and accountability. For guidelines on incident resolution, please refer to our Incident Resolution Procedures.
Please join the conversation. We'd love your thoughts!
@asyncapi/tsc_members Your input is important to us — please share your thoughts and vote!
cc @smoya @AceTheCreator @alequetzalli @thulieblack
The text was updated successfully, but these errors were encountered: