Commodore Account
    • 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
    [Proposal for Stewardship Team] INTRODUCTION This proposal recommends the implementation of a Stewardship Team (ST). The Stewardship Team will consist of 5-7 high-context members who will provide leadership and direction to the DAO, establish priorities, and help manage proposals and expensive projects on behalf of all members. The ST will be able to solve key problems within Krause House such as developing a clear roadmap or DAO-wide understanding of what projects are most urgent. The ST will also be a robust team that can protect against potential future issues like hostile whale takeovers or Sybil attacks. This team would be compensated on a biweekly basis (every 2 weeks) and members could be elected or removed based on community voting. Why? Krause House DAO could greatly benefit from a strong sense of direction. The vast majority of DAO members do not have a clear idea of the following: - Short-term objectives or goals (beyond the less actionable ones of buying a team which is typically understood as building treasury and building community) - Priorities for Season 2 and beyond, including the most important initiatives - Currently operating projects and where projects can collaborate This lack of awareness creates highly siloed projects and a huge barrier to new contributors who don’t know what they should work on. As proposals begin coming in for Season #2, Krause House DAO also needs a team of people who can negotiate with project leads, monitor expensive initiatives closely, and keep others up to date on treasury information. This team will also serve the DAO and protect against a variety of malicious proposals. RESPONSIBILITIES OF STEWARDSHIP TEAM The Stewardship Team (ST) will be responsible for several key things, including the tasks currently done by the Teams Team and Proposal Team. Facilitate DAO-wide Clarity and Focus The ST will host a meeting at least once a week (but up to as many times as is valuable) to discuss DAO issues, governance, compensation, treasury, ongoing projects, priorities, roadmap, goals/objectives and any other important matters. This will be a time for new people to join in and get scope on the DAO’s operations, and for existing members to tune in to hear the latest weekly developments. The ST will also regularly update asynchronous materials that facilitate clarity such as Notion documentation and the website. Manage Proposals and the Treasury The ST will review proposals for projects and discuss compensation, collaborations, expectations, and timelines with project leads. Proposals will be moved to Snapshot for a community vote once the project’s scope and compensation are clearly aligned with the DAO’s priorities. The ST will monitor expensive projects after they have received funding and hold the projects accountable to ensure that the DAO gets as much value out of its treasury as possible. The ST will also submit requests for new projects/proposals to facilitate an easy way for contributors to become Project Leads. Administration This includes controlling permissions for DAO members to Discord, Twitter, Notion and the multisig. These administrative duties will also include managing a central repository (Notion) for text files, spreadsheets, brand assets and other relevant working documents. Compensation The Stewardship Team will be streamed 400 $KRAUSE every two weeks. They will then be able to distribute this compensation amongst themselves based on what is fair. This compensation can be modified based on whether the DAO feels as though the value provided by the Stewardship Team is worth the $KRAUSE. A community proposal can be submitted to reduce, increase, or terminate the funding stream. STEWARDSHIP TEAM NOMINEES FOR SEASON 2 The following high-context and experienced members are being nominated for positions on the Stewardship Team for Season 2: [Proposal for Stewardship Team] INTRODUCTION This proposal recommends the implementation of a Stewardship Team (ST). The Stewardship Team will consist of 5-7 high-context members who will provide leadership and direction to the DAO, establish priorities, and help manage proposals and expensive projects on behalf of all members. The ST will be able to solve key problems within Krause House such as developing a clear roadmap or DAO-wide understanding of what projects are most urgent. The ST will also be a robust team that can protect against potential future issues like hostile whale takeovers or Sybil attacks. This team would be compensated on a biweekly basis (every 2 weeks) and members could be elected or removed based on community voting. Why? Krause House DAO could greatly benefit from a strong sense of direction. The vast majority of DAO members do not have a clear idea of the following: - Short-term objectives or goals (beyond the less actionable ones of buying a team which is typically understood as building treasury and building community) - Priorities for Season 2 and beyond, including the most important initiatives - Currently operating projects and where projects can collaborate This lack of awareness creates highly siloed projects and a huge barrier to new contributors who don’t know what they should work on. As proposals begin coming in for Season #2, Krause House DAO also needs a team of people who can negotiate with project leads, monitor expensive initiatives closely, and keep others up to date on treasury information. This team will also serve the DAO and protect against a variety of malicious proposals. RESPONSIBILITIES OF STEWARDSHIP TEAM The Stewardship Team (ST) will be responsible for several key things, including the tasks currently done by the Teams Team and Proposal Team. Facilitate DAO-wide Clarity and Focus The ST will host a meeting at least once a week (but up to as many times as is valuable) to discuss DAO issues, governance, compensation, treasury, ongoing projects, priorities, roadmap, goals/objectives and any other important matters. This will be a time for new people to join in and get scope on the DAO’s operations, and for existing members to tune in to hear the latest weekly developments. The ST will also regularly update asynchronous materials that facilitate clarity such as Notion documentation and the website. Manage Proposals and the Treasury The ST will review proposals for projects and discuss compensation, collaborations, expectations, and timelines with project leads. Proposals will be moved to Snapshot for a community vote once the project’s scope and compensation are clearly aligned with the DAO’s priorities. The ST will monitor expensive projects after they have received funding and hold the projects accountable to ensure that the DAO gets as much value out of its treasury as possible. The ST will also submit requests for new projects/proposals to facilitate an easy way for contributors to become Project Leads. Administration This includes controlling permissions for DAO members to Discord, Twitter, Notion and the multisig. These administrative duties will also include managing a central repository (Notion) for text files, spreadsheets, brand assets and other relevant working documents. Compensation The Stewardship Team will be streamed 400 $KRAUSE every two weeks. They will then be able to distribute this compensation amongst themselves based on what is fair. This compensation can be modified based on whether the DAO feels as though the value provided by the Stewardship Team is worth the $KRAUSE. A community proposal can be submitted to reduce, increase, or terminate the funding stream. STEWARDSHIP TEAM NOMINEES FOR SEASON 2 The following high-context and experienced members are being nominated for positions on the Stewardship Team for Season 2: - commodore#0145 - flexchapman#5934 - GladRobot#6845 - Lewwwk#4227 - Magnus#3558 - Dogstoevsky#0585 - eli_#0534 - Mario Lopes#2725 Defining Success This team’s objective is relatively ambiguous, therefore we’d like to pre-define a series of ways to determine if this team is operating successfully. * Has the ST hosted consistent weekly meetings? * Have the weekly ST meetings been well run, public (to ticket holders), & helpful? * Has the ST helped people turn general ideas into specific actionable proposals? * Has the ST successfully vetted proposals? Helping good ideas turn into proposals and giving constructive feedback on ideas potentially harmful to the DAO? * Has the ST remained engaged with project leaders offering support as they need? * Has the ST remained contextually aware of the large initiatives the DAO is pursuing to provide maximum context for decision making? * Has the ST operated in alignment with the mission, vision, and values of our DAO?

    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