Precedence: list
MIME-Version: 1.0
References: <20181127131739.658683ac@ncopa-desktop.copa.dup.pw>
 <CAC-Fq46M+Jy-H4OVEVVVm07UDc4rZfSNV2gDWmG6zHjosL=6Fw@mail.gmail.com>
 <20181203222343.28e1b6fc@ncopa-desktop.copa.dup.pw> <CAC-Fq47ZzzxN87-7GUfxSaU2=1hZZgTJmC38ho83+_yPG-Tgug@mail.gmail.com>
 <25dd0082-3bc3-d358-4972-80ee64cbb943@toastin.space>
In-Reply-To: <25dd0082-3bc3-d358-4972-80ee64cbb943@toastin.space>
From: Dan Williams <me@deedubs.com>
Date: Mon, 3 Dec 2018 20:58:33 -0500
Message-ID: <CAC-Fq44amzps6oH=8SQ8cj8Udu0hQssrjo1njiC2xi8=FUVKrg@mail.gmail.com>
Subject: Re: [alpine-devel] a release engineering team?
To: Chloe Kudryavtsev <toast@toastin.space>
Cc: alpine-devel@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="0000000000000244a3057c289b01"

--0000000000000244a3057c289b01
Content-Type: text/plain; charset="UTF-8"

My concern is multiple channels to track. So IMHO we should choose one.  I
think we should think carefully before turning off pull requests on one of
the social code platforms.

Dan Williams

On Mon., Dec. 3, 2018, 8:27 p.m. Chloe Kudryavtsev <toast@toastin.space
wrote:

> On 12/3/2018 4:34 PM, Dan Williams wrote:
> > Yeah my comment on isolation was assuming there was a reason NOT to go
> full
> > a GitHub. I think as a relteam we are going to want a single path for
> code
> > to flow through. I have had great experiences with Gitlab.
>
> I'd just like to mention that while GitHub is a great host, going all-in
> on their workflow (applies equally to GitLab, so on) has some downsides
> (in particular, the PR-style workflow).
>
> I wouldn't mind having all of the bug tracking and release goals on it,
> but would urge us to keep (and maybe even expand the scope of) patchwork.
>
>
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>
>

--0000000000000244a3057c289b01
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">My concern is multiple channels to track. So IMHO we shou=
ld choose one.=C2=A0 I think we should think carefully before turning off p=
ull requests on one of the social code platforms.=C2=A0<br><br><div data-sm=
artmail=3D"gmail_signature">Dan Williams</div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr">On Mon., Dec. 3, 2018, 8:27 p.m. Chloe Kudryavtsev=
 &lt;toast@toastin.space wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On =
12/3/2018 4:34 PM, Dan Williams wrote:<br>
&gt; Yeah my comment on isolation was assuming there was a reason NOT to go=
 full<br>
&gt; a GitHub. I think as a relteam we are going to want a single path for =
code<br>
&gt; to flow through. I have had great experiences with Gitlab.<br>
<br>
I&#39;d just like to mention that while GitHub is a great host, going all-i=
n <br>
on their workflow (applies equally to GitLab, so on) has some downsides <br=
>
(in particular, the PR-style workflow).<br>
<br>
I wouldn&#39;t mind having all of the bug tracking and release goals on it,=
 <br>
but would urge us to keep (and maybe even expand the scope of) patchwork.<b=
r>
<br>
<br>
---<br>
Unsubscribe:=C2=A0 <a href=3D"mailto:alpine-devel%2Bunsubscribe@lists.alpin=
elinux.org" target=3D"_blank" rel=3D"noreferrer">alpine-devel+unsubscribe@l=
ists.alpinelinux.org</a><br>
Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:alpine-devel%2Bhel=
p@lists.alpinelinux.org" target=3D"_blank" rel=3D"noreferrer">alpine-devel+=
help@lists.alpinelinux.org</a><br>
---<br>
<br>
</blockquote></div>

--0000000000000244a3057c289b01--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---