Add GC guide

chanreg.md

@@ -118,8 +118,8 @@ registration is appropriate for your project or community.
 ### Benefits of group registration
 
 On-topic projects and communities who have formally registered with
-Libera.Chat have extra tools at their disposal to help manage their
-IRC presence:
+Libera.Chat [have extra tools](/guides/groupcontacts) at their disposal to 
+help manage their IRC presence:
 
 - Your liaisons with us, known as group contacts, will be invited to
   `#libera-communities` where they can more easily reach Libera.Chat staff and
@@ -156,9 +156,10 @@ IRC presence:
 Group contacts are the people ultimately responsible for your project here on
 Libera.Chat. They are empowered to claim channels within your namespace,
 assign cloaks to other users, and act as liaisons between Libera.Chat staff
-and your project. We **strongly recommend** having between 2-4 group contacts
-and that at least one group contact is publicly listed to act as a point of
-contact for any users interested in your project.
+and your project. They also [get access to some extra tools](/guides/groupcontacts)
+for managing these responsibilities. We **strongly recommend** having between
+2-4 group contacts and that at least one group contact is publicly listed to
+act as a point of contact for any users interested in your project.
 
 Group contacts must have registered accounts with NickServ on Libera.Chat.
 Usually, you will want to establish yourself as one of the group contacts if

content/_guides/cloaks.md

@@ -72,8 +72,10 @@ If your project or community has had an official group registration approved,
 then you are probably able to request cloaks for your users and contributors.
 Registered projects are represented by Group Contacts (also known as GCs).
 Only these people have the right to request cloaks for group members.
