git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Promoting Git developers

From
Christian Couder <christian.couder@gmail.com>
Date
Mar 15, 2015, 08:46 UTC
Message-ID
<CAP8UFD2ba3jQSsQrGGWM-8HTfGR+zZhmbkxiEBhSR+Ho=B0MuA@mail.gmail.com>
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:
Show 26 quoted lines
> 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.

Show 9 quoted lines
>> 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.

Previous: Junio C HamanoNext: Junio C Hamano
Message 30 of 43 in “Promoting Git developers (was: Bashing freelancers)”
  1. Christian CouderMar 7, 2015
  2. Michael J GruberMar 9, 2015
  3. David KastrupMar 9, 2015
  4. Philip OakleyMar 9, 2015
  5. Junio C HamanoMar 10, 2015
  6. Christian CouderMar 10, 2015
  7. Junio C HamanoMar 10, 2015
  8. Jason St. JohnMar 11, 2015
  9. Duy NguyenMar 11, 2015
  10. Junio C HamanoMar 11, 2015
  11. Duy NguyenMar 12, 2015
  12. Junio C HamanoMar 12, 2015
  13. Fredrik GustafssonMar 12, 2015
  14. Junio C HamanoMar 12, 2015
  15. Junio C HamanoMar 11, 2015
  16. Jeff KingMar 11, 2015
  17. Junio C HamanoMar 11, 2015
  18. Jeff KingMar 11, 2015
  19. Junio C HamanoMar 11, 2015
  20. Andrew ArdillMar 11, 2015
  21. Jeff KingMar 12, 2015
  22. Junio C HamanoMar 12, 2015
  23. Jeff KingMar 12, 2015
  24. Junio C HamanoMar 12, 2015
  25. Jeff KingMar 12, 2015
  26. Junio C HamanoMar 12, 2015
  27. Christian CouderMar 15, 2015
  28. Christian CouderMar 11, 2015
  29. Junio C HamanoMar 11, 2015
  30. Christian CouderMar 15, 2015
  31. Junio C HamanoMar 15, 2015
  32. Randall S. BeckerMar 15, 2015
  33. Christian CouderMar 16, 2015
  34. David KastrupMar 16, 2015
  35. Stefan BellerMar 16, 2015
  36. Christian CouderMar 17, 2015
  37. Junio C HamanoMar 17, 2015
  38. David LangMar 16, 2015
  39. Junio C HamanoMar 17, 2015
  40. David LangMar 17, 2015
  41. Christian CouderMar 17, 2015
  42. Thomas Ferris NicolaisenMar 17, 2015
  43. Christian CouderMar 17, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.