Re: Teams: first draft list
On Tue, Jun 21, 2022 at 05:21:11PM +0200, zimoun wrote: > * Kernel > > + Tobias Geerinckx-Rice Feel free to add my name to the kernel team. signature.asc Description: PGP signature
Re: Teams: first draft list
Liliana Marie Prikler writes: > Am Freitag, dem 01.07.2022 um 12:28 +0200 schrieb Ricardo Wurmus: >> [...] >> An example: >> >> ./pre-inst-env guile --no-auto-compile -l etc/teams.scm -c '(cc r >> core)' >> >> This prints “git send-email” arguments to Cc members of the R and >> Core >> teams when a patch is received by Debbugs. >> >> Another example: >> >> ./pre-inst-env guile --no-auto-compile \ >> -l etc/teams.scm -c '(list-teams)' | recsel -p name,members > > Could we perhaps make that script itself executable, so that we can > write > $ ./etc/teams.scm list-teams | recsel -p name,members > $ ./etc/teams.scm cc r core Yes, we can. Just like etc/committer.scm it would need to have a .in template to let us plug in the right guile shebang. > After some pondering, I think I might want to join the emacs and games > teams, especially the former given that I'm often explaining to people > on IRC that they can load subdirs.el :) Good good. Feel free to add yourself to etc/teams.scm.in once it hits the repo. -- Ricardo
Re: Teams: first draft list
Am Freitag, dem 01.07.2022 um 12:28 +0200 schrieb Ricardo Wurmus: > [...] > An example: > > ./pre-inst-env guile --no-auto-compile -l etc/teams.scm -c '(cc r > core)' > > This prints “git send-email” arguments to Cc members of the R and > Core > teams when a patch is received by Debbugs. > > Another example: > > ./pre-inst-env guile --no-auto-compile \ > -l etc/teams.scm -c '(list-teams)' | recsel -p name,members Could we perhaps make that script itself executable, so that we can write $ ./etc/teams.scm list-teams | recsel -p name,members $ ./etc/teams.scm cc r core After some pondering, I think I might want to join the emacs and games teams, especially the former given that I'm often explaining to people on IRC that they can load subdirs.el :)
Re: Teams: first draft list
Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Now the question is merely how to represent and present this. It’s not >> a bad idea to have the team associations in the repository so that we >> can present the data on the website and also use it with our tools to >> notify the right people. > > Mathieu suggested that we have a team file in guix.git, which would > allow us to eventually write tools like ‘get-tutors.scm’ as Mathieu > calls it. Attached is a draft etc/teams.scm, which defines teams, their members, and procedures to fetch a relevant subset of the information. An example: ./pre-inst-env guile --no-auto-compile -l etc/teams.scm -c '(cc r core)' This prints “git send-email” arguments to Cc members of the R and Core teams when a patch is received by Debbugs. Another example: ./pre-inst-env guile --no-auto-compile \ -l etc/teams.scm -c '(list-teams)' | recsel -p name,members I haven’t defined any other members yet, because I think it’s better for people to do this by themselves to avoid adding people who don’t actually want to be a member of any team. -- Ricardo teams.scm Description: Binary data
Re: Teams: first draft list
On +2022-06-22 09:56:14 +0300, Efraim Flashner wrote: > On Wed, Jun 22, 2022 at 12:21:15AM +0200, zimoun wrote: > > On Tuesday, 21 June 2022, wrote: > > > > > On +2022-06-21 17:21:11 +0200, zimoun wrote: > > > > > > > > Here below a collection of answers. The teams are more or less. Maybe, > > > > we could join some for having another structure. WDYT? > > > > > > Where is the RISC/MES team? :) > > > > > > > Embeded / Bootstrap ;-) > > I would suggest adding "Ports" to that list, or "Odd Architectures". We > just had a discussion on IRC about changing some mesa flags and it's > definitely a case where pinging someone who has had to deal with > underused architectures would help since 'auto' doesn't work for all the > architectures. Plus in my mind there often seems to be a bunch of > overlap between bootstrap level things and odd architectures, in terms > of getting into the weeds of common tools. > > Seeing I managed to not get myself added to all the teams I can join the > embedded/bootstrap team, with or without the 'odd architectures' bit. > IMHO "RISC" should be somewhere in the team title, so that a flag/clue/cue for those interested in RISC will be advertised in any quoted reference to the team that may be archived in mailing lists or blogs or news etc. This would tell the RISC-interested that they might find friends by checking further :) > -- > Efraim Flashner אפרים פלשנר > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted -- Regards, Bengt Richter
Re: Teams: first draft list
Hi y'all, This looks great, thanks for putting in the work! Im getting back into the Guile + Guix documentation, and realize its a subject the @whereiseveryone and others are also working on, and thus it could probably use a concentrated team of its own. What do others think? Best, Blake On Wed, Jun 22, 2022, 20:51 Ludovic Courtès wrote: > Hi, > > Ricardo Wurmus skribis: > > > Now the question is merely how to represent and present this. It’s not > > a bad idea to have the team associations in the repository so that we > > can present the data on the website and also use it with our tools to > > notify the right people. > > Mathieu suggested that we have a team file in guix.git, which would > allow us to eventually write tools like ‘get-tutors.scm’ as Mathieu > calls it. > > The web site could fetch that file and present one tile per team on a > page. > > > It wouldn’t help with keeping mailing aliases on fencepost up to date, > > though. > > Argh, yes. Maybe this can be addressed later? Having a list of teams a > name would already help, even if there are no email aliases. > > Then perhaps we could automate alias creation with @guix.gnu.org > addresses? Not sure what it would take… > > > I also wonder about how / if we should notify teams about relevant > > patches. Will contributors Cc the relevant teams or will we have team > > predicates, e.g. a procedure that spits out the appropriate teams when > > given a patch? > > I think we can start small and build up automation incrementally. > > Thanks, > Ludo’. > >
Re: Teams: first draft list
Hi, Ricardo Wurmus skribis: > Now the question is merely how to represent and present this. It’s not > a bad idea to have the team associations in the repository so that we > can present the data on the website and also use it with our tools to > notify the right people. Mathieu suggested that we have a team file in guix.git, which would allow us to eventually write tools like ‘get-tutors.scm’ as Mathieu calls it. The web site could fetch that file and present one tile per team on a page. > It wouldn’t help with keeping mailing aliases on fencepost up to date, > though. Argh, yes. Maybe this can be addressed later? Having a list of teams a name would already help, even if there are no email aliases. Then perhaps we could automate alias creation with @guix.gnu.org addresses? Not sure what it would take… > I also wonder about how / if we should notify teams about relevant > patches. Will contributors Cc the relevant teams or will we have team > predicates, e.g. a procedure that spits out the appropriate teams when > given a patch? I think we can start small and build up automation incrementally. Thanks, Ludo’.
Re: Teams: first draft list
Josselin Poiret schreef op wo 22-06-2022 om 14:30 [+0200]: > Hello, > > zimoun writes: > > Then maybe, we could hook Mumi and add regexps based on commit messages > > for notifying a specific team. Well, it is a rough approximation with > > many false-positive but hey the aim is to deal with patches so these > > false-positive do not matter, IMHO. > > Maybe we could attribute files to teams? It seems like the simplest and > more robust way, since it easily grants 99% coverage (excluding new > files, that is), and the structure of the Guix files seem well-amenable > to such classification. FWIW, I'm in the Rust team for the build system, not the individual rust packages. Greetings, Maxime. signature.asc Description: This is a digitally signed message part
Re: Teams: first draft list
Hello, zimoun writes: > Then maybe, we could hook Mumi and add regexps based on commit messages > for notifying a specific team. Well, it is a rough approximation with > many false-positive but hey the aim is to deal with patches so these > false-positive do not matter, IMHO. Maybe we could attribute files to teams? It seems like the simplest and more robust way, since it easily grants 99% coverage (excluding new files, that is), and the structure of the Guix files seem well-amenable to such classification. WDYT? -- Josselin Poiret
Re: Teams: first draft list
Hi Ricardo, On Wed, 22 Jun 2022 at 09:59, Ricardo Wurmus wrote: > I also wonder about how / if we should notify teams about relevant > patches. Will contributors Cc the relevant teams or will we have team > predicates, e.g. a procedure that spits out the appropriate teams when > given a patch? We discussed about tools to achieve that. IMHO, the first step is to expose such list; on the website? in the repo? and update the node «Submitting Patches» to point on the website or repo or else. Then maybe, we could hook Mumi and add regexps based on commit messages for notifying a specific team. Well, it is a rough approximation with many false-positive but hey the aim is to deal with patches so these false-positive do not matter, IMHO. We have not discussed how we maintain the list of team; we can discuss later. Cheers, simon
Re: Teams: first draft list
Hi simon, > Here below a collection of answers. The teams are more or less. Maybe, > we could join some for having another structure. WDYT? Thank you for the initiative! I had been meaning to go through the whole thread and collect and organize all submissions, but you’ve done all the work already. Thanks! Now the question is merely how to represent and present this. It’s not a bad idea to have the team associations in the repository so that we can present the data on the website and also use it with our tools to notify the right people. It wouldn’t help with keeping mailing aliases on fencepost up to date, though. I also wonder about how / if we should notify teams about relevant patches. Will contributors Cc the relevant teams or will we have team predicates, e.g. a procedure that spits out the appropriate teams when given a patch? -- Ricardo
Re: Teams: first draft list
On Wed, Jun 22, 2022 at 12:21:15AM +0200, zimoun wrote: > On Tuesday, 21 June 2022, wrote: > > > On +2022-06-21 17:21:11 +0200, zimoun wrote: > > > > > > Here below a collection of answers. The teams are more or less. Maybe, > > > we could join some for having another structure. WDYT? > > > > Where is the RISC/MES team? :) > > > > Embeded / Bootstrap ;-) I would suggest adding "Ports" to that list, or "Odd Architectures". We just had a discussion on IRC about changing some mesa flags and it's definitely a case where pinging someone who has had to deal with underused architectures would help since 'auto' doesn't work for all the architectures. Plus in my mind there often seems to be a bunch of overlap between bootstrap level things and odd architectures, in terms of getting into the weeds of common tools. Seeing I managed to not get myself added to all the teams I can join the embedded/bootstrap team, with or without the 'odd architectures' bit. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: Teams: first draft list
On Tuesday, 21 June 2022, wrote: > On +2022-06-21 17:21:11 +0200, zimoun wrote: > > > > Here below a collection of answers. The teams are more or less. Maybe, > > we could join some for having another structure. WDYT? > > Where is the RISC/MES team? :) > Embeded / Bootstrap ;-)
Re: Teams: first draft list
On +2022-06-21 17:21:11 +0200, zimoun wrote: > > Here below a collection of answers. The teams are more or less. Maybe, > we could join some for having another structure. WDYT? Where is the RISC/MES team? :)
Teams: first draft list
Hi, On Sat, 04 Jun 2022 at 14:07, Ricardo Wurmus wrote: > As a first step I’d suggest collecting teams, setting up the email > aliases, and updating the website to show the existing teams. Here’s > a draft of three teams: Here below a collection of answers. The teams are more or less. Maybe, we could join some for having another structure. WDYT? Cheers, simon * Python + Arun Isaac + Lars-Dominik Braun + Maxim Cournoyer + Ryan Prior * Haskell + Lars-Dominik Braun + Simon Tournier * R + Ricardo Wurmus + Simon Tournier * Julia + Efraim Flashner + Simon Tournier * OCaml / Dune + Julien Lepiller + Simon Tournier * Java / Maven + Julien Lepiller * Algebra / Maths + Andreas Enge + Eric Bavier * Emacs + Arun Isaac + Maxim Cournoyer + Nicolas Goaziou * Lisp + Arun Isaac + Guillaume Le Vaillant * Ruby + Ryan Prior * Go + Ryan Prior * Embedded / Bootstrap + Ekaitz Zarraga + Ludovic Courtes + Thiago Jung Bauermann + Vagrant Cascadian * Rust + Aleksandr Vityazev + Arun Isaac + Efraim Flashner + John Soo + Maxim Cournoyer + Maxime Devos + Nicolas Goaziou + Tobias Geerinckx-Rice * Kernel + Tobias Geerinckx-Rice * Core / Tools / Internals + Arun Isaac + Josselin Poiret + Ludovic Courtès + Ricardo Wurmus * Games / Videos + Blake Shaw + Maxime Devos + raingloom * Traductions + Florian Pelz + Julien Lepiller + Maxime Devos + Thiago Jung Bauermann + Tobias Geerinckx-Rice * Installer + Josselin Poiret + Mathieu Othacehe * Home + Andrew Tropin + Blake Shaw + Josselin Poiret + Ludovic Courtès
