Thread: Creating a list of Press Contacts and similar
Hi Josh, From a previous email you sent though (in regards to the Press Release): "Finally, we need a list of press contacts, with e-mail, phone, and snail-mail addresses -- preferably one on each continent. And we shouldn't link to the main postgreSQL site, with is *not* set up for Press access." Totally agree with these points. The main PostgreSQL site isn't ready yet, and Dave Page doesn't appear to have had time to finish off the next generation one yet. Do you feel it's worthwhile adding a non-public form on the Advocacy website so that we can all add contacts as we feel are appropriate? An additional thought to that, is whether it would be worthwhile adding a simple email address "subscribe" field to the Advocacy site so people who are interested in keeping up with the releases of PostgreSQL can do so through it. :-) Regards and best wishes, Justin Clift -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
Justin,
> "Finally, we need a list of press contacts, with e-mail, phone, and
> snail-mail addresses -- preferably one on each continent. And we
> shouldn't link to the main postgreSQL site, with is *not* set up for
> Press access."
>
> Totally agree with these points. The main PostgreSQL site isn't ready
> yet, and Dave Page doesn't appear to have had time to finish off the
> next generation one yet.
>
> Do you feel it's worthwhile adding a non-public form on the Advocacy
> website so that we can all add contacts as we feel are appropriate?
It's a bit to bite off and chew, but we could team up with OpenOffice.org on
this. Scott and I wrote half a program in PHP/MySQL that manages a large,
multilingual press contacts list, and does "mail blasts: It needs
finishing, though ... there's currently no UI and it needs to be ported to
Postgres so that some of the program can be built into views and functions.
That may be too much to do in time for 7.3, though.
> An additional thought to that, is whether it would be worthwhile adding
> a simple email address "subscribe" field to the Advocacy site so people
> who are interested in keeping up with the releases of PostgreSQL can do
> so through it.
That would be easy and great. We'd need to check the submissions, though, to
avoid duplication. So instead of just "e-mail address", let;s ask for:
Name:
Organization:
E-mail Address:
Preferred Langauge:
Phone (optional):
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Josh Berkus wrote: <snip> > It's a bit to bite off and chew, but we could team up with OpenOffice.org on > this. Scott and I wrote half a program in PHP/MySQL that manages a large, > multilingual press contacts list, and does "mail blasts: It needs > finishing, though ... there's currently no UI and it needs to be ported to > Postgres so that some of the program can be built into views and functions. Wouldn't hurt to give it a shot I reckon. :) When you say "no UI" though, what *is* there? > That may be too much to do in time for 7.3, though. > > > An additional thought to that, is whether it would be worthwhile adding > > a simple email address "subscribe" field to the Advocacy site so people > > who are interested in keeping up with the releases of PostgreSQL can do > > so through it. > > That would be easy and great. We'd need to check the submissions, though, to > avoid duplication. So instead of just "e-mail address", let;s ask for: > > Name: > Organization: > E-mail Address: > Preferred Langauge: > Phone (optional): To keep it simple, we should probably have a field for the email address on the front page, and probably their preferred language, then when they submit that it stores it that in the database (checking for duplicate emails) and gives them the further option to fill out the rest of the forms. Two stage approach but it would mean minimal effort is needed to sign up but they still have the option to take a bit more time and effort to give better detail. What do you reckon? :) Regards and best wishes, Justin Clift > -- > -Josh Berkus > > ______AGLIO DATABASE SOLUTIONS___________________________ > Josh Berkus > Complete information technology josh@agliodbs.com > and data management solutions (415) 565-7293 > for law firms, small businesses fax 621-2533 > and non-profit organizations. San Francisco -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
Justin,
> To keep it simple, we should probably have a field for the email address
> on the front page, and probably their preferred language, then when they
> submit that it stores it that in the database (checking for duplicate
> emails) and gives them the further option to fill out the rest of the
> forms. Two stage approach but it would mean minimal effort is needed to
> sign up but they still have the option to take a bit more time and
> effort to give better detail.
>
> What do you reckon?
My concern is, without a name & organization, we may end up harvesting them,
under a different e-mail address, somewhere else, and sending them duplicate
e-mails. Or sending their agency duplicate e-mails; news services tend to
take a dim view of sending e-mails to every one of their reporters, even when
it's not your fault.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Josh Berkus wrote: > > Justin, > > > To keep it simple, we should probably have a field for the email address > > on the front page, and probably their preferred language, then when they > > submit that it stores it that in the database (checking for duplicate > > emails) and gives them the further option to fill out the rest of the > > forms. Two stage approach but it would mean minimal effort is needed to > > sign up but they still have the option to take a bit more time and > > effort to give better detail. > > > > What do you reckon? > > My concern is, without a name & organization, we may end up harvesting them, > under a different e-mail address, somewhere else, and sending them duplicate > e-mails. Or sending their agency duplicate e-mails; news services tend to > take a dim view of sending e-mails to every one of their reporters, even when > it's not your fault. Sounds like we need a manual verification or similar prior to email sendout when we notice people with the same domain name (i.e. @cnet.com) subscribed through it? Something that groups the emails with the same domain name then lets the admin approve/reject some or similar. ? Regards and best wishes, Justin Clift > -- > -Josh Berkus > > ______AGLIO DATABASE SOLUTIONS___________________________ > Josh Berkus > Complete information technology josh@agliodbs.com > and data management solutions (415) 565-7293 > for law firms, small businesses fax 621-2533 > and non-profit organizations. San Francisco -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi