public inbox for [email protected]  

help / color / mirror / Atom feed

From: Josh Berkus <[email protected]>
To: [email protected]
Cc: Dave Page <[email protected]>
Subject: Re: Integration Requirements
Date: Tue, 6 Dec 2005 09:24:35 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4850808@ratbert.vale-housing.co.uk>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4850808@ratbert.vale-housing.co.uk>

Dave,

The below go far beyond "integration requirements" and stray into the area of 
dictating exactly how new web code should be built.  If you do that, you 
won't get any contributors.  Would you write WWW code on your own time if 
someone told you exactly what programming structures to use?

Integration requirements would be something like:
-- Needs to be able to run on FreeBSD
-- Must use the postgresql.org CSS, which is documented in __________ (note 
Magnus' comment on the lack of CSS documentation).
-- Can't have processor/ram requirements beyond ______________ unless a server 
is going to be donated,
-- Must be in one of the following programming languages: PHP, Perl, Ruby ... 
if in something other than PHP or Perl must be part of a long-term commitment 
for code maintenance.
etc.

> - 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.

This isn't really practical for a KB or many other components, which need to 
be highly dynamic, not a bunch of static pages.

> - Navigation; Gevik was working on a tree-style thingy in PHP. Perhaps the
> CMS could export an XML file describing the navigation tree, which the PHP
> handler on the main website could use to generate it's treeview in dynamic
> mode. By accepting some sort of pointer to the currently selected node as a
> GET value, we should be able to make the tree fully mirrorable.

This is functional specification based on a lot of assumptions about the shape 
of the final interface, and I can't imagine it even being applicable to 
something I, personally, would build.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Integration Requirements
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox