Re: [RFC] Migrating to GitHub issues

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 On Tue, 2 Nov 2021, Nikita Popov wrote: > Hi internals, > > The migration from bugs.php.net to GitHub issues has already been discussed > in https://externals.io/message/114300 and has already happened > for > documentation issues. > > I'd like to formally propose to use GitHub for PHP implementation issues as > well: https://wiki.php.net/rfc/github_issues > > Regards, > Nikita > -- PHP 7.4 Release Manager Host of PHP Internals News: https://phpinternals.news Like Xdebug? Consider supporting me: https://xdebug.org/support https://derickrethans.nl | https://xdebug.org | https://dram.io twitter: @derickr and @xdebug