From: Lars-Dominik Braun <lars@6xq.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Formalizing teams
Date: Tue, 28 Dec 2021 11:52:13 +0100 [thread overview]
Message-ID: <YcrsXVN37pSwV3k1@noor.fritz.box> (raw)
In-Reply-To: <87mtkmwrre.fsf@gmail.com>
Hi Maxim,
> I've grown to like our apparent lack of structure; we interact globally
> on any topic of interest and the discussions all happen in a shared
> space, which makes it easy to stay informed with everything that's going
> on (do we really need more mailing lists to follow? I don't think so --
> our current volume doesn't warrant it).
to me this is a disadvantage. I don’t have enough time at my hands to
look at every single thread and patch in my inbox and decide whether
I can/want to work on it. Thus I’d prefer if I could unsubscribe
from -patches (I’m not even subscribed to -bug/-commit) and instead
only look at bugs/patches/commits related to packages/components I’m
interested into/I actually use.
To that end having more structure would help. Teams are just one option,
but we need a way to efficiently connect people with skills to review/help
with those who need the review/help. This sounds similar to what
Gentoo’s Bug Wranglers[1] do. I believe someone brought up to automate
this by suggesting reviewers for patches based on the commit history
of packages/components.
[1] https://wiki.gentoo.org/wiki/Project:Bug-wranglers
Cheers,
Lars
next prev parent reply other threads:[~2021-12-28 10:52 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 [this message]
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
-- 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=YcrsXVN37pSwV3k1@noor.fritz.box \
--to=lars@6xq.net \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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://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).