abbeytitcomb
    • 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
    # [Org Design] Funding Core Teams: Mission, Vision, and Purpose A major takeaway from the [Paris Contributor Offsite](https://www.notion.so/forest-text-046/Paris-Offsite-July-2022-Notes-Recording-89bf519f21a7480d95917754f43b6327) was that a high-level (purpose/vision/mission/manifesto) statement should exist and be formalized as the “North Star” to guide the Core Teams as we [transition to the DAO](https://radicle.community/t/the-next-phase-of-the-radicledao/2776). This takeaway confirmed the [Collaborative Vision](https://radicle.community/t/radicle-2022-beyond-a-collaborative-vision/2873) work started by @thom and myself a month prior. As the Org Design workstream continues its work (see [Part 1](https://radicle.community/t/org-design-funding-core-teams-principles-criteria-part-1/2994) and [Part 2](https://radicle.community/t/org-design-funding-core-teams-principles-criteria-part-2/3013) — our recent deliverables), we'd like to keep pushing this initiative forward. Here is the first draft of a proposed **Mission, Vision, and Purpose** document based on contributor feedback sourced from the collaborative vision exercise. ## Radicle's Mission, Vision, and Purpose ### Objective Co-create a high-level mission & purpose to guide the decisions of the Core Development Org and work of its Core Teams. It should be long-term and remain fairly static, but Core Teams have the ability revise & update it as long as its done in a public, transparent, and community-inclusive way. It's important to note that this is *not* proposing a DAO-wide Mission, Vision, and Purpose at this point in time. This document will be used to guide the Core Development Org. Other Orgs (e.g. RGP, EGF) can choose to align with the document as well. In the future, we can imagine a Mission, Vision, and Purpose being ratified across the DAO – probably one that spawns from this document. ## Survey Analysis Below 👇 is a synthesis of the responses to the internal survey collected in June. This adds extra context to the messaging kit below. [https://miro.com/app/board/uXjVOrQRxAY=/](https://miro.com/app/board/uXjVOrQRxAY=/) Problem Statement Radicle Core Belief Mission Vision Values Radicle DAO Brand Promise Target Audience ### Problem Statement - Our reliance centralized platforms & corporations for the production & distriution of critical open source infrastructure is inherently unsustainable. - Open-source technologies that protect online civil liberties require non-corporate decentralized forms to ensure long-term neutrality, viability, and capture resistance. ### Radicle Core Belief At Radicle we believe… * Free and open source software is a *public good* and public goods *can* be funded sustainably. * We need censorship-resistant, permissionless, trust-minized, and sustainable infrastructure to free the Internet. * The future of open-source software will be written by self-sustaining, community owned & governed, decentralized online organizations. The technology we build abides by the following principles: * Free and open source — We build free software because we respect user’s essential freedoms: the freedom to run it, to study and change it, and to redistribute copies with or without changes. * Censorship-resistant — We build software that is technically, socially, and politically resilient. * Permissionless — We build software that anyone has the freedom to use to collaborate with others. No single party can prevent anyone from accessing it. * Extensible & Protocol-First — We build extensible, interoperable, modular software because it makes us a better citizen of the Internet. :saluting_face: * Easy-to-use — We build easy-to-use software because we believe making decentralized technology user-friendly is necessary to ensure it can compete with centralized alternatives. * Trust-minimized — We build software that has no single point of failure and we minimize or eliminate our software’s reliance on trusted third parties. * Local-first — We believe local-first architectures lead to a better user experience. * Social-centric — We build social-centric software so you can choose what you see, choose what you block, and choose who you can trust. ### Mission *What we are doing day-by-day to make our vision a reality. Mission may last 2-3 years.* * Build unstoppable, permissionless, decentralized open-source infrastructure for developers. * Enable a sustainble future for open-source maintainers & contributors, where they can get paid for their work without relying on intermediaries. * Become a decentralized, community-owned & operated, self-sustaining free and open-source project. ### Vision ⭐ *Our view of the future we want to live in. Vision lasts a long time.* * A world where we can live as free citizens on the Internet, with our digital rights protected by capture-resistant free and open source software. * A world where we control the software the use, not the other way around. * A truly free and open Internet that protects our digital rights. * A world in which free software is not dependent on corporate intermediaries. ### Values ⭐ > I feel like this should just be where we publish our organizational principles. Not sure if there should be a different set of values that we list here. * Autonomy — We enable as much individual and team autonomy as possible to enable them to build faster and work more smoothly. * Trust — We optimistically trust contributors to do the right thing to enable them to build faster and work more smoothly. * Collective responsibility — We are responsible for holding each other accountable rather than relying on a hierarchy. * Open-Source — We are open and transparent where appropriate. * Evolutionary — We encourage experimentation with adaptability in mind. ### RadicleDAO Brand Promise ⭐ *The highest order aspirational benefit we promise to our customers* * **Own your code** * What does it mean to own your code? 1. To have the freedom to run, copy, distribute, study, change and improve the code you use/create 2. To control the production, distribution, and monetization of your code. 3. To guarantee the long-term viability & resilience of your code ### Target Audience ⭐ *Clear defined group of people who we are selling the product to. There may be other audience types who we don't directly sell to.* * Developers/DAOs building free and open source software * Developers/DAOs building privacy-preserving and censorship-resistant software * Developers/DAOs building decentralized and peer-to-peer technologies.

    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