git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	Git List <git@vger.kernel.org>,
	Jonathan Nieder <jrnieder@gmail.com>,
	A Large Angry SCM <gitzilla@gmail.com>
Subject: Re: [PATCH] Documentation/CommunityGuidelines
Date: Tue, 11 Jun 2013 13:55:48 -0700	[thread overview]
Message-ID: <7va9mw9xkb.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130611203303.GA14907@sigill.intra.peff.net> (Jeff King's message of "Tue, 11 Jun 2013 16:33:03 -0400")

Jeff King <peff@peff.net> writes:

> So there are no hard rules, and this is not a democracy[1]. For the most
> part the community runs itself in an open and collective fashion, and
> the dictator's job is easy; but ultimately, he or she is in charge of
> what gets applied and what doesn't. Rules like "break ties in favor of
> reviewers" are just a guideline for the dictator to use in making
> decisions.
>
> I do not think any of that is news to you, but I think the point needs
> to be made, as it applies to any concrete rules.

My original draft had "I am hoping we do not have to come to that"
after "(I heard some communities break ties this way)", but I
removed it by mistake.

And I think you are right. I also am hoping that I am being fair to
dictate ;-)


> -Peff
>
> [1] Note that I think a benevolent dictator is a _terrible_ way to run a
>     real government, but it works in an open source project. I think the
>     difference is that dictatorship is open to abuse of power. In the
>     real world, there is a lot of power to abuse, and it is hard for
>     people to opt out of it. In the open source world, there is not that
>     much power, and if there is a bad dictator everyone can go somewhere
>     else (another project, or even a fork). So while a dictator _can_
>     play favorites, or start deciding which patches to take based on
>     what they had for breakfast, there is a real incentive to remain
>     fair and reasonable.

  reply	other threads:[~2013-06-11 20:55 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 13:28 [PATCH] Documentation/CommunityGuidelines Ramkumar Ramachandra
2013-06-10 13:50 ` Célestin Matte
2013-06-10 14:04   ` Matthieu Moy
2013-06-10 16:25     ` Robin H. Johnson
2013-06-10 17:42       ` Junio C Hamano
2013-06-10 19:01         ` Jonathan Nieder
2013-06-10 19:45           ` Ramkumar Ramachandra
2013-06-10 20:41             ` A Large Angry SCM
2013-06-10 20:56               ` Ramkumar Ramachandra
2013-06-10 21:09                 ` A Large Angry SCM
2013-06-11  5:16         ` Felipe Contreras
2013-06-11  8:56         ` Ramkumar Ramachandra
2013-06-11  4:41 ` Michael Haggerty
2013-06-11  6:28   ` Felipe Contreras
2013-06-11 10:45   ` Ramkumar Ramachandra
2013-06-11 11:49     ` Felipe Contreras
2013-06-11 12:33     ` Thomas Rast
2013-06-11 13:40       ` Ramkumar Ramachandra
2013-06-11 14:40         ` Michael Haggerty
2013-06-11 15:34           ` Felipe Contreras
2013-06-11 18:16           ` Ramkumar Ramachandra
2013-06-11 18:43             ` Michael Haggerty
2013-06-11 18:55               ` Ramkumar Ramachandra
2013-06-11 19:06                 ` Junio C Hamano
2013-06-11 19:39                   ` Felipe Contreras
2013-06-11 23:48               ` Felipe Contreras
2013-06-11 19:55           ` Brandon Casey
2013-06-12 11:56         ` Theodore Ts'o
2013-06-12 12:29           ` Ramkumar Ramachandra
2013-06-12 13:58           ` Felipe Contreras
2013-06-11 15:06       ` Felipe Contreras
2013-06-11 15:41         ` Thomas Rast
2013-06-11 15:52           ` Felipe Contreras
2013-06-11 16:10   ` Thomas Rast
2013-06-11 16:17     ` Felipe Contreras
2013-06-11 17:00   ` Junio C Hamano
2013-06-11 18:24     ` Michael Haggerty
2013-06-11 18:29     ` John Keeping
2013-06-11 18:46       ` Ramkumar Ramachandra
2013-06-11 19:54         ` John Keeping
2013-06-12 11:26           ` Ramkumar Ramachandra
2013-06-12 13:14             ` John Keeping
2013-06-11 18:52       ` Michael Haggerty
2013-06-11 19:19         ` John Keeping
2013-06-11 19:46         ` Philip Oakley
2013-06-12  0:08           ` John Szakmeister
2013-06-12 14:49           ` Jakub Narebski
2013-06-12 20:54             ` Philip Oakley
2013-06-11 19:35       ` Felipe Contreras
2013-06-11 20:33     ` Jeff King
2013-06-11 20:55       ` Junio C Hamano [this message]
2013-06-11 23:19         ` Felipe Contreras
2013-06-12 12:27           ` Theodore Ts'o
2013-06-12 14:06             ` Felipe Contreras
2013-06-12 12:03       ` Ramkumar Ramachandra
2013-06-12 20:02   ` Junio C Hamano
2013-06-13  3:45     ` Michael Haggerty
2013-06-13  4:22       ` Junio C Hamano
2013-06-11  5:38 ` Felipe Contreras
2013-06-11 11:11   ` Ramkumar Ramachandra
2013-06-13 10:19 ` Thomas Adam
2013-06-13 13:36   ` Felipe Contreras
2013-06-14  9:48   ` Christian Couder

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=7va9mw9xkb.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitzilla@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=mhagger@alum.mit.edu \
    --cc=peff@peff.net \
    /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.
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 NNTP newsgroup(s).