From: Ariadne Conill <ariadne@dereferenced.org>
To: Kevin Daudt <kdaudt@alpinelinux.org>, ~alpine/devel@lists.alpinelinux.org
Subject: Re: team-maintained packages
Date: Fri, 10 Jul 2020 10:08:51 -0600
Message-ID: <5716335.JtOabaumii@localhost>
In-Reply-To: <20200708201321.GA2534782@alpha>
References: <1765542.52O7J0OIYB@localhost> <20200701200421.GA2450243@alpha> <20200708201321.GA2534782@alpha>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Wednesday, July 8, 2020 2:13:21 PM MDT Kevin Daudt wrote:
> On Wed, Jul 01, 2020 at 10:04:21PM +0200, Kevin Daudt wrote:
> > 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
> 
> I've now added members to these teams and made them public. Do we also
> want a Gnome team btw?
> 
> Let me know if you think anything should be changed.

I think the next step is to validate that aports-turbo will work with the 
change.  Based on what I have seen of the code it should be fine, but would be 
nice to verify it.

Ariadne