From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Cc: "Jeff King" <peff@peff.net>,
"Michal Suchánek" <msuchanek@suse.de>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Emily Shaffer" <emilyshaffer@google.com>,
"Git List" <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: Should we do something with #git-devel on Freenode?
Date: Wed, 26 May 2021 18:59:24 -0500 [thread overview]
Message-ID: <60aee0dc3a6b0_75dc20855@natae.notmuch> (raw)
In-Reply-To: <875yz5m5hd.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
>
> On Fri, May 21 2021, Felipe Contreras wrote:
>
> > Jeff King wrote:
> >> Of course there's value in coordinating. Everybody _can_ hang out on
> >> their favorite venues and eventually talk to each other, but it's much
> >> easier if everybody agrees where to go. :)
> >
> > I don't think it works that way.
> >
> > I "everybody" agrees to move to Discord, many old-timers won't. Same
> > with Gitter. And if most people were on IRC, many youngsters wouldn't
> > come.
> >
> > There's a limit to how many chat applications you are willing juggle,
> > and adding one more just to chat with git developers is something many
> > people won't do.
>
> In the case of IRC though there's many IRC-to-X gateways that allow you
> to somewhat have your cake and eat it too, e.g. there's one for
> discord[1].
I have tried some of them, they don't quite cut it for me.
> I haven't tried it, but I use another channel that has an
> irc-to-Telegram (the app) gateway[2]. It works quite well. Aside from
> the Freenode v.s. Librechat question I wonder if there'd be interest in
> having such a thing running for #git or #git-devel.
I think that would be very nice (if it works correctly).
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-26 23:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:47 Should we do something with #git-devel on Freenode? Emily Shaffer
2021-05-19 19:08 ` Jonathan Nieder
2021-05-19 23:22 ` Junio C Hamano
2021-05-20 7:11 ` Michal Suchánek
2021-05-20 17:19 ` Jeff King
2021-05-20 18:08 ` Emily Shaffer
2021-05-20 21:20 ` Junio C Hamano
2021-05-21 11:19 ` Kevin Daudt
2021-07-02 12:15 ` Ævar Arnfjörð Bjarmason
2021-07-02 15:23 ` Junio C Hamano
2021-05-21 18:38 ` Felipe Contreras
2021-05-21 20:12 ` Randall S. Becker
2021-05-26 23:35 ` Ævar Arnfjörð Bjarmason
2021-05-26 23:59 ` Felipe Contreras [this message]
2021-05-27 0:24 ` Đoàn Trần Công Danh
2021-05-26 18:47 ` Taylor Blau
2021-05-26 20:01 ` Kevin Daudt
2021-05-27 17:18 ` Jan Krüger
2021-05-27 21:54 ` Ævar Arnfjörð Bjarmason
2021-05-28 1:26 ` Felipe Contreras
2021-05-28 1:36 ` Taylor Blau
2021-05-28 3:29 ` Felipe Contreras
2021-05-28 8:00 ` Jan Krüger
2021-05-28 14:37 ` Phillip Susi
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=60aee0dc3a6b0_75dc20855@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=jrnieder@gmail.com \
--cc=msuchanek@suse.de \
--cc=peff@peff.net \
/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).