aspirationtech
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • 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
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
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
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Taking stock of governance and identifying areas for improvement ## Number 1 "Most pressing/critical governance issue" > [name=Allan] Board is unable to discern in reality what the community really wants, as most voices are silenced by loud protests from a small highly vocal group. > [name=Guillaume] Conversations need to happen within the community. Trust needs to be (re)built, and the right venues need to be found. > [name=Joost] > * limited group is contributing to the core - barriers to entry / active recruitement > [name=Mikel] > * Small portion of community is engaged in OSMF governance, we need to increase this by developing governance structures that include local and regional groups > [name=Rory] Many Guidelines (organised editing, Attribution etc) are not enforced by the Foundation > [name=Paul] > * We need a conflict of interest policy > [name=Tobias] We need to define membership prerequisites and transparency. ## NOTES * Example: out of 41 conversations, 10 listed "Board not making decisions, not active in resolving issues", 1 person expressed fear that board was making decisions * Need to do more study of what community wants from board and wants OSM to look like * We don't have a single platform or space where all parts of the community participate * Perceptions depend on which parts of community/where you are active * e.g. German experience different from who allan talked to or US/UK * Driven by linguistics/region, as well as expectations on how people talk to each other * Different ways to get better picture of what people think * Besides surveys, there are other ways to percolate what people think * Local chapters can gather points of view, even though not everyone agrees * Single communications channel/platform is likely not possible * But..we should at least try * OSM Africa has translater bot * We could possibly do more things * Could other board members do any outreach? * We could also scope more broadly shared conversations * Could also invite folks to board meetings * Let's also reach out to normal mappers * Tough to reach out to folks you don't know about * Analyze tagging to understand who's doing the mapping [`osm-tag-csv-history`](https://github.com/rory/osm-tag-csv-history) * Local chapters and Communities working group doing lots of outreach * Increasing participation and safety * We are in bad position to analyze this. Selection bias, or "Survival of the grumpiest": need to not care about the bullshit * Have targeted conversation about negative impact * Is more drastic action called from with disruptive members of the community * Do we need a CoC, clarify what is unacceptable * Create consequence no matter what you have contributed * Some things might not be addressable via CoC * There are etiquette guidelines * No one enjoys moderation * We do not take care of culture of communication spaces * We need different structures * When looking at places where CoC has been implemented, it hasn't helped with problem participants * Nothing will work without enforcement * Civility will come from enforcement * Graduated enforcment is an option * Not clear what to do whan you have an issue to raise * Know who to contact * CoC can make some people feel less safe * ## ACTION ITEMS ### Better understanding and community disposition on board * Allan to share top-lines when able * Joost to ask LCC WG for timeline on their outreach * Could other board members do any outreach? (ask to all board members to try) * Invite local chapters to board meetings e.g. via lottery (Mikel/Rory) ### Trust and safety for community * Proposal: a WG? Not something the board can do, but could give structure * Diversity and inclusivity special committee? * Doesn't address attacks/slander * Ask moderators to remind people about etiquette guidelines * Summarize key points (Mikel) * Share and get feedback from * D&I special committee and ask for next steps and recommendations? (Mikel) * Mailing list moderators (Paul) * Forum moderators (Tobias) * Help.osm.org? () * Wiki admins (Tobias) * DWG (Allan) Some prior art: https://gitlab.com/osmfoundation/board/-/issues/129 ### Enforcement of policies etc * Largely ignore (internal) FOSS policy * Board *announcing* and then doing gentle, friendly, formal reminders noting exceptions and suggestion alternative actions (ACTION ITEM: Rory, and learn from Guillaume's efforts) * Ideally include "escalation path" guidelines * On organized editing guidelines, there is contact info, and DWG gets small number of complaints * People might not know how * Questions about whether folks are not making complaints because they don't have confidence * Don't know if LWG see active enforcment as their role or where responsibility lies * Membershipo: (Guillaume to ping) * CoI (Mikel to ping MIkel)

    Import from clipboard

    Paste your markdown or webpage here...

    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 lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    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 with Wallet
    Wallet ( )
    Connect another wallet

    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

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    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 and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    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.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        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
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

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

        Syncing

        Push failed

        Push successfully