Welcome to the PEAR community! By this point, you have decided to contribute some of your time and effort to improving the PEAR repository. Before you go any further, we'd like to introduce you to the common practices and communication channels that PEAR developers use in order to collaborate across geographical and national divides. Additionally we will tell you the different places where you can find more information about the inner workings and rules of PEAR.
Mailing lists are the most important way to communicate in PEAR. We are running a number of public mailing lists, which are listed on the PEAR website. For starters the PEAR developers mailing list email@example.com is the primary place where discuss various aspects of their packages and of the PEAR repository as a whole. firstname.lastname@example.org is a general support list that should be used for questions on using PEAR packages, installing PEAR, and other issues not directly related to the development of PEAR packages.
If you would like to get started with maintaining packages in PEAR, you are expected to be subscribed to email@example.com. (Subscription instructions)
Note: During your first steps in the PEAR community, you may stumble across the term "pear-dev", which is the abbreviation for the developers mailing list in PEAR's lingo.
Some people enjoy communicating via IRC channels. We are running the #pear channel in the EFnet network. Some of the most active PEAR developers hang out regularly on this channel. However, for serious inquiries or discussions, you should email the developers mailing list firstname.lastname@example.org, as these discussions are the only official communication method of PEAR, and are archived for future reference.