Publicly visible teams and tagging

[seanbudd]

Select Topic Area

Product Feedback

Body

Issue

Currently organization teams have two options:

• visible: visible to everyone in the organisation
• hidden: visible to only owners and members of the team

Community contributors to a repository are unable to see, tag, or request reviews from teams.
This makes it impossible for community contributors to know who is responsible for a repository, and who they can contact for support on an issue or pull request.
This creates a culture where:

• new contributors have no idea who to contact, often tagging active community members at random, sometimes those not associated with the organisation
• knowledgeable contributors have to choose an organisation member at random
• knowledgeable contributors mass tag all members of an organisation

This creates a less than ideal communication platform, where on large projects, almost always the wrong person is tagged in an issue or pull request. This often leads to questions unanswered, or playing "forward the tag", chaining tags until the right person is found.

Repositories can work around this by manually maintaining a document with a list of contactable experts, however this is still less than ideal, as groups of subject matter experts still either get mass tagged as a group, or picked out at random without good load balancing.

Solution

Create a third category of teams, fully public, where:

• the team is listed in a fully publicly accessible manner
• the team can be tagged by any member of the public
• load balancing algorithms similar to PR reviews are employed that notify the full team, or a member of the team

[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. ⭐