From: "Ludovic Courtès" <ludo@gnu.org>
To: david larsson <david.larsson@selfhosted.xyz>
Cc: Ricardo Wurmus <rekado@elephly.net>,
guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Guix-devel
<guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org>
Subject: Re: Formalizing teams
Date: Fri, 01 Apr 2022 11:14:34 +0200 [thread overview]
Message-ID: <87h77dnp1h.fsf@gnu.org> (raw)
In-Reply-To: <87af3b65ad24f3543914cdc6abe88d8a@selfhosted.xyz> (david larsson's message of "Thu, 31 Mar 2022 23:15:44 +0200")
Hi David,
david larsson <david.larsson@selfhosted.xyz> skribis:
> On 2022-01-03 16:22, Ludovic Courtès wrote:
[...]
>> This brings a related but slightly different topic: how to let
>> people
>> filter incoming patches and bug reports in general.
>> How does it even work on git*.com? Do they let you subscribe to
>> issues/merge requests that match certain patterns or touch certain
>> files?
>
> github.com uses CODEOWNERS file which is well described here:
> https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#about-code-owners
Yes, I like that approach; I suppose mumi could parse and honor such a
file with relatively little effort. (I’d suggest “CODEFELLOWS” or a
similar name, but that’s another story. :-))
Ludo’.
next prev parent reply other threads:[~2022-04-01 9:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:46 Formalizing teams Ludovic Courtès
2021-12-22 16:04 ` Jack Hill
2021-12-22 16:22 ` indieterminacy
2021-12-22 19:43 ` Filip Łajszczak
2022-01-03 15:09 ` Ludovic Courtès
2021-12-27 5:17 ` Maxim Cournoyer
2021-12-28 10:52 ` Lars-Dominik Braun
2021-12-28 15:44 ` Kyle Meyer
2021-12-28 18:03 ` Ricardo Wurmus
2021-12-29 21:04 ` Lars-Dominik Braun
2021-12-28 14:44 ` Ricardo Wurmus
2021-12-29 9:05 ` Efraim Flashner
2022-01-03 15:22 ` Ludovic Courtès
2022-01-03 15:57 ` Ricardo Wurmus
2022-01-04 22:35 ` adriano
2022-03-31 21:15 ` david larsson
2022-04-01 9:14 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 15:13 Blake Shaw
2021-12-23 21:51 ` Jonathan McHugh
2021-12-24 12:23 ` Hartmut Goebel
2021-12-24 15:37 ` indieterminacy
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=87h77dnp1h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david.larsson@selfhosted.xyz \
--cc=guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rekado@elephly.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).