Content-Type: text/plain; charset=utf-8
Precedence: list
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: =?utf-8?Q?Re=3A_=5Balpine-devel=5D_Ad=C3=A9lie_on_Alpine=2C_two_?=
 =?utf-8?Q?months_later?=
From: Jakub Jirutka <jakub@jirutka.cz>
In-Reply-To: <20170724195040.GA18090@vimes.1042.ch>
Date: Mon, 24 Jul 2017 22:46:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5301B93A-A3AA-4AD3-8191-EBA542A6C3D3@jirutka.cz>
References: <5975E0C0.1030008@adelielinux.org> <57A1A151-0352-40DA-BC91-52980CEE99C3@shiz.me> <59761031.6000605@adelielinux.org> <20170724195040.GA18090@vimes.1042.ch>
To: Alpine-devel <alpine-devel@lists.alpinelinux.org>,
 Jean-Louis Fuchs <ganwell@fangorn.ch>

HI,

I strongly disagree that Patchwork is a great tool, at least the current =
version we have.

I can=E2=80=99t imagine something that can be worse, less productive =
than Patchwork. It=E2=80=99s more or less just bad a web UI for mailbox. =
There=E2=80=99s no clear relation between related patches, =E2=80=99cause =
it=E2=80=99s just nearly impossible to reconstruct such information from =
separated patches in mail. It=E2=80=99s simply not possible to set any =
reasonable integration with CI on top of this. Not even talking about =
its =E2=80=9Csupport=E2=80=9D for code-reviews, that is more or less =
non-existing.

Patchwork is based on ancient workflow from CVS era. Pull/Merge request, =
the feature in GitHub, GitLab and other git-based tools, is proper =
git-way. It starts and ends with git. You create new branch in your =
clone of the repository, push some commits and opens a pull request =
(this can be done from CLI ofc, but well only via vendor-specific API). =
On git level, pull request is a reference in the target git repository. =
Maintainer can work with it directly via git (see =
https://gist.github.com/piscisaureus/3342247), without leaving terminal. =
When the contributor push new changes to the pull request, maintainer =
can simply pull them via git and view in context, it=E2=80=99s just a =
branch.

Comments on pull requests are unfortunately not stored in git (they can =
be, but GH/GL don=E2=80=99t do that), so this happens outside of git =
(yet still can work with it from CLI).

I=E2=80=99m one of the Alpine devs who interacts with user contributions =
the most. I don=E2=80=99t use our Patchwork at all, because it=E2=80=99s =
unreasonable waste of my time to work with such bad tool. Mostly for =
lack of CI integration, but not just that. It=E2=80=99s really horrible =
for reviews. I understand that it may be quite comfortable for =
contributors (that don=E2=80=99t know git), but I believe that only to =
the moment when changes are requested.

I understand why some ppl don=E2=80=99t like GitHub (it=E2=80=99s =
third-party commercial service after all), but what I really don=E2=80=99t=
 understand is how can anyone say minimalism and Mailing-List/Patchwork =
in one sentence. Have you ever considered the =E2=80=9Cmail=E2=80=9D =
part of it? Mails are insanely complex nowadays.

Sorry for grammar, I wrote it in hurry.

Jakub

> On 24. Jul 2017, at 21:50, Jean-Louis Fuchs <ganwell@fangorn.ch> =
wrote:
>=20
> Hi
>=20
> On Mon, Jul 24, 2017 at 10:20:17AM -0500, A. Wilcox wrote:
>> Duly noted.  I would ask if there are any plans to install something
>> like GitLab, Pagure, or Phabricator for Alpine at some point, but I
>> don't really want to open such a can of worms :)
>=20
> http://patchwork.alpinelinux.org/project/aports/list/
>=20
> Alpine uses patchwork, which is a great tool developed at ozlabs.
> Patchwork 2.0 will support RESTAPI events, so you can plugin almost
> anything into patchwork (Jenkins for example). I love the
> mailinglist/patchwork approach, because I am a hopeless minimalist
> (using only terminal programs and a browser). I hope Alpine will
> continue into build into that direction.
>=20
> I have use GitHub a lot, while disliking it for various reasons.
>=20
> Best,
>    Jean-Louis



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---