HackMD
  • API
    API  HackMD API beta testing
    HackMD API is now in beta, join us for a test drive.
    Getting started Got it
      • Create new note
      • Create a note from template
    • API  HackMD API beta testing
      API  HackMD API beta testing
      HackMD API is now in beta, join us for a test drive.
      Getting started Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • ODF (Beta)
      • 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
        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
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML ODF (Beta)
    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
    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
    # **Posted to discuss -- Oskar** ## Session 1 - Openness > The software we create is a public good. It is made available via a free and open source license, for anyone to share, modify and benefit from. We believe in permission-less participation. Deliverables - wall of shame --- [Oskar] Principles will be covered not in order - we want to build up to Liberty, have tried to pair them so that they make more sense. Oskar's opening remarks are not gospel, you might have your own interpretation of the principles. Discussed why we are doing these sessions - increase engagement in high resolution, and develop collective ability to think about Principles. Pairing Principles helps see the tensions, positives and negatives. Talked through [intro slides](https://hackmd.io/p/B1KE8Q79Q#/). --- [Michael] How do you feel about the fact that we have guardians, can we talk about having a completely permissionless codebase, Corey? [Corey] Difficult to answer, I hope so. We can't say that anyone can just do what they want. Proof of work is a push forward in creating open permissionless networks, knew it was fair due to how incentives were structured; how do you do that in a codebase? We need some type of hierarchy around who gets to build a codebase. [Ricardo] We should study how others, e.g. Linux handle this [Igor] Linux Foundation was essentially a few people’s decicions as governance
Linus + one or two people who decided which patches to allow [Michael] Are we naive for thinking it can be done differently? [Oskar] POW - by virtue of having a free license, anyone can make changes. You can just fork it and run own version of Status. Protocol that has most consensus gets followers, doesn't preclude someone from forking it and making their own universe. [Corey] Don't have to use offical Status client to use Status, we're giving you the main signal to go off and do something different. We have to be certain that the base layer protocol is secure. [Michael] How do we demonstrate that the client is secure, how do we present that to people? [Ricardo] This would be one layer up in e.g. Android, people should be able to check it above the level of the app. This technology hasn't yet been realised. [Michael] Can we use Discuss DMs instead of emails? Not practical if we need to contact people outside Status network. **Action item** - describe centralised/proprietary services we're using and be clear about why that is and why it's justified. Services policy for why we use services that we do. [rewritten as WoS -- Oskar] Making good progress on Status as our IM client, but let's separate out other collaboration tools like email, discussion etc. Can justify Google in some way as it helps with `continuance`, but need to balance those things against `openness`. [Adam] Decentralised tech harder to debug overall. Openness is a prerequisite to inclusivity. [Michael] We'd like to have completely open finances, what are our barriers there? [Yessin] 1. Protection of individuals' privacy. People may not want their salary public, due to e.g. tax optimisation purposes or other personal interests. 2. HR centralised point of view, people may start comparing salaries and become unhappy with situation. Not an absolute barrier, but a consideration. [Chad] Doesn't need to happen instantly, but a pathway to openness would be great. In prior company, financial dashboards transparently reflected burn rate, headcount, etc. Non-sensitive info, but was super helpful for context. [Michael] Can we have headcount and total salary cost? [Yessin] Open KPIs can happen. [Oskar] Shared examples from Buffer and NomadList: https://buffer.com/salary https://nomadlist.com/open [Barry] Have experienced this before in another company - settled on voluntary disclosure as not everyone wanted to participate. [Adam] Can we focus at org level first re financials? [Yessin] What can't be made public - individual salaries. Other financial information can be made public. [Ricardo] What about changing how we make payments, e.g. salaries > bounties? [Michael] As we DAOify, we have legacy obligations. Dialogue should shift from optimising centralised legacy company to how we build into the future. Can't switch off the legacy entity completely, DAO will interface with that long into the future. [Yessin] DAO would be largely without legal entity footprint. Maybe contributors would form their own legal entities in each jurisdiction to interface with the DAO. [Igor] Would radical transparency lead to overall higher costs? [Ricardo] Some things need to have delayed openness, e.g. sensitive projects, can talk about these later but need to act first. [JB] Using language/knowledge that the general public can't understand - barrier to adoption. To be open, may have to compromise on other things to reach a wider audience. Although we're being open on Discuss, the level of discussion may not resonate with many readers. [Michael] Need our own house in order before we can succintly express that to the mass market. ---- ## Wall of shame - wrt openness ideally Note: not all of this is wall of shame right now 1. Reliance on Google and Slack 2. Not fully open to community contributions 3. Weren't using our own product 4. Closed financial info. Lack of pathway for how we'll get to openness. 5. Balancing openness and disclosure of security issues/vulnerabilities? 6. We don't have an inventory with rationale for centralized/proprietary services. Desired action: describe centralised/proprietary services we're using and be clear about why that is and why it's justified. Services policy for why we use services that we do. 7. ... 8. ...

    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 Sign in via Google

    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