One of a few posts to start discussing the “go-live” configuration. Obviously we can roll forward as our uses change.
Groups got some attention during our testing, and right so. They have a lot of flexibility - they can be public or hidden, open, request-to-join, or invite-only, can have an incoming email address associated with them, and can be used to @-notify from forum posts and private messages. They also allow for flair & badges so that people can see you’re in a group.
The aim is to create themed groups that people can self-select to join because they care about bugs/discussions/etc on that topic. So, what groups to create? We have 63 teams on GitHub, so mirroring that might be a bit much, but it’s a starting point. How about:
- CLI / Hammer
- One per plugin that has more than one member on GH
I’ll also add a “developers” group that can’t be @-notified (too many people, too spammy, I think), so that developers can be easily identified. Did I miss any?