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

Badges for PHP-FIG standards #130

Closed
graste opened this issue Jun 28, 2014 · 9 comments
Closed

Badges for PHP-FIG standards #130

graste opened this issue Jun 28, 2014 · 9 comments

Comments

@graste
Copy link

graste commented Jun 28, 2014

How about adding badges for the accepted PHP-FIG standards like PSR-0, PSR-1, PSR-2, PSR-3 and PSR-4? I think it would be nice to see if a project adheres to certain standards (at least those that do try to follow those standards).

@liuggio
Copy link
Member

liuggio commented Jun 28, 2014

good idea! @packagist has also this info...

@agiuliano
Copy link
Member

:+1

@giorrrgio
Copy link
Member

👍

@liuggio
Copy link
Member

liuggio commented Jun 30, 2014

@graste would you like to work on it?

@graste
Copy link
Author

graste commented Jul 9, 2014

Thanks for asking, but I'll have to decline. :-)

@liuggio
Copy link
Member

liuggio commented Jul 10, 2014

the problem is how to show this information ...
Who has an idea?

@liuggio
Copy link
Member

liuggio commented Jul 10, 2014

@hpatoio only psr0/psr4 from the autoload...

@graste
Copy link
Author

graste commented Jul 12, 2014

Yeah, on packagist there's only psr-0/psr-4 autoload information available for packages. That doesn't prevent creation of buttons for the other psrs I guess:

[![PSR-0](https://poser.pugx.org/img/psr-0.svg)](http://www.php-fig.org/psr/psr-0/ "leaphly/cart-bundle is PSR-0 compatible")

The text of the badges is fixed, which means it's a one-time job to create the resources. The title of the link to the standard mentions the project as being compatible. On the homepage only psr-0/psr-4 are made available and it might be nice to make markdown etc. embeds available for the standards, that are not in a composer json file.

Another possibility would be to scan the keywords of packages for psr-x tags or allow extra information parsing or even creating a composer issue for such a default schema extension.

@liuggio liuggio closed this as completed Apr 19, 2015
@liuggio
Copy link
Member

liuggio commented Apr 19, 2015

closed to inactivity

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

No branches or pull requests

4 participants