public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: [email protected]
To: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: [Kennisgres-pgdn] RE: Mailing list, Joint PostgreSQL Knowledge Base
Date: Sat, 3 Dec 2005 20:56:37 -0000
Message-ID: <[email protected]> (raw)


-----Original Message-----
From: "Josh Berkus"<[email protected]>
Sent: 03/12/05 20:15:02
To: "[email protected]"<[email protected]>
Cc: "Jim Nasby"<[email protected]>, "Gevik babakhani"<[email protected]>, "Dave Page"<[email protected]>, "Denis Lussier"<[email protected]>, "Scott Yara"<[email protected]>, "Marc Fournier"<[email protected]>, "[email protected]"<[email protected]>, "Andy Astor"<[email protected]>, "Stephen Slezak"<[email protected]>, "[email protected]"<[email protected]>, "Shahzad Khokhar"<[email protected]>
Subject: Re: [Kennisgres-pgdn] RE: Mailing list, Joint PostgreSQL Knowledge Base

> 1) Should be part of www.postgresql.org or be kb.postgresql.org.

Aside from being a dubious "business requirement" imho, I should remind you that a decision was made long ago by the community to merge all the postgresql.org subsites together, and not to create new ones. Reviewing and potentially overturning that decision is definitely not something for this forum.

Regards, Dave

-----Unmodified Original Message-----
So, can we start composing business requirements?

I can think of a few:

1) Should be part of www.postgresql.org or be kb.postgresql.org.
2) Should support full-text, category, date, and author searching.
3) Should publish credit for submitters and sponsors of articles.
4) Should manage bi-directional translation of articles.
5) Should be extremely easy to write & edit articles, requiring no 
knowledge of HTML or CVS or other command-line techniques.
6) Should support an approval process for both new articles and edits.

-- 
--Josh Berkus

Josh Berkus
PostgreSQL Project Core Team
www.postgresql.org

(all opinions expressed are my own; I do not speak
 for the Project unless specifically noted.)

view thread (4+ 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], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [Kennisgres-pgdn] RE: Mailing list, Joint PostgreSQL Knowledge Base
  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