From nobody Fri Mar 29 15:55:19 2024 Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id CD941781D5C for <~alpine/devel@lists.alpinelinux.org>; Mon, 8 Jun 2020 08:13:54 +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=1591604033; 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; bh=RhGeVuuTgNlQoJA6tMHIDIvsL1lmaXKPUlJ01YNRW0g=; b=sHJCqip8FjWnD4fXR0JjgCQtQf/yAbvrhN6cZFBkMnIVI/vsz9lM11bD/0kIYeO27wmoww f3kKTy2+qoOS1Sj4Q/utDM1mqvD1hjT/tdhzsKnV9C0rUps+7Fwm97jkEbt80jLCrFqA4F ni7Pf9cK3Qf8zE9auQS22G5Ta21phBU= From: Ariadne Conill 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" X-Spam-Score: 0.90 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 # 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? Ariadne [1]: https://gitlab.alpinelinux.org/groups/core From nobody Fri Mar 29 15:55:19 2024 Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 7477C781B61 for <~alpine/devel@lists.alpinelinux.org>; Mon, 8 Jun 2020 08:45:36 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: <07962f2e60cd308eeca6cde744dab9ac7dc23bd1.camel@cogitri.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1591605934; bh=Ps42fYJOtvUu+Ihc79bWJo+rKub+scgCSR5CHjMQxzk=; h=Subject:From:To:In-Reply-To:References; b=ZyzEv4garrCVvyjTaDgn8oI4Vmfgfbvzsfl7SiTN2ZFqnEoeQyMgtdBt+y+7ucBuV czW5pZTxdlG9kC1Jwestv8sUY94lVyrbeL1SYU47tfZgb7Nkv1JpDe1Ls97/dYC9BA gjZ25VMNjqI/GOjdREaYTadmSks6ADeDUatd6tearXfr7RRlf9pHpd005U1OdTI44P B+eY4rFabWDgHqkq5MNtPCcM5Lg8+K+VQGhVUzZXTI1Uor6XL94C4mY6ez7Am0lWJP T2Xab4xc8f0Dbk9Gk9PbUPRqfumQPQ9bs9ngFVrfS7yAZdVrP6XyhPDLpl6UglOg97 pMZ/BeGW790XQ== Subject: Re: team-maintained packages From: Rasmus Thomsen To: Ariadne Conill , ~alpine/devel@lists.alpinelinux.org Date: Mon, 08 Jun 2020 10:45:33 +0200 In-Reply-To: <1765542.52O7J0OIYB@localhost> References: <1765542.52O7J0OIYB@localhost> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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. 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. Regards, Rasmus From nobody Fri Mar 29 15:55:19 2024 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 From nobody Fri Mar 29 15:55:19 2024 Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 15218781E21 for <~alpine/devel@lists.alpinelinux.org>; Mon, 8 Jun 2020 08:59:54 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 4515AAE11B; Mon, 8 Jun 2020 08:59:53 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 7382CAE11A; Mon, 8 Jun 2020 08:59:52 +0000 (UTC) Date: Mon, 8 Jun 2020 10:59:47 +0200 From: Natanael Copa To: Ariadne Conill Cc: ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages Message-ID: <20200608105947.39003711@ncopa-desktop.copa.dup.pw> In-Reply-To: <1765542.52O7J0OIYB@localhost> References: <1765542.52O7J0OIYB@localhost> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 08 Jun 2020 02:13:49 -0600 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. I am in favor of this. > > >From an APKBUILD perspective, the maintainer line would look like this: > > # Maintainer: Alpine KDE team > # 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. I wonder if it is necessary to list the coordinator in every APKBUILD. It gives us unnecessary work when role changes. Should be enough with the url to the team. > > Thoughts? > > Ariadne > > [1]: https://gitlab.alpinelinux.org/groups/core > From nobody Fri Mar 29 15:55:19 2024 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 From nobody Fri Mar 29 15:55:19 2024 Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 55D42782BCF for <~alpine/devel@lists.alpinelinux.org>; Mon, 8 Jun 2020 10:47:01 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 89C4CAE59C; Mon, 8 Jun 2020 10:47:00 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id C4CD5AE59B; Mon, 8 Jun 2020 10:46:59 +0000 (UTC) Date: Mon, 8 Jun 2020 12:46:53 +0200 From: Natanael Copa To: Rasmus Thomsen Cc: Ariadne Conill , ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages Message-ID: <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> In-Reply-To: <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 08 Jun 2020 11:12:13 +0200 Rasmus Thomsen wrote: > 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? Sure. > 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. I don't think the teams will be bigger than 1-2 initially so there will not be any coordination work. But it will prepare us to scale. It will also serve as a form of documentation on who takes care of what. But I agree, we don't want needless administrative work. > 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. I think anyone in the team could review and merge the MRs if the teams wants that. I also support that even people who are not on the team should be able to review and merge MRs, like we do now. Coordinators role would be to have overview and be a communication point for the team. A contributor wants to help with something, lets say documentation, and it is known that there are 2 other people working on it too. Who should the contributor speak with to avoid double work? The coordinator. I expect the coordinator role be nothing more than a name in the documentation of who is doing what initially, but the role will be more significant as the size of the team increases. -nc From nobody Fri Mar 29 15:55:19 2024 Received: from magnesium.8pit.net (magnesium.8pit.net [45.76.88.171]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 15CC5782BD8 for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 10:59:48 +0000 (UTC) Received: from magnesium.8pit.net (localhost [127.0.0.1]) by magnesium.8pit.net (OpenSMTPD) with ESMTP id 1f410159 for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 12:59:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=soeren-tempel.net; h=date :to:subject:from:references:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; s=opensmtpd; bh=HQa9CWT hVSE1jrYEgSYjf+HaOME=; b=f87S+ia5WONTyUWWLCB3I2BbW9NwG+h+LMIo0cn YIUUpTZbG6R1r/rRfVH0saJ+d3hz9Xox0L9AIXyA34nY7XIw4peEsgNNeoRRcED0 4VxADwjnPW81UuJ9iyHi/Vyz9WOBRF7ay/KZByL/cIiwZMvtiH33Mq+TMBBiVF3R bHs0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=soeren-tempel.net; h=date:to :subject:from:references:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; q=dns; s=opensmtpd; b=H bXamRofanIq9AiNvE/fpWtOmxHY2Ul4N4rvGSZ2tKxHebbhBuK3e2AfwsRvEc6zR Dh6v1BkUeF3y23ItSgvo7+Vx0p9wW0gwRvF+VRBZRCzGqlAwlZNrXbSMsdZRPNJm p9q1L/VGMC7qDqSxgJ8IfwSVQwh//JoBWLBhLNASpk= Received: from localhost (ip4d17229f.dynamic.kabel-deutschland.de [77.23.34.159]) by magnesium.8pit.net (OpenSMTPD) with ESMTPSA id 2792fd87 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:YES) for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 12:59:47 +0200 (CEST) Date: Tue, 09 Jun 2020 12:59:46 +0200 To: ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages From: =?UTF-8?Q?S=C3=B6ren?= Tempel References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> In-Reply-To: <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> Message-Id: <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I like the proposal in general, I am not so sure about team coordinators though. Natanael Copa wrote: > Coordinators role would be to have overview and be a communication > point for the team. A contributor wants to help with something, lets > say documentation, and it is known that there are 2 other people > working on it too. Who should the contributor speak with to avoid > double work? The coordinator. I think team coordination is something that could just be decided internally by the team itself. For instance, an IRC channel or similar would imho also be sufficient for coordination within the team without having a central team coordinator. Cheers, S=C3=B6ren From nobody Fri Mar 29 15:55:19 2024 Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 9CD8D781A65 for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 11:31:49 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1591702305; bh=0KEnNPLoVTaVqrJG7Ko4+1EbLIunNw8gyzNZCagvqTI=; h=Subject:From:To:In-Reply-To:References; b=QunEkvpQEMp0MP7NFuhE14PxOYP4Dir+1EbbikAeW9CCNFZUvaGoxC144oK8QycCz 4x1baWsd1kd4XrDAN5neI8ByNjv/6Kddo5VNciQCZ5QBSnNtJSphbYge6bCguSTZYu R/CVvMHve2FdBin0bZ8XRBTzPRXYKg3v8o6cN/bVH7tEHoCQ8vKxhuQwwd0mLcq+PM bQO6721X6rlfPgZGp2fWqyhEVPeF/aVmRbWGX563QYNpAeEz7b3JPBSDemfxKNXrx/ /gW2w3cxo6EPgD80d1F0Myw1Eilivynx8Si4X+IYJ/BoDr8KZtzYk/lhP1bKATn0re OokGVv/uBaCJQ== Subject: Re: team-maintained packages From: Rasmus Thomsen To: =?ISO-8859-1?Q?S=F6ren?= Tempel , ~alpine/devel@lists.alpinelinux.org Date: Tue, 09 Jun 2020 13:31:43 +0200 In-Reply-To: <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-QRsoY+jKamB6iwEpB/jx" Mime-Version: 1.0 --=-QRsoY+jKamB6iwEpB/jx Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempel wrote: > Natanael Copa wrote: > > Coordinators role would be to have overview and be a communication > > point for the team. A contributor wants to help with something, > > lets > > say documentation, and it is known that there are 2 other people > > working on it too. Who should the contributor speak with to avoid > > double work? The coordinator. >=20 > I think team coordination is something that could just be decided > internally by the team itself. For instance, an IRC channel or > similar > would imho also be sufficient for coordination within the team > without > having a central team coordinator. Maybe the gitlab group could be used for communication since we'll have one per team anyway I think. Regards, Rasmus --=-QRsoY+jKamB6iwEpB/jx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEErepJabCshwIJ3OXBERUkFRgVTqYFAl7fcx8ACgkQERUkFRgV TqaSHg//e5aLNP4l/NWdLqktVxOUfmcUaEOzP+xiVDS0XfXg1Tlp47BOGGtIIFzA vxtjsh5bLb2lQag0b4kfi5R3iUd4/5A2SUJnTqG1Ga8rPI0C+1lYxItDoivxxKG/ mKsoz3PG8ne94lOMuEZsStoIo68YrZhdVrVhz8WPI/9viRXvgvjuD5Q4MwApECtM zS4pucw4EaiqtYtVuvY8XgI1T5unQWYmRvC90OdZ4Kwyilaponm0Nn8OkJXyAAPU FHHE+z0/aAKDYm3r26NxdJYpYMkR8SowZFbaXuC5Q4mE0s8Q8LMqzDyg9w4e5hgR x0wPyBJWZ7X0Kykcwlp93EhMy2C4Ro6c2L3naxXkLl7x5mrclrwkZ5900Sfkelh6 fpYPBLEGSe1TsWAHR6RTSsGD/mVFWPUGwsrcBPcXHv/ts18FlmPDqFeEJleLXowl whcuLtiVDT8TGVlVQ8jlgqoJ9DbB5idKABTjEqBbOTvVjTXz2cTYJGF4Oz6+SosB WdzpZM1rHN/InMOT2gdlaIb4f/oyNL9DtnfWjluHW5QGlm2Isl5/Zl0avXPFLX9c vO3ydiBcRBl+rB6Vdt+LmgWEyCeoeXnQgNViiZ/g4q8fnkQuSnNWQvbw7dgCO2hI sFIwV+/Sar4OQfKXQEzyeeCCeQPQPn/B9mp2VoczBy6XhpG/nVs= =NMPF -----END PGP SIGNATURE----- --=-QRsoY+jKamB6iwEpB/jx-- From nobody Fri Mar 29 15:55:19 2024 Received: from mail-oi1-f178.google.com (mail-oi1-f178.google.com [209.85.167.178]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 5C317782C29 for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 11:42:40 +0000 (UTC) Received: by mail-oi1-f178.google.com with SMTP id a3so6433540oid.4 for <~alpine/devel@lists.alpinelinux.org>; Tue, 09 Jun 2020 04:42:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PXAIWpiYZp0Ktt2yDRfnD/THQV4/r/woeNTI82fa93E=; b=VUXpv57UsltKPoR7QORwwHIy+pP0erycufgP3SXrvmvfKnuEGqoiyWpcCygb0o15dq hNooFnX2v5kCcUssoQTXltaPgGEEET3qhquS886qc7BPAjJQi74vJfKKT/d/UMemt2jh p6MClvonBxfmz0bOxsr5Jtgg/CKNkn/pOVBea8EiAAM8uF7CycdiSbzxWltHbOedw2wP GWvbAtHN3ewESRnr0FD5LJUTasKDRgX8nJYjMVhrO+m3o97FZ3xiR9EzmZv2Sd9K03hi Wk//9zMdT47wWgD/hZ5tuqQUswLd3T1/UsOs603z3/0NJdHmuYBc1PfG27n5jCfSRAt/ qwnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PXAIWpiYZp0Ktt2yDRfnD/THQV4/r/woeNTI82fa93E=; b=fxsuN+aUP7PvCtkWhRFwIM5mh5Jn+mAKtIFt8GehanCAfueTELgHgjZB4tYDJOMpbc lKdKQgANCGJNE/G5HMDhttpapT64GFowuqFC/U6yyL354RUwotVmmmh6vWa+vDAMQALv EpD0V9oOhTElepVEWz+AnJqZWqvDqIhx/tzbgLaeDOUWuBnMYTH6Gi4qKL9BSryd6Om5 cNoYYg21E/zRtWo2QzXGScz+vUphDKELWTXU05UL7POCq33oBXvy80YTya1kpqB/ya++ 5+boXRtEDpzGZSLvqm53rT6t28QlnhrRrQ4EEcsAnGqQRDY1OAxS37wt5HJuRxBF4x1G C+fQ== X-Gm-Message-State: AOAM532clptYHV7nIWmFRWZwxpiKV10VDug0FiyCIY1uCqSyKwcakBER UOWj9+NBI1yjqwYduM4djZaI1aDJkotcxLHSabc= X-Google-Smtp-Source: ABdhPJyFbTMhfx51J2dWFtgfLqv9UZbJGWUYN3gMscCMtLxy2v/kfGl4MQmS+CoRRYG+d0lVVh0enBe45VEV1A/4OBU= X-Received: by 2002:aca:da56:: with SMTP id r83mr2848712oig.106.1591702958985; Tue, 09 Jun 2020 04:42:38 -0700 (PDT) MIME-Version: 1.0 References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> In-Reply-To: From: Will Sinatra Date: Tue, 9 Jun 2020 07:42:26 -0400 Message-ID: Subject: Re: team-maintained packages To: Rasmus Thomsen Cc: =?UTF-8?Q?S=C3=B6ren_Tempel?= , ~alpine/devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000075550105a7a53979" --00000000000075550105a7a53979 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Would the teams cover single packages, or rather large concepts? Would there be for instance a lisp team in charge of all lisp packages, or just an SBCL team in charge of SBCL, and a CLISP team in charge of CLISP, etc. On Tue, Jun 9, 2020, 7:32 AM Rasmus Thomsen wrote: > On Tue, 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempel wrote: > > Natanael Copa wrote: > > > Coordinators role would be to have overview and be a communication > > > point for the team. A contributor wants to help with something, > > > lets > > > say documentation, and it is known that there are 2 other people > > > working on it too. Who should the contributor speak with to avoid > > > double work? The coordinator. > > > > I think team coordination is something that could just be decided > > internally by the team itself. For instance, an IRC channel or > > similar > > would imho also be sufficient for coordination within the team > > without > > having a central team coordinator. > > Maybe the gitlab group could be used for communication since we'll have > one per team anyway I think. > > Regards, > > Rasmus > --00000000000075550105a7a53979 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Would the teams cover single packages, or rather large co= ncepts?

