Package Development Standards: “pds/skeleton” Now Open For Review!

The new Package Development Standards initiative is proud to present its first publication, pds/skeleton (and the related research) for public review. If you are a package author, you are invited to post your comments and criticisms of the publication as issues on the relevant Github repository.

The pds/skeleton publication describes a set of standard top-level PHP package directories and files. If you are an author of more than three packages on Packagist, chances are you already follow the standard! That’s because PDS initiative researches the PHP package ecosystem to recognize commonly adopted development practices. (See this list of over than 47,000 packages; if your package is there, it has been tentatively noted as already compliant.)

The public review period will last at least 2 weeks, perhaps longer. If there are no substantial errors revealed during that time, the standard will advance to “beta” status for adoption, and then to “stable” if no further errors are discovered in use.

Meanwhile, if you review the publication and determine that your package follows it, you should add pds/skeleton to your Composer “require-dev” block, because that will help the initiative track formal adoption rates.

Are you stuck with a legacy PHP application? You should buy my book because it gives you a step-by-step guide to improving your codebase, all while keeping it running the whole time.

3 thoughts on “Package Development Standards: “pds/skeleton” Now Open For Review!

    • Hi Fabian,

      My first thought is that “provides” says that a package “makes X available”, not that a package “uses X”. (I may be wrong about that, and need to read the schema more closely.)

      My second thought is something that I’ve only spoken publicly about on . It is that by require-dev-ing the standard in your package, the standard can do two things:

      1. Deliver the standards document into the package, for reference by developers as they work on the package.

      2. Possibly also deliver some code related to the standard. In the case of pds/skeleton, that might mean a validation script, or a skeleton-generator script. But I would want to think more carefully about this one.

      Hope that makes sense.

Leave a Reply

Your email address will not be published. Required fields are marked *