From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200512040124.jB41OIQ15877@candle.pha.pa.us>
Subject: Re: Integration Requirements WAS: Launching PostgreSQL KB
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE92E8D8@algol.sollentuna.se>
To: Magnus Hagander <mha@sollentuna.net>
Date: Sat, 3 Dec 2005 20:24:18 -0500 (EST)
CC: josh@agliodbs.com, pgsql-www@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII


The only comment I have is that I hope those who want a knowledge base
realize it is a huge job, and requires people with technical knowledge.

---------------------------------------------------------------------------

Magnus Hagander wrote:
> > While we discuss on the *other list* the business 
> > requirements for a Postgres KB, it would be really helpful to 
> > get together on *this* list a document giving the 
> > requirements for projects to be incorporated into the 
> > PostgreSQL.org web infrastructure.  Such a document would be 
> > very helpful, as well, to others wanting to add things to the 
> > web site.
> 
> Josh, you are doing this backwards. You said it yourself in another
> mail, start with the *functinoal requirements*.
> 
> At this point, the integration requirements should be "work directly in
> the current website without any other product". If this cannot be done,
> then we need to look at other products. But we cannot answer this
> question until we have the functional specification.
> 
> My suggestion therefor - write a functional specification *completely
> without considering what technical issues might show up with either
> one*, and then we take it from there. And consider doing this on a more
> "diplomatic" place than a technical mailinglist for a different project.
> 
> 
> One quick comment on Daves mail:
> > - Moving data; originally we'd looked at exporting from the 
> > cms into the filesystem, and having script that did a cvs 
> > add/remove/commit over the entire tree, into the main web 
> > CVS. This is still preferrable from an 'ease of rebuilding' 
> > point of view, but might be easier just to rsync the content 
> > from the filesystem of the cms machine to wwwmaster.
> 
> I think long-term, just dumping the files over is not a managable idea
> unless we have corporate committment for maintaining the backend.
> Because sure, the website will work, but if the backend goes down nobody
> will be able to use any of these uber-cool KB functions that's the whole
> reason it exists. It's more like a stop-gap solution.
> 
> (Bottom line, of course, I still think this should be *actually
> integrated* in the main website, and not just copied over from somewhere
> else. If possible. Again, see above point, it's way to early to actually
> comment on that now if the project is run that way.)
> 
> 
> //Magnus
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073