From: Emily Shaffer <nasamuffin@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Josh Steadmon <steadmon@google.com>,
git@vger.kernel.org, avarab@gmail.com,
christian.couder@gmail.com, me@ttaylorr.com,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [RFC PATCH] doc: describe the project's decision-making process
Date: Mon, 22 Apr 2024 14:12:10 -0700 [thread overview]
Message-ID: <CAJoAoZmR37h5XLa4NnJ+5iZfLNJVfzBgRs4bvaJN4sa=UDtxNw@mail.gmail.com> (raw)
In-Reply-To: <xmqq1q6xw6hv.fsf@gitster.g>
On Mon, Apr 22, 2024 at 12:18 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Emily Shaffer <nasamuffin@google.com> writes:
>
> > Thanks for writing this. I, for one, would love to see the process
> > evolve a little to account for the scale of work coming through the
> > list on any given day. However, that's a discussion that will be
> > easier to have once we have the status quo written and checked in.
> > ...
> > So, if nobody disagrees with the content of this document, I think we
> > should absolutely merge it. It will be great for newbies to see what
> > they're getting into, and for me to send to my boss to explain why my
> > predictions for my team's patches landing are so broad.
>
> Isn't it a bit too late to say "if nobody disagrees with", after it
> was pointed out that the world around here does not work that way
> (yet) about a week ago?
Well, so far we heard from one person who perceives it as status quo
(the author), one person new to the project, the maintainer, and me :)
I think Josh is working on a v2 with links as you asked.
I have certainly followed the process Josh described here for a couple
of large projects coming from my team - to mind, config-based hooks,
submodules UX proposal, and libification proposal all came with
discussion before any patches. I'd love to hear from others who have
been implementing large-scale changes in a different way, like brian,
or Taylor and the other GitHub folks, too - if this patch is too
different from what actually happens with their work, let's trim until
it isn't, instead.
>
> If we have an agreeable v2 already posted on the list that I missed,
> then sorry, please disregard the above comment.
>
> I still don't think it captures "the status quo", which is what you
> want this document to be, about "larger-scale decisions", as the
> Introduction of the document says. Can we have a set of pointers in
> the document, when it gets rerolled, to an actual example of how we
> made such a larger-scale decision? Without such illustration with a
> real world example, it looks to me that what it describes is what we
> wish the process to be (which is not necessarily I would object to),
> but labeling it as "describing the status quo" is very much
> objectionable.
>
> Thanks.
next prev parent reply other threads:[~2024-04-22 21:12 UTC|newest]
Thread overview: 44+ 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
2024-04-22 18:41 ` Emily Shaffer
2024-04-22 19:18 ` Junio C Hamano
2024-04-22 21:12 ` Emily Shaffer [this message]
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-21 5:56 ` Patrick Steinhardt
2024-05-17 20:35 ` [PATCH v4] " Josh Steadmon
2024-05-17 22:12 ` Junio C Hamano
2024-05-21 5:58 ` Patrick Steinhardt
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='CAJoAoZmR37h5XLa4NnJ+5iZfLNJVfzBgRs4bvaJN4sa=UDtxNw@mail.gmail.com' \
--to=nasamuffin@google.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=sandals@crustytoothpaste.net \
--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.
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).