public inbox for [email protected]  

help / color / mirror / Atom feed

From: Josh Berkus <[email protected]>
To: [email protected]
Subject: Re: EnterpriseDB Postgres
Date: Wed, 8 Aug 2007 22:08:08 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

All,

> > If people want to make 'no self approval of your or your companies
> > items' a new moderation rule, I have no problem with that.
>
> Good idea.  We have enough people and enough diversity that making
> this explicit in the moderation rules is reasonable. :)

I don't have a problem with that.  Actually I usually try to get someone from 
-WWW to approve anything I post, including stuff for the Project.  Otherwise 
I never know what stupid cut-and-paste errors I might miss.

I'll point out though that our policy on News/Events/Training postings has 
always been one of permissiveness.  For example, there has been an ongoing 
one-upsmanship in the Training postings for the last 6 months and WWW has 
refused to get involved in constraining it.  If we started deciding that we'd 
block certain kinds of news posts (like those with too much hyperbole) then 
that would be a major change of direction for our website approval policy.  
It would also make it highly politicized.

> Speaking of which, I'd love to figure out a system whereby I can
> avoid (the appearance of) similar conflicts of interest in the
> PostgreSQL Weekly News, as I have been in a position to announce
> things I've done, are doing, etc., and have never felt comfortable
> about it.  I guess that's a subject for another thread, though.

I haven't seen a problem except that I'm not keen on your reporting on 
flamewars, even resolved ones.  But that's an editorial decision that you and 
I will continue to disagree on.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco

view thread (80+ 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]
  Subject: Re: EnterpriseDB Postgres
  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