From: Thomas Rast <trast@inf.ethz.ch>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
"A Large Angry SCM" <gitzilla@gmail.com>
Subject: Re: [PATCH] Documentation/CommunityGuidelines
Date: Tue, 11 Jun 2013 14:33:12 +0200 [thread overview]
Message-ID: <87li6g969j.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <CALkWK0nNn8Rcu4JpV4r+0ct+_cuW3aUHXKV4bcB-Hn6Xg8Y+bA@mail.gmail.com> (Ramkumar Ramachandra's message of "Tue, 11 Jun 2013 16:15:12 +0530")
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> Michael Haggerty wrote:
>> Thank you for drafting a proposed CommunityGuidelines document; I think
>> such a document would be helpful. But I don't like the overall flavor
>> of your proposal; frankly, it sounds to me more like
>>
>> Documentation/GuidelinesForCommunityToBendOverBackwardsToLiveWithFCsProvocations
>
> It has nothing to do with Felipe. I've merely documented repeating
> patterns in fire threads as violations, in an attempt to avoid fires.
> I have not worked forward from axioms to derive "transcendentally
> desirable behavior", but rather backwards from a disaster to derive
> "patterns that have been shown to lead to large fires". Why? Because
> it's easier to derive unambiguous statements using my approach; as I
> will show shortly, there are various problems with your arguments.
>
> What gives you the impression that I documented everyone else's
> violations, but not Felipe's? ;)
It has become clear, also in discussion on IRC, that your preferred
approach is to fight the fires, attempting to extinguish flames as they
happen.
My approach -- and in my perception also that preferred by most of the
regulars who have spoken in this whole mess -- is that since there is a
fire hazard, it would be more effective firefighting to just remove the
hazard, thus preventing future fires.
I infer that in your view, there is an inalienable right for the fire
hazard to remain part of the community that you are not willing to give
up. I for one no longer have such qualms in this instance.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-06-11 12:33 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 [this message]
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
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=87li6g969j.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf.ethz.ch \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
/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 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.