Re: [PATCH] Documentation: propose community voting process
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 30, 2026, 17:18 UTC
- Message-ID
- <xmqqse1nw1hj.fsf@gitster.g>
- In-Reply-To
- <CAJoAoZnqzKv8ocsi1a-nC6LaRnpKKCO0Bxt-Pdn0dDUziEcpAg@mail.gmail.com>
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.