public inbox for [email protected]  
help / color / mirror / Atom feed
From: Guido Barosio <[email protected]>
To: Simon Riggs <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: [email protected]
Subject: Re: replace training blurb with upcoming pug meetings?
Date: Wed, 28 May 2008 19:15:25 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<1211997489.5508.39.camel@jd-laptop>
	<[email protected]>

"Shortcuts": seems nasty there, and IMHO too big for a shortcut list.
I am sure that we can find a better place for it!
"Support us": How much support do we receive via this link? :s

Between both *dialogs* we can create a new place for upcoming pugs, though.

gb.-

On Wed, May 28, 2008 at 7:11 PM, Simon Riggs <[email protected]> wrote:
>
> On Wed, 2008-05-28 at 10:58 -0700, Joshua D. Drake wrote:
>>
>> On Wed, 2008-05-28 at 19:47 +0200, Magnus Hagander wrote:
>> > Robert Treat wrote:
>> > > In an effort to give more visibility to the pugs, one idea that was
>> > > floated around was replacing the training blurb on the main site with
>> > > an "upcoming pugs" section, modeled after the upcoming events.  The
>> > > training blurb would then be changed to a direct link saying "looking
>> > > for training?" (or similar) which would take you to the full training
>> > > page.  There are some logistical issues that would need to be worked
>> > > out to make this happen, but before we go down that path, I wanted to
>> > > get a general consensus on the idea. thoughts?
>> >
>> > Any way we can have both? I agree it's a good idea to get upcoming
>> > pugs, but I'd like to keep the training info somehow.
>>
>> I think it is a matter of deciding the purpose of the space. IMO .Org
>> should be all about community, not all about advertising for commercial
>> providers. That isn't to say we shouldn't help the people who help us
>> (obviously) but it is to say that a PUG should come before CMD, EDB or
>> any other commercial entity listed.
>>
>> That being said, we have a problem in that the front page is remarkably
>> cluttered. It is trying to tell people entirely too much all at once.
>> Something has to give if we are going to add PUGS. Training or Latest
>> News seems the most appropriate.
>
> Yes, it is cluttered, so I think we should scroll down the page and make
> more space for ourselves.
>
> The community includes commercial people too. And the commercial people
> only exist because they are wanted and needed.
>
> The suggestion to have a list of PUGs over training could go the other
> way too. We could say "Want a PUG?". If they do, they'll click. That is
> of course fairly silly, but then so is "Want training?", which hides
> anything interesting and unusual and effectively kills it. If we do that
> I may as well pack up and just offer one course called "Training".
>
> People want a way to scan all things that might be of interest, not one
> category or another. Yes, we need a way to expand the PUGs.
>
> --
>  Simon Riggs           www.2ndQuadrant.com
>  PostgreSQL Training, Services and Support
>
>
> --
> Sent via pgsql-www mailing list ([email protected])
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-www
>



-- 
Guido Barosio
-----------------------
http://www.globant.com
[email protected]



view thread (29+ 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]
  Subject: Re: replace training blurb with upcoming pug meetings?
  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