Would there be for ins= tance a lisp team in charge of all lisp packages, or just an SBCL team in c= harge of SBCL, and a CLISP team in charge of CLISP, etc.

On Tue, Jun 9= , 2020, 7:32 AM Rasmus Thomsen <oss@c= ogitri.dev> wrote:
On Tue, = 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempel wrote:
> Natanael Copa <ncopa@alpinelinux.org> wrote:
> > Coordinators role would be to have overview and be a communicatio= n
> > point for the team. A contributor wants to help with something, > > lets
> > say documentation, and it is known that there are 2 other people<= br> > > working on it too. Who should the contributor speak with to avoid=
> > double work? The coordinator.
>
> I think team coordination is something that could just be decided
> internally by the team itself. For instance, an IRC channel or
> similar
> would imho also be sufficient for coordination within the team
> without
> having a central team coordinator.

Maybe the gitlab group could be used for communication since we'll have=
one per team anyway I think.

Regards,

Rasmus
--00000000000075550105a7a53979-- From nobody Fri Mar 29 15:55:19 2024 Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 046A1782C40 for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 12:24:00 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 9C0DAAFB6C; Tue, 9 Jun 2020 12:23:59 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 00358AFB6B; Tue, 9 Jun 2020 12:23:57 +0000 (UTC) Date: Tue, 9 Jun 2020 14:23:52 +0200 From: Natanael Copa To: Will Sinatra Cc: Rasmus Thomsen , =?ISO-8859-1?B?U/ZyZW4=?= Tempel , ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages Message-ID: <20200609142352.5a992606@ncopa-desktop.copa.dup.pw> In-Reply-To: References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, 9 Jun 2020 07:42:26 -0400 Will Sinatra wrote: > Would the teams cover single packages, or rather large concepts? Depends on the need, but I'd guess teams make more sense for larger concepts, like documentation, infra, kernel, toolchain, GNOME. Some teams may be unrelated packages (like developer relations), while others may be about maintaining a group of packages (for example kernel) The idea is to create teams as the need for them shows up. > Would there be for instance a lisp team in charge of all lisp packages, or > just an SBCL team in charge of SBCL, and a CLISP team in charge of CLISP, > etc. Depends on what the need is and what makes sense. If there is only a single person interested in those things there may not be need to create a team either. > On Tue, Jun 9, 2020, 7:32 AM Rasmus Thomsen wrote: >=20 > > On Tue, 2020-06-09 at 12:59 +0200, S=F6ren Tempel wrote: =20 > > > Natanael Copa wrote: =20 > > > > Coordinators role would be to have overview and be a communication > > > > point for the team. A contributor wants to help with something, > > > > lets > > > > say documentation, and it is known that there are 2 other people > > > > working on it too. Who should the contributor speak with to avoid > > > > double work? The coordinator. =20 > > > > > > I think team coordination is something that could just be decided > > > internally by the team itself. For instance, an IRC channel or > > > similar > > > would imho also be sufficient for coordination within the team > > > without > > > having a central team coordinator. =20 > > > > Maybe the gitlab group could be used for communication since we'll have > > one per team anyway I think. > > > > Regards, > > > > Rasmus > > =20 From nobody Fri Mar 29 15:55:19 2024 Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 508F5782C4B for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 12:24:50 +0000 (UTC) Received: by mail-qk1-f175.google.com with SMTP id 205so20525507qkg.3 for <~alpine/devel@lists.alpinelinux.org>; Tue, 09 Jun 2020 05:24:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y91K2rc0/LgoZF1ADSRxG61gSANJNLSE77//SDaClYA=; b=D2kVuWLSOgPzR2TmvcjnkMD/+CuFR1y8eFE/mrWzpupAzSZJo2GEAvwiUSbjKHPD1d dZrwZSgYtBZpkqbSWadmRttPWiZVAgw7APMACkp+1wRn1TBqRcYfdRthEDF5AVfaCUTj U9ij+xHsO7hoB72BvDh7xNM1bbIVXUGALhusK5YEugO4dH/ZhHhBmxUn6O3v5892KwyS Bs9gHGfqKciv+JIsOPglWa5f8PVfVhJOrn3rKsmD3kK9xwLglAP4DBqmQeN6/2C6Z6NG NxZ7u+V65djk+doLFeGvfI1xpJYT9XLwEnMHwEbyyPr/iPNAcU1lIiq3nZoeM44rzBBL gHFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y91K2rc0/LgoZF1ADSRxG61gSANJNLSE77//SDaClYA=; b=WY8es/1chAm3u9MYiBi/hv4iE84DF8EvXi21vXMyYg3kv3e7gQf2Xn2FIGqwrCaBPx P8xLMZ/WFEUE6q9Wy0AkPX0t9HW71or7Kqg1OfU9wlnuO8A/naCSIueTrfbeb7J4cI1t lvV8zyU69JF5ZC7zfSC/Mkb/LMJHNmiYufmXNg5L6pkKHYhfc21AZQStM8UBdqINc5i0 zeCEAnv4XdNsFxFpSeRYDlGMR4XXFCyi9Mhl91RBjMJfsx6Q2noHdZ1Ms/5tP3AbLrc6 QAf3CLbJ3zMqAixOMayfEMB4YOZwb4t3SJwRUNp0VoA0WbpmJGfy50cIF2KEKjFZoyBV Lo6Q== X-Gm-Message-State: AOAM532CEYeXVGiFwf5Qs1YMtloTpZlegpSDM23QN/Q2L/TKXJ9M8xvt wNuqMP7XKkb5bUs8uoMcWSx0RMJg4r5yvo7sZ7E= X-Google-Smtp-Source: ABdhPJzSIRuRFyG+Ui4xCqeRr3XZFP6+HNm3Ws5Ed14VLacEeklUzVSGmUXCSb7rdzlFI4a9sqpW+X98SaSxGAVL+xE= X-Received: by 2002:a37:9cb:: with SMTP id 194mr26626834qkj.456.1591705489179; Tue, 09 Jun 2020 05:24:49 -0700 (PDT) MIME-Version: 1.0 References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> In-Reply-To: From: Timothy Legge Date: Tue, 9 Jun 2020 09:24:37 -0300 Message-ID: Subject: Re: team-maintained packages To: Will Sinatra Cc: Rasmus Thomsen , =?UTF-8?Q?S=C3=B6ren_Tempel?= , "~alpine/devel" <~alpine/devel@lists.alpinelinux.org> Content-Type: multipart/alternative; boundary="0000000000004507b705a7a5d0de" --0000000000004507b705a7a5d0de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am willing to help out with Perl packages. I have not ventured much further at this point. On Tue, Jun 9, 2020 at 8:42 AM Will Sinatra wrote: > Would the teams cover single packages, or rather large concepts? > > Would there be for instance a lisp team in charge of all lisp packages, o= r > just an SBCL team in charge of SBCL, and a CLISP team in charge of CLISP, > etc. > > On Tue, Jun 9, 2020, 7:32 AM Rasmus Thomsen wrote: > >> On Tue, 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempel wrote: >> > Natanael Copa wrote: >> > > Coordinators role would be to have overview and be a communication >> > > point for the team. A contributor wants to help with something, >> > > lets >> > > say documentation, and it is known that there are 2 other people >> > > working on it too. Who should the contributor speak with to avoid >> > > double work? The coordinator. >> > >> > I think team coordination is something that could just be decided >> > internally by the team itself. For instance, an IRC channel or >> > similar >> > would imho also be sufficient for coordination within the team >> > without >> > having a central team coordinator. >> >> Maybe the gitlab group could be used for communication since we'll have >> one per team anyway I think. >> >> Regards, >> >> Rasmus >> > --0000000000004507b705a7a5d0de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am willing to help out with Perl packages.=C2=A0 I have = not ventured much further at this point.

