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