HackMD
  • API
    API  HackMD API beta testing
    HackMD API is now in beta, join us for a test drive.
    Getting started Got it
      • Create new note
      • Create a note from template
    • API  HackMD API beta testing
      API  HackMD API beta testing
      HackMD API is now in beta, join us for a test drive.
      Getting started Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • ODF (Beta)
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        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
    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 Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML ODF (Beta)
    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
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    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
    LCCWG Moderation Subcommittee Scope of Work Proposal # Scope of Work - Background This proposal was developed by OpenStreetMap volunteers who came together to define the work to be completed by the Moderation Subcommittee, a sub-group of the Local Chapters and Communities Working Group (LCCWG). Learn more about other focus items of the LCCWG [here](https://wiki.osmfoundation.org/wiki/Local_Chapters_and_Communities_Working_Group). The OpenStreetMap Foundation (OSMF) Board [set out to](https://blog.openstreetmap.org/2020/12/11/message-from-osmf-board-chair-on-mailing-list-behavior/) "find partners to help instate a moderator team for the OSMF-talk and talk mailing lists". In their December 2020 meeting, the OSMF Board requested that the LCCWG take the lead on this initiative and subsequently this group has been formed. This group of volunteers is not the moderation team that the Board has asked for, instead we have committed to help set it up. We wholeheartedly agree with the Board that when established "these moderators need to have the trust of the community". As such we kindly ask for feedback on today's proposals as this is how we will ensure we are on the right path. The kind support of a few initial volunteers has enabled us to have a proposal ready for review, but we will continue to need support and hope to include representation from all parts of the OSM community. Please reach out if you are interested in being involved with this work. # Committee Scope of Work We aim to be inclusive by addressing and incorporating feedback. As such we are open to adjusting to your input on the process and content as we co-create. | You said: | We will: | | -------- | -------- | | This moderator team should start to work on enforcing the current Etiquette guidelines as soon as possible. <br />***Source**: OSMF Board [statement](https://blog.openstreetmap.org/2020/12/11/message-from-osmf-board-chair-on-mailing-list-behavior/).*<br /><br />Implementation is required across all OSM community channels/spheres (mailing lists, social media, communication channels including Weekly OSM, local and regional chat groups, events, and chapter coordination).<br /> ***Source**: "Immediate changes" section of the call for action [open letter](https://wiki.openstreetmap.org/wiki/File:A_Call_to_Take_Action_and_Confront_Systemic_Offensive_Behaviour_in_the_OSM_Community.pdf).*| Part 1. Define a process for moderation of the [Etiquette Guidelines](https://wiki.osmfoundation.org/wiki/Etiquette) that will apply initially to just the osmf-talk & talk mailing lists. <br /><br />Part 2. Recruit moderators into a moderation team that can moderate communications channels and respond to complaints. <br /><br />Part 3. Review existing moderation support material and make recommendations. | Work on updating/replacing our Etiquette rules, which must focus on balancing all participants’ interests. <br />***Source**: OSMF Board [statement](https://blog.openstreetmap.org/2020/12/11/message-from-osmf-board-chair-on-mailing-list-behavior/).*<br /><br />The existing [Code of Etiquette](https://wiki.osmfoundation.org/wiki/Etiquette) needs to be replaced by a strong Code of Conduct. <br />***Source**: "Immediate changes" section of the call for action [open letter](https://wiki.openstreetmap.org/wiki/File:A_Call_to_Take_Action_and_Confront_Systemic_Offensive_Behaviour_in_the_OSM_Community.pdf).* | Review existing Etiquette Guidelines and redefine based on OpenStreetMap's mission and values, today's cultural norms, a review of other community codes of conduct and etiquette, and community feedback.<br /><br />Note: We remain open-minded as to whether this will be a revision of the Etiquette Guidelines or an entirely new document (e.g. a "Code of Conduct")| |The OSMF should restructure governance to be more equitable: an example of this would be committing to Board Seat allocation for OSMF members who are women and non-binary, and who are citizens of Low and Middle Income Countries. <br />***Source**: "Immediate changes" section of the call for action [open letter](https://wiki.openstreetmap.org/wiki/File:A_Call_to_Take_Action_and_Confront_Systemic_Offensive_Behaviour_in_the_OSM_Community.pdf).*| We will not address this. However in establishing a moderation team we aspire to ensure the make-up is representive of society as a whole. | |Further changes should form part of OSMFs agenda over the coming 1-2 years. <br />***Source**: "Further changes" section of the call for action [open letter](https://wiki.openstreetmap.org/wiki/File:A_Call_to_Take_Action_and_Confront_Systemic_Offensive_Behaviour_in_the_OSM_Community.pdf).*| These are outside of the scope of our group and we will not be addressing them. ## An Iterative Process We will design an iterative process that we estimate will involve at least two cycles of moderation design, implementation on community lists, and feedback from the community. We plan to undertake the 'process for moderation' and 'etiquette guideline revision' work in parallel (subject to enough volunteer support). This process will require sufficient time for committee meetings, consultation with communities, research, feedback and OSMF board review. We estimate that the work will take approximately 6 months, but we will propose a more detailed workflow following community consultation. ## A Commitment to Community Participation Your participation and support is required to shape and strengthen this initiative. Feedback is welcome and encouraged, and we intend to involve you throughout this process. Please reach out to local@openstreetmap.org if you are interested in joining the subcommittee to support this work. You will have many opportunities to review and provide feedback on draft documents. The first task for the Subcommittee will be to develop a detailed workflow that outlines opportunities for your participation. The stages of involvement will differ according to the scale of each task, but you can expect to see stages related to initial evidence gathering, review of work in progress, followed by reviews of the proposed outcome across increasingly wider groups of the OpenStreetMap community. What's the best way for us to consult with you and/or your local community? Your input will be integral to developing the strongest workflow. We will try our best to provide opportunities for participation without exhausting you with too many messages or questions.

    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 Sign in via Google

    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