From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Senol Yazici'" <sypsilon@googlemail.com>, <git@vger.kernel.org>
Subject: RE: Delivery Status Notification (Failure)
Date: Mon, 18 Feb 2019 11:12:49 -0500 [thread overview]
Message-ID: <000b01d4c7a4$ce4db4b0$6ae91e10$@nexbridge.com> (raw)
In-Reply-To: <CAFacdQ8NDKfd0p8=9Rh3s4FPeS9mbqpQt8mw3AZoJn9jHjriPg@mail.gmail.com>
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)
Regards,
Randall
next prev parent reply other threads:[~2019-02-18 16:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5c62b41d.1c69fb81.fe791.877b@mx.google.com>
[not found] ` <CAFacdQ-soWD176VHgd+raHaV=VPpzKXrDrLFavPcNEoewZwBYA@mail.gmail.com>
[not found] ` <5c657002.1c69fb81.d433c.32ce.GMR@mx.google.com>
2019-02-18 10:46 ` Delivery Status Notification (Failure) Senol Yazici
2019-02-18 16:12 ` Randall S. Becker [this message]
2019-02-18 20:59 ` Johannes Schindelin
2019-02-19 1:08 ` Jason Pyeron
2019-02-19 11:43 ` Changing https://git-scm.com/about/distributed, was " Johannes Schindelin
[not found] <CAHMHMxWhYEMWCPgPp7qX9S_i0-CtS6OBj2TdCVXsyromnwVawQ@mail.gmail.com>
[not found] ` <5ddbd7b7.1c69fb81.dbdb8.eb94.GMR@mx.google.com>
2019-11-25 13:36 ` Σταύρος Ντέντος
[not found] <CAFF4x5LfJ7qY73JE-=mah5vx9PdeNhc0i0X6kQohPpvDTCd3Sw@mail.gmail.com>
[not found] ` <5cff8197.1c69fb81.4940.6de6.GMR@mx.google.com>
2019-06-11 10:29 ` Xeno Amess
2017-11-23 18:51 Problem installing Git Phil Martel
2017-11-23 21:30 ` Igor Djordjevic
[not found] ` <001a1148fe243ade02055ead2599@google.com>
2017-11-23 21:41 ` Delivery Status Notification (Failure) Igor Djordjevic
-- strict thread matches above, loose matches on Subject: below --
2017-05-16 23:22 [Bug] git branch -v has problems with carriage returns Animi Vulpis
[not found] ` <CA+izobutP-JY84RGG-JbPA5twbckL1uVwxknBRLVTuGG0MEJcg@mail.gmail.com>
[not found] ` <CA+izobuSKtoQzNJuvuisjh7h3FF=nbt8u-hOHfdeFp8ZjgZF+Q@mail.gmail.com>
[not found] ` <591f6844.82dcca0a.451e5.8f76.GMRIR@mx.google.com>
2017-05-19 21:51 ` Delivery Status Notification (Failure) Atousa Duprat
[not found] <CAFAMDXb-_8WAMw7qOdAyJQKuLwtg+kAYOJO7xivCq7OTMyB26Q@mail.gmail.com>
[not found] ` <047d7b2ed8ab924fe60510bc0ea0@google.com>
2015-03-08 0:36 ` Amate Yolande
[not found] <CAN_hzmqrrue8jif3AJv4pZwmyMpQ6u558HaRX6dQKZCF0c_H1w@mail.gmail.com>
[not found] ` <bcaec5396b50ba47be04d7e99955@google.com>
2013-03-14 22:01 ` Harring Figueiredo
2013-03-14 22:12 ` Junio C Hamano
2013-03-14 23:36 ` Harring Figueiredo
[not found] <CAAymXMrufs69Vg=O3Kt7Ot3kYERP=55TMFiHGkV75mUFkzr74A@mail.gmail.com>
[not found] ` <001636c927b40af7cb04ba0aca6e@google.com>
2012-02-28 19:02 ` Rajat Khanduja
2012-02-28 19:48 ` Jeff King
[not found] <BANLkTin+Qn9FzvTJauOPVCJnk8v4ajVnSw@mail.gmail.com>
[not found] ` <000e0cd5cff499795e04a05dc387@google.com>
2011-04-08 2:41 ` David Xu
[not found] <AANLkTine9j=PsfsOPmEWmDLUDrHCJF0MQ6X+6XJkQD0d@mail.gmail.com>
[not found] ` <0015174c437c389602048ce7f16c@google.com>
2010-08-03 9:31 ` Simon Grönlund
2010-01-29 14:17 Implement --password option for git svn perl script Laszlo Papp
[not found] ` <001636ed7681994278047e4e4a6f@google.com>
2010-01-29 14:18 ` Fwd: Delivery Status Notification (Failure) Laszlo Papp
2010-01-29 15:04 ` Frank Li
2010-02-01 16:16 ` Laszlo Papp
2010-02-02 4:15 ` Tay Ray Chuan
2010-02-02 4:30 ` Frank Li
2010-02-02 6:37 ` Laszlo Papp
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='000b01d4c7a4$ce4db4b0$6ae91e10$@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).