hackbase-type1
Type-1 Hackbase:
    "Liquid shared rented/owned house"
< RFC >

Replication instructions and info.
More → info@totalism.org

Revisions:
    2016-11-20 stub
    2016-12-06 draft
    2017-11-23 updated
    2020-08-15 moveover
    2020-08-20 overview

Related:
    🔗hackbases (there are several types!), 🔗hacking-housing, 🔗puzzles, and 🔗architecture.







Basic idea

____________________________________________________________

Via Hackerspaces.org🔗Hackbase:
    
    A Hackbase or Hackerbase is a Live-in Hackerspace - a hackerspace with a capacity for coliving:
        → everything you would expect from a hackerspace + place to stay (sleep, eat, ...)
        ... this includes being publicly accessible (via a clear and non-discriminatory process)
        able to host short or long-term stays
        → residents cover their own costs (which are usually far less than "normal" lifestyles)
        extension on the practices of sharing already present in hackerspaces
        hosts hacker Residencies and Exchanges

________________________________________________________________





Specifically, "LIQUID" means ...

    * anyone can come, stay & leave at any time

    * the space must thus be able to facilitate that:
        maximize ability to host people, minimize cost
        be highly reconfigurable

    * a place functionally useful for both (co-)living and (co-)working

    * maximize "positive" and "negative" freedom:
        See → Wiki🔗Two_Concepts_of_Liberty
        == Minimum "must", maximum "can"

 




Necessary pieces


    * PLACE → find & choose suitable

        * low-cost !

        * relatively easy to get to, internationally:
            document travel access well!

        * interesting location:
            very populated? (cities, interesting suburbs, ...)
            very natural? (nature, landscapes, ...)

        * relatively free from interference:
            (from neighbours, building owners)

        * somewhat reconfigurable:
            (free to change interior at least to a normal extent)

        * [...]
        ---------------------
        (classification related to 🔗land-attributes) ###



    * EQUIPMENT → tools

        * don't worry too much from the beginning to have everything

        * necessary (house):
            * a functioning kitchen
            * household textile: towels, blankets, pillows, covers, sleeping bags, ...
            * beds & temporary sleep areas
            * other house basics (washing machine, couches, mood lights, ...)
            * basic sound system
            * a medic box

        * necessary (lab):
            * work furniture (ergonomics): table, chairs
            * power plugs everywhere
            * net: internet uplink, house wifi coverage, LAN cables
            * simple house server
            * basic DIY tools: screwdrivers, battery multi-tool...
            * boxes / strong bags to organize things (cables, ...)
            * [...]

        * (CHT reference):
            →🔗stuff (list of equipment)
            →🔗ordering (investigating & ordering new equipment)



    * HOUSE MANUAL → master document

        * open editable by anyone:
            in this way, rules are maintained by consensus
            suggestion: using etherpad + 🔗E2H works best!

        * must contain:
            * basic info (where, purpose, financials, etc)
            * how to get there (travel!)
            * rules, routine & house dynamics:
                (→🔗roles, 🔗newcomers)
            * basic location context:
                nearby shops, transportation points, cultural sites
                (→🔗maps)

        * (CHT reference):
            🔗manual (also partially, 🔗web)



    * INTERIOR ARCHITECTURE → reconfigurable, ergonomic

        * create a transformable ("reconfigurable") space:
            * unfixed roles for rooms! (not separating sleeping/working space)
            * easily movable furniture
            * don't assemble things in a way that are difficult to change
            * use trays for everything:
                (don't clutter any surface directly)
                ### a photo
            * [...]

        * maximize ergonomics:
            quality sitting & work surfaces

        * maximize potential sleeping space:
            * repurposing secondary space (basements, attics, sheds, terraces...)
            * couches!
            * in-house tents!
            * build "sleeping pods"
            * practice "hot-bunking" (see Wiki🔗Hot_Racking (radical)
            * [...]

        * (some more ideas):
            * see 🔗hacking-housing for non-standard architecture inspiration
            * consider smoking and non-smoking places!
            * [...]



    * FINANCES → sustainable, low/no investment

        * do not extract from crew! collect only sustainable costs:
            expected ~400€/month (all inclusive) anywhere in EU

        * find effective suppliers:
            food in bulk, energy, internet, order-in hardware, etc

        * try organising a common work connection:
            CHT example → 🔗coop

        * CHT's detailed & generally proposed implementation:
            →🔗subfinance
            →🔗manual#____BUDGETING ("sustainable contribution") - simpler



    * COMMON WORKFLOW → tools for notes, ideas & guiding action

        * basically, you need a way where any crew can instantly access & contribute to the base 

        * (CHT reference):
            🔗E2H
            🔗workflow, especially "localnet"
            also see parts of 🔗manual



    * PUBLICATION → publish site & promote existence

        * set up a website:
            * a hackerspaces.org entry will do at beginning

        * make the basic listings:
            * your own https://wiki.hackerspaces.org profile
            * link on Hackerspaces.org🔗Hackbases
            * add to 🔗alike
            * join #hackbases on Freenode
            * more!:
                * Nomadwiki
                * HackerCouch
                * [...]

        * consult 🔗pr for more






Existing instances

See:
    → Hackerspaces.org🔗Hackbases
    → https://pad.land/hackbases
    → 🔗alike

Future direction:
    Define inter-coordination infrastructure.
    How can a network of independent bases work together?
    see → 🔗intersub, 🔗consolidation


<----------- this could transclude from #alike via attributes! ###





(Site generated by E2H, an "Etherpad hypermedia" project by @dcht00). Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.


Edit Site

Edit CSS