Overblogging etc - Mailing list pgsql-www

I think its time we put some restrictions on what gets put on the front
page of the web site in blogs as well as other things. Since I don't
have a blog currently, it makes me slightly more objective in this.

Blogs

I suggest we allow 1 blog per week per person and that the blogs must be
about something constructive, not just a one liner about getting out of
the bath or other trivial subjects. Since we have only a few blog slots
it's a shame when long useful blogs are replaced by trivial ones.

In particular, Devrim's important info about a PostgreSQL RPM repository
has been pushed off by 4 blogs from another community member.

I don't think we will be able to agree what constitutes trivial, but
single sentence blogs should be banned. I wouldn't have a problem with
the same subject expanded into a useful multi-paragraph blog, but single
sentences give the appearance of triviality. If we don't set a minimum
standard for blog content, people will stop reading them *all*.

Events

ISTM that the criteria for inclusion on the Events page must be that it
is publicly accessible and that anyone can attend, upon payment of any
fee. I think that probably *is* the case with every event listed, but
that should be the clear criteria: no private events and the event
message should clearly express that.


We should also have a Listings Policy that is available on the website,
plus a link and reminder "Does this submission follow the listings
policy?" on the event submission screens.

Short note to Dave: the code for displaying two company names who are
advertising training doesn't exclude duplicates, so you get occasional
strange looking sentences mentioning the same company twice.

Perhaps the web page should also continue to scroll down the page, so
that attempts by people to push information down aren't really feasible
any longer.

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com