Re: Teams migration on Codeberg

Am Sat, Jun 14, 2025 at 01:41:58PM +0200 schrieb Noé Lopez: > I don’t think you need to sign it, that was for committers. Indeed, for non-committers this is not required, sorry for the wrong information! Andreas

Re: Teams migration on Codeberg

Gabriel Wicki writes: > Hi Andreas! > > Thanks for the explanation! > > On Sat, Jun 14, 2025 at 12:46:33PM +0200, Andreas Enge wrote: >> you need to send us a signed message with your codeberg name, which >> will be added to etc/teams.scm; > Signed with what key? I guess this is intended for peo

Re: Teams migration on Codeberg

Gabriel Wicki writes: > Hi Y'all > > It could well be that I missed the memo - otherwise I guess this is > either a WIP or a topic to be discussed and implemented, for which this > message could be a starting point. > > I am member of several teams (as per etc/teams.scm

Re: Teams migration on Codeberg

Hello, Am Sat, Jun 14, 2025 at 12:33:16PM +0200 schrieb Gabriel Wicki: > I am member of several teams (as per etc/teams.scm), but since our move > to codeberg I get drastically less messages for reviews you need to send us a signed message with your codeberg name, which will be added

Teams migration on Codeberg

Hi Y'all It could well be that I missed the memo - otherwise I guess this is either a WIP or a topic to be discussed and implemented, for which this message could be a starting point. I am member of several teams (as per etc/teams.scm), but since our move to codeberg I get drastically

Re: [PATCH 1/2] teams: Add hurd team.

Ludovic Courtès writes: > Janneke Nieuwenhuizen skribis: > >>> Am Tue, Dec 03, 2024 at 02:34:10PM +0100 schrieb Janneke Nieuwenhuizen: * etc/teams.scm (hurd): New team. >>> >>> I think you should simply push these two patches :) >> >> Pushed as 38bbed33a28524c26ca794117f6dfed1529e2807, thank

Re: [PATCH 1/2] teams: Add hurd team.

Hi, Janneke Nieuwenhuizen skribis: >> Am Tue, Dec 03, 2024 at 02:34:10PM +0100 schrieb Janneke Nieuwenhuizen: >>> * etc/teams.scm (hurd): New team. >> >> I think you should simply push these two patches :) > > Pushed as 38bbed33a28524c26ca794117f6dfed1529e2807, thanks. Thanks! I support this n

Re: [PATCH 1/2] teams: Add hurd team.

Andreas Enge writes: Hello Andreas, > Am Tue, Dec 03, 2024 at 02:34:10PM +0100 schrieb Janneke Nieuwenhuizen: >> * etc/teams.scm (hurd): New team. > > I think you should simply push these two patches :) Pushed as 38bbed33a28524c26ca794117f6dfed1529e2807, thanks. Janneke -- Janneke Nieuwenhuiz

Re: [PATCH 1/2] teams: Add hurd team.

Hello, Am Tue, Dec 03, 2024 at 02:34:10PM +0100 schrieb Janneke Nieuwenhuizen: > * etc/teams.scm (hurd): New team. I think you should simply push these two patches :) Thanks, Andreas

[PATCH 1/2] teams: Add hurd team.

