[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Teams
From: |
Josselin Poiret |
Subject: |
Re: Teams |
Date: |
Sun, 05 Jun 2022 10:19:35 +0200 |
Hello everyone,
Ricardo Wurmus <rekado@elephly.net> 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 (which I'd gladly join);
* System;
* Home;
* Internals?
Maybe that would add too many teams, but I think the first three could
be pretty useful.
How do we automatically make Mumi understand which team a patch should
notify? I've just started using public-inbox/lei and the `dfn:` search
term is pretty useful, it lets you select only patches that change
specific files. For example, `dfn:gnu/installer*` would match all
patches that touch the installer.
Best,
--
Josselin Poiret
- Teams, Ricardo Wurmus, 2022/06/04
- Re: Teams, Maxime Devos, 2022/06/04
- Re: Teams, Ekaitz Zarraga, 2022/06/04
- Re: Teams, Tobias Geerinckx-Rice, 2022/06/04
- Re: Teams,
Josselin Poiret <=
- Re: Teams, Ludovic Courtès, 2022/06/06
- Re: Teams, Andrew Tropin, 2022/06/14
- Re: Teams, Blake Shaw, 2022/06/14
- how to write services (was: Re: Teams), catonano, 2022/06/15
- Re: how to write services (was: Re: Teams), Ricardo Wurmus, 2022/06/15
- Re: how to write services (was: Re: Teams), Blake Shaw, 2022/06/15
- Re: how to write services (was: Re: Teams), Maxime Devos, 2022/06/15
- Message not available
- Re: how to write services (was: Re: Teams), Maxime Devos, 2022/06/15
- Message not available
- Re: how to write services (was: Re: Teams), Maxime Devos, 2022/06/15
- Message not available
- Re: how to write services (was: Re: Teams), Maxime Devos, 2022/06/15