public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: Josh Berkus <[email protected]>
Cc: Alexey Borzov <[email protected]>
Cc: Dave Page <[email protected]>
Cc: [email protected]
Subject: Re: Update on 'portal' changes
Date: 08 Mar 2004 18:16:48 -0500
Message-ID: <1078787808.2753.320.camel@camel> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Mon, 2004-03-08 at 12:45, Josh Berkus wrote:
> Alexey,
> 
> > OK, let's paraphrase: what is the reason for having one project for all 
> websites 
> > instead of one project per website? I got the impression that *different* 
> > developers work on different websites...
> 
> Well, GForge/GBorg is seperate.  Techdocs should be generated by Bricolage.  

speaking of do you have a status update on that?  a couple of weeks back
i mentioned doing an overhaul to the techdocs code in cvs and you said
not to bother since it was going away... well, it's still there, so can
I push forward with my cvs changes or are you pretty close to being
done?
 
> PGFoundation is apparently going to be seperate.  Advocacy should be going 
> away as soon as the foundation gets its act together.   

Actually Advocacy is waiting on the next generation portal stuff... not
the foundation stuff. 

General Bits is 
> hosted & adminned by Elein.   
> 

And it's a completely separate and independent site from the PostgreSQL
web teams sites... kind of like the plpgsql cookbook and oleg and
teodors fts search site. 

> What else is there?
> 

"developer" which many are hoping to fold back into the main site once
the next generation portal is done. 

not to mention "archives" and search.... both of which should probably
be put under cvs at some point...

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

view thread (28+ 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], [email protected], [email protected]
  Subject: Re: Update on 'portal' changes
  In-Reply-To: <1078787808.2753.320.camel@camel>

* 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