Message-ID: <07962f2e60cd308eeca6cde744dab9ac7dc23bd1.camel@cogitri.dev>
Subject: Re: team-maintained packages
From: Rasmus Thomsen <oss@cogitri.dev>
To: Ariadne Conill <ariadne@dereferenced.org>, 
	~alpine/devel@lists.alpinelinux.org
Date: Mon, 08 Jun 2020 10:45:33 +0200
In-Reply-To: <1765542.52O7J0OIYB@localhost>
References: <1765542.52O7J0OIYB@localhost>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2020-06-08 at 02:13 -0600, Ariadne Conill wrote:
> Hello,
> 
> ...
> 
> # Maintainer: Alpine KDE team <
> https://gitlab.alpinelinux.org/groups/kde>
> # Coordinator: Whoever <whoever@alpinelinux.org>
> 
> The "coordinator" role would be the preferred member in the group for
> contact 
> about the package, but the team as a whole could also make decisions
> about the 
> package as well.
> 
> Thoughts?

Hello,

I think I overall like the idea of having maintenance teams (as long as
it's not mandatory to be in one to be permitted to touch an APKBUILD),
but I don't really see the point of having a coordinator. If you have a
preferred member which should be contacted for changes the APKBUILD
might as well be maintained by that individual directly.

Also, I'm not sure if we're having enough people who are actually
interested in forming such teams to make them actually viable. E.g. the
GNOME team would probably be just me, and KDE possibly you and
PureTryOut. I think that it might just end up being a lot of
bureaucracy without any substantial gain in the end when maintainers
aren't responsive enough and as such core members end up deciding
whether changes are merged or not in the end anyway.

Regards,

Rasmus