HackMD
  • Beta
    Beta  Get a sneak peek of HackMD’s new design
    Turn on the feature preview and give us feedback.
    Go → Got it
      • Create new note
      • Create a note from template
    • Beta  Get a sneak peek of HackMD’s new design
      Beta  Get a sneak peek of HackMD’s new design
      Turn on the feature preview and give us feedback.
      Go → Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Please check the box to agree to the Community Guidelines.
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive Export to Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive Import from Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Export to Google Drive Gist
    Import
    Dropbox Google Drive Import from Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    Write
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Please check the box to agree to the Community Guidelines.
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Fedora Twitter Account ## Purpose Information and communication in the open source ecosystem has become increasingly more social, if such a thing is possible. It is increasingly important to use social media tools to connect to users, contributors, and allies within the broad open source community. Understanding who is reaching out to the Fedora Project is the first step in building a social media strategy. Is it users, developers, or potential contributors? How do they interact with Fedora’s online presence? How is the Fedora brand perceived and discussed, particularly in relation to Red Hat as well as other upstream projects? As Fedora listens, it will also be in the process of sharing its own voice with the community, building conversations and content that can keep people engaged and listening to what the Fedora Project has to say. This will strengthen existing relationships and build new ones. This social media plan is meant to codify the plan to converse with and listen to the people the Fedora Project wants to reach. Like any relationship, it will take time to build the ties we want to achieve. But with careful planning and execution, positive and measurable results will be achieved. ## Content The goals and objectives of the @fedora social media channel will be: * Increase awareness of the Fedora Project and its many deliverables * Establish members of the Fedora Project as thought leaders in their respective fields of expertise * Build rapport and interest among members of the media and members of the desktop, Linux, and open source communities * Drive traffic to Fedora Magazine and the Fedora Community Blog to increase awareness of what the Fedora Project has to offer * Increase attendance at Fedora events (and involvement in the Fedora Project in general) Content on @fedora will be ecumenical in nature, with a focus on Fedora and any related projects. “Ecumenical” in this instance means that while the channel’s content will focus on Fedora’s efforts, good citizenship practice in open source communities recommends posting content on other non-Fedora projects (e.g., tweeting congratulations about an important milestone for another project, such as Debian or openSUSE). Twitter content will include links to original content, to be hosted on the Fedora long-form content sites, as well as blog posts, technical articles, success stories, and multimedia content. Broader desktop technology-related content will also be aggregated on the Twitter channel as well. ## Twitter Tactics The goal for participation on Twitter is to have an active, participating, and growing audience that's listening to and engaging with you as a thought-leader in your area of expertise. It's critical to recognize inbound clicks to the Fedora sites will not be the number one goal of tweeting. The clicks/impression rate on Twitter is abysmal. The goal on Twitter should be to make connections and establish Fedora as a key influencer in our sector. ### Have a Voice Consistency, authenticity and credibility are three things to keep top of mind when you are developing your brand's voice. Your goal is to embody the lifestyle of your brand, resonate with your audience and invite conversation. Use keywords in your tweet that are unique to your brand to create an insider feel to the Fedora community. ### Crafting Your Tweets Write tweets to be shared, not to drive clicks. Post tweets that are entertaining. Post facts that are relevant to that brand's point of view. Keep it short and simple. Tweets that are 100 characters or less have a higher rate of engagement and it also allows space for people to add their own comments in retweets. Only half of your tweets should link back toFedora domains. Avoid using dishonest or sensational copy to promote your links. ### Share Images Too! Tweets with images in them have two times more engagement than tweets without pictures. Share pictures that give your followers insight into the people's lives that fuels the Fedora brand that they can't find on the Fedora sites. ### Make Targeted Connections Use Twitter to get in touch with users whose doors may have been traditionally closed to you to generate conversations. Retweet their content, favorite their posts, respond to their questions. Building relationships on Twitter takes time and persistence, but connecting with the right people can help take your brand to new levels. ### Tips and Tricks When retweeting a follower, try to always use a quote tweet option. Highlight what about the tweet particularly resonated with you, show support for another user or totally disagree and start a conversation. ## Metrics To measure the impact of the success of this plan, a variety of metrics will be measured that determine the quantity and the quality of communications within the channels. A monthly report should be available to the Fedora Social Media team that will identify where things are working and where they are not. As the plan matures, areas in need of concentration will be identified in the report, with ideas of how to improve. Specific targets will be discussed and determined within the team. The metrics will include: Tweets: Aggregated content Tweets: Original content Followers (\*)Mentions (\*)Retweets (\*)Retweets with comments *Starred (\*) metrics are better indicators of quality, as they represent interactivity, a highly desired goal.*

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully