git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Josh Steadmon <steadmon@google.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, avarab@gmail.com,
	christian.couder@gmail.com, Enrico Mrass <emrass@google.com>,
	Emily Shaffer <nasamuffin@google.com>
Subject: Re: [RFC PATCH] doc: describe the project's decision-making process
Date: Mon, 6 May 2024 16:17:03 -0400	[thread overview]
Message-ID: <Zjk6v3Y7zJqtPVVq@nand.local> (raw)
In-Reply-To: <mdgbdajenbv23r63hreieemielgdtdkwjzb65pdv3b4rylyyxi@4d3eeymtjvva>

On Mon, May 06, 2024 at 12:36:06PM -0700, Josh Steadmon wrote:
> How would you feel about a doc outlining how the process changes as you
> go from: A) small/medium patch series, to B) larger discussions with
> (parts of) the proposal recorded in patches, to C) large discussions
> with no patches? This is the structure I'm leaning towards for my V2
> draft.

That sounds like a reasonable direction to take.

> > Another way of thinking about this is that I would be extremely
> > reluctant to see a similar document proposed for reviewing at the patch
> > series level. In my opinion, the system of reviewers and participants
> > discussing the series and the maintainer solely determining whether or
> > not consensus has been reached is a good one, and I would be extremely
> > hesitant to recommend changing it.
>
> Sorry, I'm not sure I understand why you wouldn't want the patch series
> process documented? I'm just trying to capture the status quo, not to
> propose or recommend any changes.

Apologies, I misspoke here. I don't mean to say that such a document
shouldn't exist, but rather that I'd be hesitant to see a prescriptive
document outlining how patches are reviewed at too granular a level.

Having a document like Documentation/ReviewingGuidelines.txt makes sense
to me and seems like a good thing to keep.

Thanks,
Taylor


  reply	other threads:[~2024-05-06 20:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 23:20 [RFC PATCH] doc: describe the project's decision-making process Josh Steadmon
2024-04-16  0:24 ` Junio C Hamano
2024-04-22 21:10   ` Josh Steadmon
2024-04-22 21:30     ` Junio C Hamano
2024-04-23 22:41       ` Junio C Hamano
2024-04-17 16:32 ` Enrico Mrass
2024-04-17 16:58   ` Junio C Hamano
2024-05-03 14:45     ` Junio C Hamano
2024-05-03 15:48       ` Josh Steadmon
2024-05-03 18:08         ` Junio C Hamano
2024-05-03 19:29           ` Taylor Blau
2024-05-06  7:12             ` Patrick Steinhardt
2024-05-06 20:14               ` Taylor Blau
2024-05-06 19:36             ` Josh Steadmon
2024-05-06 20:17               ` Taylor Blau [this message]
2024-04-22 18:41 ` Emily Shaffer
2024-04-22 19:18   ` Junio C Hamano
2024-04-22 21:12     ` Emily Shaffer
2024-04-23  1:10   ` Junio C Hamano
2024-05-09  0:01 ` [PATCH v2] " Josh Steadmon
2024-05-09 18:10   ` Junio C Hamano
2024-05-09 19:20     ` Junio C Hamano
2024-05-09 21:13       ` [PATCH 0/2] Describe patch-flow better in SubmittingPatches Junio C Hamano
2024-05-09 21:13         ` [PATCH 1/2] SubmittingPatches: move the patch-flow section earlier Junio C Hamano
2024-05-09 21:13         ` [PATCH 2/2] SubmittingPatches: extend the "flow" section Junio C Hamano
2024-05-10 10:08           ` Karthik Nayak
2024-05-10 15:59             ` Junio C Hamano
2024-05-10 19:09               ` Karthik Nayak
2024-05-10 16:55       ` [PATCH v2 0/2] Describe life cycle of a patch series Junio C Hamano
2024-05-10 16:55         ` [PATCH v2 1/2] SubmittingPatches: move the patch-flow section earlier Junio C Hamano
2024-05-10 16:55         ` [PATCH v2 2/2] SubmittingPatches: extend the "flow" section Junio C Hamano
2024-05-10 16:56         ` [PATCH] decisions: focus on larger scale issues Junio C Hamano
2024-05-15 20:36           ` Josh Steadmon
2024-05-15 20:50             ` Junio C Hamano
2024-05-15 20:35         ` [PATCH v2 0/2] Describe life cycle of a patch series Josh Steadmon
2024-05-16 21:20 ` [PATCH v3] doc: describe the project's decision-making process Josh Steadmon
2024-05-16 22:01   ` Junio C Hamano
2024-05-17 20:18     ` Josh Steadmon
2024-05-17  6:29   ` Patrick Steinhardt
2024-05-17 16:40     ` Junio C Hamano
2024-05-17 20:35 ` [PATCH v4] " Josh Steadmon
2024-05-17 22:12   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zjk6v3Y7zJqtPVVq@nand.local \
    --to=me@ttaylorr.com \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=emrass@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nasamuffin@google.com \
    --cc=steadmon@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).