Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 6B281782B23 for <~alpine/devel@lists.alpinelinux.org>; Mon, 8 Jun 2020 08:54:44 +0000 (UTC) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced.org; s=default; t=1591606483; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2BnocfSw22kamlBMKS8zqNjoWyM4/HxplxaAobtXRRw=; b=Vq5xuKgRIVYHuVbjf18Hjoj8zvmamFy/YlxKphj6mdgfnVTu/ppvnUZIiZGQ5sVukhs4NG wWndJGdUsntlQ+f0+JBV9uKbNcypXabFrZB3BIkxcxSauzyiPxlShpy39+hqvpXZKkchR2 fMlUdfA5KKXJ3ftu33Rd/H1fmU6u93Q= From: Ariadne Conill To: ~alpine/devel@lists.alpinelinux.org, Rasmus Thomsen Subject: Re: team-maintained packages Date: Mon, 08 Jun 2020 02:54:39 -0600 Message-ID: <2069486.hgyNDFmY9b@localhost> In-Reply-To: <07962f2e60cd308eeca6cde744dab9ac7dc23bd1.camel@cogitri.dev> References: <1765542.52O7J0OIYB@localhost> <07962f2e60cd308eeca6cde744dab9ac7dc23bd1.camel@cogitri.dev> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.90 Hello, On Monday, June 8, 2020 2:45:33 AM MDT Rasmus Thomsen wrote: > On Mon, 2020-06-08 at 02:13 -0600, Ariadne Conill wrote: > > Hello, > > > > ... > > > > # 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. > > > > Thoughts? > > Hello, > > I think I overall like the idea of having maintenance teams (as long as > it's not mandatory to be in one to be permitted to touch an APKBUILD), > but I don't really see the point of having a coordinator. If you have a > preferred member which should be contacted for changes the APKBUILD > might as well be maintained by that individual directly. That is a fair point. > Also, I'm not sure if we're having enough people who are actually > interested in forming such teams to make them actually viable. E.g. the > GNOME team would probably be just me, and KDE possibly you and > PureTryOut. I think that it might just end up being a lot of > bureaucracy without any substantial gain in the end when maintainers > aren't responsive enough and as such core members end up deciding > whether changes are merged or not in the end anyway. I think we do. I also think that with some of the other changes I have in mind, we will be able to get more cross-distribution pollination going on in the APKBUILDs. But I am still thinking on the best way to achieve that right now. The idea is to avoid bureaucracy, and just have a group point of contact for packages. Normal policies including non-maintainer pushes would apply to group maintained packages. Thanks, Ariadne