rfc:template
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revisionNext revision | |||
— | rfc:template [2013/02/24 21:55] – See if I've fixed our capabilities of modifying the actual template bjori | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | ====== PHP RFC: Your Title Here ====== | ||
+ | * Version: 0.9 | ||
+ | * Date: 2013-02-24 (use today' | ||
+ | * Author: Your Name, your_email_address@example.com | ||
+ | * Status: Draft (or Under Discussion or Accepted or Declined) | ||
+ | * First Published at: http:// | ||
+ | |||
+ | This is a suggested template for PHP Request for Comments (RFCs). Change this template to suit your RFC. Not all RFCs need to be tightly specified. | ||
+ | |||
+ | You RFC should move PHP forward. As [[http:// | ||
+ | large chunk of our userbase, and not something that could be useful in some | ||
+ | extremely specialized edge cases [...] Make sure you think about the full context, the huge audience out there, the consequences of making the learning curve steeper with | ||
+ | every new feature, and the scope of the goodness that those new features bring." | ||
+ | ===== Introduction ===== | ||
+ | |||
+ | The elevator pitch for the RFC. | ||
+ | |||
+ | ===== Proposal ===== | ||
+ | |||
+ | All the features and examples of the proposal. | ||
+ | |||
+ | To [[http:// | ||
+ | for inclusion in one of the world' | ||
+ | |||
+ | Remember that the RFC contents should be easily reusable in the PHP Documentation. | ||
+ | ===== Backward Incompatible Changes ===== | ||
+ | |||
+ | What breaks, and what is the justification for it? | ||
+ | |||
+ | ===== Proposed PHP Version(s) ===== | ||
+ | |||
+ | List the proposed PHP versions that the feature will be included in. Use relative versions such as "next PHP 5.x" or "next PHP 5.x.y" | ||
+ | |||
+ | ===== SAPIs Impacted ===== | ||
+ | |||
+ | Describe the impact to CLI, Development web server, embedded PHP etc. | ||
+ | |||
+ | ===== Impact to Existing Extensions ===== | ||
+ | |||
+ | Will existing extensions be affected? | ||
+ | |||
+ | ===== New Constants ===== | ||
+ | |||
+ | Describe any new constants so they can be accurately and comprehensively explained in the PHP documentation. | ||
+ | |||
+ | ===== php.ini Defaults ===== | ||
+ | |||
+ | If there are any php.ini settings then list: | ||
+ | * hardcoded default values | ||
+ | * php.ini-development values | ||
+ | * php.ini-production values | ||
+ | |||
+ | ===== Open Issues ===== | ||
+ | |||
+ | Make sure there are no open issues when the vote starts! | ||
+ | |||
+ | ===== Unaffected PHP Functionality ===== | ||
+ | |||
+ | List existing areas/ | ||
+ | |||
+ | This helps avoid any ambiguity, shows that you have thought deeply about the RFC's impact, and helps reduces mail list noise. | ||
+ | |||
+ | ===== Future Scope ===== | ||
+ | |||
+ | This sections details areas where the feature might be improved in future, but that are not currently proposed in this RFC. | ||
+ | |||
+ | ===== Proposed Voting Choices ===== | ||
+ | |||
+ | Include these so readers know where you are heading and can discuss the proposed voting options. | ||
+ | |||
+ | ===== Patches and Tests ===== | ||
+ | |||
+ | Links to any external patches and tests go here. | ||
+ | |||
+ | If there is no patch, make it clear who will create a patch, or whether a volunteer to help with implementation is needed. | ||
+ | |||
+ | Make it clear if the patch is intended to be the final patch, or is just a prototype. | ||
+ | |||
+ | ===== References ===== | ||
+ | |||
+ | Links to external references, discussions or RFCs | ||
+ | |||
+ | ===== Rejected Features ===== | ||
+ | |||
+ | Keep this updated with features that were discussed on the mail lists. | ||
rfc/template.txt · Last modified: 2020/06/28 18:09 by girgias