git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: "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: Thu, 20 May 2021 13:19:02 -0400	[thread overview]
Message-ID: <YKaaBj0KmJ3K5foC@coredump.intra.peff.net> (raw)
In-Reply-To: <20210520071141.GZ8544@kitsune.suse.cz>

On Thu, May 20, 2021 at 09:11:41AM +0200, Michal Suchánek wrote:

> > It looks like most of the Freenode admins have moved to
> > https://libera.chat/, so that would be a close equivalent.  Another
> > alternative is OFTC <https://www.oftc.net/>, which is used by
> > irc.debian.org, for example.
> > 
> > There are also other real-time chat programs such as Zulip (open
> > source, used in Outreachy), Discord (used by LLVM), and Slack (used by
> > Chromium); each has its benefits and flaws.
> 
> Or Matrix used by Mozilla, GNOME, and others.
> 
> Unlike the others Matrix intends to be not just a chat application
> (opensource or proprietary) but open standard which has multiple
> implementetions of both the server and the client.
> 
> In that way it is the most flexible option allowing communication
> between people with different UX preferences.

I don't have much of an opinion either way, as I do not usually use the
irc channel at all. And my comment is perhaps more about #git than
#git-devel.

But I would say that the decision to move to another application would
be one that can be made by individual people. I.e., the reason people
come to freenode #git to ask questions is because there are useful
people hanging out there who will answer them. And likewise to
#git-devel, because that's where the people who can have useful
discussions are.

So if there is a critical mass of useful people that will hang out on
the Matrix equivalent of #git (or whatever other tool), then that may
become a new place. And people who want to do that should let people
know where they can be found (whatever happens, I'd appreciate a PR to
https://github.com/git/git-scm.com updating the "Community" page).

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 think Emily's question is
more "where do folks who hang out on #git-devel want to hang out now".
And that's why I say my comments are probably more relevant for #git
(where devs don't need to coordinate as much; useful people can just
hang out and help folks with questions).

-Peff

PS A lot of this may reflect my view that there is no "official"
structure for a lot of Git. We all used gmane as an archive because it
was the best option at the time. Then it got worse, and Eric made
public-inbox because it was what he wanted. And we all used it because
it was so good. But there never needed to be any official adoption
decision. Likewise for irc. I don't think #git or even #git-devel has
any official status. It is simply where people doing things chose to go.
Now they may choose to go somewhere else, but they don't necessarily
have to do it as a unit.

  reply	other threads:[~2021-05-20 17:19 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 [this message]
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
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=YKaaBj0KmJ3K5foC@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=jrnieder@gmail.com \
    --cc=msuchanek@suse.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).