Re: potential roadmap for pearweb
| From: | Pierre | Date: | Fri, 04 Nov 2005 16:04:14 +0000 |
| Subject: | Re: potential roadmap for pearweb | ||
| References: | 1 | Groups: | php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-4594@lists.php.net to get a copy of this message | ||
On Fri, 04 Nov 2005 00:37:16 -0600
cellog@php.net (Greg Beaver) wrote:
> Hi all,
>
> I think we could get things moving along in pearweb with a few focused
> changes to the existing codebase.
Besides keeping BC, we should not focus on the current code base :)
> I'd like to suggest this basic idea
> as a starting point:
>
> 1) remove the magic
> * add explicit includes to pear-prepend.php in all files that
> need it. After doing this, we will have a better sense of how
> things should work.
> * In addition, stuff that is specific to the
> manual should be handled with the peardoc build. The sidebar is
> (or should be) static HTML, and login is not needed.
Nearly nothing should be dynamic on pearweb. Only the
developers area and part of the server side of the installer
have to be dynamic (ie xml-rpc).
Reading the archives of this list will give you an idea :)
> In addition, we probably need to provide a testing mysql database that
> people can use to test pearweb remotely. Once we have this, it will
> be easy to make a PEAR-installable package of pearweb using some of
> the new package2.xml features. This, of course, could significantly
> reduce the barrier to entry for hacking on pearweb.
We do not have the resource on this server.
As I already said here, I already work on a new pearweb. With 4 main
goals in mind (with no particular order):
- specific and easier developer area (pear/pecl developer, helper, qa,
or doc)
- Public area mostly static, regenerate on demand (meaning a page will
not be regenerate if there is no need to)
- the manual is pure html and updated more than once a week (external
resource is used to transform to html and upload the result to the
pear host)
- Fully unit tested (this is the hard part, but we should care really
only about rest and xmprpc)
I hope we will be ready to switch before the end of this year.
I'm getting close to be able to publish the code and put some demo
online, it will be published middle november - end of december (if no
problem will use my precious free time...).
Regards,
--Pierre