-If you are a GC, then you will have a standing invite to `#libera-communities`
-where you may request cloaks for projects that you are a registered GC for.
+
+Instructions for managing group cloaks can be found in the
+[GC Guide](/guides/groupcontacts#managing-group-cloaks), along with other
+useful tools.
 
 While it is not mandatory, we do recommend having some internal standards for
 your users to meet to be eligible for your project's cloaks. Bearers of your

content/_guides/creatingchannels.md

@@ -118,43 +118,12 @@ Once you have resolved the conflict, you can resume
 
 ### Special Instructions for Group Contacts
 
-Libera.Chat uses an Atheme feature called `ProjectServ` to track group
-registrations. It shows some additional information in `NickServ` and allows
-for convenient features such as `CLAIM` in `ChanServ`.
+Libera.Chat uses Atheme's `ProjectServ`, which provides Group Contacts with
+some [additional tools for managing group namespaces](/guides/groupcontacts).
 
-If you already have a group registration set up with us, and you are listed as
-a Group Contact (GC) for the namespace you have chosen, it will be displayed
-to you in your `NickServ` info. Look for a line like:
-
-```irc
-NickServ: Group contact for projectname (#projectname; projectname/*)
-```
-
-`CLAIM` will allow you to acquire a channel _within your namespace_ even if
-that channel is already registered to someone else, without the need for staff
-intervention. It can also be used for initial registration even if it is not
-already taken.
-
-```irc
-09:23 -- ChanServ: ***** ChanServ Help *****
-09:23 -- ChanServ:  
-09:23 -- ChanServ: Help for CLAIM:
-09:23 -- ChanServ:  
-09:23 -- ChanServ: The CLAIM command allows you to take control of a channel
-09:23 -- ChanServ: belonging to a project you are authorized to represent.
-09:23 -- ChanServ:  
-09:23 -- ChanServ: Syntax: CLAIM <#channel>                            
-09:23 -- ChanServ:  
-09:23 -- ChanServ: Examples:
-09:23 -- ChanServ:     /msg ChanServ CLAIM #coolproject-dev            
-09:23 -- ChanServ:  
-09:23 -- ChanServ: ***** End of Help *****
-```
-
-Using `CLAIM` to grab a channel from someone else might be seen as hostile, or
-it could confuse people, so it is a good idea to at least give some warning.
-Try to ask for the cooperation of people who have already occupied or
-registered a channel before taking it from them.
+This includes a new command in `ChanServ` to `CLAIM` a channel that already
+exists within a registered namespace. This will add you as a new founder of an
+existing channel, or register the channel if it didn't exist.
 
 ## Setting channel modes
 

content/_guides/groupcontacts.md

@@ -0,0 +1,134 @@
+---
+title: Managing Groups
+category: chanop 
+weight: 45
+---
+
+Groups are projects and communities that have done the
+[group registration process](/chanreg).
+
+Libera.Chat uses an Atheme feature called `ProjectServ` to track group
+registrations. It shows some additional information and provides convenient
+features in `NickServ` and `ChanServ`.
+
+Please note that this process is completely separate from
+[channel registration](/guides/creatingchannels). You do _not_ need a group
+registration to create channels. The features in this guide are only available
+for channels that are managed by a registered group.
+
+## Check if a channel is managed by a group
+
+You can tell if a channel is part of a namespace by looking at the `INFO`
+output from `ChanServ`.
+
+For example, `/msg ChanServ INFO #libera` shows:
+
+```irc
+ChanServ: The #libera namespace is registered to the libera.chat project
+```
+
+## Check if you are a Group Contact
+
+If you already have a group registration set up with us, and you are listed as
+a Group Contact (GC) for the namespace you have chosen, it will be displayed
+to you if you do `/msg NickServ INFO`. Look for a line like:
+
+```irc
+NickServ: Group contact for projectname (#projectname; projectname/*)
+```
+
+## Check what channels the group manages
+
+GCs can audit the channels registered within their namespace with `ChanServ`.
+The `LISTGROUPCHANS` command will output a list of every channel registered in
+their namespace.
+
+```irc
+-- ChanServ: ***** ChanServ Help *****
+-- ChanServ:
+-- ChanServ: Help for LISTGROUPCHANS:
+-- ChanServ:
+-- ChanServ: The LISTGROUPCHANS command shows registered channels which belong
+-- ChanServ: to a namespace that you are a group contact for. If a filter is given,
+-- ChanServ: only shows the channels which match the filter. Otherwise, all channels
+-- ChanServ: in your namespaces are reported.
+-- ChanServ:
+-- ChanServ: Syntax: LISTGROUPCHANS [filter]
+-- ChanServ:
+-- ChanServ: Examples:
+-- ChanServ:     /msg ChanServ LISTGROUPCHANS
+-- ChanServ:     /msg ChanServ LISTGROUPCHANS #coolproject-*
+-- ChanServ:
+-- ChanServ: ***** End of Help *****
+```
+
+`CLAIM` can be used for any channels that should not be there.
+
+## Managing group cloaks
+
+`NickServ` can be queried by GCs for a list of every cloak that has been
+assigned for their project or community through the `LISTGROUPCLOAKS` command.
+
+```irc
+-- NickServ: ***** NickServ Help *****
+-- NickServ:
+-- NickServ: Help for LISTGROUPCLOAKS:
+-- NickServ:
+-- NickServ: The LISTGROUPCLOAKS command shows accounts who are assigned a cloak belonging
+-- NickServ: to one of the cloak namespaces you are a group contact for.
+-- NickServ: If a filter is given, only shows accounts which match the filter.
+-- NickServ: Otherwise, all accounts with cloaks in your namespaces are reported.
+-- NickServ:
+-- NickServ: Syntax: LISTGROUPCLOAKS [filter]
+-- NickServ:
+-- NickServ: Examples:
+-- NickServ:     /msg NickServ LISTGROUPCLOAKS
+-- NickServ:     /msg NickServ LISTGROUPCLOAKS coolproject/*
+-- NickServ:
+-- NickServ: ***** End of Help *****
+```
+
+GCs have a standing invitation to the `#libera-communities` channel where they
+may request cloak changes for projects that they are a registered GC for.
+
+## Claiming channels for a group
+
+`CLAIM` allows you to acquire a channel _within your namespace_ even if
+that channel is already registered to someone else, without the need for staff
+intervention. It can also be used for initial registration even if it is not
+already taken.
+
+```irc
+-- ChanServ: ***** ChanServ Help *****
+-- ChanServ:  
+-- ChanServ: Help for CLAIM:
+-- ChanServ:  
+-- ChanServ: The CLAIM command allows you to take control of a channel
+-- ChanServ: belonging to a project you are authorized to represent.
+-- ChanServ:  
+-- ChanServ: Syntax: CLAIM <#channel>                            
+-- ChanServ:  
+-- ChanServ: Examples:
+-- ChanServ:     /msg ChanServ CLAIM #coolproject-dev            
+-- ChanServ:  
+-- ChanServ: ***** End of Help *****
+```
+
+Using `CLAIM` to grab a channel from someone else might be seen as hostile, or
+it could confuse people, so it is a good idea to at least give some warning.
+Try to ask for the cooperation of people who have already occupied or
+registered a channel before taking it from them.
+
+## Other changes
+
+Libera.Chat requires that GC and namespace changes be requested through email
+tickets so that there is a paper trail of the change requests. Primary GCs can
+request changes through a ticket sent to <projects@libera.chat>
+
+If a namespace has been abandoned and there is no GC available to make this
+request, transfer of the namespace may be requested through the
+[group registration process](/chanreg).
+
+If you have other questions about changes or processes for your groups, all 
+GCs have access to #libera-communities to get support from fellow GCs and
+network staff.