[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Teams
From: |
zimoun |
Subject: |
Re: Teams |
Date: |
Sun, 05 Jun 2022 11:51:20 +0200 |
Hi Ricardo,
On Sat, 04 Jun 2022 at 14:07, Ricardo Wurmus <rekado@elephly.net> 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 the needs, I
guess. It is not a big deal if there are some overlaps.
For what is it is worth, I would suggest that people with commit access
appear at least once in one team, if possible.
> * R team
> Simon Tournier
> Ricardo Wurmus
In addition, add me to:
* Julia team
Cheers,
simon
- Re: how to write services (was: Re: Teams), (continued)
- Re: how to write services (was: Re: Teams), catonano, 2022/06/16
- Re: how to write services (was: Re: Teams), Ricardo Wurmus, 2022/06/16
- Re: how to write services (was: Re: Teams), Brian Cully, 2022/06/16
- Re: how to write services, indieterminacy, 2022/06/18
- Re: how to write services, Maxime Devos, 2022/06/18
- Re: how to write services, indieterminacy, 2022/06/18
- How to write a service (was: Re: Teams), catonano, 2022/06/15
Re: Teams, Lars-Dominik Braun, 2022/06/05
Re: Teams, Andreas Enge, 2022/06/05
Re: Teams,
zimoun <=
Re: Teams, indieterminacy, 2022/06/05
Re: Teams, Mathieu Othacehe, 2022/06/05
Re: Teams, Maxim Cournoyer, 2022/06/06
Re: Teams, Ryan Prior, 2022/06/06
Re: Teams, Vagrant Cascadian, 2022/06/07