public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Dave Page <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: [email protected]
Cc: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: [pgsql-advocacy] We need an Advocacy wiki
Date: Sat, 04 Aug 2007 17:24:39 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Dave Page wrote:
>>> and I am reluctant to go that route anyway for public-facing pages
>>> that represent the project via a
>>> postgresql.org address.
> 
> I don't see any need to have any public facing pages on a Wiki - are we
> too lazy to write things up for the website when we want to present them
> to the world? It's not like it's difficult to do.
> 
> For collaboration work however, the Wiki is important I think - but I
> agree with Greg, we shouldn't need a second one. Can't we have an area
> on the current one with looser permissions?

Agreed. The whole idea behind a wiki is "reasonably loose permissions",
right? AS Greg already suggested, perhaps we just need a "better way"
for people to request permissions? (For example, right now it just says
"contact greg or neil", but it doesn't tell you how - not even an email
address...)

And a structure of the wiki that has a section for advocacy of course -
but we already have that.

/Magnus

view thread (74+ 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]
  Subject: Re: [pgsql-advocacy] We need an Advocacy wiki
  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