public inbox for [email protected]  
help / color / mirror / Atom feed
From: Josh Berkus <[email protected]>
To: Dave Page <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: [email protected]
Subject: Re: Approval process for news/events/training is broken
Date: Mon, 15 Oct 2007 08:44:40 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Dave,

>> 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"?
> 
> It's certainly not commercial, but yes that does seem worth clarifying.

Actually, I'd argue that it's commercial.  That was what I had in mind 
when I drafted the rules.  For one thing, like the tools SW makers, EDB 
tends to bury us under press releases and need reigning in, in a way 
that OSS projects generally don't.

> It's a bit subjective. I'd be happy with any level of content from a
> single session up, as long as it includes details so people don't spend
> serious money getting somewhere only to find just a single session.

Well, we need to draw some line for PostgreSQL content.  A 200-session 
conference with one session which covers using PHP with PostgreSQL 
alongside MySQL and DB2 really shouldn't go on the site.  Maybe we 
should just re-write that as "significant PostgreSQL content" and leave 
it up to WWW what "significant" is?

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

Sure.  Mind you, they usually do.   We haven't had a problem with 
trainers not providing enough content, just posting too frequently.

BTW, have we fixed the training events so that they stop displaying once 
they start?

--Josh




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