From: Philip McGrath <philip@philipmcgrath.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
59322@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope.
Date: Fri, 18 Nov 2022 14:33:36 -0500 [thread overview]
Message-ID: <2144765.irdbgypaU6@bastet> (raw)
In-Reply-To: <867czsk6rw.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
Hi,
On Friday, November 18, 2022 3:26:27 AM EST zimoun wrote:
> Hi,
>
> On Fri, 18 Nov 2022 at 08:01, Liliana Marie Prikler
<liliana.prikler@ist.tugraz.at> wrote:
> >> - #:scope (list "gnu/packages/racket.scm")))
> >> + #:scope (list "gnu/packages/chez.scm"
> >> + "gnu/packages/racket.scm")))
> >
> > I'm not sure whether this accurately captures the intent of teams.
> > Yes, chez-scheme is required in Racket's bootstrap, but the only
> > "legal" changes to Racket's variant also affect racket.scm. On the
> > other hand, the Racket team would weigh in on changes that only affect
> > the Chez side, which imho is unwarranted.
>
> Why not? Considering the only person part of the Racket team is Philip,
> the false-positive seems acceptable, no?
>
I don't have a strong view: feel free to just drop this patch for now if you
feel it needs more discussion but the others are ready to merge.
Since the chez-scheme-for-racket package inherits from the chez-scheme
package, any change to the chez-scheme package will affect racket, racket-
minimal, and racket-vm-cs.
I could certainly imagine having a Chez team that doesn't necessarily care
about Racket. Likewise, in both languages, I imagine there could be people
interested in packages that use the language but who wouldn't necessarily be
interested in the packaging of the compilers and run-time systems themselves.
But, since no one else has signed on and I've made the majority of changes to
both files in the last two years, designing a more fine-grained team structure
seemed premature.
I guess I've also thought of teams as less "would way in on" changes and more
as "would like to be CC'ed about" them. I'd rather get a little more email
than miss relevant changes (even though I can't keep up with the whole patches
mailing list).
-Philip
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-18 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:36 [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Philip McGrath
2022-11-16 21:39 ` [bug#59322] [PATCH 1/2] " Philip McGrath
2022-11-17 7:30 ` Liliana Marie Prikler
2022-11-18 0:45 ` [bug#59322] [PATCH v2 0/4] " Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 1/4] " Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 2/4] gnu: chez-scheme-for-racket: Support riscv64 Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 3/4] gnu: racket-vm-cs: Avoid duplicate work Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope Philip McGrath
2022-11-18 7:01 ` Liliana Marie Prikler
2022-11-18 8:26 ` zimoun
2022-11-18 19:23 ` Liliana Marie Prikler
2022-11-18 19:33 ` Philip McGrath [this message]
2022-11-19 7:54 ` Liliana Marie Prikler
2022-11-19 23:52 ` Philip McGrath
2022-11-20 1:49 ` Liliana Marie Prikler
2022-11-23 18:44 ` [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Ludovic Courtès
2022-11-21 16:50 ` [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope zimoun
2022-12-01 21:08 ` bug#59322: [PATCH 0/2] gnu: racket: Update to 8.7 Ludovic Courtès
2022-11-16 21:39 ` [bug#59322] [PATCH 2/2] gnu: racket-vm-cs: Avoid duplicate work Philip McGrath
2022-12-04 13:25 ` [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Enrico Schwass via Guix-patches via
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=2144765.irdbgypaU6@bastet \
--to=philip@philipmcgrath.com \
--cc=59322@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=liliana.prikler@ist.tugraz.at \
--cc=zimon.toutoune@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).