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

SZEDER Gábor <szeder.dev@gmail.com> writes:

> On Fri, Jan 24, 2020 at 03:44:40PM -0800, Junio C Hamano wrote:
>
>> ...  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.

I am not that dogmatic ;-) I would be very unhappy and probably
would not have joined if the main development community was closed,
but I do not think the "knowledge" the "closed mentoring list for
those who are shy" are meant to impart to newbies will be something
that will be so well kept secret that are shared among only those in
the closed list.  I expect the mentoring list to be repeating what
those who graduated "new"-ness consider pretty much common public
knowledge.

Having said that, my reading did hiccup when queuing Emily's text,
in that it listed the mentoring list first, and (more problematic)
the only choice among the three described with a word "great" was
that one.  Also, now I re-read it, the last sentence "You must join
the group to view messages or post", without explaining why it is
set up that way is bound to give a wrong impression, I suppose.  I
presume that the reason why those who wanted to make the mentoring
list closed was because they thought it would be nicer for shysters,
but if that is the case, it probably is better to spell that out.

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

I have no problem with seeing an expanded invitation to the main
list.  I do not have a strong opinion on the order of three items.

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

I'll mark the topic on hold (it is in 'next'), and would give the
stakeholders some time to settle the discussion, perhaps with
counter-proposals in an incremental patch form.  Would it be
reasonable to set the deadline around the end of the next week?

  reply	other threads:[~2020-02-06 16:34 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
2020-02-06 16:33                 ` Junio C Hamano [this message]
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=xmqqh803fzf1.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=szeder.dev@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.
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).