From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Nomen Nescio <nobody@dizum.com>, git@vger.kernel.org
Subject: Re: Consensus on a new default branch name
Date: Tue, 16 Jun 2020 10:38:16 -0400 [thread overview]
Message-ID: <20200616143816.GN666057@coredump.intra.peff.net> (raw)
In-Reply-To: <20200616022239.GD164606@google.com>
On Mon, Jun 15, 2020 at 07:22:39PM -0700, Jonathan Nieder wrote:
> In Git, we make most decisions by a rough consensus of active
> contributors, as judged by the maintainer.[...]
Thanks for writing this out. I agree completely with how you described
the decision making process.
We do bear the responsibility to think carefully about our users, and to
respect their time, and their expectations that things don't break. But
as with any feature, it's a juggling act between stability and progress
that developers and the maintainer must deal with. Somebody might not
care about this name change, but likewise, others might not care about a
particular technical feature. At some point users have to put their
trust in Git's developers that the end product will be stable and
useful. If we break that trust too much, then forking is an option, as
you note. Our track record has been pretty good so far, and I think if
we approach this change carefully, it can continue to be.
-Peff
next prev parent reply other threads:[~2020-06-16 14:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 1:58 Consensus on a new default branch name Nomen Nescio
2020-06-16 2:22 ` Jonathan Nieder
2020-06-16 2:31 ` Taylor Blau
2020-06-16 14:38 ` Jeff King [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-17 0:01 Anonymous Remailer (austria)
2020-06-15 20:57 Taylor Blau
2020-06-15 21:10 ` Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31 ` Jeff King
2020-06-16 14:52 ` Oleg
2020-06-16 16:00 ` Jeff King
2020-06-16 17:11 ` Oleg
2020-06-16 17:32 ` Konstantin Ryabitsev
2020-06-16 18:54 ` Oleg
2020-06-16 22:18 ` Jeff King
2020-06-16 16:10 ` Konstantin Ryabitsev
2020-06-16 16:13 ` Santiago Torres Arias
2020-06-16 16:48 ` Jeff King
2020-06-16 16:14 ` Jason Pyeron
2020-06-16 16:47 ` Jeff King
2020-06-16 17:44 ` Steve Litt
2020-06-16 19:00 ` Oleg
2020-06-17 18:06 ` Michal Suchánek
2020-07-01 17:31 ` Michal Suchánek
2020-07-01 21:57 ` Jeff King
2020-07-02 12:21 ` Whinis
2020-07-02 21:15 ` Philip Oakley
2020-07-02 21:59 ` Whinis
2020-07-02 22:47 ` Philip Oakley
2020-07-02 23:08 ` Whinis
2020-07-01 22:25 ` Jonathan Nieder
2020-06-15 22:38 ` Elijah Newren
2020-06-16 14:32 ` Jeff King
2020-06-17 20:13 ` Junio C Hamano
2020-06-15 23:24 ` brian m. carlson
2020-06-16 0:50 ` James Ramsay
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=20200616143816.GN666057@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=nobody@dizum.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).