Re: pear weekly news

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.. The database could hold the 'live' version eg. the published one, which reads from cvs at publish time.. - where you can fill in any addition data 'like author'... This way the publish step could also be used to build a cached live version of the page - served static rather than pull the list of packages every time from the database. RSS/Index/Archives can the focus on using the database table.. maybe even take the 'report' and replace it with filename??? I guess a 'summary' for RSS would probably be neccesary.. 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 regards alan Martin Jansen wrote:

On Sat Jul 06, 2002 at 10:1813AM +0200, Martin Jansen wrote:

On Fri Jul 05, 2002 at 03:1832PM +0200, Tomas V.V.Cox wrote:

The solution is simple: if someone wants to take care on developing a reduced news manager go for it, if not, use a static template included from a PHP.

I can do such a thingie.

To start a first discussion on how the dynamic solution for the weekly news might look like, here is a suggestion for the table layout: CREATE TABLE weeklynews ( id int(10) unsigned NOT NULL default '0', year year(4) NOT NULL default '0000', week tinyint(4) NOT NULL default '0', report text NOT NULL, language char(2) NOT NULL default '', author int(11) NOT NULL default '0', PRIMARY KEY (id), UNIQUE KEY week (week), FULLTEXT KEY report (report) ); Most things should be obvious here. The column "author" keeps a foreign key to the table "users". Language is "en", "fr", "de" and so on. Comments? Alan? - Martin