> > 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
--
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www
No comments:
Post a Comment