caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Adrien Nader <adrien@notk.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Group registration on Freenode.net for #ocaml channels
Date: Fri, 5 Jan 2018 20:58:58 +0000	[thread overview]
Message-ID: <57C8A925-70E0-408D-807C-A411A00E0D0B@recoil.org> (raw)
In-Reply-To: <20180105200833.GA26414@notk.org>


> On 5 Jan 2018, at 20:08, Adrien Nader <adrien@notk.org> wrote:
> 
> Now that group registration is possible again, I'm looking at the
> process: http://freenode.net/groupreg . It's not legalese but it's
> clearly not very entertaining.
> The main takeaway is « Represents an official relationship between
> freenode and your project or organisation. ». Everything else is a
> consequence.
> 
> Is there a legal/formal entity that wants to establish that official
> relationship with freenode? This doesn't imply managing the IRC channels
> but only doing the registration and deciding who gets to actually manage
> the IRC channels. If so, what should that contact email address be? If
> not, can "we" register as an informal group?
> [ Note that without any answer within 30 days, i.e. post-FOSDEM, I will
> assume there is no interest from a formal entity to enter a relationship
> with freenode and that we can register as an informal group ]

Dear Adrien,

Thanks for looking into this.  I think an ‘informal project-oriented group’
is most appropriate for a programming language community like ours
on Freenode.

Feel free to put me down as a contact if it helps.

regards,
Anil

  reply	other threads:[~2018-01-05 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 20:08 Adrien Nader
2018-01-05 20:58 ` Anil Madhavapeddy [this message]
2018-01-05 21:42   ` Adrien Nader
2018-01-21 13:48     ` Adrien Nader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57C8A925-70E0-408D-807C-A411A00E0D0B@recoil.org \
    --to=anil@recoil.org \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).