Re: Updated SummerofCode.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 20 Mar 2008 22:35:07 +0100
Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> > Yes in fact it does.
>
> But the emails notifying people of new tickets is still on the same
> listserver, no?

I have to check but... I think all of this is moot now that I think
about it. First to be fair to Marc, I can remember the last time
anything took 3 days to fix. Secondly, if it is taking 3 days the whole
world is screaming and we have more important and potentially dangerous
things going on that are not a web site update.

IMO this is very simple:

* Unless you are a committer you must submit via -www, all committers
must honor this. (don't accept a patch privately) So we don't have these
communication issues in the future.

* If there is a problem where email is not coming through, start
talking to people. The primary sysadmins are on jabber.postgresql.org,
several can be found on #postgresql at any given time in the day, we
have phone numbers on pmt.postgresql.org, there is
sysadmins(at)postgresql(dot)org and if it comes down to it, just start
emailing directly that there appears to be a clog up somewhere.

This idea that somehow we would just wait 36 hours for someone to
notice is kind of silly. There are those of us who live on these lists.
We notice the moment something bogs down.

Sincerely,

Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH4tuuATb/zqfZUUQRAsxcAJ9qDKuZFnZEqyqOEQ3/jQJHqopWswCgmm0R
JHMF+cgNDzNC3rhGO+NnEaI=
=4GT5
-----END PGP SIGNATURE-----