Hex.Camp
      • 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
      • 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
    • Engagement control
    • 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 Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control 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
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
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Community Creation Guide Hex.Camp is an open source software project which builds software intended to be used by many independently-run communities. For example, [VicHex.ca](https://vichex.ca/) is the community for Victoria, Canada. Hardware and cloud infrastructure is designed to be shared between multiple communities, so there is very little incremental financial cost to creating new communities that can each host millions of websites. We are also designing the infrastructure so that it each community can operate independently when it makes sense to do so. Each community is defined by the following: - a domain name, eg. [VicHex.ca](https://vichex.ca), [SeaHex.org](https://seahex.org), [VanHex.org](https://vanhex.ca) * we want each community to have it's own domain name * ideally short and memorable for local people. If a geographic top level domain is available (eg. ".ca", ".us"), it would be good to use that. Domain names with "Hex" in them are usually available for purchase, but it is not necessary to have "Hex" in the name. * initially, as the project is bootstrapping, the domain names will be held by the central project. We'd like to eventually transfer ownership of the domains to trusted entities within each community. New communities are welcome to acquire their own domain names, but they should be held by some sort of community-base "trustee" to prevent a situation where the owner of the domain takes the community hostage. * in the event that a community has to change it's domain name, the hexagon IDs for each website will remain static, so it would be feasible to rewrite all the links, eg. [6kgveaaaaaaa.seahex.org](https://6kgveaaaaaaa.seahex.org/) could be changed to point at "6kgveaaaaaaa.seahex.us" instead. * Coming soon: We will be using the "peerhex.org" domain and subdomains as a placeholder for incubating new cities and areas. This way, we can have global coverage, even if we have no users yet in some areas. - a geographic "footprint" - defined as a set of [H3 hexagonal cells](https://h3geo.org/) that covers the area of the community * typically city-scale or region-scale initially * boundaries don't necessarily have to follow political boundaries, which can shift over time and are often disputed. Local cultural usefulness should be prioritized. That said, multi-jurisdiction regions may difficulties if local laws are in conflict and must be complied with. Hex.Camp covers the entire globe, so regions in active conflict may require special handling. * neighbouring communities must "tile" - that is, any H3 hexagon ID must exclusively belong to one community, but not the other * communities may be nested within other communities to form a hierarchy - eg. a neighbourhood community within a city * in some cases, a community might have more than one "parent" community in the hierarchy (a node in a [Directed Acyclic Graph](https://en.wikipedia.org/wiki/Directed_acyclic_graph)), for example a city that is on the border between two larger regions. eg. [Kansas City](https://en.wikipedia.org/wiki/Kansas_City_metropolitan_area) is mostly in Missouri but some of it is in Kansas. * the footprint can be defined as a CSV file: - [VicHex.ca](https://github.com/hexcamp/hexcamp-community-vichex/blob/main/vichex.ca.csv) - [SeaHex.org](https://github.com/hexcamp/hexcamp-community-seahex/blob/main/seahex.org.csv) - [VanHex.ca](https://github.com/hexcamp/hexcamp-community-vanhex/blob/main/vanhex.ca.csv) * it would be nice to have a map viewer tool to show the community boundary (not built yet) * it would also be nice to have a tool that will resolve any H3 hexagon ID and return which community it belongs to (not build yet) * initially, the footprint definition can be somewhat coarse. For example, the VanHex.ca definition includes some hexagons that are large enough that they cross the Canada-US border. In the future, the definition could be refined with smaller hexagons to make it more fine-grained. Hypothetically, when definitions change, some locations might change from one community to another, but the hexagon IDs would stay the same. For affected websites, HTTP redirects could be used when this situation arises. - a set of users to act as "community stewards" * people that have local knowledge and who want to better their community * help to build governance structures * help make moderation decisions * help filter local news and events * make decisions about hexagon reservations and allocations * help fundraise and allocate where funds go * deal with local legal requirements * make feature requests to the central Hex.Camp developers * "incubating" communities might use people from outside the community in order to bootstrap * the [New_ Public](https://newpublic.org/) project has a similar concept with their [Neighborhood Steward Fellowship](https://newpublic.org/fellowship) and [Launchpad program](https://localstewards.newpublic.org/) ... we'll be watching what they do * because communities are local in nature, it is possible to meet up regularly in a local setting like a coffee shop ## Community Resources - a git repo to contain hexagon reservations and allocations * some hexagons are reserved for use by the global Hex.Camp project * [GitHub: hexcamp/hexcamp-community-vichex](https://github.com/hexcamp/hexcamp-community-vichex) * [GitHub: hexcamp/hexcamp-community-seahex](https://github.com/hexcamp/hexcamp-community-seahex) - a landing page * [VicHex.ca](https://vichex.ca/) - GitHub: [vichex-landing-page](https://github.com/hexcamp/vichex-landing-page) ## More Community Resources (to be documented...) - a welcome page (GitHub/HackMD) - DNS configuration - Kubernetes / ArgoCD configuration - an IPFS Cluster - map tiles - search - an AT Protocol PDS server - a local news feed (Graze.Social) - publishing/repair pipeline - authentication - secrets management - monitoring - fundraising for sustainability and endowment fund - financial accounting - reporting # Source Document * [HackMD](https://hackmd.io/VUyQTJFRQbGbzqnwgeoykw) * [GitHub](https://github.com/hexcamp/hackmd-notes/blob/main/hexcamp-dev-portal/communities/index.md) Publish-to: [6kgru5w3nwza.vichex.ca/communities/](https://6kgru5w3nwza.vichex.ca/communities/)

    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