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>
 <afb56fbb1bdfc7debc6712eb28cd873ad5cf116e.camel@cogitri.dev> <CAJH62qksawos3r2vo3AiWPuMm9=32RxM1ZJQo4LxNzGN065m4A@mail.gmail.com>
In-Reply-To: <CAJH62qksawos3r2vo3AiWPuMm9=32RxM1ZJQo4LxNzGN065m4A@mail.gmail.com>
From: Timothy Legge <timlegge@gmail.com>
Date: Tue, 9 Jun 2020 09:24:37 -0300
Message-ID: <CALTFL3VC8=SvJxVZadqYZafKMzyfQdoVS3C=QCfvCQSB+nKhcg@mail.gmail.com>
Subject: Re: team-maintained packages
To: Will Sinatra <wpsinatra@gmail.com>
Cc: Rasmus Thomsen <oss@cogitri.dev>, =?UTF-8?Q?S=C3=B6ren_Tempel?= <soeren@soeren-tempel.net>, 
	"~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 <wpsinatra@gmail.com> 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 <oss@cogitri.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 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

<div dir=3D"ltr">I am willing to help out with Perl packages.=C2=A0 I have =
not ventured much further at this point.</div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 9, 2020 at 8:42 AM Will=
 Sinatra &lt;<a href=3D"mailto:wpsinatra@gmail.com">wpsinatra@gmail.com</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"auto">Would the teams cover single packages, or rather large concep=
ts?<div dir=3D"auto"><br></div><div dir=3D"auto">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.</div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 9, 20=
20, 7:32 AM Rasmus Thomsen &lt;<a href=3D"mailto:oss@cogitri.dev" target=3D=
"_blank">oss@cogitri.dev</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">On Tue, 2020-06-09 at 12:59 +0200, S=C3=B6ren Tempe=
l wrote:<br>
&gt; Natanael Copa &lt;<a href=3D"mailto:ncopa@alpinelinux.org" rel=3D"nore=
ferrer" target=3D"_blank">ncopa@alpinelinux.org</a>&gt; wrote:<br>
&gt; &gt; Coordinators role would be to have overview and be a communicatio=
n<br>
&gt; &gt; point for the team. A contributor wants to help with something,<b=
r>
&gt; &gt; lets<br>
&gt; &gt; say documentation, and it is known that there are 2 other people<=
br>
&gt; &gt; working on it too. Who should the contributor speak with to avoid=
<br>
&gt; &gt; double work? The coordinator.<br>
&gt; <br>
&gt; I think team coordination is something that could just be decided<br>
&gt; internally by the team itself. For instance, an IRC channel or<br>
&gt; similar<br>
&gt; would imho also be sufficient for coordination within the team<br>
&gt; without<br>
&gt; having a central team coordinator.<br>
<br>
Maybe the gitlab group could be used for communication since we&#39;ll have=
<br>
one per team anyway I think.<br>
<br>
Regards,<br>
<br>
Rasmus<br>
</blockquote></div>
</blockquote></div>

--0000000000004507b705a7a5d0de--