Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split PSR-5 into two PSR proposals #1038

Merged
merged 8 commits into from
Jun 23, 2018
Merged

Conversation

ashnazg
Copy link
Contributor

@ashnazg ashnazg commented May 31, 2018

No description provided.

@ashnazg ashnazg changed the title Remove tag catalog stuff Split PSR-5 into two PSR proposals Jun 1, 2018
@ashnazg
Copy link
Contributor Author

ashnazg commented Jun 4, 2018

Ping Working Group (@michaelcullum @neuro159 @muglug @ondrejmirtes)

susceptible to becoming out of date.

PHPDoc as a notation has existed for more than ten years now, is heavily inspired by JavaDoc, and is currently in use by a
significant percentage of public PHP projects in the field.
PHPDoc as a notation has existed for more than fifteen years now, is heavily inspired by JavaDoc,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ulf Wendel presented phpdoc and its notation in October 2000. In case you want to be more exact than "more than fifteen years" ;-)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering about that... my only mental timeline was knowing roughly when Josh had it and Greg joined in :-D

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

relative time information without a clear reference date ages badly - maybe mention a year instead of "x years ago" which will be outdated next year...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, that's what I'll be doing now that I have the actual landmark.

@jaapio
Copy link
Member

jaapio commented Jun 10, 2018

Looks good to me. I think it is good to split this psr in 2. Definition format and tags are different things

@muglug
Copy link
Contributor

muglug commented Jun 11, 2018

Looks good to me

@Jean85
Copy link
Member

Jean85 commented Jun 12, 2018

@neuro159 @muglug @ondrejmirtes since we are using PullApprove, you can use GitHub's reviews to signal your 👍


### 3.2 Non-Goals

* This PSR does not provide a recommendation on how and when to use the concepts described in this document,
so it is not a coding standard.
* This PSR does not introduce new concepts that guess at matching best practices or design patterns in the foreseeable
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel this conflicts with Ln 22.

* This PSR does not introduce new concepts that guess at matching best practices or design patterns in the foreseeable
future.
* This PSR does not provide a recommendation on how and when to use the concepts described in this document, so it is
not a coding standard.
* This PSR facilitates the creation of annotations by allowing the notation needed for Symfony/Doctrine style
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd remove this as a non-goal, but not add it as a goal so we have some intentional ambiguity there honestly.


## 1. Summary

The purpose of this PSR is to document (in a catalog style) the de facto list of Tags historically in use
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tags shouldn't be capitalised throughout as it's not a proper noun.

@ashnazg
Copy link
Contributor Author

ashnazg commented Jun 18, 2018

@neuro159 @ondrejmirtes ? The phpDocumentor team wants to send in some PRs, but this split will need to merge first.

@ashnazg
Copy link
Contributor Author

ashnazg commented Jun 20, 2018

Anyone?

@ashnazg
Copy link
Contributor Author

ashnazg commented Jun 22, 2018

Ping @michaelcullum @Jean85 ... is this ok to merge now?

@mindplay-dk
Copy link
Contributor

Where is the working group currently discussing and working on things?

I was heavily involved in PSR-5 previously and have some important things I'd like to point out.

@Jean85
Copy link
Member

Jean85 commented Sep 19, 2018

@mindplay-dk please reach out to @ashnazg to get involved. If needed, involve me too.

@mindplay-dk
Copy link
Contributor

@Jean85 I've sent him an e-mail, thanks :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants