public inbox for [email protected]  

help / color / mirror / Atom feed

From: Chander Ganesan <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Kris Jurka <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Kevin Hunter <[email protected]>
Cc: Postgres WWW List <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Josh Berkus <[email protected]>
Subject: Re: Training events policy ... first test case
Date: Wed, 07 Nov 2007 20:52:24 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <20071104123014.21e2e19d@scratch>
References: <200711041951040000@204315953>
	<20071104123014.21e2e19d@scratch>

Joshua D. Drake wrote:
>>> Your suggestion implies that instead of doing this publicly a www
>>> team cabal should decide this in some back room and not inform
>>> anyone of it.
>>>
>>>       
>> You have some proof they're doing anything inappropriate? Confident a
>> judge would accept it if they sued for damage to their reputation and
>> loss of potential business by allegations made in a public forum?
>>
>>     
>
> Well let's start at the top. Has *anyone* bothered to contact the party
> and just talk to them? See what is going on? A lot of this seems it may
> be circumspect.
>   
Any progress on this?  How about a policy with regard to event posting?  
I think at the very least something should be done about events that 
appear to be overzealous in nature (to say the very least). 

Berkus original post in this thread was with regard to preventing the 
"flooding" of training listings.  While we've addressed a "front page" 
issue, with regard to jockeying for position...I don't think anything 
has been done to address the flooding issue.

-- 
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560
Phone: 877-258-8987/919-463-0999
http://www.otg-nc.com

view thread (76+ 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]
  Subject: Re: Training events policy ... first test case
  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