Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116383
MIME-Version: 1.0
References: <CAF+90c90pTtjxuMaQ88h+njhByfbv4qs=xx72CVPSw40tde6Cg@mail.gmail.com>
 <alpine.DEB.2.23.453.2111150940130.4221@singlemalt.home.derickrethans.nl>
 <CAF+90c__1D5UMMpi6yX6obtuUZVL4NQRO_nR-Yr7gFq-Sc0teg@mail.gmail.com>
 <7988332.T7Z3S40VBb@come-prox15amd> <CADK1yXL7QOtx23tyvWMm4z24ReVut-5PvAdQwi7zijo4KxL3xw@mail.gmail.com>
 <54427380-981f-fed7-3a0c-a8010b8a0d97@gmail.com>
In-Reply-To: <54427380-981f-fed7-3a0c-a8010b8a0d97@gmail.com>
Date: Mon, 15 Nov 2021 18:27:01 +0100
Message-ID: <CADyq6sJwL0Yf0dvDAS7UCF51SORJzMpAYeWPQgEAB3kqWE3mLw@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000092f4f705d0d71e54"
Subject: Re: [PHP-DEV] [RFC] Migrating to GitHub issues
From: ocramius@gmail.com (Marco Pivetta)

--00000000000092f4f705d0d71e54
Content-Type: text/plain; charset="UTF-8"

Chiming in, since it seems like people are suggesting Gitlab and further
"exotic" tools.

On Mon, Nov 15, 2021 at 6:06 PM Rowan Tommins <rowan.collins@gmail.com>
wrote:

> On 15/11/2021 14:49, Deleu wrote:
> > I had already decided to spend time and effort learning about the
> > project and then having to learn about their ticketing system and git
> > repository is just unnecessary extra work.
>
>
> In any project above a handful of developers, learning the conventions
> and expectations of the community is always going to be far more
> complicated than learning how to use the actual tools in question. We
> should definitely choose a tool that is *easy to use*, and easy to
> authenticate on (but not so easy it fills up with spam, like the current
> one), but saying that developers will struggle to use anything other
> than the One True Website is frankly insulting to the intelligence of
> the average developer.
>
>
The point of using Github (over other tools) is:

 * the community is already there
 * the repository is already frikken there
 * it's about pumping stuff into the issue tracker, nothing new is added
 * integrated CVE reports that already fit within the ecosystem
 * 2fa auth requirement for organization members (gitlab has this too,
AFAIK, but it's a checkbox to add somewhere)
 * including pre-existing users in discussions (yes, leading to pings),
even those that didn't declare a public mail - no registration and no GDPR
to manage on PHP-SRC's end
 * rich editing of issues, with code fragments from the repo, rather than
copy-pasta'd stuff all over the place
 * cross-linking of PHP sources with other project sources, including
backlink references that make bugs and workarounds easier to follow by
community members

This stuff is not to be under-estimated: going self-hosted means having yet
another insular environment, where the PHP-SRC folks are trapped in a bit
of a void, and the actual discussions will keep happening on PHP-SRC diffs
anyway.

Instead of fearing the "One True Website", adopt and plan for disaster,
should it become an Evil Corp seeding ground: what is there to be lost, and
how hard would it be to recover?

Greets,

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--00000000000092f4f705d0d71e54--