git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Senol Yazici'" <sypsilon@googlemail.com>, <git@vger.kernel.org>
Subject: Re: [RFE] Demilitarize Documentation (was RE: Delivery Status Notification (Failure))
Date: Mon, 18 Feb 2019 11:51:57 -0500	[thread overview]
Message-ID: <001601d4c7aa$460c0e70$d2242b50$@nexbridge.com> (raw)

On February 18, 2019 11:13, I wrote:
> To: 'Senol Yazici' <sypsilon@googlemail.com>; git@vger.kernel.org
> Subject: RE: Delivery Status Notification (Failure)
> 
> On February 18, 2019 5:47, Senol Yazici
> > I just stumbled over following page
> >
> > https://git-scm.com/about/distributed
> >
> > and was wondering if it is possible to
> >
> > - demilitarise that “dictator/lieutenant” thing and
> > - de-religionise that “blessed” thing
> >
> > I did not had the feeling that git is “pro military”, or is against “non
> religious”
> > developers/users.
> 
> I think there is a point here. In some of my customers, we have replaced
> these terms with the following (the Repository is optional in the second two):
> 
> * Blessed: Repository of Record
> * Dictator: Committer [Repository]
> * Lieutenant: Contributor [Repository]
> 
> This seems more closely aligned with the real roles being applied to activities
> associated with the repositories involved.
> 
> Taking a lesson from other Open Source projects, Jenkins has deprecated
> Master/Slave in favour of Controller/Agent. This seems not only more
> acceptable to some, but in my view more descriptive. The terms on the page
> above do not actually make any descriptive sense to a newbie. And confusion
> could ensue from the dictionary definitions:
> 
> * Lieutenant: an aide or representative of another in the performance of
> duty : assistant (not what that repository is for)
> * Dictator: one holding complete autocratic control : a person with unlimited
> governmental power (not how the git team behaves)
> * Blessed: honored in worship : hallowed; of or enjoying happiness (although
> I can see the happiness part of this one)

It probably would be worth submitting this as an issue to the documentation project at https://github.com/git/git-scm.com. Depending on the response from the committers, I might be willing to take that on, but digging deeper, I'm not sure the terms I proposed as sufficient.


             reply	other threads:[~2019-02-18 16:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 16:51 Randall S. Becker [this message]
2019-02-18 17:26 ` [RFE] Demilitarize Documentation (was RE: Delivery Status Notification (Failure)) Michal Suchánek
2019-02-18 18:39 ` Junio C Hamano
2019-02-19  8:02   ` Senol Yazici
2019-02-19  9:39     ` Michal Suchánek
2019-02-19 14:47       ` Johannes Schindelin
2019-02-19 16:28         ` Michal Suchánek
2019-02-19 10:01     ` SZEDER Gábor
2019-02-19 11:00       ` Senol Yazici
2019-02-19 14:58       ` Johannes Schindelin
2019-02-19 16:20         ` Michal Suchánek
2019-02-20 19:54           ` Johannes Schindelin
2019-02-19 20:16         ` Philip Oakley
2019-02-20 11:17         ` SZEDER Gábor
2019-02-19 11:19     ` Ævar Arnfjörð Bjarmason
2019-02-19 13:33       ` Michal Suchánek
2019-02-19 13:52       ` Christian Couder
2019-02-19 13:58         ` Michal Suchánek

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='001601d4c7aa$460c0e70$d2242b50$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=sypsilon@googlemail.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).