Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116356
MIME-Version: 1.0
References: <CAF+90c90pTtjxuMaQ88h+njhByfbv4qs=xx72CVPSw40tde6Cg@mail.gmail.com>
 <alpine.DEB.2.23.453.2111150940130.4221@singlemalt.home.derickrethans.nl>
In-Reply-To: <alpine.DEB.2.23.453.2111150940130.4221@singlemalt.home.derickrethans.nl>
Date: Mon, 15 Nov 2021 10:55:18 +0100
Message-ID: <CADyq6s+OkprQX4hhpbfF=xAm=n1V8hJTpU2GXjkJhpF=msXfXQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP internals <internals@lists.php.net>, Nikita Popov <nikita.ppv@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000002037a605d0d0cfeb"
Subject: Re: [PHP-DEV] [RFC] Migrating to GitHub issues
From: ocramius@gmail.com (Marco Pivetta)

--0000000000002037a605d0d0cfeb
Content-Type: text/plain; charset="UTF-8"

Hey Derick

On Mon, Nov 15, 2021 at 10:47 AM Derick Rethans <derick@php.net> wrote:

> Dear Internals,
>
> I think it is a mistake to decide on a whim to move over to GitHub
> issues without having evaluated anything else.
>
> GitHub is a proprietary platform, where unlike with the code
> repositories, the interactions and issues are not easy to migrate out of
> again. It is also now owned by MSFT, and although they are making
> friendly noises towards Open Source, I remain largely skeptical (with as
> a hint, the stuff they're pulling with AI code completion).
>
> I understand and share that "bugsnet" has many issues, and I don't
> necessarily object moving to something else.
>
> However, in the last 25+ years we've always hosted this ourselves, and
> this prevented any sort of vendor lock in. I think it is important to
> own our own data here, or at least have full access to any interactions.
>
> This jump to GitHub Issues feels rushed, and I worry that we end up
> making the wrong decision, especially because from the RFC it seems we
> need to build some functionality (tags scheme, for example) on top of
> it. And this will need to be maintained separately, and I worry that too
> few people are going to be interested in gardening the issues on GH.
>
> I believe we would be much better served having a look what is
> available, and see what else is suitable. I'm therefore intending to
> vote no on this.
>
> cheers,
> Derick
>

Remember that all information on public repos is also available on
http://www.gharchive.org/
If data retention is the problem, mirroring that could be an effective
solution.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--0000000000002037a605d0d0cfeb--