git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] MyFirstContribution: link #git-devel to Libera Chat
Date: Tue, 8 Jun 2021 12:02:24 -0700	[thread overview]
Message-ID: <YL++wKvEWrvKtCp1@google.com> (raw)
In-Reply-To: <C8A2DA3C-8D30-44AD-99FF-C5394C5F3B30@gmail.com>

On Tue, Jun 08, 2021 at 11:34:02PM +0530, Atharva Raykar wrote:
> 
> On 08-Jun-2021, at 22:53, Emily Shaffer <emilyshaffer@google.com> wrote:
> > 
> > On Tue, Jun 08, 2021 at 07:21:14PM +0530, Atharva Raykar wrote:
> >> 
> >> It's pretty safe to say that most of the regulars on #git-devel are now
> >> on Libera Chat. This will help new contributors find the right place, if
> >> they choose to ask questions on `#git-devel`.
> >> 
> >> Since there seems to be no way to directly link Libera's web chat to
> >> `#git-devel` directly,
> > 
> > I just typed "web.libera.chat/#git-devel" and it worked perfectly fine.
> > 
> >> I have put a generic link over the text 'Libera
> >> Chat'. Users will have to manually type `#git-devel` in the webchat
> >> interface, but that should be obvious enough to not be worth mentioning.
> > 
> > Generally, this is a bad approach to take for absolute-beginner
> > documents like this one. Even if it "should" be obvious, why not just
> > say it? Some skills - like how to examine the compiler errors from your
> > C compiler and fix your code accordingly - are a necessary prerequisite
> > to be useful on the Git project; other skills - like how to use IRC -
> > are not, and we can teach them, especially in a guide like this :)
> 
> Got you. In fact, the fault in my reasoning was perfectly
> demonstrated by the fact that I did not attempt one of the most
> "obvious" ways to get the link to #git-devel directly.
> 
> I cannot decide what's obvious for other people :)

Or maybe Libera thought it was too obvious to document? :thinkyface:

Thanks again, looking forward to v2 :)

 - Emily

  reply	other threads:[~2021-06-08 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 13:51 [PATCH] MyFirstContribution: link #git-devel to Libera Chat Atharva Raykar
2021-06-08 14:01 ` Junio C Hamano
2021-06-08 17:23 ` Emily Shaffer
2021-06-08 18:04   ` Atharva Raykar
2021-06-08 19:02     ` Emily Shaffer [this message]
2021-06-08 17:23 ` Emily Shaffer
2021-06-08 18:06 ` [PATCH v2] " Atharva Raykar
2021-06-08 19:06   ` [PATCH v3] " Atharva Raykar
2021-06-08 19:18     ` Atharva Raykar
2021-06-08 20:49     ` Emily Shaffer
2021-06-09  0:23       ` Junio C Hamano

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=YL++wKvEWrvKtCp1@google.com \
    --to=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=raykar.ath@gmail.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 NNTP newsgroup(s).