public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: Git List <git@vger.kernel.org>,
	 git-mentoring <git-mentoring@googlegroups.com>,
	 Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: git-mentoring Google group replacement?
Date: Fri, 28 Feb 2025 15:21:33 -0800	[thread overview]
Message-ID: <xmqqcyf11wqq.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZnk88ZFZFdEtUxMnUa1OZiXYOgcw8DSbB+A0LzyCPFugg@mail.gmail.com> (Emily Shaffer's message of "Fri, 28 Feb 2025 14:42:43 -0800")

Emily Shaffer <nasamuffin@google.com> writes:

> Thoughts? Alternate suggestions? I'd also be happy to host a list with
> some other service, but I don't have any personal experience on which
> services are good to use or not.

I am perfectly fine to close the unusable list, and suggest folks to
redirect to discord or other services.  If the discord channel is
already found to be useful by those new folks who have been helped
there, that would be excellent, and then the question would become

 - what other avenues to ask for help, other than this list, are
   there that community members are willing to support by visiting
   there frequently and help out?  can we compile a list?  I am
   perfectly fine we start with a list with one entry in it.

 - where do we want to advertise such a list?
   Documentation/Contributing?  todo:MaintNotes (aka "A note from
   the Maintainer")?

 - how would we maintain such a list to keep it up-to-date?


  reply	other threads:[~2025-02-28 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 22:42 git-mentoring Google group replacement? Emily Shaffer
2025-02-28 23:21 ` Junio C Hamano [this message]
2025-03-02 11:11 ` Christian Couder

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=xmqqcyf11wqq.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-mentoring@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.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