[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3726: Register Tahoe-LAFS project with Libera.Chat

[Tahoe-LAFS]

#3726: Register Tahoe-LAFS project with Libera.Chat
-------------------------+-----------------------
     Reporter:  sajith   |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------
Description changed by sajith:

Old description:

> 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 [[https://libera.chat/chanreg#project-
> registration|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 at libera.chat>
> Reply-To: redacted at libera.chat
> To: sajith at 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-[redacted].tahoe-lafs.org
>     (with any content)
> 1B) Create the file /.well-known/libera-[redacted].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-[redacted] (with any content)
> 2B) Creation of the branch libera-[redacted] 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.

New description:

 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 [[https://libera.chat/chanreg#project-
 registration|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 at libera.chat>
 Reply-To: redacted at libera.chat
 To: sajith at 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.

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3726#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage