From: Mathieu Othacehe <othacehe@gnu.org>
To: guix-devel@gnu.org
Subject: Pick your team!
Date: Sun, 25 Sep 2022 09:46:59 +0200 [thread overview]
Message-ID: <87wn9rlwuk.fsf@gnu.org> (raw)
Hello,
We recently introduced a teams.scm[1] file defining different teams such
as "Julia team", "Lisp team" or "Mentors".
If you are a newcomer seeking for some guidance to contribute to a Lisp
package, you can run the following command:
--8<---------------cut here---------------start------------->8---
mathieu@meije ~/guix [env]$ ./etc/teams.scm list-members lisp
Guillaume Le Vaillant <glv@posteo.net>
jgart <jgart@dismail.de>
--8<---------------cut here---------------end--------------->8---
so that you know who can help you with you endeavor.
Now, we are going a step further, and by running:
--8<---------------cut here---------------start------------->8---
mathieu@meije ~/guix [env]$ git send-email --to XXX@@debbugs.gnu.org $(./etc/teams.scm cc-members HEAD~2 HEAD) *.patch
--8<---------------cut here---------------end--------------->8---
the teams concerned by the two last commits you are sending to review
will automatically by put in CC.
This is automatic but not magic! It works by defining a scope of files
that are mentored by a team. For instance, the installer team has the
following scope:
--8<---------------cut here---------------start------------->8---
(define-team installer
(team 'installer
#:name "Installer script and system installer"
#:scope
(list (make-regexp "^guix/installer(\\.scm$|/)"))))
--8<---------------cut here---------------end--------------->8---
So, we can all improve this mechanism by:
1. Defining your team scope, if you are already part of a team
2. Joining a team
To do that, you can send patches to the etc/teams.scm.in file.
Thanks,
Mathieu
[1]: https://git.savannah.gnu.org/cgit/guix.git/tree/etc/teams.scm.in
next reply other threads:[~2022-09-25 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 7:46 Mathieu Othacehe [this message]
2022-09-25 10:46 ` Pick your team! Lars-Dominik Braun
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=87wn9rlwuk.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.