* etc/teams.scm (hurd): New team. Change-Id: Id3b4d8ac3eed8c7773a45d0fe8a17154c6427aa1 --- etc/teams.scm | 9 + 1 file changed, 9 insertions(+) diff --git a/etc/teams.scm b/etc/teams.scm index 4f86dfb954..ab9b9e9160 100755 --- a/etc/teams.scm +++ b/etc/teams.scm @@ -610,6 +610,15 @@ (def

[PATCH 2/2] etc: teams: Add entry for Janneke Nieuwenhuizen.

r) +  (define (find-team name) (or (hash-ref %teams (string->symbol name)) -- 2.46.0

Re: bug#72891: [PATCH RFC] doc: Define the purpose, membership, and creation of teams.

Hi Ludo, As you mentioned elsewhere, this patch deserves the attention of guix-devel, hence CC: guix-devel. :-) [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams. Ludovic Courtès Fri, 30 Aug 2024 12:12:04 +0200

Defining the role of teams

Hello Guix, Ludovic Courtès skribis: > Team members are expected to coordinate and work together (e.g., for > review) on everything in the team’s scope, onboard new members willing > to help, and coordinate with the rest of the project. > > (That

Adding Qt and Telephony teams

Hello Guix! To get this a bit more broadcasted (as suggested by Liliana), I'm reaching out with adding a Qt and Telephony teams (see: #64634 and #64635); you are welcome to join them if these are of interest to you and you would be happy to conduct reviews on relevant patches. Happy ha

Re: Call for members to join the Xfce, LXQt and Localization teams

宋文武 writes: > Zhu Zihao writes: > >> count me in :) > > Good, all three? Thank you! As we talked in #guixcn, join you to the xfce and localization team, thanks!

Re: Call for members to join the Xfce, LXQt and Localization teams

Zhu Zihao writes: > count me in :) Good, all three? Thank you!

Re: Call for members to join the Xfce, LXQt and Localization teams

count me in :) 宋文武 writes: > Hello, I recently joined/created teams for xfce, lxqt, and localization, > in which I am the only member so far, so I'd like to call for more > members. > > I think Team members mostly do (in the scope and area of expertise by team): > - R

Call for members to join the Xfce, LXQt and Localization teams

Hello, I recently joined/created teams for xfce, lxqt, and localization, in which I am the only member so far, so I'd like to call for more members. I think Team members mostly do (in the scope and area of expertise by team): - Review patches from guix-patches. - Handle issues or usages su

Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches)

On Mon, Feb 13, 2023 at 03:07:58PM +0100, Andreas Enge wrote: > Am Sun, Feb 12, 2023 at 10:13:35PM +0100 schrieb Josselin Poiret: > > 4. staging merge happens, and the branch gets deleted. > > I failed to compile my profile on staging, since rust-rav1e, a dependency > of ffmpeg, failed to build; s

Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches)

Am Sun, Feb 12, 2023 at 10:13:35PM +0100 schrieb Josselin Poiret: > 4. staging merge happens, and the branch gets deleted. I failed to compile my profile on staging, since rust-rav1e, a dependency of ffmpeg, failed to build; see bug #61475. Andreas

Time for RFC? (was Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches))

Hi, On Sun, 12 Feb 2023 at 22:13, Josselin Poiret wrote: > 1. Document this workflow in the manual, in a dedicated node, with a >rationale as well. One thing worth mentioning would be how to handle >grafting/ungrafting now. Also remove the staging/core-updates >criterion. Maybe it

Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches)

how to handle >grafting/ungrafting now. Also remove the staging/core-updates >criterion. > 2. Teams start organizing around the features they are currently working >on, and document them accordingly. They can also draft how they work, >what they do and their roadmap if they w

Moving forward with teams and feature branches (was: Discussion notes on releases and branches)

stead of a hodgepodge of unrelated patches that no one wants to debug. These feature branches would be managed by teams, with one person from the team being responsible for the feature and it getting merged into master. Those features could be ephemeral or long-running and each team would be fr

Re: Teams: please add yourself to etc/teams.scm.in

Hello, Am Sun, Jul 03, 2022 at 03:04:36PM +0200 schrieb Ricardo Wurmus: > etc/teams.scm.in is now part of the repository. The configure script > generates the executable etc/teams.scm. > Please feel free to add yourself to teams in that file by adding a > definition like this:

Teams: please add yourself to etc/teams.scm.in

> 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 \ >

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

end-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 >

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 > team

Re: Teams: first draft list

s 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

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

Re: Teams: first draft list

esent 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. > >

Re: Teams: first draft list

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

Re: Teams: first draft list

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 o

Re: Teams: first draft list

ybe 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 > g

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 th

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 s

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 les

Re: how to write services (was: Re: Teams)

caton...@gmail.com writes: I asked for indications about the process (what magic to use in the REPL) My experience with Guix, in general, is that the REPL isn't particularly useful for any task beyond very simple testing (eg, what are the contents of ‘%base-services’). It's a shame, but I

