From: Simon Tournier <zimon.toutoune@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: Some team related thoughts and questions...
Date: Fri, 06 Jan 2023 18:14:03 +0100 [thread overview]
Message-ID: <87mt6vh9gk.fsf@gmail.com> (raw)
In-Reply-To: <87358qakxm.fsf@yucca>
Hi Vagrant,
On Tue, 03 Jan 2023 at 22:11, Vagrant Cascadian <vagrant@debian.org> wrote:
> Perhaps a description would for the team(s) would help a bit here. I
> see embedded as dealing with bootloaders or firmware commonly used on
> embedded systems, and perhaps cross-compilers?
Well, currently the ’team’ record contains the description field. So it
can be expanded if it helps.
> I wonder if the team.scm script could also have a few regexps in it for
> the patch description. For example, "deterministic" or "reproducible"
> might be a useful search term for my recently proposed Reproducible
> Builds team, which otherwise would only be interested in a small pool of
> reproducible builds tooling packages, but reproducible builds issues
> actually could be relevent for all packages in guix.
I guess something like,
./etc/teams.scm list-teams | recsel -q deterministic
should list the teams where ’deterministic’ appears. It is far from
being perfect but it allows minimal queries.
> Lastly, I use the name "Vagrant Cascadian" with my contributions to
> guix, but I may use a different email address depending on the nature of
> the contribution (e.g. reproducible builds). I am not sure what would
> happen if I added "Vagrant Cascadian" twice, with two different email
> addresses. Does it handle that reasonably?
You would like to have an email address different depending on the
team, right?
Currently, a person (record <person>) has one name (string) and one
email (string) and then this person is part of one more teams (list).
Well, it is not implemented but the macro ’define-member’ could be
tweaked to associate one email to one team for a person, I guess.
Cheers,
simon
next prev parent reply other threads:[~2023-01-06 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 6:11 Some team related thoughts and questions Vagrant Cascadian
2023-01-06 17:14 ` Simon Tournier [this message]
2023-01-06 18:42 ` Vagrant Cascadian
2023-01-09 11:58 ` Simon Tournier
2023-01-10 23:32 ` Vagrant Cascadian
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=87mt6vh9gk.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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 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).