From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Subject: Re: Clarification of IRC network for #glibc IRC channel?
Date: Fri, 11 Jun 2021 00:40:21 -0400 [thread overview]
Message-ID: <129f801d-baa8-cc4e-360d-b9dcc4c19ac7@redhat.com> (raw)
In-Reply-To: <be034819-a15a-40ec-bde0-fff030979963@redhat.com>
On 5/31/21 12:51 PM, Carlos O'Donell wrote:
> Community,
>
> The recent changes to Freenode and subsequent creation of
> Libera.Chat make it difficult for new community members,
> and existing ones, to know which network/channel will have
> the right people to help answer questions and facilitate
> discussions about glibc.
>
> I want to clarify our official IRC channel to ensure that
> we don't have any confusion over where to expect help will
> come from. I'm looking for any feedback from the community.
>
> Does the community have any preference about which IRC
> network to use?
>
> Should we move #glibc to Libera.Chat
>
> Should we use #glibc on OFTC to be on the same network as #gcc?
>
> Should we be on all the networks?
Thank you Mike and Andreas for your feedback.
Adhemerval, Tulio, Do you have any opinion?
I usually talk to both of you via IRC.
I think my plan will look like this:
- Setup official #glibc channel on OFTC to be near #gcc.
- Maintain unofficial #glibc channel on Libera.Chat (already registered).
- Shutdown Freenode channel.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-06-11 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 16:51 Carlos O'Donell
2021-05-31 18:37 ` Mike Frysinger
2021-06-01 15:55 ` Andreas K. Huettel
2021-06-11 4:40 ` Carlos O'Donell [this message]
2021-06-11 15:10 ` Tulio Magno Quites Machado Filho
2021-06-11 15:11 ` Adhemerval Zanella
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=129f801d-baa8-cc4e-360d-b9dcc4c19ac7@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.ibm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).