Re: PEAR2 code and docs

On Mon, 2010-06-21 at 11:31 +0200, till wrote: > Hey, > > is it possible to link to the designated repository of a component on > the PEAR2 website? > Is this a feature request for the website? If so, it's a feature that will be added, but has not been added yet. Currently, the PEAR2 website uses Pyrus as the data layer so only information from the package XML is available for display. We're going to add a DB layer to contain package metadata like ratings and comments. A link to the source code will also be added. > Also, how do we handle documentation and all that. It's fishy that > there is none. ;-) > I have no idea how documentation will be handled. I think the current plan is to use docbook. I'm not crazy about using docbook. I feel the PEAR1 docs suffered rot and were not maintained because docbook is too much of a barrier for contributors. > Sort of related - how does the PEAR2 proposal process work? > As far as I recall, The PEAR2 proposal process is: 1. You create a project in the PEAR2 sandbox. This requires no approval. Your package is pear installable, but not pear-approved (TM). 2. If and when you feel you are ready, you propose your project using something quite similar to PEPR. 3. Your project gets approved and moves out of sandbox into main. Hope this clears up some of your questions, Mike