Why not?

Sent from my iPhone

On Jul 22, 2013, at 7:14 AM, Lukas Kahwe Smith <notifications@github.com> wrote:

> In bylaws/004-psr-workflow.md:
> 
> > +if they agree that this is necessary. The purpose of this rule is to give PHP-FIG members the chance
> > +to consider *all* known alternatives during the Review stage.
> > +
> > +Unless a proposal is moved to Draft stage again, it must remain in Review stage for a minimum of two weeks
> > +before an acceptance vote is called. This gives every PHP-FIG Member sufficient time to get familiar
> > +with and influence a proposal before the final vote is called.
> > +
> > +When the Editor(s) and sponsors agree that the proposal is ready to become a PSR, an acceptance vote is called.
> > +The coordinator must publish a thread on the Mailing List with the subject "[VOTE][Accept] PSR-N: Title of the proposal"
> > +to announce the vote. The vote must adhere to [the voting protocol][voting].
> > +
> > +### 2.4 Accepted
> > +
> > +If the acceptance vote passes, then the proposal officially becomes an accepted PSR. The proposal itself is moved
> > +from `/proposed` to `/accepted` by a PHP-FIG member with GitHub access and prefixed with its PSR number, such as
> > +"PSR-4-autoloader.md". Comments must be removed from this document, but a copy of the commented proposal must be kept
> why use a PSR here as an example that has not yet passed?
> 
> —
> Reply to this email directly or view it on GitHub.