From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: "Jason St. John" <jstjohn@purdue•edu>,
Christian Couder <christian.couder@gmail•com>,
Michael J Gruber <git@drmicha•warpmail.net>,
David Kastrup <dak@gnu•org>, git <git@vger•kernel.org>
Subject: Re: Promoting Git developers
Date: Thu, 12 Mar 2015 15:58:24 -0700 [thread overview]
Message-ID: <xmqq7ful257z.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150312223836.GB24492@peff.net> (Jeff King's message of "Thu, 12 Mar 2015 18:38:36 -0400")
Jeff King <peff@peff•net> writes:
> Seeing my name in "shortlog" was nice, but not that exciting. I
> submitted a patch, it was taken, and of course it ends up in any
> automated lists of authors. What was much more rewarding was being
> mentioned specifically in "A note from the maintainer" as a helpful
> person. That had much more value because:
>
> 1. It was one of a handful of names.
>
> 2. It was picked by a human.
>
> So in that sense, it is quite the opposite of including shortlog output
> in the release announcements (I still think the shortlog thing we have
> been discussing is a good thing, but not at the same level).
Yes, and that cuts both ways, unfortunately. There always will be "I
am doing more reviews than X and my reviews are higher quality. Why
was X singled out and got thanked but not me?", "X is really doing a
good job reviewing in this cycle, but could other people who send
reviews of lessor quality (to my mind) feel that it is unjustified
if I thanked X and nobody else?", etc. A mechanically generated list
avoids these issues, but the satisfaction you get from being on the
list is not very high, exactly because it is not hand picked.
> I do not know that it is worth having a "Best of 2015" Git awards
> ceremony, but it is sometimes nice to thank people personally when
> you appreciate their efforts. I sometimes mail people off-list to
> do so.
Yeah, I do the same, but revealing that we do so would defeat what
we tried to achieve by doing so off-list in the first place. Now
those who haven't got such a piece of e-mail for a while can start
to suspect that they have fallen out of favour or something ;-(.
next prev parent reply other threads:[~2015-03-12 22:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 7:18 Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-09 13:57 ` Michael J Gruber
2015-03-09 14:31 ` Promoting Git developers David Kastrup
2015-03-09 18:32 ` Philip Oakley
2015-03-10 7:45 ` Junio C Hamano
2015-03-10 11:51 ` Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-10 17:23 ` Promoting Git developers Junio C Hamano
2015-03-11 1:04 ` Jason St. John
2015-03-11 2:13 ` Duy Nguyen
2015-03-11 4:16 ` Junio C Hamano
2015-03-12 2:15 ` Duy Nguyen
2015-03-12 4:53 ` Junio C Hamano
2015-03-12 7:45 ` Fredrik Gustafsson
2015-03-12 18:43 ` Junio C Hamano
2015-03-11 2:36 ` Junio C Hamano
2015-03-11 7:31 ` Jeff King
2015-03-11 7:38 ` Junio C Hamano
2015-03-11 7:54 ` Jeff King
2015-03-11 21:28 ` Junio C Hamano
2015-03-11 23:17 ` Andrew Ardill
2015-03-12 22:31 ` Jeff King
2015-03-12 22:36 ` Junio C Hamano
2015-03-12 22:43 ` Jeff King
2015-03-12 5:05 ` Junio C Hamano
2015-03-12 22:38 ` Jeff King
2015-03-12 22:58 ` Junio C Hamano [this message]
2015-03-15 9:12 ` Christian Couder
2015-03-11 13:53 ` Christian Couder
2015-03-11 20:42 ` Junio C Hamano
2015-03-15 8:46 ` Christian Couder
2015-03-15 22:18 ` Junio C Hamano
2015-03-15 22:43 ` Randall S. Becker
2015-03-16 9:10 ` Christian Couder
2015-03-16 9:20 ` David Kastrup
2015-03-16 17:06 ` Stefan Beller
2015-03-17 20:08 ` Christian Couder
2015-03-17 20:16 ` Junio C Hamano
2015-03-16 23:39 ` David Lang
2015-03-17 5:25 ` Junio C Hamano
2015-03-17 5:56 ` David Lang
2015-03-17 20:15 ` Christian Couder
2015-03-17 9:43 ` Thomas Ferris Nicolaisen
2015-03-17 19:51 ` 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=xmqq7ful257z.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=dak@gnu$(echo .)org \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=jstjohn@purdue$(echo .)edu \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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