Requests for Change documents. Similar to PSR, PEP, JSR, and other document-oriented changes.
Documents will go by SPEP, which stands for SimplePie Enhancement Proposal. Since they may include other "metadata" documentation, each one will live in it's own subdirectory. This is the pattern adopted by the PHP-FIG, so there is some precedent there.
-
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
-
"Support" or "Supported" refer to the fact that we (humans) will provide support and/or actively test particular software. It does not refer to (and makes no claims about) whether or not particular software functions in a given environment context (machines).
-
"SimplePie Core Team" is defined by
simplepie/.github. -
"SimplePie" refers to the overarching SimplePie project, which may include any of the sub-projects under the SimplePie umbrella. It does not implicitly or explicitly refer to any particular repository of code.
-
"SimplePie NG", "Feed Locator", "Text Encoder", and other names refer to their specific project repositories.
-
"SimplePie OG" refers to the original
simplepie/simplepierepository, and is a play-on-words. In "SimplePie NG", the "NG" stands for Next-Generation. "NG" is similar to "OG", and "OG" is a slang acronym for original gangsta, or sometimes old gee, where "gee" is short for gangsta. From this term, we derive "original" (or "old"), referring to the original SimplePie project.
These documents are expected to apply to all repositories (as appropriate) inside this GitHub organization with the following exceptions:
-
Archived repositories are exempted from these documents.
-
The original
simplepie/simplepierepository (aka, "SimplePie Classic", "SimplePie OG") is exempted from these documents.
| # | Title |
|---|---|
| SPEP-1 | PHP Version Support Guidelines |
| SPEP-2 | One-Way Git Merges |
TBD
TBD
TBD