Re: PEAR2 code and docs

From: Date: Wed, 23 Jun 2010 14:41:51 +0000
Subject: Re: PEAR2 code and docs
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-53589@lists.php.net to get a copy of this message
On Wed, Jun 23, 2010 at 4:07 PM, Michael Gauthier <mike@silverorange.com> wrote: > 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. Yes, I guess it was a question, but if not available it's also a feature request. > 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. Can we integrate external services like disqus or intensedebate here to get stuff done faster? IMHO, we should build a system when necessary aka later. >> 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. Well, maybe we can phpdoc what is available first and run it through some hooks when a release is pushed? I also agree that docbook might not be feasible, really. I guess I'd like something as simple as markdown-based wiki of some thought. I have no idea what system though. But maybe that could be translated to docbook if ppl need that to easily go to other formats. Don't know how the toolchain works - e.g. how chm's are integrated, pdf, etc.. >> 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. Yup. I have an email exchange with Brett re the incubator system, maybe we put that on the wiki (wiki.php.net ?) and see what ppl think. Till > > > Hope this clears up some of your questions, > > > Mike > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >

« previous php.pear.dev (#53589) next »