Re: Promoting Git developers

["Jason St. John" <jstjohn@purdue.edu>]

On Tue, Mar 10, 2015 at 1:23 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> I don't want to write again about each of these points now. I am more
>> interested in discussing a good strategy to try to revert the sad
>> trend of Git developers being promoted less and less, because I think
>> that it is really very important.
>
> I would suspect that those who agree with you would appreciate if
> you or somebody volunteered to act as our CKDO (chief kudos
> distribution officer).  I do not think I have enough time to do that
> well.  One good place to start might be to scan the list and
> summarize something like the following on weekly or monthly basis,
> as these are not something you can get by pointing people to "git
> shortlog" output.
>
>  - Those who gave helpful review comments, "how about going this
>    way" illustration patches, etc.  Bonus points to those who helped
>    onboarding newcomers.
>
>  - Those who asked pertinent questions on common pain points, and
>    those who answered them helpfully.
>
> If you are more ambitious, the source of the kudos may want to cover
> activities outside of this mailing list (e.g. giving talks and
> tutorials at conferences, etc.).
>

I don't know how feasible or desirable this would be, but I'll offer
it anyway. In the Git release notes for something like "git foo
learned a new option --bar", a simple "(Thanks|Kudos) to John Smith"
at the end of each bullet point may be a good way to recognize
developers in a concise manner without needing to dig through the
output of "git log" or "git shortlog".

Or if that would make the release notes too cumbersome to review, what
about using systemd's method? systemd's release notes include a
"contributions from" section at the very end that lists everyone with
a patch included in the release.

> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html