public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Dave Page <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Approval process for news/events/training is broken
Date: Mon, 15 Oct 2007 10:19:27 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Mon, Oct 15, 2007 at 08:51:38AM +0100, Dave Page wrote:
> Josh Berkus wrote:
> > Dave, all:
> > 
> >>> http://developer.postgresql.org/index.php/NewsEventsApproval
> >> Looks very good to me.
> > 
> > No objections or modifications?  Can we make the document canonical and link 
> > the criteria from the Submit page, then?
> 
> No, I'm fine with it. We should format it up as part of the main site
> rather than linking to the wiki.

One clearification - does "Postgresql family news" include all pgfoundry
projects, or just "major" ones? If second, how do we define which are
major?

Also, looking back at the news just added today, is "EnterpriseDB Postgres"
considered a "postgresql family product" or a commercial one? Maybe a
guidance bullet on "downstream distributions"?


As for events, I'm not sure I agree with the very last point, about
"conferences with little pg content". I think that depends a lot - in some
areas, having a single postgresql session *is* a major event. It no longer
is in the US for example, but in a lot of other places it is.


Training events - should we require that they include information about the
cost to attend?


(and +42 on making it a real webpage, since we need something that's very
stable if we point our visitors to it)


> > If we're going to restrict what we accept, we should let submitters know the 
> > rules.
> 
> Yep.

Absolutely

//Magnus

view thread (31+ 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]
  Subject: Re: Approval process for news/events/training is broken
  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