Re: how to write services (was: Re: Teams)

Blake Shaw schreef op do 16-06-2022 om 06:20 [+0700]: > But, perhaps it's just getting late and the matters are now & the > details are slipping my mind, but im starting to realize im unsure of > many examples of file-like objects that aren't a file? The email > where you responded re: packages was

Re: how to write services (was: Re: Teams)

caton...@gmail.com writes: > Ricardo, the general map of the concepts involved in conceiving a > service is useful > > But in my toot I asked for something different > > I asked for indications about the process (what magic to use in the > REPL) There is no REPL magic. I write the service in c

Re: how to write services (was: Re: Teams)

Il giorno mer, 15/06/2022 alle 17.01 +, Blake Shaw ha scritto: > > Catonano: > I think writing a home-service is much easier given that you don't > need to do produce an entire system generation before you find out > what you did wrong;  I suspected something like this This is why I hypotize

Re: how to write services (was: Re: Teams)

Thanks for the feedback, abelian groups are a good example because so many groups are abelian (fields etc). But, perhaps it's just getting late and the matters are now & the details are slipping my mind, but im starting to realize im unsure of many examples of file-like objects that aren't a file?

Re: how to write services (was: Re: Teams)

Blake Shaw schreef op wo 15-06-2022 om 21:40 [+]: > On the contrary, lets say I'm writing an intro book on CT. If I'm > demonstrating something trivial, say the initial object, I'm not > going to refer to it as "an initial-like object" for the sake of > generality. Neither does Guix? If you'r

Re: how to write services (was: Re: Teams)

Blake Shaw schreef op wo 15-06-2022 om 21:40 [+]: > > AFAIK no relation to GNU. > > I thought recalled hearing it used in relation to GNU/Linux. A quick > search > brings up this stackexchange discussion[1], which quotes the book > "Linux > Philosophy" with the following: > > #+begin_example

Re: how to write services (was: Re: Teams)

Blake Shaw schreef op wo 15-06-2022 om 21:40 [+]: > > Something I dislike about the ‘file AND file-like objects’ > > construction > > is that it suggests that files and file-like objects are separate > > and > > are handled separately, whereas files (as in, 'local-file' or > > 'computed-file')

Re: how to write services (was: Re: Teams)

Blake Shaw schreef op wo 15-06-2022 om 17:01 [+]: > Thats very good advice and will be a useful guide in refactoring the > parts of the system services documentation. I think in general, we > need to find a nice middle ground between the extremely general and > the immediately sensible, as I re

Re: how to write services (was: Re: Teams)

Ricardo: Thats very good advice and will be a useful guide in refactoring the parts of the system services documentation. I think in general, we need to find a nice middle ground between the extremely general and the immediately sensible, as I remember when I first got into guix 1.5 years ago, arri

Re: how to write services (was: Re: Teams)

caton...@gmail.com writes: > Il giorno mer, 15/06/2022 alle 01.52 +0700, Blake Shaw ha scritto: >> >> I found the documentation to be a bit confusing (understandably, as >> its new), but once the workflow snapped together its been amazing to >> see how easy it is to create new services.  > > Th

how to write services (was: Re: Teams)

Il giorno mer, 15/06/2022 alle 01.52 +0700, Blake Shaw ha scritto: > > I found the documentation to be a bit confusing (understandably, as > its new), but once the workflow snapped together its been amazing to > see how easy it is to create new services.  This is something I'm specifically intere

How to write a service (was: Re: Teams)

Il giorno mer, 15/06/2022 alle 01.52 +0700, Blake Shaw ha scritto: > > I found the documentation to be a bit confusing (understandably, as > its new), but once the workflow snapped together its been amazing to > see how easy it is to create new services.  I'm specifically interested in this issue

Re: Teams

On Tue, 14 Jun 2022 08:47:37 -0400 guix-devel-requ...@gnu.org wrote: Hi Guixers, Count me in for any packaging on teams. I'd like to help out with python and/or rust. all best, jgart

