From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Google Summer of Code '07 application
Date: Sat, 10 Mar 2007 07:06:25 +0000 [thread overview]
Message-ID: <200703100706.28375.andyparkins@gmail.com> (raw)
In-Reply-To: <7vk5xq5atd.fsf@assigned-by-dhcp.cox.net>
On Friday 2007, March 09, Junio C Hamano wrote:
> But one thing I think everybody can be proud of about this
> community is that we haven't had any meaningless flamewar at
> all. Even the discussions on the hotter side in the past,
> perhaps primarily coming from crashing cultures, tended to
> produce useful improvements.
I have to agree. As a relative newbie, and all-round submitter of
opinions but not code, I have to say that the thing that keeps me
attached to the git project where I have never become involved with
other projects is that even when you are getting blasted and argued
with and told you are wrong, everyone uses logical arguments; points
are taken seriously and addressed under the assumption that the
questioner is not an idiot. This is different to the usual "that's
just how it is, if you don't like it why don't you fork the project".
> One example that comes to my mind is the UI change in 1.5.0. It
> started when Carl Worth was sufficiently irritated by how
> different and inapproachable git was to new people, and at some
> point the discussion almost went near "well, distributed is
> different from CVS, so shut up and come back later when your CVS
> braindamange is healed", but we quite didn't go that way.
> Instead, the discussion resulted in the "usability and
> teachability" theme.
It's this attitude that encouraged me to write and post my git-niggles
list. It was a pleasure to see positive responses, and then see Shawn
posting patches that addressed some of them. I would never have dared
post something so potentially-controversial if I hadn't seen that
people rarely get shouted down on the list.
I'd like to reiterate though - I don't think that it is the /acceptance/
of ideas that makes the git community strong - it is that ideas are
taken seriously. For me, I don't mind if something I suggest is
ignored, never implemented or disagreed with; all I am actually after
is the feeling that someone listened to me and understood what I was
asking for. "I like it but I'm not going to implement it", "here's
where you would go if you wanted to implement that", "I see what you're
asking for but I think that it's better to do it like this" are all
highly acceptable responses. Surprisingly, responses like this are
not the norm in many projects. Equivalents of "Get the hell off our
mailing list" /are/ common.
In short - the thing that makes the git community great, is not their
friendliness or their willingness to implement every request that comes
along, it is the attitude that most people are not idiots and that
every idea merits listening to.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-03-10 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 5:07 Google Summer of Code '07 application Shawn O. Pearce
2007-03-09 2:21 ` Shawn O. Pearce
2007-03-09 6:01 ` J. Bruce Fields
2007-03-09 15:39 ` Shawn O. Pearce
2007-03-09 22:09 ` Junio C Hamano
2007-03-10 7:06 ` Andy Parkins [this message]
2007-03-10 17:39 ` J. Bruce Fields
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=200703100706.28375.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.org \
/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).