Date: Tue, 9 Jun 2020 14:23:52 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Will Sinatra <wpsinatra@gmail.com>
Cc: Rasmus Thomsen <oss@cogitri.dev>, =?ISO-8859-1?B?U/ZyZW4=?= Tempel
 <soeren@soeren-tempel.net>, ~alpine/devel@lists.alpinelinux.org
Subject: Re: team-maintained packages
Message-ID: <20200609142352.5a992606@ncopa-desktop.copa.dup.pw>
In-Reply-To: <CAJH62qksawos3r2vo3AiWPuMm9=32RxM1ZJQo4LxNzGN065m4A@mail.gmail.com>
References: <1765542.52O7J0OIYB@localhost>
	<20200608105947.39003711@ncopa-desktop.copa.dup.pw>
	<7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev>
	<20200608124653.009172bf@ncopa-desktop.copa.dup.pw>
	<29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net>
	<afb56fbb1bdfc7debc6712eb28cd873ad5cf116e.camel@cogitri.dev>
	<CAJH62qksawos3r2vo3AiWPuMm9=32RxM1ZJQo4LxNzGN065m4A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, 9 Jun 2020 07:42:26 -0400
Will Sinatra <wpsinatra@gmail.com> wrote:

> Would the teams cover single packages, or rather large concepts?

Depends on the need, but I'd guess teams make more sense for larger
concepts, like documentation, infra, kernel, toolchain, GNOME.

Some teams may be unrelated packages (like developer relations), while
others may be about maintaining a group of packages (for example kernel)

The idea is to create teams as the need for them shows up.

> Would there be for instance a lisp team in charge of all lisp packages, or
> just an SBCL team in charge of SBCL, and a CLISP team in charge of CLISP,
> etc.

Depends on what the need is and what makes sense. If there is only a
single person interested in those things there may not be need to
create a team either.


> On Tue, Jun 9, 2020, 7:32 AM Rasmus Thomsen <oss@cogitri.dev> wrote:
>=20
> > On Tue, 2020-06-09 at 12:59 +0200, S=F6ren Tempel wrote: =20
> > > Natanael Copa <ncopa@alpinelinux.org> wrote: =20
> > > > Coordinators role would be to have overview and be a communication
> > > > point for the team. A contributor wants to help with something,
> > > > lets
> > > > say documentation, and it is known that there are 2 other people
> > > > working on it too. Who should the contributor speak with to avoid
> > > > double work? The coordinator. =20
> > >
> > > I think team coordination is something that could just be decided
> > > internally by the team itself. For instance, an IRC channel or
> > > similar
> > > would imho also be sufficient for coordination within the team
> > > without
> > > having a central team coordinator. =20
> >
> > Maybe the gitlab group could be used for communication since we'll have
> > one per team anyway I think.
> >
> > Regards,
> >
> > Rasmus
> > =20