rfc:github_issues

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:github_issues [2021/11/03 03:03] – Fix numerous typos/grammar mistakes theodorejbrfc:github_issues [2021/12/04 14:22] (current) – nikic
Line 2: Line 2:
   * Date: 2021-11-01   * Date: 2021-11-01
   * Author: Nikita Popov <nikic@php.net>   * Author: Nikita Popov <nikic@php.net>
-  * Status: Under Discussion+  * Status: Accepted
  
 ===== Introduction ===== ===== Introduction =====
Line 207: Line 207:
  
   * Reporting of security issues against PHP.   * Reporting of security issues against PHP.
-  * 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.) 
   * Commenting/updating on existing issues.   * Commenting/updating on existing issues.
  
Line 213: Line 212:
  
   * Reporting documentation problems. (Already disabled.)   * Reporting documentation problems. (Already disabled.)
 +  * Reporting of issues against PECL extensions. (Extensions should have their own issue tracker. Most of them already track issues on GitHub, not bugs.php.net.)
   * Reporting non-security issues against PHP.   * Reporting non-security issues against PHP.
 +
 +It may be possible to migrate security issues to GitHub as well, by making of use of the [[https://docs.github.com/en/code-security/security-advisories/about-github-security-advisories|security advisories]] feature. However, larger changes to the handling of security issues should be decided within the security response group, and as such are considered out of scope of this proposal.
  
 ===== Alternatives ===== ===== Alternatives =====
Line 234: Line 236:
  
 The requirement for an alternative would be that a) it is hosted (i.e. the PHP project does not need to maintain infrastructure for it), b) has good GitHub integration and c) is "sufficiently better" than GitHub issues to make it worth using a separate product. As PHP does not have a particularly sophisticated issue tracking workflow, I'm doubtful that the tradeoff will be worthwhile. The biggest "advantage" of using a separate product is likely that it will make reporting bugs significantly harder for the casual user, which might make low-quality submissions less likely. The requirement for an alternative would be that a) it is hosted (i.e. the PHP project does not need to maintain infrastructure for it), b) has good GitHub integration and c) is "sufficiently better" than GitHub issues to make it worth using a separate product. As PHP does not have a particularly sophisticated issue tracking workflow, I'm doubtful that the tradeoff will be worthwhile. The biggest "advantage" of using a separate product is likely that it will make reporting bugs significantly harder for the casual user, which might make low-quality submissions less likely.
 +
 +===== Vote =====
 +
 +Voting started 2021-11-20 and ends on 2021-12-04.
 +
 +<doodle title="Migrate from bugs.php.net to GitHub issues as proposed?" auth="nikic" voteType="single" closed="true">
 +   * Yes
 +   * No
 +</doodle>
rfc/github_issues.1635908605.txt.gz · Last modified: 2021/11/03 03:03 by theodorejb

Page Tools