FIG

Transcript

1. PHP FIG: Standardising PHP PHP Hampshire September 2013
2. “Coming together is a beginning; keeping together is progress; working together is success.”
3. PHP FIG: Standardising PHP PHP Hampshire September 2013
4. Who? • Michael Cullum • phpBB Team Member • Lover of Symfony michaelcullumuk m@michaelcullum.com michaelcullum
5. Firstly: WHAT IS FIG?
6. FIG • Framework • Interoperability • Group
7. phpBB Propel Symfony PPI AWS Zend Framework Apache Agavi Assetic Aura Cake PHP Composer Doctrine eZ Publish Flow/Typo3 Jackalope Joomla Lithium Laravel PEAR phpDocumenter Drupal PyroCMS SabreDEV Sugar CRM Zikula
9. PROBLEM:
10. PHP IS BAD AT SHARING
11. PHP IS BAD AT INTEROP
12. Getting off the Island
13. PHP == LONDON STREET
15. PHP FIG! Well, mostly…. SOLOUTION:
16. AND THINGS ARE GETTING BETTER!!
17. A BIT OF A TRIP BACK IN TIME…
18. THINGS STARTED GREAT!
19. THEN THEY MESSED UP!
20. BUT THEY CAME BACK AND LIVED HAPPILY EVER… PRODUCING PSRS
21. PSRS? HOW DOES FIG ACTUALLY HELP?
22. PHP STANDARD RECOMMENDATIONS
23. TARGET AUDIENCE: “Us, but kind of everyone else”
24. A BUNCH OF DEVELOPERS DOING POLITICS
25. HOW DO WE MAKE PSRS?
26. FORM A WORKING GROUP
28. ASSIGN PSR NUMBER
30. REVIEW
32. ACCEPT
33. CURRENT PSRs
34. PSR-0 The most important one (and one you’ve all probably used).
35. Auto- loading
36. PSR-0 • How to autoload libraries • Very simple terms: • Namespace is formatted as <vendor>/<package>/<namespace>/<classname> • Acme/Foo/Bar/MyClass will exist as a class in file: Acme/Foo/Bar/MyClass.php • Composer does this.  • Problem: Composer will put Acme’s Foo Project in /vendor/acme/foo/ resulting in the following directory nesting: /vendor/acme/foo/acme/foo/bar/myclass.php
37. PSR-1 Basic Coding Standard
38. PSR-1 • Coding Standards that affect interop • Such as file must have logic or affect behaviour but not both, line endings & Encoding • Used often in conjunction with PSR-2
39. PSR-2 Coding Style Guide
40. PSR-2 • Extends (Requires/Includes PSR-1) • Coding standards such as where to have brackets, spaces etc. • Spaces vs Tabs • Called a guide, not a standard • Not really for interop, just continuity and allows many libs to not have to create their own. • CS Fixers
41. PSR-3 Logging Interface
42. PSR-3 • A common interface for logging libraries to use and applications to expect. • Common Interfaces make libs interchangeable. • First of many… • GH: php-fig/log • Composer: fig/log
43. INTO THE FUTURE
44. Up and Coming PSRs •Caching Interface •PHPDoc Standard •Package Oriented Autoloader
45. CACHING • Another interface • Allows caching libraries and for frameworks to share a cache or drop caching libs in and out • In the making for a long time. Hopefully in the next couple of months should go through.
46. Package Orientated Autoloader • Solves the problem of /vendor/acme/foo/acme/foo/bar/myclass.php • Allows Acme/Foo/Bar/MyClass to map to a custom directory. • /vendor/acme/foo/bar/myclass.php • Composer will support this
47. PHPDoc • Standard for Docblocs • Allows you to interchange & share API Generators (phpDocumenter etc.) Docbloc Example: /** * Get user id from username * * @param string $username User’s Name * @return int Users’ Id */
48. You want to get involved right?
49. Getting Involved • Using the PSRs: Github - php-fig/fig-standards http://php-fig.org • Help work on the PSRs: Contribute on the ML. Google Groups. Link on the website.
50. Getting Involved • Become a voting member: Apply on the ML. NB: Projects apply, not people. • Spread the word: Write a blog post, recommend usage, explain to colleagues.
52. Slides Available @ speakerdeck.com/unknownbliss/fig
53. PHP FIG: Standardising PHP PHP Hampshire September 2013