Received: from vps892.directvps.nl (ikke.info [178.21.113.177])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id E4267781D45
	for <~alpine/devel@lists.alpinelinux.org>; Wed,  1 Jul 2020 20:04:22 +0000 (UTC)
Received: by vps892.directvps.nl (Postfix, from userid 1008)
	id ACA7C440122; Wed,  1 Jul 2020 22:04:21 +0200 (CEST)
Date: Wed, 1 Jul 2020 22:04:21 +0200
From: Kevin Daudt <kdaudt@alpinelinux.org>
To: Ariadne Conill <ariadne@dereferenced.org>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: team-maintained packages
Message-ID: <20200701200421.GA2450243@alpha>
References: <1765542.52O7J0OIYB@localhost>
 <1718657.Euugps0dR9@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1718657.Euugps0dR9@localhost>

On Tue, Jun 09, 2020 at 08:37:05PM -0600, Ariadne Conill wrote:
> Hello,
> 
> On Monday, June 8, 2020 2:13:49 AM MDT Ariadne Conill 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.

Sadly, you cannot assign issues to groups in Gitlab (and apparently
unlikely to be added[0]). I think as an alternative we could assign it
to the coordinator who can delegate it, perhaps combined with mentioning
the group.

> > >From an APKBUILD perspective, the maintainer line would look like this:
> > # Maintainer: Alpine KDE team <https://gitlab.alpinelinux.org/groups/kde>

I assume abuild, apk-tools and aports-turbo have no issues with this?
(mainly the url in the e-mail part).

> > # 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?
> > 
> > Ariadne
> > 
> > [1]: https://gitlab.alpinelinux.org/groups/core
> 
> As an update to this, it appears we have consensus on the following points:
> 
> 1. Teams should exist and be managed using Gitlab.
> 2. Teams may own packages, the Maintainer entry points to their Gitlab group 
> URI.
> 3. Teams should have a coordinator role that is reflected as the "Owner" role 
> in the group.  The coordinator role may change from time to time based on 
> consensus of the group.
> 
> Accordingly, I would like to propose the following groups as an initial test 
> of this proposal.  The member lists here are not exhaustive, I know I am 
> missing people who would probably like to be members or should be members of 
> these teams.
> 
> [..]
> 
> There are other parts of the system that could benefit from this, but lets wait 
> on those until we become more comfortable with team maintenance and SIGs in 
> general.
> 
> Ariadne
> 

As no one seems to have opposed this, I think we can go ahead and start
creating these groups.

I will be creating this as 'user' groups, which means creating projects
will be disabled. This is consistent how we did it for the currently
existing groups as well.

Kevin

[0]:https://gitlab.com/gitlab-org/gitlab/-/issues/6008