Hi! Liliana Marie Prikler <liliana.prik...@gmail.com> skribis:
> Am Montag, dem 25.11.2024 um 13:27 -0500 schrieb Greg Hogan: [...] >> This team would of course be distinct from the core-packages team, >> which manages the most fundamental packages and challenging updates. > I think there is a risk that this still overlaps with core-packages on > the account of GCC being our main C/C++ toolchain. > > Note: while I'm already swamped with work on gnome and emacs, I would > be interested in joining a hypothetical c++ team. > >> diff --git a/etc/teams.scm b/etc/teams.scm >> index fe3291f914..e257650a04 100755 >> --- a/etc/teams.scm >> +++ b/etc/teams.scm >> @@ -611,0 +612,14 @@ (define-team zig >> +(define-team c++ >> + (team 'c++ >> + #:name "C/C++ team" >> + #:description >> + "C and C++ compilers, libraries, tools, and programs" > I would limit the scope to "libraries and tools". That programs happen > to be written in C/C++ is almost always incidental :) Yes, the description could clarify that Greg wrote above, which is that its scope is disjoint from that of the ‘core-packages’ team. Ludo’.
