Hi web masters, There is an ongoing RFC and discussion around enabling GitHub Issues for php-src and essentially turning off bugs.php.net for new tickets. [1,2,3]
There are a bunch of php/web-* repos that do not yet have GitHub Issues enabled. Do we want to switch them all over to using GitHub Issues instead of bugs.php.net? Current status: ([x] means issues are already enabled, [ ] otherwise) [x] https://github.com/php/web-bugs [ ] https://github.com/php/web-doc [3] [x] https://github.com/php/web-doc-editor [ ] https://github.com/php/web-gcov [ ] https://github.com/php/web-gtk [x] https://github.com/php/web-jenkins [x] https://github.com/php/web-master [ ] https://github.com/php/web-news [x] https://github.com/php/web-pecl [ ] https://github.com/php/web-people [x] https://github.com/php/web-php [ ] https://github.com/php/web-php-distributions [x] https://github.com/php/web-pres2 [ ] https://github.com/php/web-qa [x] https://github.com/php/web-rmtools [ ] https://github.com/php/web-shared [ ] https://github.com/php/web-testfest [ ] https://github.com/php/web-wiki [ ] https://github.com/php/web-windows It's no trouble to go ahead and enable for all, but I don't want to do it without at least some general mumblings of approval. Thanks, Peter [1] https://wiki.php.net/rfc/github_issues [2] "[RFC] Migrating to GitHub issues" - https://externals.io/message/116302 [3] "[VOTE] Migrating to GitHub issues" - https://externals.io/message/116467 [4] On behalf of the docs team, I'll make the unilateral decision to enable GH Issues there.
