Re: [RFC] Migrating to GitHub issues

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/