All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
	David Kastrup <dak@gnu.org>, git <git@vger.kernel.org>,
	Jeff King <peff@peff.net>, Scott Chacon <schacon@gmail.com>
Subject: Re: Promoting Git developers
Date: Sun, 15 Mar 2015 09:46:28 +0100	[thread overview]
Message-ID: <CAP8UFD2ba3jQSsQrGGWM-8HTfGR+zZhmbkxiEBhSR+Ho=B0MuA@mail.gmail.com> (raw)
In-Reply-To: <xmqqfv9b5krc.fsf@gitster.dls.corp.google.com>

On Wed, Mar 11, 2015 at 9:42 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> On Tue, Mar 10, 2015 at 6:23 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>>
>>> 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.
>>
>> Ok, I can start something about this two points every week or every
>> few week. It would be best if I could get help from at least one
>> person as I think it is a lot of work.
>
> No kidding; even though it may no longer be an impossibly large task
> as in the infrationary epoch reported in the Git Traffic, this forum
> is still a high traffic place.

I wrote something about a potential Git Rev News news letter:

https://github.com/git/git.github.io/pull/15

Peff, could you give me write access so that I don't need to send pull requests?
If some people are interested to contribute even if it is only
sporadically, I would suggest they ask for write access too.

>> I also appreciate very much that you are willing to improve the
>> release notes by adding a summary with people's names.
>
> Just in case you misunderstood, I do not think it is a good idea to
> add names to release notes and I will not do so.
>
> I was and am planning add the list of contributors at the end of the
> e-mail when the release notes is sent out, i.e. in the "Announce"
> message that is sent to the list (and CC'ed to lwn.net).

Ok, that is already very nice.

Thanks,
Christian.

  reply	other threads:[~2015-03-15  8:46 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
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 [this message]
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='CAP8UFD2ba3jQSsQrGGWM-8HTfGR+zZhmbkxiEBhSR+Ho=B0MuA@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=schacon@gmail.com \
    /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.