Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116379
To: internals@lists.php.net
Date: Mon, 15 Nov 2021 18:01:15 +0100
Message-ID: <7311055.EvYhyI6sBW@come-prox15amd>
In-Reply-To: <CADK1yXL7QOtx23tyvWMm4z24ReVut-5PvAdQwi7zijo4KxL3xw@mail.gmail.com>
References: <CAF+90c90pTtjxuMaQ88h+njhByfbv4qs=xx72CVPSw40tde6Cg@mail.gmail.com> <7988332.T7Z3S40VBb@come-prox15amd> <CADK1yXL7QOtx23tyvWMm4z24ReVut-5PvAdQwi7zijo4KxL3xw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Migrating to GitHub issues
From: come@chilliet.eu (=?ISO-8859-1?Q?C=F4me?= Chilliet)

Le lundi 15 novembre 2021, 15:49:04 CET Deleu a =C3=A9crit :
> Gitlab is not where the wide PHP Community is located. Composer,
> widely-used and adopted packages, frameworks, PSRs, PHP itself and PHP Do=
cs
> are all hosted on GitHub. Choosing something else increases the barrier f=
or
> newcomers to become contributors. I speak from experience that when I tri=
ed
> to contribute to Alpine Linux, one of the major turn off was GitLab
> hosting. 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.

This is exactly the problem with moving to Github, we are forcing everyone =
to come with us, as others are inciting us to go there by being there (comp=
oser, =E2=80=A6).
Then people only know how to use Github and we are stuck there forever.

If we survived all these years with bugs.php.net, we should be alright with=
 gitlab for sure.

I think the PHP project could lead the way out of github instead of followi=
ng the others in.

C=C3=B4me