Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

New repository structure #3

Closed
wants to merge 1 commit into from

5 participants

@guilhermeblanco

Hi,

I have updated the repository structure and also updated the initial README.md, improving its documentation and describing each Specification status.

@norv

I'm not sure what kind of approval process (unless I'm missing some discussion).
I suppose the result of this approval is 'ongoing'. Therefore, considering the tools, it would be pulled in the public repository folder 'ongoing', on github, which is available for pull and commentary.
Maybe the choice of words gets in the way here: I'm not sure in what stages, if any, is the specification in progress not available for public commenting/review. (regardless of the name of the status itself).

One -> once

@norv

Compatibility

@renan

What is wrong with using Pull Requests for new proposals?

@michaelcullum michaelcullum commented on the diff
README.md
((10 lines not shown))
+original idea, they settled a group called PHP Standards Group, which can also
+be referred as Framework Interoperability Group (FIG).
+
+Every proposal is referred here as a Specification or a Recommendation (PSR).
+
+## Recommendation statuses
+
+Each PSR must go through a couple of statuses until it becomes a valid
+Recommendation signed by Standards Group.
+
+The specification working statuses are:
+
+- Step 1: Early Draft Review
+
+ > One an idea of a Recommendation is approved by Board, a group of experts

by Board? Should be a board or the board. Happens in a few other places too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@philsturgeon

This is being taken care of from a few angles, mainly from the new discussion about how we revise PSR's, etc. It's been inactive a while so im gonna prune this off.

@sun sun referenced this pull request from a commit in sun/fig-standards
@mvriel mvriel Fixes #3: Add Inline PHPDoc description db15c21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
View
88 README.md
@@ -1,4 +1,86 @@
-Repository for maintaining Framework Interop Group specification proposals.
+# PHP Standards Group (aka. Framework Interoperabilit Group)
-In order to propose fork, add document, send a PR. Alternatively simply create a ticket
-to start a discussion.
+## Introduction
+
+In mid 2009 a group of known PHP project leaders joined forces with the
+intention to bring some standardization between different projects. From that
+original idea, they settled a group called PHP Standards Group, which can also
+be referred as Framework Interoperability Group (FIG).
+
+Every proposal is referred here as a Specification or a Recommendation (PSR).
+
+## Recommendation statuses
+
+Each PSR must go through a couple of statuses until it becomes a valid
+Recommendation signed by Standards Group.
+
+The specification working statuses are:
+
+- Step 1: Early Draft Review
+
+ > One an idea of a Recommendation is approved by Board, a group of experts

by Board? Should be a board or the board. Happens in a few other places too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
+ > is formed to develop the first draft of the specification that Board can
+ > review or add comments.
+
+- Step 2: Public Review
+
+ > After PSR is drafted, it goes for review by the public where anyone can
+ > read and comment on the draft. The Board uses the public feedback to
+ > further revise the document.
+
+- Step 3: Proposed Final Draft
+
+ > At this stage of the draft specification, Board will approve and
+ > specification group will use it as the basis for contract and sample
+ > implementations (aka. as Reference Implementation and Technology
+ > Compatibility Kit).
+
+- Step 4: Final Release
+
+ > The spec group then sees that the Reference Implementation (RI) and the
+ > Technology Compatiblity Kit (TCK) are completed before sending to the Board
+ > for final approval.
+
+Every Specification is organized by its current status. These statuses
+represent at which stage the document is currently and also allow better
+separation of what was already proposed, and what is approved or rejected by
+the Board.
+
+The specification approval statuses are:
+
+- Accepted
+
+ > PHP Standards Recommendation that have been approved by Board.
+
+- Inactive
+
+ > Recommendations that have not posted a Final Release and have not changed
+ > internal status in the last 18 months.
+
+- Ongoing
+
+ > Currently Recommendations that are in the works, like being drafted,
+ > written or discussed by FIG.
+
+- Proposed
+
+ > Recommendations that are ready to be voted by Board
+
+- Rejected
+
+ > Proposals that have been voted down by Board during Draft Approval, Board
+ > Review or Final Approval.
+
+- Withdrawn
+
+ > PSRs that are withdrawn from the Board by their Specification Leads before
+ > going to Final Release.
+
+## Proposing a Recommendation
+
+Github is the central point of support of FIG.
+
+Anyone is allowed to fork and add a document or even open a ticket proposing
+a new PSR.
+The Board then will be able to guide any contributor until the proposed idea
+becomes ready to be reviewed.
View
0  accepted/PSR-0.md → ...ed/PSR-0 - Autoloader/3 - Final Release/README.md
File renamed without changes
View
2  inactive/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  ongoing/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  proposed/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  rejected/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  sample/PSR-# - Title/0 - Early Draft Review/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  sample/PSR-# - Title/1 - Public Review/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  sample/PSR-# - Title/2 - Proposed Final Draft/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  sample/PSR-# - Title/3 - Final Release/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
View
2  withdrawn/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
Something went wrong with that request. Please try again.