I would use Discourse groups for that. Discourse groups work well for “first responders” type of features (via group email, e.g., the main @network group has it own email, as @contact). We should spawn categories only when necessary to work on transversal issues. As threads can be entirely recomposed (split, merge, move, rename), we can keep talking and take time to collectively think about categories later on.
Currently there are two groups:
- @contact is composed of the people present at the LibreHosters kickoff meeting. If you’re not there yet, PM me or another group owner. It responds collectively to
contact@libreho.st. - @network is about the same people, but is the larger group of librehosters. You belong if you’re using the Librehosters / librehost api and appear in the librehosters directory. Maybe it could be renamed
librehosters– I gatherednetwork@libreho.stwas easier on the eye and tongue thanlibrehosters@libreho.st…
Where is Gualter? We’d need some email aliases. 
I changed a couple of things from the list, notably renamed ‘Application’ to ‘Services’ since I understand it’s about the various applications provided by librehosters. I also added the existing two groups @contact and @network.
Here’s what it would look like as Discourse groups:
See Operations Work Groups Possible Structure - #8 by mattronix
Future
| @name | Name | Description | Lab | Members | |
|---|---|---|---|---|---|
| @dns | DNS WG | DNS Management Work Group | dns@libreho.st, hostmaster@libreho.st | librehosters/dns-wg | |
| @idp | Identity and Authentication WG | Keycloak / LDAP Management Work Group | idp@libreho.st | librehosters/idp-wg | @mattronix |
| @docker | Docker WG | Docker Management and Advisory WG | docker@libreho.st | librehosters/docker-wg | @pierreozoux |
| @security | Security WG | Security, Compliance and RIsk Management Work Group | security@libreho.st | librehosters/security-wg | |
| @operations | Operations WG | Administrators and First Responders | operations@libreho.st | librehosters/operations-wg | |
| @discourse | Discourse WG | Discourse Maintainers, Staff & Developers | discourse@libreho.st | librehosters/discourse-wg | @pierreozoux, @how |
As far as discussion is concerned we should keep using the Discourse. If we start spreading the discussion thin on the gitlab it will become a mess. We can use wiki posts here (this is one) and use the lab repo for issues and identified tasks.
The proposed labs endpoints all live as a repository under librehosters group to simplify following each WG activity. Each WG may develop further under their own group, e.g., librehosters-infra for internal infrastructure management. Having -wg projects in lab allows to manage issues and milestones transversally among work groups.