all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: elpa.git and `new-master`
Date: Thu, 17 Dec 2020 19:39:54 +1100	[thread overview]
Message-ID: <CAC=50j_M6x_Pz3ddiNRPp=SgySBxKiqx1q1kY3Da8_H0GQC=TA@mail.gmail.com> (raw)
In-Reply-To: <87lfdw26eu.fsf@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]

On Thu, 17 Dec 2020 at 19:18, Joost Kremers <joostkremers@fastmail.fm>
wrote:

>
> On Thu, Dec 17 2020, Eli Zaretskii wrote:
> >> From: Stefan Monnier <monnier@iro.umontreal.ca>
> >> Date: Wed, 16 Dec 2020 15:46:49 -0500
> >> Cc: Lars Ingebrigtsen <larsi@gnus.org>, Boruch Baum <
> boruch_baum@gmx.com>,
> >>  Emacs-Devel List <emacs-devel@gnu.org>
> >>
> >> OK, I renamed `new-master` to `main`.
> >> Will have to ask for a sysadmin to do the server-side dance, now.
> >>
> >> But before I do that: if we want to do this for `elpa.git`, why not do
> it
> >> for `nongnu.git`, and for `emacs.git` as well?
> >
> > Not for emacs.git, please.  Let's leave that at 'master'.
>
> If you keep 'master' in one repo, it should probably be kept
> in all Emacs-related repos. It's less confusing that way.
>
> I agree. Things are far less confusing if they are consistent.

I also feel that people have focused on how easy it is to make this change
technically, but have ignored the change management repercussions. In
addition to communicating the change, it is also important to consider what
documentation, howtos, tutorials etc that will need to be updated. Thie
importance is increased by the fact that regardless of personal position,
calling the trunk or initial repository master is the common and expected
practice for many users. It is also the default for many tools.

This is not a vote for or against, simply highlighting the point it is the
technical ease of making the change is not the same as the impact of the
change. As many on this list tend to have a strong technology bias, it is
easy to overlook the impact of such changes and how they impact on uses who
have less of a technical focus. We can expect to see an increase in
messages from people who are confused becauwse the information they found
on forums like stack overflow etc no longer works.
-- 
regards,

Tim

--
Tim Cross

[-- Attachment #2: Type: text/html, Size: 2810 bytes --]

  reply	other threads:[~2020-12-17  8:39 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16  6:47 elpa.git and `new-master` Boruch Baum
2020-12-16  7:38 ` Jean Louis
2020-12-16  8:24   ` Andreas Schwab
2020-12-16  9:31     ` Jean Louis
2020-12-16  9:59       ` Andreas Schwab
2020-12-16  8:49   ` Pankaj Jangid
2020-12-16  9:34     ` Jean Louis
2020-12-16  9:01   ` Alfred M. Szmidt
2020-12-16 12:29   ` Joost Kremers
2020-12-16 13:48     ` Jean Louis
2020-12-16 14:04       ` Lars Ingebrigtsen
2020-12-16 14:40         ` Jean Louis
2020-12-16 14:26     ` Stefan Monnier
2020-12-16 20:08     ` Stephen Leake
2020-12-17  3:58     ` Tim Landscheidt
2020-12-17  5:54     ` Richard Stallman
2020-12-17  8:25       ` Joost Kremers
2020-12-17 16:22       ` Stephen Leake
2020-12-18  5:48         ` Richard Stallman
2020-12-16 17:03   ` Clément Pit-Claudel
2020-12-16  9:03 ` Lars Ingebrigtsen
2020-12-16 10:19   ` Pankaj Jangid
2020-12-16 14:15     ` Boruch Baum
2020-12-16 13:48   ` Gregory Heytings via Emacs development discussions.
2020-12-16 13:53     ` Lars Ingebrigtsen
2020-12-16 14:43       ` Gregory Heytings via Emacs development discussions.
2020-12-16 15:24         ` Pankaj Jangid
2020-12-16 15:37         ` Jean Louis
2020-12-16 17:54         ` Alfred M. Szmidt
2020-12-16 16:23       ` Eli Zaretskii
2020-12-16 16:16   ` Dmitry Gutov
2020-12-16 18:24     ` Stefan Monnier
2020-12-16 18:46       ` Dmitry Gutov
2020-12-16 19:03         ` Boruch Baum
2020-12-16 19:06           ` Stefan Monnier
2020-12-16 19:21             ` Boruch Baum
2020-12-16 19:55               ` Stefan Monnier
2020-12-16 19:22             ` Andreas Schwab
2020-12-16 19:56               ` Stefan Monnier
2020-12-16 20:06                 ` Andreas Schwab
2020-12-16 20:12                 ` Boruch Baum
2020-12-16 20:19                   ` Lars Ingebrigtsen
2020-12-16 21:16                     ` Boruch Baum
2020-12-16 21:38                       ` Stefan Monnier
2020-12-16 20:38                   ` Stefan Monnier
2020-12-16 20:46         ` Stefan Monnier
2020-12-16 20:53           ` Dmitry Gutov
2020-12-16 21:09           ` Lars Ingebrigtsen
2020-12-16 21:34             ` Stefan Monnier
2020-12-17  0:11           ` Caio Henrique
2020-12-17  3:37           ` Eli Zaretskii
2020-12-17  8:15             ` Joost Kremers
2020-12-17  8:39               ` Tim Cross [this message]
2020-12-17 15:14             ` Stefan Monnier
2020-12-16 20:41       ` Juri Linkov
2020-12-16 21:24         ` Boruch Baum
  -- strict thread matches above, loose matches on Subject: below --
2020-12-15  4:46 Stefan Monnier
2020-12-15 16:09 ` Eli Zaretskii
2020-12-15 16:53   ` Stefan Monnier
2020-12-15 18:24     ` Eli Zaretskii
2020-12-15 19:02       ` Stephen Leake
2020-12-15 19:16         ` Eli Zaretskii
2020-12-15 21:09       ` Dmitry Gutov
2020-12-15 21:33       ` Stefan Monnier
2020-12-16 15:36         ` Eli Zaretskii
2020-12-15 18:57 ` Stephen Leake
2020-12-15 21:35   ` Stefan Monnier
2020-12-16  5:43   ` Richard Stallman
2020-12-16  8:33   ` Tim Cross
2020-12-17  5:55     ` Richard Stallman
2020-12-16  9:00   ` Alfred M. Szmidt
2020-12-15 19:03 ` Stephen Leake
2020-12-15 21:43 ` Jonas Bernoulli
2020-12-15 22:34   ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC=50j_M6x_Pz3ddiNRPp=SgySBxKiqx1q1kY3Da8_H0GQC=TA@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.