On Tue, Jun 9, 2020 at 8:42 AM Will= Sinatra <wpsinatra@gmail.com= > wrote:
Would the teams cover single packages, or rather large concep= ts?

Would there be for instanc= e a lisp team in charge of all lisp packages, or just an SBCL team in charg= e of SBCL, and a CLISP team in charge of CLISP, etc.

On Tue, Jun 9, 20= 20, 7:32 AM Rasmus Thomsen <oss@cogitri.dev> wrote:
On Tue, 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempe= l wrote:
> Natanael Copa <ncopa@alpinelinux.org> wrote:
> > Coordinators role would be to have overview and be a communicatio= n
> > point for the team. A contributor wants to help with something, > > lets
> > say documentation, and it is known that there are 2 other people<= br> > > working on it too. Who should the contributor speak with to avoid=
> > double work? The coordinator.
>
> I think team coordination is something that could just be decided
> internally by the team itself. For instance, an IRC channel or
> similar
> would imho also be sufficient for coordination within the team
> without
> having a central team coordinator.

Maybe the gitlab group could be used for communication since we'll have=
one per team anyway I think.

Regards,

Rasmus
--0000000000004507b705a7a5d0de-- From nobody Fri Mar 29 15:55:19 2024 Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 3DD00782C6C for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 12:26:20 +0000 (UTC) Received: by mail-qk1-f175.google.com with SMTP id q8so20511159qkm.12 for <~alpine/devel@lists.alpinelinux.org>; Tue, 09 Jun 2020 05:26:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=hxfljURE54DW30ft0lKhtPHGZ07BWTjhhBJf+BwF2CU=; b=iXn5l6AfgUgmCdfGRHkAEWXVxchkpEWF/hWv4+1qLwh5QPN4uXBmgm7C/Q9UrvoKr+ Ly2xSx8JIV9/lAjIAtr27hI/KGdjapqPtmWhAbTyBXy96GU6VX7PplcHt3xBsTnKgfTJ kOvD/j7iekr8u9s0XpvBm55eJs6Z4baqqOm4a1Ie5LmBIornhYX3/dI4bZBKH8+D324T 3svRsXgoVBn/l6BejcrfYMpMTkACziOP0joCMsD2DyfhTLKQWz24dDaVGIr9C70Wvf1B /wHLukm9SAiRdShSjHnAlljwQy7bpVW7HW293BdwroBC80fFjzvo9fd4NnMLY5DkVDjR CJQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=hxfljURE54DW30ft0lKhtPHGZ07BWTjhhBJf+BwF2CU=; b=R89YQulA0rOXaWfkiKVDQdm/wpxJlNNDkx+VktSwUeb6O3R5AMTrmQKR8fq2V7AzSK i8AYLkt8zQdw9Is1HUnVQeRzsuvYFA6tpaaqu5VSFjUs5dt5uqs2gV9sq8oydVKlIa8B 7cVVVu4oQpt75LaCjse6tqU4GceaYznMzTmayKBBPlJPzhFnVRLPpGdtaJpL8X7m544f RXw6d71I2M2rX7SeRcwVlI9XYTihPrrPELBCsZ28ESRzBkqcN49ERoXcLiERS88TfWM+ MzbNSp59WKvDjmWDaXxvHh/e/30hcy10ZfDW4043w++rq/3mY7ceq1JQyjBIk9PQUptq MLWw== X-Gm-Message-State: AOAM531jJFz8I8O2VXk7I0UOR7YmzJ+EUEd79g/Kk3bz0dCleSeQWVlX tT92VcrpBr3MpikZu2CbvDup9b1mDdkNKeX5zQnoZ+Q4da4= X-Google-Smtp-Source: ABdhPJwXs5ttvOzAlJB1D9JSUm+d44OAl7FSuiiiRTGOKOFwwUHInm9rIovWQXgKrpgli/kCjFTZhpcIN/+EPasoUwI= X-Received: by 2002:a05:620a:24c:: with SMTP id q12mr27791572qkn.172.1591705578987; Tue, 09 Jun 2020 05:26:18 -0700 (PDT) MIME-Version: 1.0 References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> In-Reply-To: From: Timothy Legge Date: Tue, 9 Jun 2020 09:26:07 -0300 Message-ID: Subject: Re: team-maintained packages To: "~alpine/devel" <~alpine/devel@lists.alpinelinux.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am willing to help out with Perl packages. I have not ventured much further at this point. On Tue, Jun 9, 2020 at 8:42 AM Will Sinatra wrote: > > Would the teams cover single packages, or rather large concepts? > > Would there be for instance a lisp team in charge of all lisp packages, o= r just an SBCL team in charge of SBCL, and a CLISP team in charge of CLISP,= etc. > > On Tue, Jun 9, 2020, 7:32 AM Rasmus Thomsen wrote: >> >> On Tue, 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempel wrote: >> > Natanael Copa wrote: >> > > Coordinators role would be to have overview and be a communication >> > > point for the team. A contributor wants to help with something, >> > > lets >> > > say documentation, and it is known that there are 2 other people >> > > working on it too. Who should the contributor speak with to avoid >> > > double work? The coordinator. >> > >> > I think team coordination is something that could just be decided >> > internally by the team itself. For instance, an IRC channel or >> > similar >> > would imho also be sufficient for coordination within the team >> > without >> > having a central team coordinator. >> >> Maybe the gitlab group could be used for communication since we'll have >> one per team anyway I think. >> >> Regards, >> >> Rasmus From nobody Fri Mar 29 15:55:19 2024 Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.176.36]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id B4E26782C3F for <~alpine/devel@lists.alpinelinux.org>; Tue, 9 Jun 2020 13:13:02 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id C653BAFC4E; Tue, 9 Jun 2020 13:13:01 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id EFCAAAFC4D; Tue, 9 Jun 2020 13:13:00 +0000 (UTC) Date: Tue, 9 Jun 2020 15:12:55 +0200 From: Natanael Copa To: Timothy Legge Cc: "~alpine/devel" <~alpine/devel@lists.alpinelinux.org> Subject: Re: team-maintained packages Message-ID: <20200609151255.4d78a7ac@ncopa-desktop.copa.dup.pw> In-Reply-To: References: <1765542.52O7J0OIYB@localhost> <20200608105947.39003711@ncopa-desktop.copa.dup.pw> <7a0647b48d615b4f61f776c3e34374f50c61b85e.camel@cogitri.dev> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, 9 Jun 2020 09:26:07 -0300 Timothy Legge wrote: > I am willing to help out with Perl packages. I have not ventured much > further at this point. Very nice! I think this illustrates the value of having teams or SIGs (special interest group). -nc >=20 >=20 > On Tue, Jun 9, 2020 at 8:42 AM Will Sinatra wrote: > > > > Would the teams cover single packages, or rather large concepts? > > > > Would there be for instance a lisp team in charge of all lisp packages,= or just an SBCL team in charge of SBCL, and a CLISP team in charge of CLIS= P, etc. > > > > On Tue, Jun 9, 2020, 7:32 AM Rasmus Thomsen wrote: =20 > >> > >> On Tue, 2020-06-09 at 12:59 +0200, S=F6ren Tempel wrote: =20 > >> > Natanael Copa wrote: =20 > >> > > Coordinators role would be to have overview and be a communication > >> > > point for the team. A contributor wants to help with something, > >> > > lets > >> > > say documentation, and it is known that there are 2 other people > >> > > working on it too. Who should the contributor speak with to avoid > >> > > double work? The coordinator. =20 > >> > > >> > I think team coordination is something that could just be decided > >> > internally by the team itself. For instance, an IRC channel or > >> > similar > >> > would imho also be sufficient for coordination within the team > >> > without > >> > having a central team coordinator. =20 > >> > >> Maybe the gitlab group could be used for communication since we'll have > >> one per team anyway I think. > >> > >> Regards, > >> > >> Rasmus =20 From nobody Fri Mar 29 15:55:19 2024 Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id C4F47782BBC for <~alpine/devel@lists.alpinelinux.org>; Wed, 10 Jun 2020 02:12:26 +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=1591755145; 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=k2TFlwtgyCpF1CmmWGeJ9sTzEVYkZVZ24GVVGUoaWJU=; b=NT6N6I7MS0qyLDa3MDqwgBeHlEoDAS2zoRBMdAg5r/Q98deDDe7SnUtGVRVf1rIchyG2KS Mysjl/kapEk6pIqJWI97sY+m80v3QVmmF4S+yPb23jfsVtZxjC7mz4ZTH6E3vUcdOI8oUH hFOLSFFNlTNiE7kFN04tZYVRij4X4FY= From: Ariadne Conill To: ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages Date: Tue, 09 Jun 2020 20:11:50 -0600 Message-ID: <2409935.lMG0q3WddN@localhost> In-Reply-To: <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> References: <1765542.52O7J0OIYB@localhost> <20200608124653.009172bf@ncopa-desktop.copa.dup.pw> <29JTA7M9GK125.2RPZSJJSZVXUA@8pit.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.40 Hello, On Tuesday, June 9, 2020 4:59:46 AM MDT S=F6ren Tempel wrote: > I like the proposal in general, I am not so sure about team coordinators > though. >=20 > Natanael Copa wrote: > > Coordinators role would be to have overview and be a communication > > point for the team. A contributor wants to help with something, lets > > say documentation, and it is known that there are 2 other people > > working on it too. Who should the contributor speak with to avoid > > double work? The coordinator. >=20 > I think team coordination is something that could just be decided > internally by the team itself. For instance, an IRC channel or similar > would imho also be sufficient for coordination within the team without > having a central team coordinator. Teams/SIGs/whatever we want to call them can organize however they wish. T= he=20 purpose of the coordinator role is to provide a point of contact for the te= am,=20 be it for newcomers who are interested in joining the team or if the core t= eam=20 requires something from a specific team*. (* I have plans for splitting the core team into a few new teams, that allo= w=20 for people to participate according to their expertise instead of being on = a=20 catch-all but lets make baby steps.) Ariadne From nobody Fri Mar 29 15:55:19 2024 Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id A0283782C16 for <~alpine/devel@lists.alpinelinux.org>; Wed, 10 Jun 2020 02:37:12 +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=1591756631; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xNRNb12LvwSRIXZiAj8NeD19YLwGpjkIhliLcGV/Tsw=; b=h4hg17SnbruxAsn57v5S2AzqPL3e8+7mAeh50uphekGG7WRg27JyCPLKQ3nofs3CDIu9pT gWM+4dqE+oGz9iz+/zJeqAiBc1PISaPwaf2TbXYXYt/hu47VqxW54ae/B/a4m40IR7ls+f zlOI3W8tBxs22Iq/YbrgcCZStjfWFXQ= From: Ariadne Conill To: ~alpine/devel@lists.alpinelinux.org Cc: Ariadne Conill Subject: Re: team-maintained packages Date: Tue, 09 Jun 2020 20:37:05 -0600 Message-ID: <1718657.Euugps0dR9@localhost> In-Reply-To: <1765542.52O7J0OIYB@localhost> References: <1765542.52O7J0OIYB@localhost> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.00 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. > >From an APKBUILD perspective, the maintainer line would look like this: > # Maintainer: Alpine KDE team > # 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? > > 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. * Alpine desktop team This team focuses on coordination of desktop-wide packaging, policy, theming etc. This team does not just produce packaging, but also themes (perhaps an alpine-backgrounds package for example), and software that integrates desktop environments with Alpine features, such as apk-tools integration, live desktop environment, GUI installer, etc. Basically a catch-all group to deal with the meta issues surrounding plumbing the alpine desktop. Members: myself, Cogitri (as coordinator), PureTryOut, Leo * X11/Wayland This team focuses on maintenance of X11 and Wayland. Members: ncopa, Cogitri, Leo * KDE This team focuses on maintenance of KDE. Members: myself, PureTryOut (coordinator). * Toolchain This team formalizes the current maintenance arrangement with the toolchain. It would take over maintenance of binutils, gcc, llvm, musl, pkgconf and other core toolchain packages. Members: myself, mps, fabled, ncopa (coordinator) * Kernel Same story as toolchain but with kernel. Members: myself, ncopa (coordinator), mps * Development Tools This group deals with producing/maintaining software such as atools, abuild etc. Members: Leo, ncopa (and whoever else is working on these kinds of tools, ncopa probably as coordinator here) 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 From nobody Fri Mar 29 15:55:19 2024 Received: from mail-qt1-f179.google.com (mail-qt1-f179.google.com [209.85.160.179]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 86371782B52 for <~alpine/devel@lists.alpinelinux.org>; Fri, 12 Jun 2020 00:54:00 +0000 (UTC) Received: by mail-qt1-f179.google.com with SMTP id e16so6004082qtg.0 for <~alpine/devel@lists.alpinelinux.org>; Thu, 11 Jun 2020 17:54:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=DFJH9yfEYY6jFC8y9EWc3LyX/o/8/c5jfLJHsS0zdeM=; b=YoZXpixpxRB9iuKnMaY0sOkhpigD1PjgO2+oFLnB4geVt8AOlIm5lIvZ7K3JCf5cem 4pDxa9+0rHPjOjjvZ1DSCphYbj+0px7SUrrnnxsD57MXwtd1Oiq87m6tz6UyLlV4mzM+ yLeieHCTBtbRrZQ91zxPTdUuLnrOxJ/ltk/nhgkYqm9PfO1fU6FNsWIt8lNrC2uSIOk2 LuZXSsusM5MKu9yDjwGpjR3YBpXaKkNkxRqBAn6c4ytJixCbvJOzhLSYlvCqbQXLHqbz 0f2Fru0ggu/eNvw1P0rjGVO4z/zwmK1MJoLTXVWf+CF5pXu007fMaByt/1Tlswa54znp b+fw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=DFJH9yfEYY6jFC8y9EWc3LyX/o/8/c5jfLJHsS0zdeM=; b=PHnz3zPx/+zZffT9wWCpjVlqb8uZylQ7PR8X30P//9+aRmSy1KdnKjlwDVYX5mpk97 irxdRs9hZ5XDEDENRzSBlgdO3PeYTMmBvpNSlbviUq9Z6QJ84v5Lm2f2M8zECmMFnukx dYIzPkk4HPQlGB8cIlnvshV/Eh2KSow0gpLsTA1h5MEvIhwHV+vk5ejtzPBL4AamKfXx 8t1Clyf8/vp3qleyoOL6DeJw7f1Gej7A8SbTiyl0MVhmOAjPMw1Gu5rQVJoYx1MjHI2k 1YQcdJ8iMr+qHzv3h1/a8lKJu8JB9EkGvZpooPSnujV2+i1KqDLuu2bIMCXzmihJzwhK iVQA== X-Gm-Message-State: AOAM5312pueVeeKdg+DVGlzbC3945XSKhmyKl/hguXCDifSAHpSw1sSd EDvZOVB2FjWFO6TAIfazIDYwepJQ X-Google-Smtp-Source: ABdhPJwgtR8qFbySXzOfXrCvSBZ4+Vco5AvKNX7gL66B7a4Bw0MjuI6G3oUtaWGgjoEztyAtCB6bUg== X-Received: by 2002:ac8:6a08:: with SMTP id t8mr678140qtr.271.1591923238658; Thu, 11 Jun 2020 17:53:58 -0700 (PDT) Received: from enterprise ([2804:431:cfcd:76dd:a8e8:7086:e235:984c]) by smtp.gmail.com with ESMTPSA id p203sm3472671qke.132.2020.06.11.17.53.57 for <~alpine/devel@lists.alpinelinux.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Jun 2020 17:53:58 -0700 (PDT) Date: Thu, 11 Jun 2020 21:53:08 -0300 From: Leo To: ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages Message-ID: <20200611215308.21392c47@enterprise> In-Reply-To: <1718657.Euugps0dR9@localhost> References: <1765542.52O7J0OIYB@localhost> <1718657.Euugps0dR9@localhost> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello > > * Alpine desktop team > > This team focuses on coordination of desktop-wide packaging, policy, > theming etc. This team does not just produce packaging, but also > themes (perhaps an alpine-backgrounds package for example), and > software that integrates desktop environments with Alpine features, > such as apk-tools integration, live desktop environment, GUI > installer, etc. Basically a catch-all group to deal with the meta > issues surrounding plumbing the alpine desktop. > > Members: myself, Cogitri (as coordinator), PureTryOut, Leo > I'd like to not be in this group. > > * Development Tools > > This group deals with producing/maintaining software such as atools, > abuild etc. > > Members: Leo, ncopa (and whoever else is working on these kinds of > tools, ncopa probably as coordinator here) > I'd like to be in this group. Regards Leo From nobody Fri Mar 29 15:55:19 2024 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 To: Ariadne Conill 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 I assume abuild, apk-tools and aports-turbo have no issues with this? (mainly the url in the e-mail part). > > # 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? > > > > 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 From nobody Fri Mar 29 15:55:19 2024 Received: from vps892.directvps.nl (ikke.info [178.21.113.177]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 1C73D78193F for <~alpine/devel@lists.alpinelinux.org>; Wed, 8 Jul 2020 20:13:22 +0000 (UTC) Received: by vps892.directvps.nl (Postfix, from userid 1008) id CE63F440122; Wed, 8 Jul 2020 22:13:21 +0200 (CEST) Date: Wed, 8 Jul 2020 22:13:21 +0200 From: Kevin Daudt To: Kevin Daudt Cc: Ariadne Conill , ~alpine/devel@lists.alpinelinux.org Subject: Re: team-maintained packages Message-ID: <20200708201321.GA2534782@alpha> References: <1765542.52O7J0OIYB@localhost> <1718657.Euugps0dR9@localhost> <20200701200421.GA2450243@alpha> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200701200421.GA2450243@alpha> 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 > > I assume abuild, apk-tools and aports-turbo have no issues with this? > (mainly the url in the e-mail part). > > > > # 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? > > > > > > 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. Kevin From nobody Fri Mar 29 15:55:19 2024 Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 39D33780FDA for <~alpine/devel@lists.alpinelinux.org>; Wed, 8 Jul 2020 20:44:38 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1594241073; bh=QQwwUJAHYVDgRKCe8uHk1J0nc/WeQE3Pzk6HXhdKqhM=; h=Subject:From:To:Cc:In-Reply-To:References; b=OvEesgGigLJLKyeWLCf/K1o3hJKwLCBoNmJDfBvodcCAA2R99dD5KddzvZ6AmW/HI 9SkM4E78+LXm1VvfTRLJ5SxRcgY9V9MZ4gc3xe4bH5+SUQen9E3W7gGA+E7yw+Ur71 gfDZCn7wF4V7DM6DEZ4cO/3wrnwISalCR7eNFEDKHBMhid3YBcFLOVWRhKaSWDbR+0 oE9d4YNtb62u6DeNo9efw8tC4UrxDXwI9WVZW8udxOkH17aR4s/tVTt1FeWbpH9i6G U5k4EVrOhEFbcWkEGXNG69wmArMTDINzmCTQmpwWqJkLr3ef6Kg7DuaCEx2Q/UngSs aHkW3CGN739VA== Subject: Re: team-maintained packages From: Rasmus Thomsen To: Kevin Daudt Cc: Ariadne Conill , ~alpine/devel@lists.alpinelinux.org Date: Wed, 08 Jul 2020 22:44:32 +0200 In-Reply-To: <20200708201321.GA2534782@alpha> References: <1765542.52O7J0OIYB@localhost> <1718657.Euugps0dR9@localhost> <20200701200421.GA2450243@alpha> <20200708201321.GA2534782@alpha> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit On Wed, 2020-07-08 at 22:13 +0200, Kevin Daudt wrote: > Do we also want a Gnome team btw? Hm, I guess we can make one but I don't think anyone but me would be in that team right now (but could be useful for future proofing). > Kevin From nobody Fri Mar 29 15:55:19 2024 Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 2D04F781D42 for <~alpine/devel@lists.alpinelinux.org>; Fri, 10 Jul 2020 16:08:56 +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=1594397334; 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=xJcTgSTTEBrqbTHb9rErQp1jhWLLsllTbKX2EtYtx3I=; b=eUP/R8FSOm+Aw/k+vLn0CVcx9xTO3cFAuTtYykfP0TcZSWp8KfbEUw5fcOnk6l8GpRVIZj eeTsdoZkDS4Pp+Q7RTUlua6sPugJPeWGqNSLZCP7wnPW5qf7nOaqrsI2siC5mCEWTCq21A Du55TD6LIbs0bXblsv84xBGl7hcLabU= From: Ariadne Conill To: Kevin Daudt , ~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" X-Spam-Score: 0.90 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 > > > > > > > > I assume abuild, apk-tools and aports-turbo have no issues with this? > > (mainly the url in the e-mail part). > > > > > > # 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? > > > > > > > > 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