Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Emily Shaffer <nasamuffin@google.com>,  git@vger.kernel.org
Subject: Re: [PATCH] Documentation: propose community voting process
Date: Thu, 22 Oct 2026 21:48:33 -0700	[thread overview]
Message-ID: <xmqq4iedc99a.fsf@gitster.g> (raw)
In-Reply-To: <b36dcec9-ad9c-4ddd-b3e1-e246d2fc093e@gmail.com> (Phillip Wood's message of "Thu, 22 Oct 2026 11:01:44 +0100")

Phillip Wood <phillip.wood123@gmail.com> writes:

> I agree we want to include those who contribute more widely, but I think 
> restricting the criteria to contributions on the mailing list where the 
> development of git takes place and the impact of any decision will be 
> felt the most is a reasonable place to draw the line. I'm not sure how 
> easy it is going to be to count reviews - does posting "LGTM" count or 
> do we want a more substantial contribution? Should verified bug reports 
> count? - that's also a useful contribution to the project.

We have patches focusing on documentation as well.  I do not think
commit count necessarily gives undue advantage to code contributors.

> I also think it would be sensible to restrict eligibility to the current 
> set of active contributors, who will have to live with the consequences 
> of the decision, by requiring eligible contributions to have been made 
> in the previous two years. I have historic contributions in a couple of 
> projects that I'm not active in anymore and I would not expect to be 
> able to influence an decisions those projects make now.

But do you care about these past projects enough to (1) notice that
they are having a policy discussion, (2) bother visiting them again
to learn their current voting procedures, and (3) actually cast a
vote to help improve them?  You may not have been active recently,
but if you care enough, and if your past knowledge of how the
project works still applies, wouldn't the project participants
appreciate your input?

I would recommend reducing the number and complexity of conditions.
Immediately after you say "last two years", I can hear someone else
arguing "too short -- why not three?" or "too long -- why not one?".
I previously mentioned "topic count", but commits are far easier to
count.  So instead of requiring two topics in released versions,
perhaps requiring five commits would be easier to implement and
explain.


  reply	other threads:[~2026-10-23  4:48 UTC|newest]

Thread overview: 39+ 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 [this message]
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-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-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-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-23  4:51         ` Kristoffer Haugsbakk
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=xmqq4iedc99a.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.com \
    --cc=phillip.wood123@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox