git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Tan <jonathantanmy@google.com>
To: emilyshaffer@google.com
Cc: gitster@pobox.com, git@vger.kernel.org,
	johannes.schindelin@gmx.de, jonathantanmy@google.com
Subject: Re: [PATCH v5 1/2] documentation: add tutorial for first contribution
Date: Wed,  8 May 2019 12:53:25 -0700	[thread overview]
Message-ID: <20190508195325.98698-1-jonathantanmy@google.com> (raw)
In-Reply-To: <20190508185807.GA14000@google.com>

> > And "official" is a phrase I have trouble with in this context.  A
> > mirror does not have to be blessed as official; that's the point of
> > a mirror---anybody can make one to help users with better
> > connectivity or availability, as long as its users trust the mirror
> > maintainer for mirror's correctness and freshness.
> 
> You're right and I'll remove it. However, I've seen at least one
> instance of confusion over Git's lack of an "official" mirror (over on
> #git on Freenode). I'd like to rephrase this to explain the reasoning
> behind having multiple mirrors, none of which are official.
> 
> To that end, I propose replacing the phrase with "one of the best places
> to clone from is this mirror on GitHub." followed by the clone command
> to git/git, then followed by:
> 
> 	NOTE: As Git is a distributed version control, the Git project also
> 	follows a distributed model. There is no central official mirror; any
> 	mirror which you can reasonably trust is being kept correct and fresh to
> 	the Git source distributed by the Git maintainer is fine to work from.
> 
> What do we think?

In the interest of avoiding mailing list churn, I think we should not
bother with explaining what an "official" mirror is right now, as long
as we already have steps that a newcomer can take (which we do). Someone
else can add it later if they wish.

For me, the "official" mirrors are whatever is listed in the latest "A
note from the maintainer" (e.g. [1]). Even if we want to link to this or
replicate part of its contents, I think we can do it after this patch is
merged.

(Also, with that paragraph, I don't think a newcomer should be expected
to know what mirror is reasonably trusted.)

[1] https://public-inbox.org/git/xmqqwolmcvyb.fsf@gitster-ct.c.googlers.com/

> Alternatively, if the desire is to just be done with it, I have no
> problem with Junio rewording however he feels is best and otherwise
> applying this patch - if there is value in reducing the churn on the
> mailing list for this patch.

This sounds good to me too.

  reply	other threads:[~2019-05-08 19:53 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 18:32 [PATCH 0/1] documentation: add lab for first contribution Emily Shaffer via GitGitGadget
2019-04-11 18:32 ` [PATCH 1/1] " Emily Shaffer via GitGitGadget
2019-04-12  3:20   ` Junio C Hamano
2019-04-12 22:03     ` Emily Shaffer
2019-04-13  5:39       ` Junio C Hamano
2019-04-15 17:26         ` Emily Shaffer
2019-04-11 21:03 ` [PATCH 0/1] " Josh Steadmon
2019-04-12  2:35 ` Junio C Hamano
2019-04-12 22:58   ` Emily Shaffer
2019-04-16 20:26 ` [PATCH v2 " Emily Shaffer via GitGitGadget
2019-04-16 20:26   ` [PATCH v2 1/1] " Emily Shaffer via GitGitGadget
2019-04-17  5:32     ` Junio C Hamano
2019-04-17  8:07       ` Eric Sunshine
2019-04-18  0:05         ` Junio C Hamano
2019-04-17 23:16       ` Emily Shaffer
2019-04-16 21:13   ` [PATCH v2 0/1] " Emily Shaffer
2019-04-19 16:57   ` [PATCH v3] " Emily Shaffer
2019-04-21 10:52     ` Junio C Hamano
2019-04-22 22:27       ` Emily Shaffer
2019-04-23 19:34     ` [PATCH v4] documentation: add tutorial " Emily Shaffer
2019-04-30 18:59       ` Josh Steadmon
2019-05-02  0:57         ` Emily Shaffer
2019-05-03  2:11       ` Phil Hord
2019-05-07 19:05         ` Emily Shaffer
2019-05-06 22:28       ` Jonathan Tan
2019-05-07 19:59         ` Emily Shaffer
2019-05-07 20:32           ` Jonathan Tan
2019-05-08  2:45         ` Junio C Hamano
2019-05-07 21:30       ` [PATCH v5 0/2] documentation: add lab " Emily Shaffer
2019-05-07 21:30         ` [PATCH v5 1/2] documentation: add tutorial " Emily Shaffer
2019-05-07 23:25           ` Emily Shaffer
2019-05-08  3:46           ` Junio C Hamano
2019-05-08 18:58             ` Emily Shaffer
2019-05-08 19:53               ` Jonathan Tan [this message]
2019-05-07 21:30         ` [PATCH v5 2/2] documentation: add anchors to MyFirstContribution Emily Shaffer
2019-05-08  3:30         ` [PATCH v5 0/2] documentation: add lab for first contribution Junio C Hamano
2019-05-17 19:03         ` [PATCH v6 0/2] documentation: add tutorial " Emily Shaffer
2019-05-17 19:07           ` [PATCH v6 1/2] " Emily Shaffer
2019-05-26  7:48             ` Christian Couder
2019-05-29 20:09               ` Emily Shaffer
2019-10-18 16:40             ` SZEDER Gábor
2019-10-18 22:54               ` Emily Shaffer
2019-05-17 19:07           ` [PATCH v6 2/2] documentation: add anchors to MyFirstContribution Emily Shaffer
2019-05-29 20:18           ` [PATCH] doc: add some nit fixes " Emily Shaffer

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=20190508195325.98698-1-jonathantanmy@google.com \
    --to=jonathantanmy@google.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    /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).