git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Taylor Blau <me@ttaylorr.com>,
	Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jan Krüger" <jk@jk.gs>, "Kevin Daudt" <me@ikke.info>,
	"Taylor Blau" <me@ttaylorr.com>, "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>
Subject: Re: Should we do something with #git-devel on Freenode?
Date: Thu, 27 May 2021 22:29:10 -0500	[thread overview]
Message-ID: <60b0638618044_49b58208a4@natae.notmuch> (raw)
In-Reply-To: <YLBJJEQEUW8MVJm8@nand.local>

Taylor Blau wrote:
> On Thu, May 27, 2021 at 08:26:53PM -0500, Felipe Contreras wrote:
> > Ævar Arnfjörð Bjarmason wrote:
> >
> > > I don't see why we'd advertise #git@liberachat and not #git@freenode in
> > > order to achieve that goal, the latter doesn't seem to be a graveyard
> > > and is probably still more active. I don't see why we'd need to pick
> > > between the two, any more than we'd pick between advertising
> > > #git@liberachat and the git-users mailing list. Both currently seem like
> > > useful venues for git users to go to get help.
> >
> > Agreed.
> >
> > The primary purpose of an IRC channel should be to help users, and if
> > right now the person that could help a user is on freenode, so be it.
> >
> > If the people with some political alignment want to emphasize
> > LiberaChat, that's fine, but keep mentioning freenode.
> 
> git-scm.com was updated recently to mention LiberaChat instead of
> Freenode [1]. That was done to reflect the reality of [2]. I suspect
> that will have been the right decision, but in case it isn't (and
> there are still people hanging around in #git on Freenode), then I'd
> be in favor of mentioning both.

As of this moment (2021-05-27T22:20:00-0500) there's 324 people on
Libera.Chat, and 762 on freenode.

So yeah... I'd say there are still people hanging around in #git on
freenode.

> For what it's worth, I also do not care about the Freenode versus
> Libera (or vice-versa?) debacle. That said, I do think having one
> central place for people to hang out is better than two (if for no
> other reason than it's fewer places to check or go to if you want
> help), but I would be fine if the status-quo were that there is an
> active #git channel on both Libera and Freenode.

Sure, one would be better than two, but rarely can we pick the reality
that is better... Reality just is.

Cheers.

-- 
Felipe Contreras

  reply	other threads:[~2021-05-28  3:29 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
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 [this message]
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=60b0638618044_49b58208a4@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=me@ikke.info \
    --cc=me@ttaylorr.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.
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).