HackMD
  • Beta
    Beta  Get a sneak peek of HackMD’s new design
    Turn on the feature preview and give us feedback.
    Go → Got it
    • 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
        • 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
        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
      • 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 Help
    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
    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
    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
    --- title: "社群規範(草稿)Code of Conduct(draft)" tags: community, coc, hackpad --- # 社群規範(草稿)Code of Conduct(draft)· > [點此觀看原始內容](https://osmtw.hackpad.tw/0BHFi7ZqUx0) 社群規範(草稿)Code of Conduct(draft)· > [http://wiki.openstreetmap.org/wiki/Community\_Code\_of\_Conduct\_%28Draft%29](http://wiki.openstreetmap.org/wiki/Community_Code_of_Conduct_%28Draft%29) > [name=李昕迪] > [http://wiki.openstreetmap.org/wiki/Humanitarian\_OSM\_Team/Code\_of\_Conduct](http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team/Code_of_Conduct) > [name=李昕迪] ## 開放街圖社群規範 Community Code of Conduct OpenStreetMap ``` General ``` ## 總則 ``` Be nice to each other. ``` 善待彼此。 ``` Be Considerate ``` **1\. 體貼他人。** ``` Work created by OpenStreetMap is seen by people around the world and by contributing to the project, you're representing not only yourself, but OpenStreetMap itself. Please keep that in mind with your words and actions. ``` 由開放街圖計畫所產出的成果,是全世界的人都可以使用的。藉由貢獻於這個計畫,您不只代表著自己一個人,而是整個開放街圖社群。發表言論或做出行動的時候,請記住這一點。 Be Respectful **2\. 尊重他人。** ``` OpenStreetMap contributors come from a variety of backgrounds and have a variety of skill sets. We believe that our diversity is a source of strength and that everyone has something to contribute to the project. Some degree of frustration and constructive disagreement is to be expected when dealing with a passionate community project. However, it is important to remember that a community where people feel uncomfortable or threatened is not a productive one. In the spirit of collaboration, please refrain from allowing healthy differences of opinion or frustration to turn into personal attacks or flame/edit wars.. We expect members of the OpenStreetMap community to be respectful when dealing with other contributors, as well as people outside the project. ``` 開放街圖的貢獻者來自許多不同的背景,也各自具備了各式各樣的技能。我們相信多元化是社群能量的源頭,而每個人都有自己可以盡力之處。有時候不免遭遇到挫折、有建設性的意見分歧也常常會在熱情的社群計畫中發生。然而,很重要的是要記住,如果一個社群裡頭有人感到不舒服或好像被威脅了,這個社群就很難有生產力了。秉著合作的精神,請記得允許讓觀點差異或衝突健康地存在,而不要做出人身攻擊或編輯戰。我們期待開放街圖的社群成員們,不論是在貢獻者彼此,或是對社群以外的人士溝通時,都能夠互相尊重。 ``` Be Collaborative ``` **3\. 願意合作。** ``` Collaboration is central to OpenStreetMap. OSM encourages members to work together both inside and outside the organization. Collaboration, internally and externally, strengthens our community. OSM members are encouraged to act transparently and when possible involve all interested parties. When a new approach is taken on an existing project or a major project is considered/started, please notify the larger community early, document the work and inform others regularly of progress. ``` 開放街圖的核心在於合作。開放街圖鼓勵成員們不論在組織內外,都一起工作。不論是內部或外界的合作,都能夠強化我們的社群。我們鼓勵開放街圖的成員們行事作風要透明公開,讓可能相關的各界納入參與。當有一個新的做法要在既有的計畫上推動、或是有個新的大型計畫要啟動時,請儘早告知相關的社群成員,進行記錄工作,並定期對外報告進展。 ``` When we disagree, we consult others ``` **4\. 當意見不同時,我們徵求其他人的想法** ``` Disagreements, both social and technical, are common in diverse communities. It is crucial for the long term success of the project that major disagreements are resolved constructively, with transparency, with the help of the community and community processes. ``` 意見分歧——不論是社會面或是技術面的——在一個多元的社群中十分常見。計畫要能夠永續經營,關鍵在於解決重大的意見分歧時,能夠有建設性、公開透明、由社群協助並依照社群的機制處理。 ``` When we are unsure, we ask for help ``` **5\. 不確定怎麼做時,我們尋求協助** ``` Nobody knows everything, and nobody is expected to be perfect in the OpenStreetMap community. Asking questions before taking a major action can prevent problems down the road, and so questions are encouraged. ``` 沒有人可以全知全能,在開放街圖社群裡也沒有人是完美的。在開始一件事關重大的行動前先發問,這可以避免過程發生更多問題,所以請大家多多發問。 ``` When asking a question, members are encouraged to do so in an open and appropriate forum. ``` 我們鼓勵社群成員們可透過公共論壇,用有禮合宜的方式提問。 ``` Step down considerately ``` **6\. 離任時,請帶著體貼的心** ``` When members of OSM leave or disengage from the project and/or community, they are asked to do so in a way that minimizes disruption to the project as a whole. Members are strongly encouraged to put forth an effort to ensure that others can pick up where they left off. ``` 當開放街圖的社群成員要從計畫或社群離開時,我們要求其在造成整體計畫最小混亂的情況下進行。我們鼓勵社群成員們付出行動,確保他們離開時其他人能夠接續他們的工作。 ``` Respect Copyright and Licenses ``` **7\. 尊重著作權與授權條款** ```txt Please be conscious of license issues, and never add data in a way that violates other licenses or copyright. While this is primarily a concern for OpenStreetMap data edits, remember that pasting data or images into a mailing list, or wiki page can also be a violation of copyright. Remember to comply with any attribution and share-alike requirements of any images/data placed on these channels, and avoid placing closed-license content there. ``` 請注意著作權相關的議題,絕對不要在違反著作權授權的情況下替開放街圖計劃增添資料。儘管這件事情主要是在開放街圖資料的編輯面向,但是在郵件列表或是維基頁面上剪貼來自他處的資料也是違反著作權的一種方式。請記得在上述管道中務必遵守各種圖像或資料標注來源以及相同方式分享的準則,並且不要放置著作權所有的內容上來。 ``` == Additions and modifications == ``` ## 增修條款 ``` This document may be subject to additions and modifications. In fact, because it is currently under development we can expect a lot '''more additional rules and guidelines''' to appear here. ``` 這份文件可能會有其他的增修條款。事實上,因為這份文件還在草擬中,我們可以預見將會有許多「增添的規範與守則」的出現。 ``` == Violations and Enforcement == ``` ## 違規與執行 ``` ''This is the tricky bit! Under discussion'' ``` ''此段落的內容仍待更多共識!'' ``` Anyone posting to the mailing list in violation of this code of conduct, may receive one or more warnings depending on the nature and severity of the infraction. Recurring violations will result in a ban of the offending user. The number of prior warnings, if any, before a ban, will depend on the nature and severity of the violation. ``` 任何在郵件列表中的內容若有違反上述的行為規範,將會收到一份以上的警告(視此違規的本質與嚴重性)。累犯者將會導致封禁違規使用者。如果在封禁前有任何事前的警告,則警告的次數將會由違規的本質及嚴重性而定。 ``` Warnings will often be accompanied by a recommendation to the offending user to desist from posting to the mailing list for a cooling off period of at least 48 hours. Failure to adhere to such recommendations (even an attempt to post in an apologetic tone) may be regarded as a violation in itself. Please just stop posting, and cool off. ``` 警告 ``` === Judging violations === ``` **1\. 如何判定違規** ``` Many of the rules and guidelines are rather broad and vague, and so the decision as to whether a particular mailing list post, or set of posts constitutes a violation will always be a matter of judgement. Community consensus will be taken into account, however final decisions need to rest with some authority (individual, or more likely, a new organisational unit). An organisational unit may need to be established, and the most likely mechanism for that to happen would be the formation of a [[Foundation]] "working group" ==== Option: Community council ==== ``` #### (1) 方法一:社群議會 ``` Members of a community council for each list, forum, channel would be empowered to judge violations and apply sanctions individually and in consultation with the council and community. The community council members will be recommended by the community on that communication channel. ==== Option: OSMF Ministry of Truth Working Group ==== ``` #### (2) 方法二:開放街圖基金會(OSMF)真理部工作小組(Ministry of Truth Working Group) ``` The foundation will establish a working group of volunteers to receive issues from the community, evaluate them and act. === Performing a ban === ``` > 顯然這條是開玩笑的。 > [name=Rex T] **2\. 實施封禁** ``` [[System Administrators]] will carry out a ban, as a setting against an account within the mailing list software. This will only be carried out at the behest of the judging authority as and when they identify a violation, and after an appropriate warning has been given. The role of the foundation is to "support not control" the project, however the mailing list runs on [[Foundation]] servers, and ultimate responsibility for actions carried out by system administrators rests with the Foundation. === Misconduct across other channels === ``` **3\. 誤轉至其他管道** ``` Other [[contact]] channels are within scope of this document. Differing enforcement methods may be required in different venues. Users responding to a mailing list ban with further misconduct on other communication channels, should be aware that a prior ban on the mailing list may well be taken into consideration in the instigation of more rapid bans on other communication channels. == Credit == ``` ## 謝啟 ``` This document, The (DRAFT) OpenStreetMap Code of Conduct, is based on the [http://www.ubuntu.com/community/conduct Ubuntu Code of Conduct] and is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0 license].

    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