rfc:umaintained_extensions

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:umaintained_extensions [2018/06/17 19:29] – stasrfc:umaintained_extensions [2018/08/22 11:23] (current) – Fix table indentation carusogabriel
Line 3: Line 3:
   * Date: 2016-08-07   * Date: 2016-08-07
   * Author: Stas Malyshev, stas@php.net   * Author: Stas Malyshev, stas@php.net
-  * Status: Under Discussion +  * Status: Accepted
   * First Published at: http://wiki.php.net/rfc/umaintained_extensions   * First Published at: http://wiki.php.net/rfc/umaintained_extensions
  
Line 18: Line 18:
   - Otherwise, ask them to submit a couple of patches for existing bugs in the extension, of their choice. If these are ok, issue them php.net account with appropriate permissions and assign them as maintainers for the claimed extension. If extensions has no bugs to fix, assign them as maintainers immediately (php.net account may not yet be needed).   - Otherwise, ask them to submit a couple of patches for existing bugs in the extension, of their choice. If these are ok, issue them php.net account with appropriate permissions and assign them as maintainers for the claimed extension. If extensions has no bugs to fix, assign them as maintainers immediately (php.net account may not yet be needed).
   - If within 3 weeks nobody steps up as a maintainer for extension, it is considered orphaned.   - If within 3 weeks nobody steps up as a maintainer for extension, it is considered orphaned.
-  - All orphaned extensions are converted to PECL modules and removed from core repository. +  - All orphaned extensions are converted to PECL modules and removed from core repository. There should be a public announcement procedure before this happens, with the details not defined of this RFC but to be worked out by RMs and the community (either with separate RFC or just by consensus). 
   - In case there are objections to moving unmaintained extension to PECL, separate RFC vote can be held about the move, initiated by the RMs of the current release or any interested party. The decision can be taken for each extension individually.     - In case there are objections to moving unmaintained extension to PECL, separate RFC vote can be held about the move, initiated by the RMs of the current release or any interested party. The decision can be taken for each extension individually.  
      
Line 34: Line 34:
 | pdo_odbc | 26 | 2007-06-22 | 2016-01-18 | 2009-12-11 | | pdo_odbc | 26 | 2007-06-22 | 2016-01-18 | 2009-12-11 |
 | readline | 4 | 2012-03-31 | 2001-01-26 | 2015-12-11 | | readline | 4 | 2012-03-31 | 2001-01-26 | 2015-12-11 |
-| pspell | 2 |  2014-03-19  | 2016-04-19 | 2008-09-16 | +| pspell | 2 | 2014-03-19  | 2016-04-19 | 2008-09-16 | 
 | sysvmsg | No bug category | | sysvmsg | No bug category |
 | sysvsem | 19 | 2002-04-29 | 2016-04-04 | 2014-09-10 | | sysvsem | 19 | 2002-04-29 | 2016-04-04 | 2014-09-10 |
Line 54: Line 54:
 in the future.  in the future. 
  
-The proposed procedure is to add years to each maintainer's status in the maintainers list, with the year to be updated manually by the maintainer. If by end of January of the year the last updated year is past the last year, the extension is deemed to be effectively unmaintained. In this case, the maintainer would be asked to clarify the maintainership status, and absent response or with negative response, the extension will be considered having no maintainer. This can be changed at any moment if the existing or new maintainer comes up (again, the priority is always towards finding the maintainer, not moving stuff out). +The proposed procedure is to add years to each maintainer's status in the maintainers list, with the year to be updated manually by the maintainer. If by end of January of the year the last updated year is past the last year (e.g., 2018 or less in January 2020), the extension is deemed to be abandoned by the maintainer. In this case, the maintainer would be asked to clarify the maintainership status, and absent response or with a negative response, the extension will be considered having no maintainer. This can be changed at any moment if the existing or new maintainer comes up (again, the priority is always towards finding the maintainer, not moving stuff out). 
  
 To initiate this procedure, the years should be initialized with the last commit or last bug response from the maintainer to the maintained extension code or bugs.  To initiate this procedure, the years should be initialized with the last commit or last bug response from the maintainer to the maintained extension code or bugs. 
Line 62: Line 62:
 Vote "Yes" is for acceptance of this RFC as the basis for PHP policy towards unmaintained extensions. Vote "No" is for rejection of this RFC.  Vote "Yes" is for acceptance of this RFC as the basis for PHP policy towards unmaintained extensions. Vote "No" is for rejection of this RFC. 
  
-<doodle title="Institute the policy of cleaning up unmaintained extensions as described in this RFC" auth="stas" voteType="single" closed="false">+Since this RFC does not change the language, technical limit for passing is 50%+1 vote, however if it does not gather 2/3 "Yes" vote, I would like to hear from the opposing voices first and maybe improve it before we can implement it to satisfy their concerns.  
 + 
 +<doodle title="Institute the policy of cleaning up unmaintained extensions as described in this RFC" auth="stas" voteType="single" closed="true">
    * Yes    * Yes
    * No    * No
 </doodle> </doodle>
  
-Voting starts on 2018-06-18, and ends on 2018-06-26 23:59 PDT.+Voting starts on 2018-06-17, and ends on 2018-06-26 23:59 PDT.
  
 ===== Patches and Tests ===== ===== Patches and Tests =====
Line 74: Line 76:
  
 ===== References ===== ===== References =====
-Discussion on internals: http://externals.io/thread/126+Discussion on internals: http://externals.io/thread/126 https://externals.io/message/95172
  
  
rfc/umaintained_extensions.1529263756.txt.gz · Last modified: 2018/06/17 19:29 by stas

Page Tools