From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Emily Shaffer <emilyshaffer@google.com>,
git@vger.kernel.org, jrnieder@gmail.com,
jonathantanmy@google.com, steadmon@google.com,
chooglen@google.com, calvinwan@google.com,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
rsbecker@nexbridge.com
Subject: Re: Review process improvements
Date: Tue, 21 Dec 2021 01:47:24 +0000 [thread overview]
Message-ID: <YcEyLMkM3fvGYCUY@camp.crustytoothpaste.net> (raw)
In-Reply-To: <211220.86fsqnwkzs.gmgdl@evledraar.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On 2021-12-20 at 11:22:32, Ævar Arnfjörð Bjarmason wrote:
> E.g. I've often chimed in on changes to do withn how/whether something
> can/should be marked for translation. I added the i18n subsystem
> initiall, so for those cases interested parties would probably find me
> anyway, but I wouldn't mind being explicit about that. Ditto for people
> we consider the authority on certain subsystems, such as (this may not
> be any one person currently), refs, the index, SHA1<->SHA256 interop
> etc.
I have limited time for the list, but I also tend to pop in on certain
topics: the SHA-256 transition, commit and tag signing, authentication,
translations, and so on. However, outside of the signing code, a lot of
that isn't centralized in one place.
I also wouldn't be able to commit to signing up for any subsystem in a
MAINTAINERS file, but I'm happy to be CC'd if folks think I'm
knowledgeable about something or if it's an area they think my opinion
would be valuable.
I can't speak for others, though, so I don't know if a MAINTAINERS-style
approach would be valuable for them.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2021-12-21 1:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 22:46 Review process improvements Emily Shaffer
2021-12-16 23:22 ` rsbecker
2021-12-17 0:05 ` Junio C Hamano
2021-12-17 18:39 ` Konstantin Ryabitsev
2021-12-20 10:48 ` Christian Couder
2021-12-20 12:29 ` Mark Brown
2021-12-22 3:26 ` Ævar Arnfjörð Bjarmason
2021-12-22 13:07 ` Fabian Stelzer
2021-12-22 15:45 ` Konstantin Ryabitsev
2021-12-22 19:42 ` Junio C Hamano
2021-12-22 21:32 ` Konstantin Ryabitsev
2022-01-10 13:03 ` Why GitGitGadget does not use Sender:, was " Johannes Schindelin
2022-01-10 17:13 ` Junio C Hamano
2021-12-23 13:50 ` Stefan Hajnoczi
2021-12-20 11:22 ` Ævar Arnfjörð Bjarmason
2021-12-20 17:14 ` Eric Sunshine
2021-12-20 21:27 ` João Victor Bonfim
2022-01-05 1:02 ` Emily Shaffer
2022-01-09 3:26 ` João Victor Bonfim
2021-12-21 1:47 ` brian m. carlson [this message]
2022-01-05 0:45 ` Emily Shaffer
2022-01-09 8:26 ` Matthias Aßhauer
-- strict thread matches above, loose matches on Subject: below --
2021-12-20 3:35 João Victor Bonfim
2021-12-20 3:47 ` João Victor Bonfim
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=YcEyLMkM3fvGYCUY@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=avarab@gmail.com \
--cc=calvinwan@google.com \
--cc=chooglen@google.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=rsbecker@nexbridge.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.
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.