From: Ariadne Conill <ariadne@dereferenced.org>
To: ~alpine/devel@lists.alpinelinux.org
Subject: team-maintained packages
Date: Mon, 08 Jun 2020 02:13:49 -0600
Message-ID: <1765542.52O7J0OIYB@localhost>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

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.

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.

Thoughts?

Ariadne

[1]: https://gitlab.alpinelinux.org/groups/core