php-fig

fig-standards

OPEN SOURCE2012–2025

php-fig / fig-standards

fig-standards

Standards either proposed or approved by the Framework Interop Group

Explore on GitHub Read Hacker News discussions

14Distinct people

15Mentions

0Explicit recommenders

12.5KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Standards either proposed or approved by the Framework Interop Group

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2012-06-26 20:03:27 UTC to 2025-07-30 16:54:42 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2012	2012-01-01 00:00:00 UTC	2013-01-01 00:00:00 UTC	3	1	2
2013	2013-01-01 00:00:00 UTC	2014-01-01 00:00:00 UTC	6	1	5
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	1	0	1
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	1	0
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	0	0	0
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	0	0	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	0	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	1	0	1
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	0	1

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction

PHP Framework Interoperability Group The idea behind the group is for project representatives to talk about the commonalities between our projects and find ways we can work together. Our main audience is each other, but we’re very aware that the rest of the PHP community is watching. If other folks want to adopt what we’re doing they are welcome to do so, but that is not the aim. Proposing a Standard Recommendation To propose a PHP Standard Recommendation (PSR): fork this repo, create a branch, checkout that branch, add the PSR in proposed/, push the branch to GitHub, and send a pull request; or, create a ticket to start a discussion on GitHub; or, start a conversation on the mailing list. GitHub usage All discussion regarding a PSR happens on the mailing list. Issues filed in GitHub are rarely monitored, and PRs are likely to be missed unless a message is sent to the mailing list regarding them. Reviews of a proposed PSR should be conducted on the mailing list, not through PR comments for the same reason. Please do not simply file an issue or PR and walk-away. The most likely outcome is that it will never get seen or addressed. Requesting Membership You do not need to be a voting member to participate in discussion on the mailing list. To become a voting member, you must send an email to the mailing list. The subject line should read: Membership Request: {$your_name} ({$project_name}) The body should include your name, the name of (and link to) the project you represent, and other details you feel are relevant. Current members will vote on your request. Do not combine separate membership requests in a single thread; one request per thread, please. Language & Translations All PSRs are written in British English or American English (Different specifications may vary, but it is consistent within the same specification). The PHP FIG does not offer official translations into other languages but other external entities are free to translate the specifications in accordance with the license. Voting Members The current list of voting members is available on the project website.

Read the full README on GitHub

What Hacker News says

6 sources

ihsw·Aug 26, 2013

For a comprehensive list of new major language features, there is a wiki: https://wiki.php.net/rfc#implemented One major feature not listed on the submitted article is namespaces, which is fairly major and it's just starting to reach critical mass in terms of reach. Despite being probably the most major feature in the past five years, most users should be able to enjoy using namespaces to their heart's content (along with all the libraries that utilize it, for example Amazon's latest PHP SDK (which is thoroughly impressive)). For reference, Python3 came out in 2008 and it's also just starting to reach critical mass in terms of library support (cough third-party Django libraries). There is also a third-party committee[1][2] with the goal of establishing things like coding guidelines, logging interfaces, HTTP request/response interfaces, an

Read the rest

d so forth. [1] http://www.php-fig.org/ [2] https://github.com/php-fig/fig-standards

In A Look at PHP's Continuing Evolution

dutchbrit·Aug 7, 2013Submission

Ask HN: Which coding guidelines do you use?

Always interesting to see what code guidelines people use in what language. Personally, I use the following for PHP: Basic Coding Standard: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-s… Coding Style Guide: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-g…

4 points · Open discussion

joemaller1·Aug 3, 2013

So we're wrong to wish for WordPress to adopt PSR standards instead of their own idiosyncratic coding style? I really like PSR compliant PHP code (it's almost PEP 8-ish), the WordPress standards are frustratingly opposite on some key concepts (braces, indentation). But WP is so popular, I don't see how this might ever be resolved. https://github.com/php-fig/fig-standards/blob/master/accepte... http://make.wordpress.org/core/handbook/coding-standards/php...

In Reasons Why WordPress Made PHP Popular, not PHP Frameworks

krapp·Jun 25, 2013

Learn to love php.net, stackoverflow and this page here: https://www.owasp.org/index.php/PHP_Security_Cheat_Sheet, but don't necessarily trust the code you find on php.net and SO. Comment religiously. You'll thank yourself in six months. You'll save yourself a lot of time if you learn to use Composer (http://getcomposer.org) to manage dependencies, and a templating system (twig, mustache, smarty, what have you) and class autoloading. PSR-0 (https://github.com/php-fig/fig-standards/blob/master/accepte...) is annoying, but it is really convenient once you get past the overhead. If you're on Windows, it really helps to get PHP running from the command line.

In The new php.net

throwawayG9·Apr 6, 2013

I feel you, but it's just a matter of finding the right circles. I would never apply for a job just because it says 'php', you have to dig deeper. At this point in my career, I would never accept a freelance gig like the one you described, because I know how that goes. You don't need to try other languages, do it only if you want to. If you wanna save time just take my word, Symfony2 has nothing to envy to Django or Rails (I have used them and also digged into their architecture). In fact, it's more modern and better designed. I'll leave these links here, you might find them useful: - http://www.phptherightway.com/ (general advice) - http://getcomposer.org/ (composer, the dependency manager) - https://packagist.org/ (the main composer repository) - https://github.com/php-fig/fig-standards/tree/master/accepte... (accepted conventions) - ht

Read the rest

tp://www.slideshare.net/fabpot/dependency-injection-with-p... (if you liked MVC, DI will blow your mind) - http://fabien.potencier.org/article/50/create-your-own-frame... (an amazing tutorial on how to create a framework, it will let you understand it inside out) - http://symfony.com/download (what should become your next framework) - http://silex.sensiolabs.org/ (minimalistic version of Symfony2, it's called Silex, and might be useful for small websites) If you still want to try something else, try something that has nothing to do with all this, like Clojure. For example, Ruby/Rails is the same as PHP/Symfony2, you won't learn much. I jumped into Rails and just started coding, because I already knew web development, I wasn't impressed, the differences were mostly syntactic sugar, monolithic vs decoupled, and issues like the lack of interfaces and type hinting. But Clojure? Mind blown. I'm gonna spend my next summer learning more Clojure, because I already know it's my perfect language, but it's hard and full of new concepts. Meanwhile, php/Symfony2/nginx is my perfect stack for web development.

In URLs are for People, not Computers

captn3m0·Mar 2, 2013

http://www.codular.com/ has some good examples. Further, anything from the symphony framework and the composer stuff is quite good. See https://github.com/php-fig/fig-standards for some of the good work that is happening.

In Beautiful PHP