Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a minimal guide for Group Contacts #384

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 3 additions & 17 deletions content/_guides/cloaks.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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 <channel>`.
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
Expand Down
73 changes: 73 additions & 0 deletions content/_guides/groups.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
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

<!-- markdownlint-disable MD044 -->

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 [[email protected]][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:[email protected]
Loading