Invite Alison as an expert to a forthcoming session

[DavidBeavan]

• [x] Invite send
• [x] response received
• [x] send on docs in advance
  • [x] repo
  • [x] readme / vision
  • [x] draft story
• [x] topic to discuss
  • [x] how to build social media? (Twitter profile)
  • [x] how to run a successful launch of first story? (output)
  • [x] how to encourage others to contribute?
  • [x] how to keep up momentum?
  • [x] any informal advice about integrating our mission with corporate comms?
• [x] confirm meeting software

[DavidBeavan]

Sent invite 2020-11-11

[DavidBeavan]

Alison is very keen, and I suggested 25 November

[DavidBeavan]

All arranged and prepared

[DavidBeavan]

• Likes the one liner of: mix of x, y, z e.g. use in Twitter bio
• Running it through GitHub currently
  • Who do you want
  • Anyone you don't want
  • How many, is the challenge not enough people rather than too many
  • Turing tends to lead towards Twitter and Linked in, forget about the rest
  • Twitter
  • Have account
  • Be transparent
  • Follow everyone associated with the Turing, open source, data science, science communicators, tv science communicators
  • Use lists that might be prepopulated with people
  • Enage with them, drop them a DM with a PERSONAL note, ask if they are interested
  • The above is a few days worth of work
  • Suggest TDataStories, nor TuringDstories. Refer to 'our data stories'
  • Put link in bio to GitHub
  • Make a tweet, about what we're all about, then pin it
  • Then start talking about it
  • Easy content is a snippet, a quote (image?) and use that in a tweet
  • Video, interview each other 30secs, even record on Zoom (make it accessible and not over produced)
    • Each of us, what we're doing, what we want?
  • Same for LinkedIn
  • Reach out to individuals
  • Ask Turing comms to retweet us out on the main account, but wait for more content from us
  • Say people get to us, then land at GitHub, then what
  • They will be thinking of themselves, how can they engage? What's in it for them?
  • Should this be a landing webpage, not the regular code/readme page
  • Think about the 'Turing 12 year old'
  • Target GitHub capable people first
  • They might be able to help others
  • Give a proper welcome, and steps (link in with our roles TBD) the process and how often
  • 'How can I get involved' section
    • Data
    • Code
    • Write
    • Ideas
    • Review
    • Communicate
    • Community
  • Consider edit to story:
  • 'Everyone in the UK has been impacted by the COVID-19 pandemic' leave out the rest
  • Stress it's a global issue, and not the individual locations.
  • Alison will join us, from end Dec onwards
  • Come up with a list of how people can engage and how it relates
  • Alison is happy to guide us with editing that now :heart: