Wordsmiths
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
    • 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 No publishing access yet

      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.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      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
    • Make a copy
    • Transfer ownership
    • Delete this note
    • 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 Help
Menu
Options
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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
  • 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 No publishing access yet

    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.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    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
    # Notes on Conflict Resolution and Values Drawing some sample from metagov's airtable [https://airtable.com/shrgnUrj0dqzZDsOd/tbltBIhUFqZE1tfle/viw6J9mO9wrlSh3cg](https://airtable.com/shrgnUrj0dqzZDsOd/tbltBIhUFqZE1tfle/viw6J9mO9wrlSh3cg) I will copy and paste sample from other projects conflict resolution section of their respective governing docs. Then hopefully we can make comments on the ones we like best and add it to our own governing doc. ## Sample Cases ### One Hive > Our Standards > > Examples of behavior that contributes to a positive environment for our community include: > > Demonstrating empathy and kindness toward other people > Being respectful of differing opinions, viewpoints, and experiences > Giving and gracefully accepting constructive feedback > Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience > Focusing on what is best not just for us as individuals, but for the overall community > > Examples of unacceptable behavior include: > > The use of sexualized language or imagery, and sexual attention or advances of any kind > Trolling, insulting or derogatory comments, and personal or political attacks > Public or private harassment > Publishing others’ private information, such as a physical or email address, without their explicit permission > Other conduct which could reasonably be considered inappropriate in a professional setting > > On-chain enforcement > > The on-chain mechanism for enforcement will depend on the completion of Celeste. > > The ability for the 1Hive protocol to enforce this covenant is limited to the direct interactions that community members have with the protocol, specifically the ability for community members to submit proposals to allocate Honey issuance or adjust protocol parameters. > > A community member will be required to stake Honey when submitting a proposal, attesting that the impact of the proposal could be reasonably considered to align with 1Hive’s social contract. A dispute can be created by another community member if they disagree with the proposers attestation by challenging the proposal and staking an equivalent amount of Honey. If after being challenged the proposal is not withdrawn, a decentralized oracle will be used to settle the dispute. > > Participants in the dispute resolution protocol are expected to review the proposal, this covenant, and related past disputes in order to provide a judgement that they feel best aligns with the established norms and intention of the 1Hive community. > > If the oracle responds in favor of the proposer the proposal will be unlocked and the challenger’s stake will be transferred to the proposer. On the other hand, if the dispute resolves in favor of the challenger the proposal will be removed from consideration and the proposers stake will be given to the challenger. > Off-chain enforcement > > While there is no canonical off-chain forum that represents the 1Hive community, there are community spaces including the 1Hive GitHub, Discourse, and Discord communities, and others forums which may emerge in the future which are expected to adhere to this covenant. ### Aragon ![](https://i.imgur.com/2oRhgxK.png) ### Bright DAO > Our Values > > We are value-driven, (not profit-driven) and will strive to support and foster an inclusive economic system. We value integrity, radical inclusion and civic responsibility. Our core principles include positivity, critical thinking and thoughtfulness. We encourage progressive ideas, constructive discussion and transparent interactions. We also adopt the pledge and standards from our partner community 1Hive; > > We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. > > Examples of behaviour that contributes to a positive environment for our community include: > > Demonstrating empathy and kindness toward other people > Being respectful of differing opinions, viewpoints, and experiences > Giving and gracefully accepting constructive feedback > Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience > Focusing on what is best not just for us as individuals, but for the overall community. > > Examples of unacceptable behaviour include: > > The use of sexualized language or imagery, and sexual attention or advances of any kind > Trolling, insulting or derogatory comments, and personal or political attacks > Public or private harassment > Publishing others’ private information, such as a physical or email address, without their explicit permission > Other conduct which could reasonably be considered inappropriate in a professional setting. ### Effect DAO > 10. **RESOLUTION OF DISPUTES** > > **10.1** Informal Dispute Resolution: Members and Guardians and/or High Guard shall cooperate in good faith to resolve any Dispute, controversy, or claim arising out of, relating to or in connection with the Constitution or the DAO, including with respect to the formation, applicability, breach, termination, validity or enforceability thereof (“Dispute”). All resolutions are subject to final approval by the High Guard. ### Ethereum World ![](https://i.imgur.com/FOwQEVp.png) ![](https://i.imgur.com/LanlO6A.png) ### HausDao >**Dispute Resolution** > > If you no longer wish to support DAOhaus, you may Rage-quit at any time. Once you Rage-quit, you will receive an amount of DAI proportional to your remaining contribution plus HAUS tokens for any portion of your original contribution that has been spent by the DAO at the time of your Rage-quit. By joining HausDAO you agree that Rage-quitting shall be the only recourse available to you should you have any dispute with HausDAO or the members of HausDAO. ### LexDao > Section 2.8 - Settlement of disputes. In any dispute between LexDAO and any of its members or former members which cannot be resolved through informal negotiation, it shall be the policy of LexDAO to prefer the use of mediation whereby an impartial mediator may facilitate negotiations between the parties and assist them in developing a mutually acceptable settlement. Neither party with a grievance against the other shall have recourse to litigation until the matter is submitted to mediation and attempted to be resolved in good faith. All LDC Membership agree that there is a preference to settle disputes amongst members or between members and LexDAO via decentralized dispute mechanisms via smart contract protocols. > > Section 2.9 - Transferability of Membership. Membership rights and interests may not be transferred except by vote of LexDAO membership. Any attempted transfer contrary to this section shall be wholly void and shall confer no rights on the intended transferee and shall be cause (though none is needed) to burn the LDC token through a Guild Kick member removal procedure. > > Section 2.10 - Withdrawal and Expulsion. A member may withdraw at any time upon notice to LexDAO through a vote to burn their LDC token. Said request will not be unreasonably denied and shall be deemed conclusively as the LDC Members intent to withdraw from LexDAO. A member may be expelled by LexDAO through the Guild Kick procedure established in paragraph 2.6 of this document and adopted by the membership. Upon termination of membership LDC token, all rights and interests in LexDAO shall cease except for rights to redemption of capital pursuant to Article V below (if any). ### Token Engineering Commons > The Pledge > > We as members, contributors, and leaders declare to make participation in the TEC community a harassment-free experience for everyone, regardless of age, sex, visible or invisible disability, ethnicity, sex characteristics, gender identity and/or expression, level of experience, education, socio-economic status, nationality, ethnicity, personal appearance, race, religion, or sexual identity and orientation. > > We promise to act in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. Actions that contradict this attitude will be handled through Gravity, facilitating clear steps to receive assistance in the search and implementation of non adversarial solutions. > > Gravity behaves according to the TEC graduated sanctions 1 and commits to its use with respect to all individuals. > Our Standards > > Examples of behavior that contributes to a positive environment for our community include: > > Demonstrating empathy and kindness toward other people > Being respectful of differing opinions, viewpoints, and experiences > Giving and gracefully accepting constructive feedback > Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience > Focusing on what is best not just for us as individuals, but for the overall community > > Examples of unacceptable behavior include: > > The use of sexualized language or imagery, and sexual attention or advances of any kind > Trolling, insulting or derogatory comments, and personal or political attacks > Public or private harassment > Publishing others’ private information, such as a physical or email address, without their explicit permission (commonly called doxing) > Other conduct which could reasonably be considered inappropriate in a professional setting > > On-Chain > Decision Making > > The Token Engineering Commons uses the Gardens 4 framework technology to manage the DAO configurations and allocate funds to projects that are aligned with its mission, vision and values. > > On-chain decision making mechanisms are Conviction Voting and TAO Voting. Conviction Voting should be used primarily for funds allocation. TAO Voting should be used for updating parameters, bug fixes, adding new features to the DAO and/or for emergency situations such as an attack to the DAO treasury. > Enforcement > > The on-chain mechanism for enforcement will depend on the completion of Celeste 2. > > The ability for the Token Engineering Commons protocol to enforce this covenant is limited to the direct interactions that community members have with the protocol, specifically the ability for community members to submit proposals to allocate TEC issuance or adjust protocol parameters. > > The proposer will be required to deposit TEC tokens when submitting a proposal, attesting that the impact of the proposal could be reasonably considered to align with TEC’s social contract. A dispute can be created by another community member if they disagree with the proposer’s attestation by challenging the proposal and staking an equivalent amount of TEC tokens. If after being challenged the proposal is not withdrawn, a decentralized oracle will be used to settle the dispute with the right to appeal that decision within Celeste. If the oracle responds in favor of the proposer the proposal will be unlocked and the challenger’s stake will be transferred to the proposer. On the other hand, if the dispute is resolved in favor of the challenger the proposal will be removed from consideration and the proposer’s stake will be given to the challenger. > > Participants in the dispute resolution protocol are expected to review the proposal, this covenant, and related past disputes in order to provide a judgement that they feel best aligns with the established norms and intention of the TEC community. > Off-chain > Decision Making > > The TEC uses Advice Process 2 as its primary practice for flat decision making to empower contributors with agency to move their cultural proposals forward. Advice Process is written in the forum in the Advice Process section and promoted verbally in community calls. When a non-financial, no-code decision will likely affect a large part of the community, the use of off-chain voting and signaling tools are expected. The TEC recommends token weighted tools for off chain decision making, like Snapshot and Tokenlog. A decision is considered legitimate when it respects this covenant, is promoted to the awareness of the community and its results aren’t challenged within 2 weeks. > > It is possible that other off-chain decision making practices and tools be integrated and their use should be aligned with this covenant. > > TEC community spaces include the TEC Discord, Discourse and Github communities. Other forums or social platforms which may emerge in the future are expected to adhere to this covenant. > Enforcement > > TEC intends to use Gravity and make use of its graduated sanctions in order to ensure community standards. > > The Gravity group aims to support the TEC by: > > Actively promoting trust and managing conflict between individuals, groups, and the community as a whole. > Recognize boundaries and areas of potential dispute, as well as explicit violations of boundaries between individuals, groups, and the community as a whole. > Supporting communication between community members and encouraging active participation. > Promote community resilience and long-lasting human relationships by proactively co-creating boundaries, discussion and exchange in a system of shared values. > Promote Advice Processes regarding the implementation of graduated sanctions 1 and commit to its use with respect to all individuals. # Hack Our Own Values and Resolution *Use this area to hack together our own Values and Conflict Resolution Part of our Constitution* #### Discuss Section > [name=boilerrat]TEC has one of the more interesting overall documents imho. Of note is it is a fork of 1Hive's covenant. So that one is worth noting as well. > [https://forum.tecommons.org/t/tec-community-covenant/572](https://forum.tecommons.org/t/tec-community-covenant/572) > > [https://github.com/thelastjosh/govbase/blob/master/documents/constitutions/1Hive_Community_Covenant.md](https://github.com/thelastjosh/govbase/blob/master/documents/constitutions/1Hive_Community_Covenant.md) [](https://) #### Moon DAO Values # Our Values We uphold values of inclusion, peace, transparency, freedom of organization and speech. Space should be in the hands of the people, not any one nation or private entity. As such, MoonDAO will support funding for individuals to go to space, acquisition and governance of symbolic assets (like lunar asteroids, or the lunar manual used in the first space mission), and fund future space research and exploration as it fits into the mission of becoming a governing body for the moon and other celestial bodies. MoonDAO is going to the moon!!

    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
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    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