From e8c9f20ed378b71d67509ca219843629038fa333 Mon Sep 17 00:00:00 2001 From: Valentin Lorentz Date: Fri, 13 Dec 2024 22:09:15 +0100 Subject: [PATCH 1/2] Add a minimal guide for Group Contacts Based on: * https://libera.chat/guides/cloaks * https://libera.chat/news/new-and-upcoming-features-2#new-commands-for-group-contacts --- content/_guides/cloaks.md | 20 ++--------- content/_guides/groups.md | 71 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 74 insertions(+), 17 deletions(-) create mode 100644 content/_guides/groups.md diff --git a/content/_guides/cloaks.md b/content/_guides/cloaks.md index b958e67..cb38cb7 100644 --- a/content/_guides/cloaks.md +++ b/content/_guides/cloaks.md @@ -54,8 +54,9 @@ and help others to find you if something goes wrong with the bot. ## Project or community cloaks [Projects and communities](/chanreg#what-is-on-topic) that are -aligned with our mission are eligible for group registrations. One of the -perks of group registration is the ability to request cloaks for participants. +aligned with our mission are eligible for [group registrations](/guides/groups). +One of the perks of group registration is the ability to request cloaks for +participants. ### Getting project or community cloaks @@ -66,21 +67,6 @@ your project or community. If your project has listed group contacts publicly, they will be listed as "Public contacts" in `/msg ChanServ INFO `. If not, ask for help in the relevant channel. -### Instructions for Group Contacts - -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. - -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 -cloaks are seen by others as representatives of your community and as such -the bearer's behaviour will reflect onto the reputation of -your project or community. - ## Re-identifying with NickServ Assigned cloaks must be associated with an account and will not appear if you diff --git a/content/_guides/groups.md b/content/_guides/groups.md new file mode 100644 index 0000000..46db679 --- /dev/null +++ b/content/_guides/groups.md @@ -0,0 +1,71 @@ +--- +title: Groups +category: chanop +weight: 70 +--- + +[Projects and communities](/chanreg#what-is-on-topic) that are aligned +with our mission are eligible for group registration, which gives them extra +management tools and improves communication between their community and Libera.Chat +staff. + +# Requesting a group registration + +Communities wishing to register a group should choose a primary contact, +which is the person in charge of being the interface between their community +and Libera.Chat staff, and secondary contact who will fill the role in their +absence. Primary and secondary contacts are also known as Group Contacts. + +Then, the primary contact should email [support@libera.chat][support], +mentioning: + +* their account name and the secondary contacts' +* which contacts want to be public +* their channel namespace (eg. `#libera` for the Libera project, which contains + `#libera` itself, in addition to `#libera-dev`, `#libera-communities`, etc.), and +* optionally a cloak namespace (eg `libera/` for the Libera project). + +When accepted, this will grant permission to use the tools listed below, +and the primary and secondary contacts will be invited to the +`#libera-communities` channel. +It will also prevent unaffiliated users from registering channels in +the namespace. + +# Listing Group contacts + +After a group is registered, when Group Contacts of a namespace use +`/msg ChanServ INFO` for a channel registered in their namespace, they will +see a full list of both public and unlisted/private Group Contacts assigned +to their project. +Others will still only see public contacts when they use ChanServ INFO + +# Claiming a channel + +Group Contacts can use the `/msg ChanServ LISTGROUPCHANS` command to list every +registered channel in their namespace, even if they were registered other users +prior to the group registration. + +They can also use the `/msg ChanServ CLAIM #channel` command to add themselves +as founder to the given `#channel`. In particular, this allows them to take over +existing channels registered prior to the group registration. + +# Project Cloaks + +If your project or community has had an official group registration approved, +then you are probably able to request [cloaks](/guides/cloaks) for your users +and contributors. +Group Contacts have the right to request cloaks for group members, +by asking on the `#libera-communities` channel, for which they have a standing +invite. + +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 +cloaks are seen by others as representatives of your community and as such +the bearer's behaviour will reflect onto the reputation of +your project or community. + +The `/msg NickServ LISTGROUPCLOAKS` command lets Group Contacts list all users +with cloaks belonging to their projects. + +[support]: mailto:support@libera.chat + From c5da02afd0b58e1f8acf7ed10a066db99d1c996b Mon Sep 17 00:00:00 2001 From: Valentin Lorentz Date: Sat, 14 Dec 2024 00:42:03 +0100 Subject: [PATCH 2/2] Fix lint --- content/_guides/groups.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/content/_guides/groups.md b/content/_guides/groups.md index 46db679..df5cd91 100644 --- a/content/_guides/groups.md +++ b/content/_guides/groups.md @@ -9,7 +9,9 @@ with our mission are eligible for group registration, which gives them extra management tools and improves communication between their community and Libera.Chat staff. -# Requesting a group registration +## Requesting a group registration + + Communities wishing to register a group should choose a primary contact, which is the person in charge of being the interface between their community @@ -19,11 +21,12 @@ absence. Primary and secondary contacts are also known as Group Contacts. Then, the primary contact should email [support@libera.chat][support], mentioning: -* their account name and the secondary contacts' -* which contacts want to be public -* their channel namespace (eg. `#libera` for the Libera project, which contains - `#libera` itself, in addition to `#libera-dev`, `#libera-communities`, etc.), and -* optionally a cloak namespace (eg `libera/` for the Libera project). +- their account name and the secondary contacts' +- which contacts want to be public +- their channel namespace (eg. `#libera` for the Libera project, which contains + `#libera` itself, in addition to `#libera-dev`, `#libera-communities`, etc.), + and +- optionally a cloak namespace (eg `libera/` for the Libera project). When accepted, this will grant permission to use the tools listed below, and the primary and secondary contacts will be invited to the @@ -31,7 +34,7 @@ and the primary and secondary contacts will be invited to the It will also prevent unaffiliated users from registering channels in the namespace. -# Listing Group contacts +## Listing Group contacts After a group is registered, when Group Contacts of a namespace use `/msg ChanServ INFO` for a channel registered in their namespace, they will @@ -39,9 +42,9 @@ see a full list of both public and unlisted/private Group Contacts assigned to their project. Others will still only see public contacts when they use ChanServ INFO -# Claiming a channel +## Claiming a channel -Group Contacts can use the `/msg ChanServ LISTGROUPCHANS` command to list every +Group Contacts can use the `/msg ChanServ LISTGROUPCHANS` command to list every registered channel in their namespace, even if they were registered other users prior to the group registration. @@ -49,7 +52,7 @@ They can also use the `/msg ChanServ CLAIM #channel` command to add themselves as founder to the given `#channel`. In particular, this allows them to take over existing channels registered prior to the group registration. -# Project Cloaks +## Project Cloaks If your project or community has had an official group registration approved, then you are probably able to request [cloaks](/guides/cloaks) for your users @@ -68,4 +71,3 @@ The `/msg NickServ LISTGROUPCLOAKS` command lets Group Contacts list all users with cloaks belonging to their projects. [support]: mailto:support@libera.chat -