Re: pear weekly news
| From: | Martin Jansen | Date: | Sat, 06 Jul 2002 11:57:03 +0000 |
| Subject: | Re: pear weekly news | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-7509@lists.php.net to get a copy of this message | ||
On Sam Jul 06, 2002 at 06:0345 +0800, Alan Knowles wrote:
> Sounds ok, revision/rollback would be nice - we used to do it by writing
> to RCS on each update.. - but the interface got very compilcated...
>
> I would suggest that a hybrid solution be used..
>
> - publishing and writing to CVS in the form of a simple html page is
> extremely easy to do (well for me anyway)..
> - After many years of dealing with posting/publishing to databases via
> web (cheesy html forms etc) or even phpmole, None of them really beats
> CVS for the staging stuff..
Do you really think that we need rollback and the like?
> I guess a 'summary' for RSS would probably be neccesary..
We can either have a own field for summary or we use the first n
characters of the report for the RSS description.
> Title: PEAR Weekly Summary for week ending 30 July
> Summary: 3 Stable Releases, 2 Beta Releases, User Autentication, Pear
> Packages,Caching on XML RPC....
>
> the latter could be preg'd from the <h3> tags..
>
> I got the preview stuff working here.. -
> http://pear.php.net/weeklynews.php/en/20020707.html
Making the report static starts to sounds reasonable for me. But
actually I'm a bit afraid that the markup may look inconsistent: Imagine
you are on vacation and someone else writes weekly summaries: He will
perhaps use another editor or prefer another markup. This will cause
some problems because the page will look different than usually, which
isn't a good thing IMO. How do you want to prevent that? (Well, you
could actually stop going on vacation ;-).
- Martin
--
Martin Jansen - mail@martin-jansen.de
http://martinjansen.com/