public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: [email protected]
To: [email protected]
Cc: Joshua D. Drake <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Cc: Magnus Hagander <[email protected]>
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
Date: Thu, 12 Jun 2008 21:28:19 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
On Thursday 12 June 2008 17:46:38 Josh Berkus wrote:
> > As I see it, promoting core information should be our largest priority,
> > which would include the top two items.
> >
> > our next priority should be promoting postgresql to the general
> > populations, which would include large event and pug informations.
> >
> > after that we have service level information, which is projects,
> > products, and training.
> >
> > now, I left out blogs because they are kind of across the map as far as
> > content, but based on popularity of them, they should probably be held
> > high on the list, I'd say somewhere below large event information but
> > above pugs.
>
> Hmmm. I'd put blogs lower on the list just because their content is less
> vetted.
>
right, but based on the stats, it's one of the things that draws a lot of
visitors, so I think that counts for something.
> > looking that list over, istm just aggregating pgfoundry and our current
> > news feed is the way to go, but there are still a number of areas that
> > should be addressed, imho.
>
> Which areas?
More focus on core announcements / events, regular pug promotion, highlighting
large community events, and sorting out training (which most seem to agree is
sub-optimal)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
view thread (19+ messages)
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]
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
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