Re: PEAR developers guide
| From: | Eric | Date: | Sat, 11 May 2002 20:07:57 +0000 |
| Subject: | Re: PEAR developers guide | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6053@lists.php.net to get a copy of this message | ||
A "Getting Started" section would be nice to have in here. I just started
looking at PEAR yesterday, and it seems that either the information on the
website isn't organized well, or there is just too much confusion between
PEAR and PHP.
Here's the problems I ran into yesterday.
1) pear requires --with-xmlrpc (seems undocumented?). The pear program
exits with a non-descriptive error if extension_loaded("xmlrpc") fails.
2) the go-pear script downloads and installs pear packages, but does not
register them (most notably the PEAR package). chicken/egg problem?
3) PEAR downloads vs. 'make install-su'.
I'm willing to help with documentation and organization. As I'm new, I
don't really know what to do yet. Is there a PEAR "TODO" list?
eric
On Sat, 11 May 2002, Martin Jansen wrote:
> Hi,
>
> I will soon start writing the PEAR developers guide and I would
> like to hear some feedback concerning my ideas. Right now I thought
> of the following contents:
>
> ====================================================================
> * What PEAR means for a developer
>
> * High quality code
> * Chance to release his/her own code and become famous
>
> * Contributing own code
>
> * Requirements for contributing code
>
> * Conforming to the coding standards
> * Documentation in an appropriate format (plain text, docbook)
> * The contributor is willing to provide support for his
> package(s)
> and is willing to release future (bug-fixing) versions.
>
> * How to contribute code
>
> * CVS account, pear.php.net account
> * Finding an appropriate package name
> * Bundling releases
>
> * How to support the PEAR community
>
> * Reporting and fixing bugs
> * Buying things from wishlists :)
> * Contributing new features to packages
> * Becoming the new maintainer for an unmaintained package
> ====================================================================
>
> Right now this is work in progress and if you have topics that
> should be additionally mentioned, post them now or be quiet
> forever :-).
>
> - Martin
>
>