Skip to content
This repository

New repository structure #3

Closed
wants to merge 1 commit into from

5 participants

Guilherme Blanco Renan Gonçalves Phil Sturgeon Michael C. Norv
Guilherme Blanco

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).

norv replied

One -> once

Norv

Compatibility

Renan Gonçalves

What is wrong with using Pull Requests for new proposals?

Michael C. michaelcullum commented on the diff
README.md
((10 lines not shown))
  6 +intention to bring some standardization between different projects. From that
  7 +original idea, they settled a group called PHP Standards Group, which can also
  8 +be referred as Framework Interoperability Group (FIG).
  9 +
  10 +Every proposal is referred here as a Specification or a Recommendation (PSR).
  11 +
  12 +## Recommendation statuses
  13 +
  14 +Each PSR must go through a couple of statuses until it becomes a valid
  15 +Recommendation signed by Standards Group.
  16 +
  17 +The specification working statuses are:
  18 +
  19 +- Step 1: Early Draft Review
  20 +
  21 + > One an idea of a Recommendation is approved by Board, a group of experts
1

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
Phil Sturgeon
Collaborator

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
Mike van Riel 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

Showing 1 unique commit by 1 author.

Oct 25, 2011
Guilherme Blanco guilhermeblanco New proposed structure. Updated root document: README.md bbc3c7c
This page is out of date. Refresh to see the latest.
88 README.md
Source Rendered
... ... @@ -1,4 +1,86 @@
1   -Repository for maintaining Framework Interop Group specification proposals.
  1 +# PHP Standards Group (aka. Framework Interoperabilit Group)
2 2
3   -In order to propose fork, add document, send a PR. Alternatively simply create a ticket
4   -to start a discussion.
  3 +## Introduction
  4 +
  5 +In mid 2009 a group of known PHP project leaders joined forces with the
  6 +intention to bring some standardization between different projects. From that
  7 +original idea, they settled a group called PHP Standards Group, which can also
  8 +be referred as Framework Interoperability Group (FIG).
  9 +
  10 +Every proposal is referred here as a Specification or a Recommendation (PSR).
  11 +
  12 +## Recommendation statuses
  13 +
  14 +Each PSR must go through a couple of statuses until it becomes a valid
  15 +Recommendation signed by Standards Group.
  16 +
  17 +The specification working statuses are:
  18 +
  19 +- Step 1: Early Draft Review
  20 +
  21 + > One an idea of a Recommendation is approved by Board, a group of experts
  22 + > is formed to develop the first draft of the specification that Board can
  23 + > review or add comments.
  24 +
  25 +- Step 2: Public Review
  26 +
  27 + > After PSR is drafted, it goes for review by the public where anyone can
  28 + > read and comment on the draft. The Board uses the public feedback to
  29 + > further revise the document.
  30 +
  31 +- Step 3: Proposed Final Draft
  32 +
  33 + > At this stage of the draft specification, Board will approve and
  34 + > specification group will use it as the basis for contract and sample
  35 + > implementations (aka. as Reference Implementation and Technology
  36 + > Compatibility Kit).
  37 +
  38 +- Step 4: Final Release
  39 +
  40 + > The spec group then sees that the Reference Implementation (RI) and the
  41 + > Technology Compatiblity Kit (TCK) are completed before sending to the Board
  42 + > for final approval.
  43 +
  44 +Every Specification is organized by its current status. These statuses
  45 +represent at which stage the document is currently and also allow better
  46 +separation of what was already proposed, and what is approved or rejected by
  47 +the Board.
  48 +
  49 +The specification approval statuses are:
  50 +
  51 +- Accepted
  52 +
  53 + > PHP Standards Recommendation that have been approved by Board.
  54 +
  55 +- Inactive
  56 +
  57 + > Recommendations that have not posted a Final Release and have not changed
  58 + > internal status in the last 18 months.
  59 +
  60 +- Ongoing
  61 +
  62 + > Currently Recommendations that are in the works, like being drafted,
  63 + > written or discussed by FIG.
  64 +
  65 +- Proposed
  66 +
  67 + > Recommendations that are ready to be voted by Board
  68 +
  69 +- Rejected
  70 +
  71 + > Proposals that have been voted down by Board during Draft Approval, Board
  72 + > Review or Final Approval.
  73 +
  74 +- Withdrawn
  75 +
  76 + > PSRs that are withdrawn from the Board by their Specification Leads before
  77 + > going to Final Release.
  78 +
  79 +## Proposing a Recommendation
  80 +
  81 +Github is the central point of support of FIG.
  82 +
  83 +Anyone is allowed to fork and add a document or even open a ticket proposing
  84 +a new PSR.
  85 +The Board then will be able to guide any contributor until the proposed idea
  86 +becomes ready to be reviewed.
0  accepted/PSR-0.md → ...ed/PSR-0 - Autoloader/3 - Final Release/README.md
File renamed without changes
2  inactive/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  ongoing/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  proposed/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  rejected/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  sample/PSR-# - Title/0 - Early Draft Review/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  sample/PSR-# - Title/1 - Public Review/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  sample/PSR-# - Title/2 - Proposed Final Draft/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  sample/PSR-# - Title/3 - Final Release/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore
2  withdrawn/.gitignore
... ... @@ -0,0 +1,2 @@
  1 +*
  2 +!.gitignore

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.