I just realized I never replied to this mail, sorry guys (especially Brett, I know promised to reply long time ago)!
-Hannes On Mon, Oct 20, 2008 at 15:25, Brett Bieber <[EMAIL PROTECTED]> wrote: > On Mon, Oct 20, 2008 at 8:52 AM, Hannes Magnusson > <[EMAIL PROTECTED]> wrote: >> Hi PEAR-group! >> >> I've been wondering whom we (phpdoc) need to bribe to get our PEAR >> channel (doc.php.net) available by default? >> >> As I see it the PEAR installer currently as 2 available-by-default channels: >> - pear.php.net (for reusable PHP classes) >> - pecl.php.net (for PHP extensions) >> >> Both of which are obviously php.net projects. >> >> I'd like to get doc.php.net listed by default for "documentation >> stuff" which includes >> - The rendering system (PhD) >> - `pear install`able docs (see http://news.php.net/php.doc/969379502) > > I think this is a good idea - and shouldn't be any problem given the > close relationship we have with you guys. But, I do believe we should > consider some things before adding a default channel. Right now, every > package installable from the default channels would have been approved > by pear/pecl lead developers directly or by proxy which alleviates > some of the security considerations, and pear/pecl has bug reporting > mechanisms so problems can be reported and handled by leads within > either pear or pecl - not just the developers of a single channel. PhD has its own category in the bugs.php.net bug tracker, called "Doc Build (PhD) Problem". > Some of the concerns I have are: > * We ensure that some review process is in order, and users aren't > avoiding the existing review process (pepr, etc). Good point. I here by promise to grant "release karma" only to people I trust 100%, and in case any of them fuck up I gladly take full responsibility to their screw ups. The only point with the channel is to distribute documentation related things such as build system, pre-rendered documentations and those alike. In the future I would love to make it possible to "pear install doc.php.net/mdb2-docs" and things like that. > * Security is taken into consideration. We currently run "Chiara_PEAR_Server" (probably outdated version though). I have *no idea* whats the best practice running a channel so I am totally open for ideas. No offence to the developers, but I hate that Chiara channel. I would love to run something else if you have any ideas. > * Distribution within the existing channels are considered first - and > the mission of each channel does not overlap. Like stated above, doc.php.net solo purpose is to distribute docs and related tools. I/we have no intentions to distribute anything else. > * End users have a formal bug reporting mechanism. Like said above; http://bugs.php.net/report.php "Doc Build (PhD) Problem". Is it possible to make that information available to the channel? I.e. is there some "meta information" which we can mention such things? (If not, I'll make a feature request for it :)) > I think channels on .php.net should already meet most of these > concerns, as long as the system is under the control of php systems > group. I'm not entirely sure what you mean by "php systems group" as systems@ is relativity in-active these days (sorry systems@ guys, but its true). I really hope however that .php.net boxes should not be something to be afraid of cause if it is we have much bigger problem then having pear channels enabled by default. > If each of these are handled, or the PEAR group is fine with allowing > some exceptions, I'm fine with adding it. I appreciate your questions/points! Shows you take your group membership seriously :) >> In the future PhD will be chunked down into smaller packages (core, >> formats and themes). Furthermore we would like to offer more `pear >> install`able manual packages, and at some point even distribute the >> actual DocBook XML sources via the channel... lots of ideas floating >> around :) > > You guys are doing excellent work... and I'm very happy that you're > using pear's installer as your distribution mechanism. Right-back-at-ya! To be honest, we didn't even consider another distribution system, the pear installer is the de-facto way of installing PHP applications IMO! -Hannes
