From: Ricardo Wurmus <rekado@elephly.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Formalizing teams
Date: Tue, 28 Dec 2021 15:44:55 +0100 [thread overview]
Message-ID: <87pmpgiy1c.fsf@elephly.net> (raw)
In-Reply-To: <87mtkmwrre.fsf@gmail.com>
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> Guix is nowhere near the size of the Rust community (yet!), but I can
>> already picture teams and members:
>>
>> co-maintainers (“core team”)
>> community
>> infrastructure
>> internationalization
>> security response
>> release
>> Rust packaging
>> R packaging
>> Java packaging
>
> We'd have to include every language/system of importance to that list
> (Python, Ruby, Emacs, LaTeX, Perl, etc.), no?
No, only those where we already have the people who could form a team.
There is no need for any of this to be comprehensive. It just needs to
be an improvement over the status quo.
FWIW, I’ll gladly make it official that I could be the person to talk to
when it comes to “R packaging”. This is already the case, but only
those people know it who don’t really need to know this.
Advertising this kind of information or recording it somewhere where our
tools could redirect incoming requests would be an improvement.
> Are our problems really organizational? I think before attempting to
> come up with a solution, we must analyze and agree on what it is that
> needs improvement to help us move forward more efficiently.
I do think it’s a lack of organization, yes. Today I’m no longer
following guix-commits, guix-patches, or bug-guix, and I’m overwhelmed
by guix-devel and help-guix. Whenever something catches my attention
I’ll read a bit and maybe reply. But by far the best way to get my
attention for a review is to ask on #guix or #guix-hpc or to
X-Debbugs-Cc (or Cc) me on emails.
Having some topic-specific streams I could tap into would allow me to be
a little more proactive.
--
Ricardo
next prev parent reply other threads:[~2021-12-28 14:51 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 [this message]
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=87pmpgiy1c.fsf@elephly.net \
--to=rekado@elephly.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).