Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 222F7782BBC for <~alpine/devel@lists.alpinelinux.org>; Mon, 8 Jun 2020 09:12:19 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1591607534; bh=dlas4e8C4M8ySIWRmWyZ08CeSME/GQ23c3VZE9XWn3k=; h=Subject:From:To:Cc:In-Reply-To:References; b=n/OVlgeLZgBAvCDAbDHzm+9JgQADRSansYxIv41XKMrDkbePUOLP1tzB6OlkJZl07 016WvExUmeRvxoNBID7hqMcX7xh9sV1XQDFGYsR5FMo3HRukOS1XfVIgKmJ0YDN+Mk eVYibw1Y2pbdk3nOgCCzDJz+s0PoHygbv8LEes+LxKxU1VMTOr3yDDENoKRwOFgiJS MvgjsxnB9GXrg80naF7DX7Au2l3wpSaZiSn1v9gBCvlro2+Ca60k1e/4+GbojSpf8s sc+zGpw/JBSCpDRMYXzp/87Jame+WojskcoMRPQGLyP/utBHQ5vbGUAawFBhv4MmS1 VNkV5JtIGuzWg== Subject: Re: team-maintained packages From: Rasmus Thomsen To: Natanael Copa , Ariadne Conill Cc: ~alpine/devel@lists.alpinelinux.org Date: Mon, 08 Jun 2020 11:12:13 +0200 In-Reply-To: <20200608105947.39003711@ncopa-desktop.copa.dup.pw> References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit On Mon, 2020-06-08 at 10:59 +0200, Natanael Copa wrote: > On Mon, 08 Jun 2020 02:13:49 -0600 > Ariadne Conill wrote: > > [...] > > > > From an APKBUILD perspective, the maintainer line would look like > > > this: > > > > # Maintainer: Alpine KDE team < > > https://gitlab.alpinelinux.org/groups/kde> > > # Coordinator: Whoever > > > > 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. Isn't the idea to have teams so that everyone can look at any APKBUILD the team maintains when they have time/feel like it? I think that: 1) We'll have a hard time finding people with enough time to coordinate a team. 2) We'll place too much workload on the coordinator instead of just distributing the load across all members of the teams. Also, I'm not quite sure what the coordinator would do. They could poke someone from the team they think could review the MR, but if that person were interested in reviewing the MR they'd probably do so when they get the email for the team-ping on that MR. So the coordinator would either end up reviewing the MR (defeating the point of the team) or would have to poke indiviuals who really should just look at the team notifications if they're interested in being in the team. Regards, Rasmus