I have already asked freenode admins about that, the main issue is that group registration requests are suspended and there is no timeline for when they will be reopened.

• https://freenode.net/group_registration.shtml
• https://blog.freenode.net/2012/06/group-registration-closure/

I have to say that i've asked if there is any chance to bypass the group registration form to have cloacking for devuan even if the group registration is suspended to Marco D'itri, that is well know to be very unfriendly with devuan and is a strong supporter of systemd, so, maybe if anyone can ask to another freenode admin the answer can be different?

ahahah, on top of that Macro D'Itri is one of the main maintainers of systemd in Debian :^) is he really the gatekeeper of freenode just like the old times on FIDONet? I guess moving on irc.dyne.org is not an option due to popularity of freenode. However we mask IPs if the privacy is the concern. So I'd say get used: when mainstream projects and reactionary gatekeepers are in control, they have no incentive in leaving space for new and smaller projects. Its the rule of the jungle, no matter how open they declare themselves...

Well, md is just one of the server admins in freenode, i hope others have no so strong opinions on systemd :)

Really is frustating that Franco says about that, just for a personal thing, disturb to other people. Where is the democracy?. @jaromil my suggestion is not for hide the IP, because I can use tor or my cloak is just for organization stuff.

Let me speak with others admins on freenode that I know that are neutrals.

Group registration has been suspended for a few months pending a migration to a new system, AFAIK.

As for what i know, this isn't true: it's more "few years" than few months, and there are no ETA for reopen group registration

Just talked to some IRCop today: they're already testing the group management on their internal test network. ETA still blurry but I enrolled to beta-test their new system as soon as it's ready for consumption. Apparently we have supporters in the Freenode staff. I'll send a proposal for cloaks to this issue when I have time to think about it and it is more pressing.

Milestone changed to Jessie 1.0 Beta

Added in progress label

Reassigned to @hellekin

Assignee removed

Preparing the message to send to Freenode Group staff:

• add emailfreenode-contact@devuan.org -> hellekin@dyne.org,onelove@devuan.org
• approve message

Message draft:

Hello,

some time ago tinyhippo helped me solve an issue with #hackerspaces and proposed me to join the beta for GMS, as I'm taking care of two projects willing to establish group presence on Freenode:

- hackerspaces.org (#hackerspaces)
- devuan.org (#devuan)

This is the registration information for Devuan. Once this is done, I can send another one for #hackerspaces, which is a bit more complicated (we have pre-existing channels outside the namespace, etc.).

*

GMS - Group Registration for Devuan

Project: Devuan Project
Homepage: https://devuan.org/ (you can preview the site at https://beta.devuan.org/)
Description: Devuan is a fork of Debian Jessie, without systemd.  It aims at continuity with Debian Wheezy for people who don't want or can't install systemd on their systems.

Devuan is an informal network of volunteers, with a fiscal sponsor to handle financial and administrative aspects of the project.  Our fiscal sponsor is the Dyne.org Foundation, a non-profit based in Amsterdam, The Netherlands, whose mission is to promote free software and free culture.  The legal representative of Dyne.org is Denis "jaromil" Roio (Freenode account: jaromil).

Contact: hellekin
Contact Email: freenode-contact@devuan.org
Namespace: devuan
Channels:
 - #devuan: main project discussion channel
 - #devuan-art: discussing Devuan branding and visual identity
 - #devuan-dev: developer channel (spits CI build information)
 - #devuan-news: newsletter working group
 - #devuan-security: discussing OS security
 - #devuan-www: Web presence working group

This is the current list of channels.  FYI, a pre-#devuan channel exists, #debianfork, whose crowd overlaps mostly with #devuan, but that is not part of this registration.

Cloaks:

We didn't define cloaks yet.  That can be done later.  Probably something like devuan/<team>/<role> and devuan/supporter/<gitlab username>.

- devuan/bot for #devuan-dev's [0__0] that informs about CI builds

Please let me know if you need any more information.

Regards,

==
hk

-- 
-------------------[  software freedom, your way  ]---------------------
Devuan GNU/Linux OS   Source Code / Issues      Devuan Discourse (Forum)
https://devuan.org/   https://git.devuan.org/   https://talk.devuan.org/

Added awaiting feedback label

this is great. the original irc-ops group is a bit scattered, still available, but not always present. If we take back control on all those channels we can import and still include all old irc-ops and will be easy to open to new ones. please proceed!!

Removed awaiting feedback label

Mail sent! I'm closing the issue until we get a response.

Status changed to closed

Reassigned to @hellekin

Status changed to reopened

tinyhippodid the paperwork: we now have a devuan group on Freenode \\o/

It means we control the #devuan namespace for official devuan channels, and can have devuan cloaks.

Currently many things are still manual. The Freenode Group Management System (GMS) code is at https://github.com/freenode/gms

Updated goal: determine cloaks

I'm reading the GMS material to determine how multiple cloaks work (across groups and within a group). Maybe we can have more than one cloak per user account, which would mean we can use them as roles (e.g., devuan/release-manager) or badges (in the same sense as Discourse badges, e.g., devuan/jessie for people involved in the first release, etc.)

As a general starting point I would suggest:

• devuan/bot
• devuan/maintainer[/package]
  • [package] may be very useful but require multiple cloaks per account in a single group
• devuan/team[/group]
  • devuan/team/editors
  • devuan/team/project
  • devuan/team/security
  • again [team] may require multiple cloaks.

The minimal first batch would be:

• devuan/bot
• devuan/maintainer
• devuan/team

Milestone changed to 1.0.0-beta2

i'm for the minimal version

OK people, we can go for it now...

Claim your cloaks :)