Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 15218781E21
	for <~alpine/devel@lists.alpinelinux.org>; Mon,  8 Jun 2020 08:59:54 +0000 (UTC)
Received: from mx1.tetrasec.net (mail.local [127.0.0.1])
	by mx1.tetrasec.net (Postfix) with ESMTP id 4515AAE11B;
	Mon,  8 Jun 2020 08:59:53 +0000 (UTC)
Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: alpine@tanael.org)
	by mx1.tetrasec.net (Postfix) with ESMTPSA id 7382CAE11A;
	Mon,  8 Jun 2020 08:59:52 +0000 (UTC)
Date: Mon, 8 Jun 2020 10:59:47 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Ariadne Conill <ariadne@dereferenced.org>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: team-maintained packages
Message-ID: <20200608105947.39003711@ncopa-desktop.copa.dup.pw>
In-Reply-To: <1765542.52O7J0OIYB@localhost>
References: <1765542.52O7J0OIYB@localhost>
X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 08 Jun 2020 02:13:49 -0600
Ariadne Conill <ariadne@dereferenced.org> wrote:

> Hello,
> 
> Now that Gitlab is deployed and in place, it is possible to have teams as 
> groups in gitlab, such as the core group[1].
> 
> As many maintainers and developers collaborate on packages anyway, I believe 
> it is useful to formalize this arrangement.
> 
> Accordingly, I believe that we should allow Gitlab groups to own packages to 
> achieve that.  A Gitlab group can be assigned issues in the issue tracker, and 
> can have designated "owners" of the group.  Groups are also publicly viewable.  
> This solves the traditional accountability issue with team maintenance.

I am in favor of this.

> 
> >From an APKBUILD perspective, the maintainer line would look like this:  
> 
> # 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.

I like the idea. The thing I am mostly worried about is when everyone
on the team thinks that someone else will take care of an incoming
issue, resulting in nobody doing it. I think that a "coordinator" role
for each team solves that.

I wonder if it is necessary to list the coordinator in every APKBUILD.
It gives us unnecessary work when role changes. Should be enough with
the url to the team.

> 
> Thoughts?
> 
> Ariadne
> 
> [1]: https://gitlab.alpinelinux.org/groups/core
>