★★★

The League of Extraordinary Packages is a group of developers who have banded together to build solid, well tested PHP packages using modern coding standards.

★★★

Our Packages

* a work-in-progress package

Our Definition Of Quality

Ask 100 developers what defines an awesome PHP package and you’ll get a lot of different answers. That also sounds like a really long and boring task, so we’ve come up with a list of rules that we think make a package awesome.
View our skeleton project

  1. Use a vendor namespace (League in our case) for PSR-4 autoloading. Shove code in a src folder.

  2. Adhere to PSR-2 as the coding style guide.

  3. Distribute code using Packagist.

  4. Write unit tests. Aim for at least 80% coverage in version 1.

  5. DocBlock all the things that require additional context.

  6. Use Semantic Versioning to manage version numbers.

  7. Keep a Changelog.

  8. Use Travis-CI to automatically check coding standards and run tests.

  9. Have an extensive README.

  10. Exclude non-essential files in .gitattributes.

Why?

We’re doing this instead of releasing code under our personal accounts for a few reasons, but the main reason is this:

A problem shared is a problem halved.

Working together we take care of business quicker, can get more feedback and respond to issues and pull requests faster.

There are no plans to reinvent any wheels, unless those wheels are old, broken, unsafe or horrible to use. If the code cannot be installed with Composer, has an API written with BizZaroCapS, doesn’t have a single unit-test, is actually broken or the lead developer has abandoned the project, then that is a problem which can most likely be solved with a fresh start, and we’ll be on the case to make it as awesome as possible.

© Copyright The League of Extraordinary Packages. Site design by Jonathan Reinink.