{"action":"reopened","issue":{"url":"https://api.github.com/repos/18F/product-guide/issues/46","repository_url":"https://api.github.com/repos/18F/product-guide","labels_url":"https://api.github.com/repos/18F/product-guide/issues/46/labels{/name}","comments_url":"https://api.github.com/repos/18F/product-guide/issues/46/comments","events_url":"https://api.github.com/repos/18F/product-guide/issues/46/events","html_url":"https://github.com/18F/product-guide/issues/46","id":137293309,"number":46,"title":"Project Storyteller Text","user":{"login":"abisker","id":15878767,"avatar_url":"https://avatars.githubusercontent.com/u/15878767?v=3","gravatar_id":"","url":"https://api.github.com/users/abisker","html_url":"https://github.com/abisker","followers_url":"https://api.github.com/users/abisker/followers","following_url":"https://api.github.com/users/abisker/following{/other_user}","gists_url":"https://api.github.com/users/abisker/gists{/gist_id}","starred_url":"https://api.github.com/users/abisker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abisker/subscriptions","organizations_url":"https://api.github.com/users/abisker/orgs","repos_url":"https://api.github.com/users/abisker/repos","events_url":"https://api.github.com/users/abisker/events{/privacy}","received_events_url":"https://api.github.com/users/abisker/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-29T15:56:01Z","updated_at":"2016-02-29T15:59:54Z","closed_at":null,"body":"@annahsebok - This text should be added directly after the current paragraph in the \"Filling out a communications plan\" portion of the Project Communications section.\r\n\r\nText:\r\n\r\nAdditionally, you need to designate a project “storyteller” who will give ongoing updates to the Comms team. This person does not have to be the product lead, and will serve as a conduit between the product and comms team. Notify the comms team of the storyteller contact in #outreach.\r\n\r\nEvery product must have:\r\n\r\n- About.yml entry\r\n- A comms plan\r\n- Ideas for ~3 blog posts (from your team)\r\n\r\nThe comms team will work with the storyteller to ensure that the above items are accurate and up-to-date. The storyteller will also meet with the comms team for 5-10 minutes each week during the blog huddle to update the comms on the following:\r\n\r\n- upcoming milestones and events (that you’re going to or could present at)\r\n- any impending risks to prepare for press and mitigate any issues\r\n- progress on comms plan / blog posts\r\n- any other ways the comms team can help your project\r\n- upcoming speaking events / conferences that the project/product is represented at\r\n- any updates that need to be conveyed to the agency partner’s comms team (and who those people might be.)\r\n- updates for 18F newsletter or Dolores or #news\r\n- updates for open source community who might be able to help with ‘help-wanted’ tags\r\n\r\nIn the first meeting with the storyteller, the comms team will go over the blog mission and how we talk about our products. Future (very, very short) meetings will follow the template listed above. "}}