From: Ariadne Conill <ariadne@dereferenced.org>
To: ~alpine/devel@lists.alpinelinux.org
Subject: Re: team-maintained packages
Date: Tue, 09 Jun 2020 20:11:50 -0600
Message-ID: <2409935.lMG0q3WddN@localhost>
In-Reply-To: <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net>
References: <1765542.52O7J0OIYB@localhost> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Hello,

On Tuesday, June 9, 2020 4:59:46 AM MDT S=F6ren Tempel wrote:
> I like the proposal in general, I am not so sure about team coordinators
> though.
>=20
> Natanael Copa <ncopa@alpinelinux.org> wrote:
> > 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.

Teams/SIGs/whatever we want to call them can organize however they wish.  T=
he=20
purpose of the coordinator role is to provide a point of contact for the te=
am,=20
be it for newcomers who are interested in joining the team or if the core t=
eam=20
requires something from a specific team*.

(* I have plans for splitting the core team into a few new teams, that allo=
w=20
for people to participate according to their expertise instead of being on =
a=20
catch-all but lets make baby steps.)

Ariadne