-
Notifications
You must be signed in to change notification settings - Fork 9
community_topics_workflow.md: change to conduct them on Forum #277
community_topics_workflow.md: change to conduct them on Forum #277
Conversation
community_topics_workflow.md
Outdated
- [ ] Submit the poll (the BBcode will appear in the post) and then repeat the above for the second poll. | ||
- [ ] Title should be "Community vote". | ||
- [ ] No group limitation. | ||
- [ ] Results "Staff only" (i.e. an anonymous vote, but admins can check if there are concerns). |
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.
Should we keep all votes public like they were before we adopted the forum?
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.
@gotmax23 i'm not sure i understand though I'm for keeping them as they were. Please suggest the wording change
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.
Sorry, I was missing a word. I meant keep all votes public instead of making community votes anonymous.
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.
@gotmax23 ah, yeah, i would prefer to see them public too.
@GregSutcliffe do the formulations above imply community votes to be private? Is there any rationale for that and can we just remove the point containing "Staff only"?
Thanks, @Andersson007 and @GregSutcliffe, for picking this up! |
My rationale is that we may get more people to vote that way - some people prefer a veil of privacy. If there's any concern over sockpuppeting or flooding, the admins can still check who voted. I'm not against making it public if you prefer though, it's your process ;) |
@GregSutcliffe ok, thanks for explaining, makes sense but let's remove it for now and get back to it later if needed:) |
Thanks @Andersson007! I'll take a closer look later today. In the meantime, it looks like there are some leftover references to the project board at the end of the doc that should be removed. |
@gotmax23 removed, thanks, PTAL |
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.
LGTM, but we need a vote before merging this.
@gotmax23 cool, thanks for reviewing! @felixfontein would you like to take a look too and if it's OK open a vote in #273 on merging this PR and going with the process you explained in your last comment there? |
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.
Besides that, LGTM.
Co-authored-by: Maxwell G <maxwell@gtmx.me>
…community-wg-nextmtg Co-authored-by: Maxwell G <maxwell@gtmx.me>
Updated the PR according to #273 (comment). |
To implement https://forum.ansible.com/t/draft-for-sc-voting-process-on-the-forum/1410
Removed all board mentions as it doesn't work:)
Closes: #273