Opened at 2021-05-31T12:35:06Z
Last modified at 2021-08-03T15:21:54Z
#3726 new defect
Register Tahoe-LAFS project with Libera.Chat
Reported by: | sajith | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | unknown | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description (last modified by sajith)
See #3721 for background.
We have registered #tahoe-lafs IRC channel with irc.libera.chat's ChanServ. We probably should also register Tahoe-LAFS project with Libera.Chat. See their docs on project registration for details. Basically: "project registration allows your project or organisation to have an official representation on our services and relationship with us."
Advantages of registering a project are, to quote Libera.Chat's docs again:
- Channels in their namespace can be claimed
- Optional cloaks are available for members. These replace the hostname part with a custom string, e.g. @yourproject/developer/alex or @yourproject/taylor
- We offer to send messages about important releases or events of your project as a “wallop” message to all our users who opted in to receiving these
Those seem like good things, so I emailed them, and received this in response:
-------- Forwarded Message -------- From: amdj <redacted@libera.chat> Reply-To: redacted@libera.chat To: sajith@redacted Subject: [Libera.Chat #423] Registering #tahoe-lafs Date: Sun, 30 May 2021 11:34:15 +0000 Hello! Sorry it's taken so long to get back to you; we've been absolutely swamped with a registration backlog, abuse mitigation, and network maintenance and patching. To assist with project verification, please perform the following: 1) Prove control over tahoe-lafs.org via either: 1A) Create the DNS TXT record libera-5kYx4CV2AJGv4dc2.tahoe-lafs.org (with any content) 1B) Create the file /.well-known/libera-5kYx4CV2AJGv4dc2.txt on the web server (with any content) 2) Prove control over the GitHub organisation via either: 2A) Creation of the source code repository https://github.com/tahoe-lafs/libera-5kYx4CV2AJGv4dc2 (with any content) 2B) Creation of the branch libera-5kYx4CV2AJGv4dc2 in the source code repository https://github.com/tahoe-lafs/tahoe-lafs/ (with any content) Regards, Aaron Jones (amdj) LiberaChat Staff
I can't do 1A, 1B, and 2A. I can do 2B. I could use this ticket number for creating a branch.
Change History (3)
comment:1 Changed at 2021-05-31T12:38:28Z by sajith
- Description modified (diff)
comment:2 Changed at 2021-05-31T21:39:16Z by sajith
comment:3 Changed at 2021-08-03T15:21:54Z by exarkun
Are there more steps to take to complete this?
In PR 1071, I created the branch libera-5kYx4CV2AJGv4dc2 in the GitHub project, and Libera.Chat staff used that to verify us.
Now #tahoe-lafs namespace is registered to the Tahoe-LAFS project. That means we can create and manage #tahoe-lafs-riffraff and the such, should we feel the urge to do so, I believe.
On irc.libera.chat, /msg ChanServ info #tahoe-lafs now returns:
I have asked to add exarkun, maylee, meejah, and myself as primary and public project contacts.
One of the project contacts should be able to join #libera-communities channel of irc.libera.chat and ask for a project cloak (tahoe-lafs/team/<nick>, tahoe-lafs/bot/<nick> and the such), in case we find that useful.