Re: suggestion
| From: | Sterling Hughes | Date: | Thu, 18 Jan 2001 22:49:51 +0000 |
| Subject: | Re: suggestion | ||
| Groups: | php.pear | ||
| Request: | Send a blank email to php-pear+get-1019@lists.php.net to get a copy of this message | ||
> hi all,
>
> Given that php.pear.net is in need of some tools, and given also that I'm
> going to start building binarycloud.com soon, I'd like to suggest
something:
>
> -Use binarycloud to build pear.php.net
> -Create a couple applications that _both_ projects will need, in
> such a way that both binarycloud.com and pear.php.net can make use of
them.
> (a bug tracker, file repository, search tools, etc)
>
> on pear, the file tracker would be used for libraries - on binarycloud.com
> it would be used for applications.
>
> Using binarycloud to support the build process for php.pear.net will
> certainly speed it up a _great_deal_, which will allow more authors to
start
> contributing to PEAR.
>
> It will also give people a chance to get familiar with the binarycloud
> codeset, and from that we can see how best to merge the error handling and
> database abstraction layers.
>
> I'm _very_ excited to see the number of standard, well documented
libraries
> in PEAR grow. I'm just as excited to see the number of applications that
use
> binarycloud grow :) !
>
The problem really with getting the pear web site out is that I think it
should have a strong integration with the new php web site. meaning, it
should tap into the user authentication (if there is any), tracking, design,
etc. ie, it should be an integrated component of the new php website (i
don't currently know what the status of the new site is). As far as
pear.php.net, there is already a database scheme layed out, as well as the
format for the pear documentation (and I have a temporary XSL stylesheet
lying around somewhere, which can change the XML into HTML quite nicely)...
What is really need for the pear website is db abstraction, for which, pear
has a strong DB layer, which supports (the database of choice :) MySQL, the
only other logic it needs to use (besides what's distributed with PHP
itself) is a templating engine, I've already got a basic one I've been
messing around with (akin to EasyTemplate), I haven't yet got a chance to
look at IntegratedTemplate yet (in the pear distribution)...
-Sterling