From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Christopher Baines <mail@cbaines.net>,
61894@debbugs.gnu.org, guix-maintainers@gnu.org
Subject: [bug#61894] [PATCH RFC] Team approval for patches
Date: Tue, 07 Mar 2023 09:53:29 +0800 [thread overview]
Message-ID: <87y1o9mina.fsf_-_@envs.net> (raw)
In-Reply-To: <87r0u86qgo.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Wed, 01 Mar 2023 23:45:27 +0100")
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Chris,
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> Regarding this change specifically though, I'm unclear how it would
>> impact the things I push for others. I pushed some patches today, would
>> this mean that I'd have to look at what team/teams are involved
>> (according to /etc/teams.scm.in) for each commit/series, and then either
>> continue if I'm a member of that team, or skip it if I'm not?
>>
>> If I'm going to not be pushing stuff I would have previously pushed
>> because I'm not in the relevant teams, maybe I should just add myself to
>> every team? I guess this is not a serious question, but I'm more making
>> the point that if teams become a formal part of patch review, then some
>> formalities over membership of a team is probably a prerequsite.
>>
> [...]
>
> Good questions.
>
> For teams like ‘core’ or ‘home’, there should be no overlap, so it’s
> quite easy to see who’s in charge.
> [...]
> For “random packages”, I’m fine with the status quo.
Hello, I'd like to know if I'm working fine according to the status
quo..
I usually push patches for others who don't have commit access, while
most packages don't have a team at all, and some with me as the only
team member.
Should I wait for another commiter's approvol under this new policy or
can I push "random packages" (eg: jwm) solo under the status quo? For
packages I as the only team member (eg: fcitx), should I looking for
another commiter for other's patches and my patches?
Thank you!
next prev parent reply other threads:[~2023-03-07 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 16:13 [bug#61894] [PATCH RFC] Team approval for patches Ludovic Courtès
[not found] ` <871qm8wf8e.fsf@cbaines.net>
2023-03-01 19:21 ` Felix Lechner via Guix-patches via
2023-03-01 22:45 ` Ludovic Courtès
2023-03-02 11:04 ` Andreas Enge
2023-03-07 1:53 ` 宋文武 via Guix-patches via [this message]
[not found] ` <ZAcTw6I31Rl3nRDE@jurong>
[not found] ` <861qm0da4y.fsf@gmail.com>
2023-03-07 18:29 ` Maxim Cournoyer
2023-03-07 22:40 ` Leo Famulari
[not found] ` <874jqvul1v.fsf@gmail.com>
2023-03-09 8:48 ` Simon Tournier
[not found] ` <ZAhRg7BjytZGGB5O@3900XT>
[not found] ` <878rg7uqb4.fsf@gmail.com>
[not found] ` <86lek6ntpb.fsf@gmail.com>
[not found] ` <874jqtte7c.fsf@gmail.com>
[not found] ` <87bkl0frnk.fsf@gnu.org>
[not found] ` <87356ar6p1.fsf@gmail.com>
[not found] ` <87bkku2e14.fsf@gnu.org>
2023-03-17 15:46 ` Maxim Cournoyer
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1o9mina.fsf_-_@envs.net \
--to=guix-patches@gnu.org \
--cc=61894@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=iyzsong@envs.net \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
/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://git.savannah.gnu.org/cgit/guix.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).