-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 19 Mar 2008 11:13:27 -0700
Josh Berkus <josh@agliodbs.com> wrote:
> Josh,
>
> > Then let's make it a open, no subscribe list. It wouldn't behave any
> > differently than it does now but would allow us to service the
> > announcement review etc...
>
> Absolutely not. Requests made to press@ are often semi-confidential;
> companies don't want to share their requests about export
> certification with Google, and reporters *definitely* don't want to
> share their story ideas with their collegues!
Huh? Just make the archives private.
>
> I'm really confused on why you're trying to turn a confidential,
> quick-response alias into a public mailing list, when you'd just
> force us to create another alias.
>
I am confused why you are confused :P. You can make it an open list
that has closed archives. This protects confidentiality but allows all
communication on the list itself to be archived for further review by
the list members itself.
Further it solves the problem of who needs to be on the list to check
things. It seems that announcements would be best reviewed by those who
are going to be asked about those announcements, thus a press list.
I was trying to avoid being on yet another list. As I already receive
press@ it made sense to me.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL political pundit | Mocker of
Dolphins
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH4VrFATb/zqfZUUQRAk0iAJ97m3LO6RYw7ps0KSPekR8lCZJlfgCdFRd9
lM20B6XgI2ASsqN0/cZiNMI=
=1789
-----END PGP SIGNATURE-----
