MIME-Version: 1.0
In-Reply-To: <50F09E23.90802@agliodbs.com>
References: <50EEA591.3030905@dalibo.info>
	<CAJKUy5jmrAZce3YRDY5HU3JHX=BEveTCt=rN6Ah2nvbLbXb-eA@mail.gmail.com>
	<50EF4E25.2030509@2ndQuadrant.it> <50EFDDBB.6080109@dalibo.info>
	<CABUevEwgtQ4+Mn2WK=QayGEQ630aWG2sGxKFtyX=HELUTo_=FA@mail.gmail.com>
	<50F09E23.90802@agliodbs.com>
Date: Sat, 12 Jan 2013 11:06:37 +0100
Message-ID: 
 <CABUevEz4g7V=b1Yb2W-_7z=xPFUxyutxFw40SP9E9Q10EU6ZAQ@mail.gmail.com>
Subject: Re: Training approval policy on pg.org
From: Magnus Hagander <magnus@hagander.net>
To: Josh Berkus <josh@agliodbs.com>
Cc: PostgreSQL WWW <pgsql-www@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Sat, Jan 12, 2013 at 12:20 AM, Josh Berkus <josh@agliodbs.com> wrote:
> Folks,
>
> If we're going to allow a much higher volume of training events,
> training needs both its own RSS feed and its own admin interface.
> Training already outnumbers public events by 4 to 1 and makes our events
> RSS feed pretty useless for anyone who's not looking for training.

I already told you earlier in this thread that training events aren't
*in* the RSS feed. There is nothing to remove.


> And the admin/moderation is a PITA.

The event moderation already has the ability to filter by training
events, though it's not filtered in the default view. And the ability
to do bulk approval, should it be needed.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www