Add ability to see who voted in Polls

[Andersson007]

Hi there,

The Poll feature of GH Discussions looks very good, let's make it much better!

Currently we cannot use it in our Steering Committee workflow for voting because:

• to make decisions we count votes made by only certain people, i.e. members of the Steering Committee
• and the Polls feature does not allow us to see who voted, so we can't extract Steering Committee votes from all the votes (non Committee folks also vote, to get their opinion is very important too).

So i suggest adding an ability to make persons who voted in Polls visible. Maybe a special toggle at the Poll creation stage.

[bryevdv]

I'd just like to second this proposal. The Bokeh core team occasionally has to use a voting process to record formal decisions. Ideally this process is public and transparent, and participation needs to be limited to the core team. We have tried out a few different mechanism in the past

• Discourse private topic (not everyone likes having to go to another site, results not publicly viewable)
• Email ballots (like wrangling cats for the organizer, results not publicly viewable)
• Other proprietary tools/services (cost, hassle)

So when I saw that polls were now available for GitHub discussions I had hoped it might be a good solution. Having an easy way to vote in the place where everyone already is, would be great! Unfortunately after creating the poll, there seem to be two big problems:

• No way to limit who votes
• No way to see who voted

Taken together, these mean there is no way to ensure that only the votes of the core team are represented, which makes GitHub polls a non-starter for our use. Ideally, polls would have options to allow both of these things:

• Specify a group to limit responses to, e.g @bokeh/core
• View who has voted already

It would also be nice to have a way to "close" the poll at a specified time (this was also suggested in another issue)

Having these features would make it incredibly easy for OSS project maintainers to conduct formal decisions in a transparent way on GitHub.

[LeaVerou]

Another +1 for this. In the CSS Working Group we ended up using manual polls where people literally edit a comment and write their name in because we needed votes to be visible: w3c/csswg-drafts#9438

[slifty]

This would help! (though being able to limit to specific user types would be even better)

[Xelliese]

A toggle during Poll creation could make it happen smoothly.

[aikenka]

Another vote - used polls for the first time today and have been struggling to find out how to identify who voted for what. Assuming from this feature request that it's not yet available. We're using polls for ADRs, and would like to have a record of the virtual attendance.

[sanjay-kv]

I was about to raise the simillar issue, i thought github discussion already have this feature and rolled poll to my community.
End up realizing there was no way I could see a list of people who voted.
double work now.

[LiteBrite82]

💬 Your Product Feedback Has Been Submitted 🎉
Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