Skip to content

Latest commit

 

History

History
90 lines (73 loc) · 6.1 KB

social-media.md

File metadata and controls

90 lines (73 loc) · 6.1 KB
Raw

LFPH Social Media Guidelines

This document covers the social media guidelines for the use of the LFPH Twitter channel and LFPH project Twitter channels.

LFPH manages multiple project handles. These guidelines apply to all LFPH project channels, regardless of who manages.

LFPH Project Twitter handles

Objectives

The objectives of project social media:

  • Share project news, roadmap updates, news releases
  • Report on performance and security updates
  • Educate on project updates
  • Share information on how-tos, demos, etc that are valuable to the community
  • Build awareness for the project
  • Drive engagement and participate in the project

Strategy and Guidelines

  • Project maintainers are expected to manage their own social media accounts. This is a great way to get some community members involved who aren't as strong at coding
  • Keep messages positive, professional, and uplifting, consistent with the values and principles of LFPH
  • Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means.
  • Share content across social media channels that benefit the ecosystem as a whole
  • Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused
  • Engage with the community through retweets and sharing of community content.
  • Ecosystem content is vendor-neutral and project-impartial sourced from contributors, maintainers, ambassadors, news outlets, etc., including blog posts, news coverage, thought leadership bylines, technology demos, sketch notes, GitHub work, cloud native-specific Meetups, etc.
  • LFPH projects should not share anything on our channels that promotes a vendor, vendor product or directs to a company website.
  • Social posts from member company handles and/or vendor channels should be rarely shared. We prefer vendor-neutral links and sahres.
  • Community content that abides by the channel guidelines + includes insight from/work with more than one LFPH project should be prioritized for sharing.
  • Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole.

Images & Videos

Images shared, unless specifically credited back to a community member, will meet the requirements of “free for commercial use” and “no attribution required.”

Setup

  • The project should set up their own social media accounts, and then pass ownership off to LFPH.
  • LFPH maintains control of all project social media accounts. For Twitter, we use the Teams feature of Tweetdeck to add project contributors as people who can post on behalf of the project.

@lfpubhealth Twitter handle

Objectives

The objectives of LFPH social media:

  • Advance topics and conversations that are relevant to and beneficial for the public health community
  • Continue building positive affinity for LFPH projects among key influencers and throughout the public health community
  • Drive engagement and participation in LFPH projects

Themes and Topics

Informational, engaging, and ecosystem-focused content:

  • LFPH projects
  • LFPH end user community
  • Contributor / SIG blog posts
  • Public health technology generally
  • LFPH event information and deadlines (i.e. CFP)
  • Technical topics that relate to our projects
  • Industry topics such as general public health education
  • Informational: Tutorials, editorials, news stories. Items that help connect the dots for our community
  • Thought leadership: insights, perspectives, learnings, and experiences

Strategy

  • Keep messages positive, professional, and uplifting, consistent with our values
  • Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means.
  • Share content across social media channels that benefit the ecosystem as a whole
  • Maintain a balance of posting on LFPH activities/news and ecosystem-focused content
  • Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused
  • Engage with the community through retweets and sharing of community content
  • Help our members amplify the relevant work they are doing

General Guidelines

For all LFPH social activity, we remain a neutral foundation. Examples of the type of content:

  • Owned content is LFPH news, blogs, case studies, survey data, etc.
  • Project content is anything sourced from LFPH’s currently hosted projects, including project news, roadmap updates, new releases, performance/security updates, blogs, conferences slides/videos, etc.
  • Ecosystem content is vendor-neutral and project-impartial sourced from contributors, maintainers, ambassadors, news outlets, etc., including blog posts, news coverage, thought leadership bylines, technology demos, sketch notes, GitHub work, etc.
  • LFPH is not able to share anything on our channels that promotes a vendor or vendor product.
  • Community content that abides by the channel guidelines + includes insight from/work with more than one LFPH project will be prioritized for sharing.
  • Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole.

Images & Videos

Images shared, unless specifically credited back to a community member, will meet the requirements of “free for commercial use” and “no attribution required.”

Hashtags

LFPH uses hashtags in our posts:

  • To measure the success of campaigns (for example, #LFPH);
  • To expand our reach beyond our current followers and tap into larger, trending topics on Twitter (for example, #PublicHealth)
  • To organize or categorize shares (for example, #projects).
  • All hashtags should be CamelCase to make sure they are accessible by people who use screen readers.

To request content to be shared

Share your tweet on the #twitter channel on our Slack.

Many thanks to CNCF for allowing us to base our guidelines off of theirs.