On Tue, 2 Nov 2021 at 14:19, Nikita Popov <nikita....@gmail.com> wrote: > > I'd like to formally propose to use GitHub for PHP implementation issues as > well: https://wiki.php.net/rfc/github_issues
In general, yes please. The only bit I'll chime in on is: > bugs.php.net will remain active for the following purposes: > Reporting of issues against PECL extensions. (We may want to discontinue > this as well. Many actively maintained extensions already use GitHub issues > rather than bugs.php.net.) Providing a bug reporting site was a useful thing to do 23 years ago, as it would have been either expensive or time consuming for each project to set up their own. It doesn't seem as sensible now as: * Having bugs.php.net remain open for some bits of PHP, but not others, would be confusing for users. * Most extensions are hosted on a platform that already provides issue tracking - though it seems quite a few extensions (including Imagick) have not realised that there is a bug tracking setting that can/should be updated on pecl. * There's an ongoing issue of extensions becoming unmaintained over time. If people are opening bugs on the PHP issue tracker, it's natural for them to have an expectation that someone from the PHP project would work on that issue at some point. So unless someone has a strong argument for keeping the bugs.php.net open for PECL extensions, I think it shouldn't be. btw it would probably be useful to dump out a list of where to report bugs for different extensions and put that as a page on bugs.php.net though. If nothing else, Google thinks Imagick is an alias for ImageMagick far too often and sometimes pecl.php.net is unresponsive. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
