Cases in which it makes sense to propose a new package

As you may have already noticed while browsing the list of existing packages, the PEAR packages provide a (often abstract) solution for a general problem. Thus your code will most likely fit into PEAR if it solves a problem that will not only occur in one (e.g. your) specific application, but that occurs in a lot of (web) applications. Examples are:

  • Support for Network protocols
  • Object oriented wrappers that provide easy access to otherwise complicated or less intuitive PHP extensions.
  • Parsing different XML dialects.

    The PEAR packages that provide XML parsing functionalities can be found in the category browser.

No matter which area is covered by a package, the API should be as abstract as possible (while not becoming too complex), so that it can be utilized painlessly in as much use cases as possible.

How best to contribute to PEAR (Previous) Cases in which it is better to improve existing packages (Next)
Last updated: Tue, 16 Sep 2014 — Download Documentation
Do you think that something on this page is wrong? Please file a bug report or add a note.
View this page in:

User Notes:

There are no user contributed notes for this page.