Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 53C5C9FB2F4 for ; Mon, 5 Feb 2007 16:24:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 00613-07 for ; Mon, 5 Feb 2007 16:24:17 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 151029FB2C9 for ; Mon, 5 Feb 2007 16:24:20 -0400 (AST) Received: from [192.168.199.197] (c213-100-160-41.swipnet.se [213.100.160.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by svr2.hagander.net (Postfix) with ESMTP id 043E9DCC158; Mon, 5 Feb 2007 21:24:18 +0100 (CET) Message-ID: <45C79275.3080109@hagander.net> Date: Mon, 05 Feb 2007 21:24:21 +0100 From: Magnus Hagander User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: josh@agliodbs.com CC: pgsql-www@postgresql.org Subject: Re: Request from training vendor re: home page References: <200702051225.25922.josh@agliodbs.com> In-Reply-To: <200702051225.25922.josh@agliodbs.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/36 X-Sequence-Number: 11441 Josh Berkus wrote: > WWW, > > You may or may not have noticed that we're getting a bit of jockeying for > home page spots among our training vendors. It's obviously not in our > interest to have different vendors manipulating the details of their > events announcements, or even posting duplicates, in order to "control" > what appears on the home page. One of the vendors involved had this > suggestion: > >> Just a thought...I notice that now "training" is split out separately on >> the PostgreSQL.org web site...which is great in the sense that >> non-training events don't get pushed off the front page by training >> events (or event spam...). >> >> I'm wondering if its possible to "somewhat equalize" things by >> preventing a single vendor event from appearing more than once on the >> front page. The idea being that training vendors (which are generally >> for-profit) would get equal opportunity for that ever-important >> front-page exposure... > > Seems like a decent idea; does it make sense to other people? How would we > enforce it? > Well, they're ordered by date. So if two vendors have a similar number of offerings, they should show up the same amount of time. As for duplicates, the person approving the event is *supposed* to look for that. Now, I realise we're all probably guilty of not always doing that, but... Not sure how we'd filter it otherwise, but I'm open for ideas :-) //Magnus