Re: Teams

ident. Very excited about it, great work :) On Tue, Jun 14, 2022, 18:31 Andrew Tropin wrote: > On 2022-06-05 10:19, Josselin Poiret wrote: > > > Hello everyone, > > > > Ricardo Wurmus writes: > > > >> As a first step I’d suggest collecting teams, setting

Re: Teams

On 2022-06-05 10:19, Josselin Poiret wrote: > Hello everyone, > > Ricardo Wurmus writes: > >> As a first step I’d suggest collecting teams, setting up the email >> aliases, and updating the website to show the existing teams. > > I think an installer team would be

Re: Teams

equirements in less rules, making it easier to ensure what you're > handing in is in order. But I still need to take a stab at it and see. > > Best, > > On Fri, Jun 10, 2022, 03:29 Arun Isaac > wrote: > > > > > Hi Guix, > > > > I like the idea of

Re: Teams

run Isaac wrote: > > Hi Guix, > > I like the idea of teams. And, it's nice to see so many volunteers raise > their hands! > > > * Rust team > > Efraim Flashner > > Aleksandr Vityazev > > Arun Isaac > > John Soo > > Maxim Cournoyer > >

Re: Teams

Hi Guix, I like the idea of teams. And, it's nice to see so many volunteers raise their hands! > * Rust team > Efraim Flashner > Aleksandr Vityazev > Arun Isaac > John Soo > Maxim Cournoyer > Nicolas Goaziou > Tobias Geerinckx-Rice However, I know very little a

Re: Teams

Hi, On Sun, 2022-06-05 at 11:51 +0200, Andreas Enge wrote: > Hello, > > Am Sat, Jun 04, 2022 at 02:07:15PM +0200 schrieb Ricardo Wurmus: > > As a first step I’d suggest collecting teams, setting up the email > > aliases, and updating the website to show the existing tea

Re: Teams

Hello, Ludovic Courtès writes: > Vagrant Cascadian skribis: > >> On 2022-06-04, 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

Re: Teams

Vagrant Cascadian skribis: > On 2022-06-04, 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: > > I'm almost afraid to vol

Re: Teams

On 2022-06-04, 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: I'm almost afraid to volunteer... but maybe architecture specific teams? If I

Re: Teams

On Sun, Jun 05, 2022 at 11:51:20AM +0200, zimoun wrote: > Hi Ricardo, > > > > * R team > > Simon Tournier > > Ricardo Wurmus > > In addition, add me to: > > * Julia team I can do the Julia team too. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D

Re: Teams

"pelzflorian (Florian Pelz)" writes: > On Sat, Jun 04, 2022 at 02:50:49PM +, Tobias Geerinckx-Rice wrote: >> I think we should also have (natural) language 'teams' who can be >> pinged when, e.g., a news item lands, through a single >> guix-transla

Re: Teams

On Saturday, June 4th, 2022 at 12:07 PM, Ricardo Wurmus wrote: > let’s add a page to the website that lists teams > and a mail alias for each of the teams That sounds great. What do you think about encouraging each team to write a dedicated intro to Guix from the perspective of that t

Re: Teams

Hi, Mathieu Othacehe skribis: > I would suggest to extend a bit the scope of this idea. What about > creating an etc/tutors.scm file as the one attached. > > This way people would run something like: > > git send-email $(get-tutors.scm HEAD^^) *.patches Nice idea, I like that! To get the ball

Re: Teams

