From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Jordan DE GEA" <jordan.de-gea@grenoble-inp.org>,
<git@vger.kernel.org>, <erwan.mathoniere@grenoble-inp.org>,
<samuel.groot@grenoble-inp.org>, <tom.russello@grenoble-inp.org>,
<Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [RFC/PATCH] Triangular Workflow UI improvement: Documentation
Date: Fri, 3 Jun 2016 23:16:41 +0100 [thread overview]
Message-ID: <6C6F62CA4181453BA51BB362DAA5C0C1@PhilipOakley> (raw)
In-Reply-To: xmqqd1nyqnr6.fsf@gitster.mtv.corp.google.com
From: "Junio C Hamano" <gitster@pobox.com>
> "Philip Oakley" <philipoakley@iee.org> writes:
>
>> That said, trying to find a good name for that 'third place' is not easy.
>> It's neither upstream, nor downstream (for Junio - the maintainer special
>> case - git.git would be his downstream). The me/git repo is like a
>> ferryman's landing across the other side of the river flow, a safe
>> harbour
>> if you will.
>
> You raise a good point here.
>
> To me, the git.git public repository that everybody pulls from is
> just like me/git for everybody else. It is a place where you
> publish your work. I think the @{push} notation during its design
> phase was once called @{publish} instead.
I'd agree that your git/git is actually an @{publish} repo, and to my mind
is a formal 'downstream' for you.
However your gitster/git repo feels like it would match the me/git
viewpoint, in that while it is 'open', it isn't really a formal publishing
place. Certainly I don't think that I 'publish' what's in my personal github
repos, which I use as an open backup (and any PR's I put to the G4W project
repo are referenced from there).
I did have a look at various thesaurus words
(//www.thesaurus.com/browse/repository) that might be usable and found:-
depot, haven, shelter, sanctuary, wharf, bunker, vault, which are all 'near'
but not quite right, if only home-depot wasn't taken I'd suggest that!
>
> A "downstream" that is the opposite of "upstream" is not something
> you would configure and control. They are those who call you
> "upstream". You know and actively configure who your "upstream" is
> and pull from there. You do not have direct control who are the
> people who are pulling from you.
>
> So in that sense, "downstream" exists as a concept that is just as
> valid as "upstream", but unlike "upstream", "downstream" does not
> manifest itself as something you explicitly tell Git about, either
> from the command line, in the remotes definition, or in the
> configuration files.
Certainly for contributors, a configured 'downstream' repo doesn't make
sense, but I do think it's worthwhile for maintainers, Leiutenants, and
dictators who do have a specific publishing place.
next prev parent reply other threads:[~2016-06-03 22:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 10:06 [RFC] Triangular Workflow: user friendly full implementation Jordan DE GEA
2016-05-26 11:04 ` Matthieu Moy
2016-05-26 18:30 ` Junio C Hamano
2016-05-30 8:46 ` [RFC] Triangular Workflow UI improvement Jordan DE GEA
2016-05-27 7:32 ` [RFC] Triangular Workflow: user friendly full implementation Philip Oakley
2016-05-30 9:07 ` [RFC] Triangular Workflow UI improvments Jordan DE GEA
2016-05-31 12:28 ` [RFC/PATCH] Triangular Workflow UI improvement: Documentation Jordan DE GEA
2016-05-31 14:33 ` Matthieu Moy
2016-06-01 9:32 ` Jordan DE GEA
2016-06-02 12:02 ` Michael Haggerty
2016-06-03 7:25 ` Philip Oakley
2016-06-03 9:52 ` Jordan DE GEA
2016-06-03 11:36 ` Matthieu Moy
2016-06-03 11:53 ` Jordan DE GEA
2016-06-05 21:28 ` Jordan DE GEA
2016-06-06 7:58 ` Matthieu Moy
2016-06-06 16:46 ` Philip Oakley
2016-06-06 16:54 ` Matthieu Moy
2016-06-06 19:21 ` Philip Oakley
2016-06-07 7:03 ` Matthieu Moy
2016-06-07 20:08 ` Philip Oakley
2016-06-03 15:46 ` Junio C Hamano
2016-06-03 22:16 ` Philip Oakley [this message]
2016-06-06 9:48 ` [RFC/PATCHv2] Documentation: triangular workflow Jordan DE GEA
2016-06-06 19:23 ` Junio C Hamano
2016-06-06 22:21 ` Philip Oakley
2016-06-07 6:58 ` Matthieu Moy
2016-06-07 8:02 ` Jordan DE GEA
2016-06-07 8:38 ` [PATCHv3] " Jordan DE GEA
2016-06-07 19:12 ` Junio C Hamano
2016-06-08 8:37 ` Jordan DE GEA
2016-06-08 13:20 ` Matthieu Moy
2016-06-09 12:35 ` [PATCHv4] " Jordan DE GEA
2016-06-09 17:02 ` Junio C Hamano
2016-06-11 15:58 ` Ramkumar Ramachandra
2016-06-11 19:31 ` Philip Oakley
2016-06-09 18:19 ` Philip Oakley
2016-06-10 16:47 ` Junio C Hamano
2016-06-11 19:25 ` Philip Oakley
2016-06-13 18:35 ` Junio C Hamano
2016-05-30 8:39 ` [RFC] Triangular Workflow UI improvement Jordan DE GEA
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=6C6F62CA4181453BA51BB362DAA5C0C1@PhilipOakley \
--to=philipoakley@iee.org \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=erwan.mathoniere@grenoble-inp.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jordan.de-gea@grenoble-inp.org \
--cc=samuel.groot@grenoble-inp.org \
--cc=tom.russello@grenoble-inp.org \
/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).