FOSS4G 2009 Press Release Process - Revision history

Wiki-Camerons: /* Release date */

2010-01-25T19:42:48Z

Release date

Wiki-Camerons: /* Day or 2 after release */

2009-07-17T19:16:50Z

Day or 2 after release

Wiki-Camerons: /* Day or 2 after release */

2009-07-17T19:16:13Z

Day or 2 after release

Wiki-Camerons: /* Day or 2 after release */

2009-07-17T19:13:37Z

Day or 2 after release

Wiki-Camerons: /* Day or 2 after release */

2009-07-17T08:55:12Z

Day or 2 after release

Wiki-Camerons: /* One day before the release */

2009-07-16T22:41:36Z

One day before the release

Wiki-Camerons: /* Day or 2 after release */

2009-07-16T22:33:59Z

Day or 2 after release

Wiki-Camerons: /* Release date */

2009-07-16T22:29:23Z

Release date

Tmitchell: /* Day or 2 after release */

2009-07-16T17:33:47Z

Day or 2 after release

Wiki-Camerons at 09:05, 16 July 2009

2009-07-16T09:05:30Z

@@ Line 35: / Line 35: @@
 # For Web Entry media releases, like SlashGeo, add the press release directly into the web page, as per "Web Submissions" form on the Contacts list.
 # Send out a Twitter message. http://twitter.com/ . Login: foss4g Password: ask Shoaib, Cameron, Harley or Simon.
 == Day or 2 after release ==
 # For major press releases: Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. We have a few hundred lists, and one person won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), and try to get a number of people to help with this job. Once you confirm someone has forwarded on a press release, add a "Y" in the column next to their name, for the date of the release. If you discover someone hasn't sent a release, and you have prodded them to resend, add a "N" next to their name, so others know that you have already checked on them.

← Older revision		Revision as of 19:16, 17 July 2009
Line 37:		Line 37:

	== Day or 2 after release ==		== Day or 2 after release ==
−	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. We have a few hundred lists, and one person won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), and try to get a number of people to help with this job. Once you confirm someone has forwarded on a press release, add a "Y" in the column next to their name, for the date of the release. If you discover someone hasn't sent a release, and you have prodded them to resend, add a "N" next to their name, so others know that you have already checked on them.	+	# For major press releases: Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. We have a few hundred lists, and one person won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), and try to get a number of people to help with this job. Once you confirm someone has forwarded on a press release, add a "Y" in the column next to their name, for the date of the release. If you discover someone hasn't sent a release, and you have prodded them to resend, add a "N" next to their name, so others know that you have already checked on them.

← Older revision		Revision as of 19:16, 17 July 2009
Line 37:		Line 37:

	== Day or 2 after release ==		== Day or 2 after release ==
−	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. We have a few hundred lists, and one person won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), and try to get a number of people to help with this job. Once you confirm someone has forwarded on a press release, add a "Y" in the column next to their name, for the date of the release.	+	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. We have a few hundred lists, and one person won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), and try to get a number of people to help with this job. Once you confirm someone has forwarded on a press release, add a "Y" in the column next to their name, for the date of the release. If you discover someone hasn't sent a release, and you have prodded them to resend, add a "N" next to their name, so others know that you have already checked on them.

← Older revision		Revision as of 19:13, 17 July 2009
Line 37:		Line 37:

	== Day or 2 after release ==		== Day or 2 after release ==
−	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. ~~There are~~ a ~~lot of email~~ lists, and ~~you probably~~ won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), ~~etc~~. ~~Note: The OSGeoListNumbers sheet contains~~ the ~~list numbers~~ for ~~many~~ of the ~~lists~~.	+	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. We have a few hundred lists, and one person won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), and try to get a number of people to help with this job. Once you confirm someone has forwarded on a press release, add a "Y" in the column next to their name, for the date of the release.

← Older revision		Revision as of 08:55, 17 July 2009
Line 37:		Line 37:

	== Day or 2 after release ==		== Day or 2 after release ==
−	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. ~~<s>(Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).</s>~~ There are a lot of email lists, and you probably won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists, etc. Note: The OSGeoListNumbers sheet contains the list numbers for many of the lists.	+	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. There are a lot of email lists, and you probably won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists (number of subscribers are listed on the OSGeoListNumbers sheet in the Contacts doc), etc. Note: The OSGeoListNumbers sheet contains the list numbers for many of the lists.

@@ Line 22: / Line 22: @@
 # Send an email to translators asking them to translate. See examples link from: [[FOSS4G_2009_Press_Releases]]. A list of translators is available in the "Translators" tab of the contact list referenced above.
-== One day before the release ==
+== One working day before the release ==
 # If the press release is referencing new web pages, then make sure these pages have been populated.
-# Send a courtesy email to the press release recipients letting them know that a press release is coming
+# Send a courtesy email to the press release recipients letting them know that a press release is coming.
 == Release date ==

← Older revision		Revision as of 22:33, 16 July 2009
Line 36:		Line 36:

	== Day or 2 after release ==		== Day or 2 after release ==
−	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. <s>(Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).</s>	+	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. <s>(Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).</s> There are a lot of email lists, and you probably won't get to check all of them, so focus on the lists with the most number of subscribers first - Media, big osgeo lists, etc. Note: The OSGeoListNumbers sheet contains the list numbers for many of the lists.

@@ Line 33: / Line 33: @@
 ## CC anyone who may be chasing down leaders to forward on press releases
 # For Web Entry media releases, like SlashGeo, add the press release directly into the web page, as per "Web Submissions" form on the Contacts list.
-# Send out a Twitter message. (Todo, ask Shoaib how to do this)
+# Send out a Twitter message. http://twitter.com/ . Login: foss4g Password: ask Shoaib, Cameron, Harley or Simon.
 == Day or 2 after release ==
 # Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. <s>(Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).</s>

← Older revision		Revision as of 17:33, 16 July 2009
Line 36:		Line 36:

	== Day or 2 after release ==		== Day or 2 after release ==
−	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. (Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).	+	# Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. <s>(Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).</s>

@@ Line 2: / Line 2: @@
 * Look back at [[FOSS4G_2009_Press_Releases]] for examples of prior press releases, translations and emails to community members.
 * For a list of community leaders, email lists, media publications and other marketing channels, use the password protected Google Doc: http://spreadsheets.google.com/ccc?key=pu9014gybzrd1M6FqyOzGWg&hl=en_GB . The FOSS4G 2009 conference chair (Cameron Shorter) and OSGeo Officer (Tyler Mitchel) have access to the list.
 == Two weeks before release date ==
@@ Line 19: / Line 26: @@
 # Send a courtesy email to the press release recipients letting them know that a press release is coming
-== Morning of the release ==
+== Release date ==