Re: [PHP-DOC] Re: [PECL-CVS] svn: /pecl/

Just a PEAR-nut perspective here, because we deal with this exact issue.

2010/8/6 Philip Olson <[email protected]>:
> Also, I think it's far worse to scatter documentation all over the Internet which is something PEAR is suffering from today.

We also suffer from scattered source code —
http://pear.php.net/bugs/bug.php?id=17646

I can think of a few instances where I've had to go to the
waybackmachine to grab external docs, or dump the last release .tgz
into cvs/svn.php.net because the external source was gone. This is a
major issue we deal with frequently, especially with the size and age
of PEAR.

I would say, as long as the source, including docs, are maintained on
a reputable, publicly available (d)vcs which the QA team has access
to, there shouldn't major issues that can't be overcome — and github
really makes this easy.

I think the others that have spoken up have a good perspective on
this. Improving the integration and flexibility of the PECL/bugtracker
systems so they can integrate with reputable external development
methods is a good thing. And as Philip stated - "The VCS landscape has
changed, so let's accept it."

-- 
Brett Bieber