git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Felipe Contreras'" <felipe.contreras@gmail.com>,
	"'Jeff King'" <peff@peff.net>,
	"'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: Fri, 21 May 2021 16:12:44 -0400	[thread overview]
Message-ID: <02ab01d74e7d$acd5cbd0$06816370$@nexbridge.com> (raw)
In-Reply-To: <60a7fe0b2dd8d_558062087@natae.notmuch>

On May 21, 2021 2:38 PM, 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.

Having been on IRC for three separate rounds, with a smattering of AOL, CompuServe, HipChat, Slack, Hangouts, Messenger, SMS, Skype, Teams... I'd be surprised if a consensus is possible.  The limiting factor for most of my circle is whether connections are even possible from corporate intranets and IRC is generally blocked. For the more blocked ones, Slack and Teams tend to be more palatable (not in my opinion). We have IRC open by exemption (specifically for #git) and will close it if IRC is discontinued. It might be worth taking a poll of what people can use instead of preference. My $0.02 bet is that that is the limiting factor for the community as a whole (work from home COVID notwithstanding).

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

I don't know about you, but when 5 or 6 chat platforms beep at me at the same time, I start looking for the exit - or Friday afternoons. As a sideways thought, maybe we should just figure out a way to go to Zoom and be done with it (I have no affiliation).

Cheers,
-Randall

-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
Still not talking about MVS.
-- In my real life, I talk too much.





  reply	other threads:[~2021-05-21 20:13 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 [this message]
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='02ab01d74e7d$acd5cbd0$06816370$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=emilyshaffer@google.com \
    --cc=felipe.contreras@gmail.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.
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).