Hello Guix, I'm fowarding this from https://codeberg.org/guix/guix/issues/6088 as recommended by Ian Eure.
Relevant to my $dayjob (research on software engineering) and interests, I want to create a team taking care of the following packages modules (with overlapping teams): - auto*, build-tools - benchmark - bison, oyacc, maybe merged as yacc, and re2c - check and *-check (*) - code - ci (core) and task-runner (sysadmin), see also https://codeberg.org/guix/guix/issues/3096 for merging them - coq (ocaml), lean (science) and logic stuff in maths (science) - debug and libunwind - hexedit, text-editors and tree-sitter (emacs) Suggestions for shorter team names and adjustments to the module list are also welcomed. At 2026-02-03T04:31Z, Ian Eure wrote: > All the teams are currently organized around specific functional areas, > I'm not sure how the suggestion to create a bespoke team just for you > is going to go over. It is not just for me, I hope the team to have other members as well to have other reviewing my work. I intend for functional area here to be similar to that of team bioinformatics or science. I often have to package research software but like y'all I also use a lot of the packages in the listed modules. The other motivation is to have review delegation (i.e. notifications) for modules without the so-called "code owners". I am totally happy if the scope of the team is reduced to unaddopted modules. Cheers, Phong
