public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joshua D. Drake <[email protected]>
To: Dave Page <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: Mailing list lists
Date: Thu, 3 Apr 2008 08:37:30 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 3 Apr 2008 14:38:39 +0100
"Dave Page" <[email protected]> wrote:
> On Thu, Apr 3, 2008 at 2:28 PM, Joshua D. Drake
> <[email protected]> wrote:
> >
> > This is actually an open thread dave :P. I brought this up before
> > EAST.
>
> Oh, sorry - it's been a busy couple of weeks.
>
> > My thought was to modify the main .Org site to be the authoritative
> > reference and have the front page of archives point there.
> I'd prefer it to all be in a database, but I feel that unless the main
> index, list intro pages and subscription pages are all managed that
> way it'll just add complexity to no great benefit.
Well first let's clearly define the problems associated. I see a couple
of things:
1. The following two pages are always out of sync.
* http://www.postgresql.org/community/lists/
* http://archives.postgresql.org
2. The two pages listed above are managed separately in terms of the
content resource. Archives is a html where WWW is databased.
I have two solutions:
1. We figure out a way to make WWW the front end portal. We can
just use a redirect from archives if the url is / . There are benefits
to this:
* We have the subscribe form and other resources immediately available.
* community/lists is already just a link point to archives so we don't
need the archives front page.
* We have a central place to manage all lists without worry of being
out of sync
2. We leave things as is but change the method of keeping the two in
sync.
* Use a cron job on wwwmaster that will write out an xml file of
current lists at the same time the mirror script updates. That xml file
should be made available via rsync.
* Have archives pull the xml file every -n- minutes that file is then
parsed as part of the main index load on archives.postgresql.org
Thoughts?
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH9Pm7ATb/zqfZUUQRAtx9AJ9Zt1+9Di8x/+97dZXAfji0m+27ewCeK4Oe
RwbTMZn0/JenOeLog9zECZw=
=hwZ5
-----END PGP SIGNATURE-----
view thread (5+ messages)
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: Mailing list lists
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