Hi! Josselin Poiret skribis: > WDYT of the following teams: > * Installer (which I'd gladly join); > * System; > * Home; > * Internals? I think these are good ideas. Count me on the System, Home, and Internals/Core teams! Ludo’.

Re: Teams

Hi Ricardo, Ricardo Wurmus writes: [...] > * Rust team [...] > Maxim Cournoyer [...] I don't think I'm specially fit for Rust packaging (I have little experience/interest in packaging *apps/libraries* with it -- I've only looked into shortening the Rust bootstrap out of necessity :-)). I'd be

Re: Teams

Hello Ricardo, I would suggest to extend a bit the scope of this idea. What about creating an etc/tutors.scm file as the one attached. This way people would run something like: --8<---cut here---start->8--- git send-email $(get-tutors.scm HEAD^^) *.patches --

Re: Teams

, Ricardo Wurmus wrote: Hi Guix, this is not a new idea[1]: let’s add a page to the website that lists teams and a mail alias for each of the teams. For example, the “R team” consists of people familiar with how R packaging works in Guix, e.g. Simon and myself. There would be an alias “guix-tea

Re: Teams

gt; 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: > >Well, a team per build system would fit more or less the needs, I >guess. It is not a big deal if there a

Re: Teams

Hi Ricardo, 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: Well, a team per build system would fit more or less

Re: Teams

Hello, Am Sat, Jun 04, 2022 at 02:07:15PM +0200 schrieb Ricardo Wurmus: > 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: if something like this makes sense, I would be i

Re: Teams

Hi Ricardo, > 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: * Python Team Lars-Dominik Braun * Haskell Team Lars-Dominik Braun Anyone interested to join these with me

Re: Teams

On Sat, Jun 04, 2022 at 02:50:49PM +, Tobias Geerinckx-Rice wrote: > I think we should also have (natural) language 'teams' who can be > pinged when, e.g., a news item lands, through a single > guix-translators@ meta-alias, and who can co-ordinate before > releases. If w

Re: Teams

Hello everyone, Ricardo Wurmus writes: > As a first step I’d suggest collecting teams, setting up the email > aliases, and updating the website to show the existing teams. I think an installer team would be good too (which I would gladly join). WDYT of the following teams: * Installer

Re: Teams

On 4 June 2022 12:07:15 UTC, Ricardo Wurmus wrote: * Rust team [...] Tobias Geerinckx-Rice OK what the hell. Would you wanna create and be the Bash team person as well? :) Best regards, David

Re: Teams

Tobias Geerinckx-Rice schreef op za 04-06-2022 om 14:50 [+]: > I think we should also have (natural) language 'teams' who can be pinged > when, e.g., a news item lands, through a single guix-translators@ meta-alias, > and who can co-ordinate before releases. > > I&

Re: Teams

On 4 June 2022 12:07:15 UTC, Ricardo Wurmus wrote: >* Rust team [...] >Tobias Geerinckx-Rice OK what the hell. I'll also join Leo on a kernel/module/initrd team if they're interested. I think we should also have (natural) language 'teams' who can be pinged when

Re: Teams

> Hi Guix, > > this is not a new idea[1]: let’s add a page to the website that lists teams > and a mail alias for each of the teams. > > For example, the “R team” consists of people familiar with how R > packaging works in Guix, e.g. Simon and myself. There would be an alias &

Re: Teams

Ricardo Wurmus schreef op za 04-06-2022 om 14:07 [+0200]: > 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: > > [...] You can add me to the Rust team and to a ne

Teams

Hi Guix, this is not a new idea[1]: let’s add a page to the website that lists teams and a mail alias for each of the teams. For example, the “R team” consists of people familiar with how R packaging works in Guix, e.g. Simon and myself. There would be an alias “guix-tea...@gnu.org”. People

Re: Formalizing teams

Hi David, david larsson skribis: > On 2022-01-03 16:22, Ludovic Courtès wrote: [...] >> This brings a related but slightly different topic: how to let >> people >> filter incoming patches and bug reports in general. >> How does it even work on git*.com? Do they let you subscribe to >> issues/

Re: Formalizing teams

On 2022-01-03 16:22, Ludovic Courtès wrote: I suppose people could explicitly Cc: the team you’re on when they need specific advice or review; that should already help. Having some topic-specific streams I could tap into would allow me to be a little more proactive. This brings a related bu

Re: Formalizing teams

your bug is about That automatically informs the right people/teams Also on Stackoverflow, you can accompany your question with some labels (tags) and every tag is "followed" by some concerned people

Re: Formalizing teams

Ludovic Courtès writes: >> Having some topic-specific streams I could tap into would allow me to be >> a little more proactive. > > This brings a related but slightly different topic: how to let people > filter incoming patches and bug reports in general. On issues.guix.gnu.org we could offer

Re: Formalizing teams

Hi! ⛄ Ricardo Wurmus skribis: > Maxim Cournoyer writes: [...] >> We'd have to include every language/system of importance to that list >> (Python, Ruby, Emacs, LaTeX, Perl, etc.), no? > > No, only those where we already have the people who could form a team. > There is no need for any of this

Re: Formalizing teams

Hello, Filip Łajszczak skribis: > Great idea. As a newcomer who created his first patch in May > https://issues.guix.gnu.org/issue/48289/ that got a review, was fixed > and submitted again, and then disappeared into oblivion, I would be > very happy to be able to ask some "Python packaging" tea

Re: Formalizing teams

Hi Ricardo, > FWIW, mumi also lets you search patches as all contents are indexed: > > https://issues.guix.gnu.org/search?query=%22%28gnu+packages+python-web%29%22+is%3Aopen+tag%3Apatch thanks, I didn’t think about that. I tried searching for python-build-system, but not all patches – especia

Re: Formalizing teams

On Tue, Dec 28, 2021 at 03:44:55PM +0100, Ricardo Wurmus wrote: > > Maxim Cournoyer writes: > > >> Guix is nowhere near the size of the Rust community (yet!), but I can > >> already picture teams and members: > >> > >> co-maintainers (“core

Re: Formalizing teams

Kyle Meyer writes: > Fwiw public-inbox indexes the file name from diffs, so you might find > searching with the "dfn:" against the archive at > useful. For example: > > https://yhetil.org/guix-patches/?q=dfn%3Agnu%2Fpackages%2Fpython-web.scm FWIW, mumi also

Re: Formalizing teams

Lars-Dominik Braun writes: > Hi Maxim, > >> I've grown to like our apparent lack of structure; we interact globally >> on any topic of interest and the discussions all happen in a shared >> space, which makes it easy to stay informed with everything that's going >> on (do we really need more maili

Re: Formalizing teams

Maxim Cournoyer writes: >> Guix is nowhere near the size of the Rust community (yet!), but I can >> already picture teams and members: >> >> co-maintainers (“core team”) >> community >> infrastructure >> internationalization >> se

Re: Formalizing teams

es (I’m not even subscribed to -bug/-commit) and instead only look at bugs/patches/commits related to packages/components I’m interested into/I actually use. To that end having more structure would help. Teams are just one option, but we need a way to efficiently connect people with skills to

Re: Formalizing teams

o bring structure to the group, or rather to > make structure visible, so that newcomers know who they can talk to to > get started on a topic, know who to ping for reviews, and so that each > one of us can see where they fit. Rust has well-defined teams: I've grown to like our apparen

Re: Formalizing teams

Good catch! TBH, I did wonder whether the feudal eptimology of the English word may raise eyebrows. Hartmut Goebel writes: > Am 23.12.21 um 22:51 schrieb Jonathan McHugh: >> I reckon 'coterie' is more elegant a term: > > IMHO we chould not use this term. > > The German translation is "Seilschaf

Re: Formalizing teams

Am 23.12.21 um 22:51 schrieb Jonathan McHugh: I reckon 'coterie' is more elegant a term: IMHO we chould not use this term. The German translation is "Seilschaft", "Klüngel" - both of which have negative meaning: Working together to the benefit of the members of the group only - ignoring comm

Re: Formalizing teams

o to ping for reviews, and so that each >> one of us can see where they fit. Rust has well-defined teams: >> >> https://www.rust-lang.org/governance > > Definitely! Perhaps this an aesthetic matter, but keeping-with the > community spirit of Guix, and the existing nomencl

Re: Formalizing teams

ust has well-defined teams: > > https://www.rust-lang.org/governance > Definitely! Perhaps this an aesthetic matter, but keeping-with the community spirit of Guix, and the existing nomenclature where the 'core' maintainers are called a "collective", perhaps we shou

  1   2   >