[sakai-pmc] Mini-Sakai 10 communications plan

[Neal Caidin]

> Sam Ottenhoff <mailto:ottenhoff at longsight.com>
> June 19, 2014 at 10:36 AM
> What about any confluence links about the latest release, current 
> releases, etc?  Update confluence pages to put a warning at the top of 
> the page pointing the user to the latest release.
Not sure if you mean this page, but yes - 
https://confluence.sakaiproject.org/display/DOC/Release+Documentation
Put warnings at the top of 2.9 and 2.8 pages?
>
> 5) Why send the user to the Apereo site to read a tiny news blurb 
> before then being sent to the Sakai site for the information?
Okay, I'll check to see the best place to put news on the 
Sakaiproject.org site . No harm posting to both. Tweet can reference the 
Sakai site.
>
> 7) Doesn't Apereo now have formal press release capabilities?
I think you are correct. I will check with Ian on that.
>
>
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> June 19, 2014 at 9:09 AM
> Hi PMC,
>
> Here is a rough communications plan for when we get Sakai 10 out the 
> door. I recently subscribed to one of the Educause lists, so I can 
> post to that. Might be good to think of other outlets to get the word 
> out in addition to, but beyond, the Sakai community.
>
> https://confluence.sakaiproject.org/display/REL/Release+Communications+Plan 
>
>
> 1) Before sending out communications, insure that following 
> documentation is updated:
>
> https://source.sakaiproject.org/release/  (and this needs to be 
> redirected to the latest release)
>
> Confluence Release notes, especially summary of new features and 
> technical requirements
>
> http://www.sakaiproject.org at the following places:
> http://sakaiproject.org/current-release
> http://www.sakaiproject.org/node/105
> http://www.sakaiproject.org/try-sakai
> http://www.sakaiproject.org/node/31
> http://www.sakaiproject.org
>
> 2) Communicate technical details, specifically how to access the 
> release artifacts, to the QA, Dev, and Prod lists
>
> 3) Communicate to the broader community the main changes, in 
> non-technical terms, for the release. Include QA, Dev, Prod and add 
> Internationalization, Accessibility, Sakai User, Pedagogy, and 
> Documentation.
>
> 4) Post a highlighted news item to the Apereo.org web site.
>
> 5) Social media - Post to Facebook as Sakai Project and to Twitter 
> (point the tweet to the Apereo.org web site?)
>
> 6) Send out an Apereo Announcement
>
> 7) Should go to outlets outside of the community (Educause... others?)
>
> Cheers,
> Neal
>

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140619/0654a963/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1265 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140619/0654a963/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140619/0654a963/attachment-0001.jpg