git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Emily Shaffer <emilyshaffer@google.com>, git@vger.kernel.org
Subject: Re: [PATCH v7] MyFirstContribution: add avenues for getting help
Date: Thu, 6 Feb 2020 02:07:04 +0100	[thread overview]
Message-ID: <20200206010704.GN10482@szeder.dev> (raw)
In-Reply-To: <xmqqh80kctcn.fsf@gitster-ct.c.googlers.com>

On Fri, Jan 24, 2020 at 03:44:40PM -0800, Junio C Hamano wrote:
> SZEDER Gábor <szeder.dev@gmail.com> writes:
> 
> > On Fri, Jan 24, 2020 at 01:26:02PM -0800, Emily Shaffer wrote:
> >> With https://lore.kernel.org/git/20191114194708.GD60198@google.com/ we
> >> now have a mentoring mailing list, to which we should direct new
> >> contributors who have questions.
> >
> > Why should a supposedly "open" open source project direct new
> > contributors to a mailing list that is not openly accessible, and even
> > reading and searching its archives requires registration?
> 
> Haven't we had that discussion when the mentoring list was launched?
> 
> I would not prefer joining a closed list of unknown people over
> coming up with a fake name and asking for help in an open list if I
> had choice when interacting with an established community as a new
> member, but I would understand it if preference of some people are
> opposite from mine.  The more important part, from my point of view,
> is that we offer choices (the proposed doc update illustrates
> three).

I remember a discussion about whether that list and its archive should
be open or closed, and I agree that offering choices is good.
However, since that mentoring list requires registration, we have to
carefully consider how to present it to newcomers.

Openly accessible knowledge is a fundamental value, and it's the
foundation of open source.  Therefore, we definitely should not direct
newcomers to a closed mailing list as the first option, it can only be
a fallback.

The text should list git@vger as the first option, since that's the
only open mailing list we have, it should clearly emphasize that
newcomers are very welcome, and should explicitly encourage them to
post their questions here, no matter how trivial or silly they think
those questions are, we'll be always glad to answer them.

The closed mailing list can be mentioned third as a fallback for those
who would prefer not to end up on public record right away or who have
any technical issues with posting to the main mailing list.


  reply	other threads:[~2020-02-06  1:07 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 21:53 [PATCH] MyFirstContribution: add avenues for getting help Emily Shaffer
2019-11-15 22:05 ` Denton Liu
2019-11-15 23:03   ` Emily Shaffer
2019-11-15 23:06 ` [PATCH v2] " Emily Shaffer
2019-11-15 23:38   ` Johannes Schindelin
2019-11-16  0:09   ` Jonathan Nieder
2019-11-16  3:05   ` Junio C Hamano
2019-11-18 21:45     ` Emily Shaffer
2019-11-19  1:45       ` Junio C Hamano
2019-11-19 18:49       ` SZEDER Gábor
2019-11-19 21:29         ` Johannes Schindelin
2019-11-19 21:41           ` SZEDER Gábor
2019-11-20  1:50             ` Eric Wong
2019-11-20 11:41             ` Johannes Schindelin
2019-11-20 23:40               ` SZEDER Gábor
2019-11-20 10:45           ` Kerry, Richard
2019-11-20 11:37             ` Junio C Hamano
2019-11-19 18:25   ` SZEDER Gábor
2019-12-13  1:31   ` [PATCH v3] " Emily Shaffer
2019-12-13  3:00     ` Derrick Stolee
2019-12-13  4:14       ` Emily Shaffer
2019-12-13  4:16       ` [PATCH v4] " Emily Shaffer
2019-12-13 17:20     ` [PATCH v3] " Junio C Hamano
2019-12-13 17:49       ` Emily Shaffer
2019-12-13 18:40         ` Junio C Hamano
2020-01-24 20:09     ` [PATCH v5] " emilyshaffer
2020-01-24 20:35       ` Junio C Hamano
2020-01-24 20:50         ` Emily Shaffer
2020-01-24 20:54           ` Emily Shaffer
2020-01-24 21:11           ` Junio C Hamano
2020-01-24 21:01       ` [PATCH v6] " Emily Shaffer
2020-01-24 21:18         ` Junio C Hamano
2020-01-24 21:20           ` Emily Shaffer
2020-01-24 21:26         ` [PATCH v7] " Emily Shaffer
2020-01-24 21:56           ` SZEDER Gábor
2020-01-24 23:44             ` Junio C Hamano
2020-02-06  1:07               ` SZEDER Gábor [this message]
2020-02-06 16:33                 ` Junio C Hamano
2020-02-06 19:49                   ` Emily Shaffer
2020-02-06 22:13                     ` Emily Shaffer
2020-02-14  2:03                   ` [PATCH] MyFirstContribution: rephrase contact info Emily Shaffer
2020-02-14  2:10                     ` Jonathan Nieder
2020-02-14 17:36                       ` Junio C Hamano
2020-01-24 22:05           ` [PATCH v7] MyFirstContribution: add avenues for getting help 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

  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=20200206010704.GN10482@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).