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
    # Draft Proposed OSMF policy on ensuring safety for attendees at SotM :::info this is just a draft of a proposed policy for the OSMF to adopt, to ensure LGBTQ+ people can always feel “safe enough” at their State of the Map conference(s). ::: ## Mikel's proposal up for vote OpenStreetMap welcomes and encourages participation by everyone. This is enshrined in our [Diversity Statement](https://wiki.osmfoundation.org/wiki/Diversity_Statement). There are, however, places in the world where people with certain attributes may face discrimination or are systematically made to feel unsafe. The OSMF will only host global State of the Map conferences in places where the safety of all segments of the population is ensured. Applications to host a SotM should describe and assess the risks in that location for certain vulnerable populations, and must certify that State of the Map will be safe from systematic or institutional discrimination for all attendees. Details of how this is assessed is the mandate of the State of the Map Working Group. Local and regional State of the Map conferences should do everything reasonably possible, in their local context, to ensure the safety of all segments of the population. It is recognized that in some regions and locations safety cannot be guaranteed for all vulnerable groups, and that this should not prevent a local or regional SotM from being held. Applications for trademark licenses should include a safety assessment. Details of the trademark application update are the mandate of the Licensing Working Group. ## Allan's suggestion ### Proposed Policy Text OpenStreetMap welcomes and encourages participation by everyone. This is enshrined in our Diversity Statement https://wiki.osmfoundation.org/wiki/Diversity_Statement. There are places in the world where people with certain attributes may face discrimination or are systematically made to feel unsafe. Applications to host a SotM should describe and assess the risks in that location for certain vulnerable populations, and certify that State of the Map will be safe for all attendees. The OSMF will not host a global SotM in a place where any segment of the population will be unsafe due to systematic or institutional discrimination. The OSMF will not grant a trademark licence for a “regional SotM” (e.g. “State of the Map [REGION]”), for an event in a place where any segment of the population will be unsafe due to systematic or institutional discrimination. > [name=Mikel Maron] I recommend we frame this in a positive way. "The OSMF will host global State of the Map conferences in places where the safety of all segments of the population is ensured." > [name=Mikel Maron] I think we need to have a slightly different policy for trademark licenses, which reflects the need to support local communities, with consideration of the local situation. Maybe this: "In granting trademark licenses for local State of the Map conferences, organizers must address and do everything in their ability to ensure the safety of all segments of the population." ## Amanda's suggestion №2 ### Proposed Policy Text OpenStreetMap welcomes and encourages participation by everyone. This is enshrined in our Diversity Statement https://wiki.osmfoundation.org/wiki/Diversity_Statement. There are places where certain attributes of people are discriminated against, or made systematically unsafe. Applications to host a SotM should describe and assess the risks in that location for certain vulnerable populations, and certify that State of the Map will be safe for all attendees. The OSMF will not host a global SotM in a place where any segment of the population will be unsafe due to systematic or institutional discrimination. The OSMF will not grant a trademark licence for a “regional SotM” (e.g. “State of the Map [REGION]”), for an event in a place where any segment of the population will be unsafe due to systematic or institutional discrimination unless that systematic or institutional discrimination is present in the entirety of the region. ### Comments > This is based on Allan's suggestion, but added the last part (from “unless …” onwards) > If a country, or region, is unsafe for LGBTQ+ people, then it not fair (IMO) to completely ban them from having a local SotM. > [name=Amanda] ## Amanda's suggestion №1 ### Proposed Policy Text OpenStreetMap welcomes and encourages participation by everyone. This is enshrined in our Diversity Statement https://wiki.osmfoundation.org/wiki/Diversity_Statement. There are places where certain attributes of people are discriminated against, or made systematically unsafe. Applications to host a SotM should describe and assess the risks in your country for certain vulnerable populations, and go into detail on how the bid will ensure that State of the Map will be safe for all attendees. For this policy “widespread LGBTQ unacceptance” is a place where the local law criminilizes homosexuality and the law is not being ignored by the state. The OSMF will not host a (global) SotM in a place with “widespread LGBTQ unacceptance”. The OSMF will not grant a trademark licence for a “regional SotM” (e.g. “State of the Map [REGION]”), for an event in a place that has “widespread LGBTQ unacceptance” if there is a place in that region which is not “widespread LGBTQ unacceptance”. ### Q&A Will this apply to events that don't use the “State of the Map” name? : No, those events are outside the jurisdiction of the OSMF. ~~How do you know if~~ What do we do in a case where a discriminatory law is not enforced, or is ignored by the state? : It is up to the organizing committee to determine that nobody will be placed at undue risk of arrest, detention, or physical harm. Using laws banning homosexual acts as an example, applicants may show that the law is not being enforced in many ways, such as (i) repeated local LGBTQ pride parades, (ii) politicians or prestigous community leaders who are openly LGBTQ (iii) travel advice from other countries stating it is not enforced (iv) reliable statistics and polls on societal acceptance of LGBTQ* people > [name=amustard Redundant] What if it's against the law, but that law is ignored, or not enforced? : If the local LGBTQ+ community feel “safe”, they will have hosted “enough” “local” pride parades.~~: If the local LGBTQ+ community feel “safe”, they will have hosted “enough” “local” pride parades.~~ What about places like Russia, or Hungary, which have passed anti-LGBTQ laws? : Since homosexuality is not illegal there, this policy would allow a regional/global SotM. The purpose of this policy is to set a very low bar. It does not guarantee a 100% safe environment for all LGBTQ people, or anyone, for that matter, at all times. What if it's legal, but there's an unequal age of consent? : That counts as “legal”. Does this mean a country cannot host a country specific SotM, (e.g. “SotM Saudi Arabia”)? : No. “SotM Saudi Arabia” covers (only) Saudi Arabia (which has enforced anti-gay laws) then the event can take place anywhere in the country. What about other forms of oppression? : ~~This policy text refers to LGBTQ* issues, because that's what affects me the most. I would welcome other campaigners suggesting additional safe guards.~~The same general principles apply to discrimination on ethnic, gender, and religious faith grounds. Since certain countries oppress women, such as Iran, would Iran be banned from hosting a regional SOTM? : The organizing committee would have to certify that women coming from abroad face no undue threat of harassment or danger by attending a SOTM in Iran. If unable to do that, the Board would decline to issue a trademark grant. *Your question here!* : *(amanda's answer here)* ### Glossary LGBTQ+ : Lesbian, Gay, Bi, Trans, Queer + (aka LGBTQ+ LGBTQIA+ etc.) ## Mikel's suggestion :::info > I have copy/pasted from one of Mikel's latest emails. 🙂 Please edit & correct > [name=Amanda] ::: > Here's what I propose to ensure this is clear. This is a rough draft. The call for proposals for SotM will explicitly ask the bids "OpenStreetMap welcomes and encourages participation by everyone. This is enshrined in our Diversity Statement https://wiki.osmfoundation.org/wiki/Diversity_Statement. There are places where people with certain attributes face discrimination or are made systematically to feel unsafe. Please describe and assess the risks in your country for certain vulnerable populations, and certify that State of the Map will be safe for all attendees." ## Your suggestion! ## Your suggestion! ## Your suggestion! "The [OpenStreetMap Diversity Statement](https://wiki.osmfoundation.org/wiki/Diversity_Statement) explains how we welcome and support diversity. SotM applications should describe and assess the local risks for vulnerable groups, and detail how they will ensure that the event will be safe for all attendees."

    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