rfc:umaintained_extensions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:umaintained_extensions [2016/09/05 05:23] – stas | rfc:umaintained_extensions [2018/08/22 11:23] (current) – Fix table indentation carusogabriel | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: Cleaning up unmaintained extensions ====== | ====== PHP RFC: Cleaning up unmaintained extensions ====== | ||
- | * Version: 1.0 | + | * Version: 1.1 |
* Date: 2016-08-07 | * Date: 2016-08-07 | ||
* Author: Stas Malyshev, stas@php.net | * Author: Stas Malyshev, stas@php.net | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
===== Introduction ===== | ===== Introduction ===== | ||
We have a number of extensions that have no assigned maintainer. The proposal is either to find a maintainer for them | We have a number of extensions that have no assigned maintainer. The proposal is either to find a maintainer for them | ||
- | or move them out of core. The RFC proposes the procedure for doing this for 7.1 release. | + | or move them out of core. The RFC proposes the procedure for doing this for 7.3 release and repeat it for each subsequent |
===== Proposal ===== | ===== Proposal ===== | ||
For the extensions that have no maintainers, | For the extensions that have no maintainers, | ||
- | - Issue a call for maintainership on internals list (and maybe other venues, as seen appropriate). | + | - Issue a call for maintainership on internals list (and maybe other venues, such as thematic PHP communities, as seen appropriate). |
- If a maintainer candidate(s) show up: | - If a maintainer candidate(s) show up: | ||
- If they are already committers, assign them as maintainers. The extension is considered maintained from now on, no further action needed. | - If they are already committers, assign them as maintainers. The extension is considered maintained from now on, no further action 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). | - 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. |
+ | - 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. | ||
| | ||
- | Option: for some extensions, which are clearly needed but nobody stepped up in person to claim maintainership, | + | Option: for some extensions, which are clearly needed but nobody stepped up in person to claim maintainership, |
- | To be clear, the ideal result of this process is that //all// extensions find a maintainer. So we want to have the process biased towards finding one. However, | + | To be clear, the ideal result of this process is that // |
==== Candidate extensions ==== | ==== Candidate extensions ==== | ||
- | These are core extensions for which there is no official maintainer registered. | + | These are core extensions for which there is no official maintainer registered. Please note that the exact content of this list is not part of the vote - it can change with new maintainers coming up or old maintainers retiring, and there probably would be a separate list maintained as necessary. |
^ Extension | ^ Extension | ||
Line 33: | 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 | + | | pspell | 2 | 2014-03-19 |
| 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 | | ||
| sysvshm | | sysvshm | ||
- | | xmlrpc \\ (claimed by Cameron Ball) | 11 | 2006-08-11 | 2016-07-17 | 2016-07-22 | | ||
| wddx | 6 | 2006-03-17 | 2016-08-11 | 2016-08-11 | | | wddx | 6 | 2006-03-17 | 2016-08-11 | 2016-08-11 | | ||
Line 43: | Line 43: | ||
Default build of PHP would not have the extensions that will be moved out. They still could be built from PECL sources. | Default build of PHP would not have the extensions that will be moved out. They still could be built from PECL sources. | ||
+ | The focus of this RFC, however, is for establishing procedures for unmaintained extensions rather than dealing with specific extensions, so decision about each extension can be taken separately. | ||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
- | The process is proposed for 7.1. | + | The process is proposed for 7.3 and all future PHP versions. |
===== Future Scope ===== | ===== Future Scope ===== | ||
We may need to refresh the list of current maintainers (since some maintainers have moved on) and repeat the process | We may need to refresh the list of current maintainers (since some maintainers have moved on) and repeat the process | ||
- | in the future. | + | in the future. |
+ | |||
+ | The proposed procedure is to add years to each maintainer' | ||
+ | |||
+ | 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. | ||
===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== | ||
+ | |||
+ | Vote " | ||
+ | |||
+ | Since this RFC does not change the language, technical limit for passing is 50%+1 vote, however if it does not gather 2/3 " | ||
+ | |||
+ | <doodle title=" | ||
+ | * Yes | ||
+ | * No | ||
+ | </ | ||
+ | |||
+ | Voting starts on 2018-06-17, and ends on 2018-06-26 23:59 PDT. | ||
===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
Line 60: | Line 76: | ||
===== References ===== | ===== References ===== | ||
- | Discussion on internals: http:// | + | Discussion on internals: http:// |
rfc/umaintained_extensions.1473053028.txt.gz · Last modified: 2017/09/22 13:28 (external edit)