All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: Patrick Steinhardt <ps@pks.im>,  Jeff King <peff@peff.net>,
	 Tuomas Ahola <taahol@utu.fi>,
	 Phillip Wood <phillip.wood123@gmail.com>,
	git@vger.kernel.org,  Justin Tobler <jltobler@gmail.com>
Subject: Re: [PATCH] Documentation: propose community voting process
Date: Fri, 30 Oct 2026 10:18:48 -0700	[thread overview]
Message-ID: <xmqqse1nw1hj.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZnqzKv8ocsi1a-nC6LaRnpKKCO0Bxt-Pdn0dDUziEcpAg@mail.gmail.com> (Emily Shaffer's message of "Fri, 30 Oct 2026 09:50:41 -0700")

Emily Shaffer <nasamuffin@google.com> writes:

> I mentioned this in another thread as well, but for full transparency,
> I'm feeling a little bias here because I haven't had the capacity to
> make meaningful code contributions to the Git project in quite a few
> years ...

Drop "code".  Documentation contributions do matter.

I would love to see somebody come up with a way to transparently and
fairly tally contributions people make that are not patches.  Those
who help end-users and other developers on IRC or Discord without
writing patches themselves are still valuable members who support
the Git ecosystem.

Those who review others' patches without making their own are just
as valuable, given how much their reviews help those patch
submissions.  Those who correct mistakes end-users make and show a
better way to do what they wanted to do are valuable contributors to
this community.  There should be some complementary ways to measure
these kinds of contributions in the past N years, in addition to
counting the number of commits that hit my tree in the past N years.

  reply	other threads:[~2026-10-30 17:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 18:05 Notes from the Git Contributor's Summit, 2026 Taylor Blau
2026-10-06 18:06 ` [NOTES 01/07] Security mailing list and security process Taylor Blau
2026-10-06 18:06 ` [NOTES 02/07] Git 3.0 Taylor Blau
2026-10-06 18:06 ` [NOTES 03/07] Documentation Taylor Blau
2026-10-07  4:49   ` Todd Zullinger
2026-10-07 17:38     ` Junio C Hamano
2026-10-06 18:06 ` [NOTES 04/07] Outreachy sponsorship Taylor Blau
2026-10-06 18:06 ` [NOTES 05/07] What can we do next with pluggable ODB? Taylor Blau
2026-10-06 18:06 ` [NOTES 06/07] AI contribution policy Taylor Blau
2026-10-21 20:03   ` [PATCH] Documentation: propose community voting process Emily Shaffer
2026-10-21 20:05     ` Emily Shaffer
2026-10-22 10:01       ` Phillip Wood
2026-10-23  4:48         ` Junio C Hamano
2026-10-23 13:49           ` Phillip Wood
2026-10-23 14:18             ` Kristoffer Haugsbakk
2026-10-23 16:26               ` Junio C Hamano
2026-10-23 18:09                 ` Kristoffer Haugsbakk
2026-10-23 22:08                   ` Junio C Hamano
2026-10-23 14:31           ` Kristoffer Haugsbakk
2026-10-24 11:18           ` Tuomas Ahola
2026-10-24 13:03             ` Weijie Yuan
2026-10-30  6:35               ` Toon Claes
2026-10-30  7:18                 ` Weijie Yuan
2026-10-24 14:56             ` Junio C Hamano
2026-10-24 15:06               ` Weijie Yuan
2026-10-26  1:17             ` Jeff King
2026-10-26  3:50               ` Junio C Hamano
2026-10-26  7:57               ` Patrick Steinhardt
2026-10-26  9:23                 ` Tuomas Ahola
2026-10-30 16:50                 ` Emily Shaffer
2026-10-30 17:18                   ` Junio C Hamano [this message]
2026-10-30 18:00                   ` Jeff King
2026-10-26 10:41               ` Phillip Wood
2026-10-22 22:59       ` brian m. carlson
2026-10-21 21:22     ` Junio C Hamano
2026-10-21 22:06     ` Junio C Hamano
2026-10-22 15:35       ` Justin Tobler
2026-10-23  4:56         ` Junio C Hamano
2026-10-30 16:30       ` Emily Shaffer
2026-10-22  7:29     ` Kristoffer Haugsbakk
2026-10-22 12:44       ` Patrick Steinhardt
2026-10-22 22:51       ` brian m. carlson
2026-10-22 23:17         ` Junio C Hamano
2026-10-30 16:53           ` Emily Shaffer
2026-10-23  4:51         ` Kristoffer Haugsbakk
2026-10-30 17:15     ` Emily Shaffer
2026-10-30 17:44       ` Junio C Hamano
2026-10-06 18:06 ` [NOTES 07/07] Protocol v2 for pushes Taylor Blau

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=xmqqse1nw1hj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=nasamuffin@google.com \
    --cc=peff@peff.net \
    --cc=phillip.wood123@gmail.com \
    --cc=ps@pks.im \
    --cc=taahol@utu.fi \
    /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.