Do good, better. CoActivate is a platform for social activism.

  • Brainstorm

last modified September 22, 2010 by strypey

  •  fundamental synergies
    • without permaculture, or something similar, we will not have a biosphere capable of supporting complex life forms like ourselves, let alone a noosphere in which free culture can exist
    • without free culture, or something similar, we will not have a noosphere capable of supporting the diversity of ideas, perspectives and point of entry that we need to make global permaculture workable
    • permaculture offers the hope of making information technology sustainable, and embedding it in self-sustaining intentional communities of free people
    • free culture offers the tools of free code software and libre knowledge systems that offer the hope of every person on the planet having access to the knowledge they need to help their community become self-sustaining, and tolerant of freedom, 
    • permaculture and free software are both examples of creative (art) use of technology (science), grounded in values (ethics), illustrating the integration of Wilbur's " big three
    • both permaculture and free culture value systems that include plenty of redundancy, back-up food supplies, and data back-ups
    • permaculture has an anlysis of building common environmental capital to increase the potential for income, while living within it - while free culture sees source code and other high-value information as common digital capital, and leverages it to create income
  • green maps (environmental purpose, open development process/ crowd-sourced, free code implementation, ownership of symbols and data layers?)
  • Crowdsourced disaster relief management
    • Sahana Software Foundation and Ushahidi - Disaster relief management software
    • Crisis Commons/ Crisis Camps - using IT to help remotely - low-carbon aid work
    • Permacorp International - focalising relief for Haiti post-earthquake
    • Biotecture Institute  - Earthship architect Michael Reynolds travels to Andaman Islands after tsunami to teach locals to rebuild their housing in a self-sufficient fashion, so rather than remaining dependent on foreign governments, corporations, and NGOs for aid (Garbage Warrior doco)
    • Permculture relief history; Geoff Lawton - rebuilding villages in Iraq, cleaning up after refugee camps in Lebanon/ Jordan (?); Robyn Francis - leads team to Cuba to help them survive the 'Special Period' (Power of Community doco); Alice Hamilton - helping Palestinians survive using permaculture
    • PINZ Disaster Response project - Discussions underway to establish a group of permaculturists resident in the Pacific to do the same sort of thing on a regular basis.
    • Council for International Development looking for groups like this to fund - sensitive to local culture and conditions, aiming to help people become self-sufficient rather than dependent on foreign aid
  • ongoing development in both free software and permaculture helps develop community communication, and facilities, and builds resilience
  •  conservations commons
    • collecting of data on biodiversity to help conservations efforts
    • to what degree is free code software being used by conservationists?
    • does copyright law apply to datasets - ie is CC licensing effective to protect openness of data?
    • to what degree does openness of data make wildlife vulnerable to poaching and biopiracy (genetic poaching)
  • need to take some of the most pertinent issues in the original article and expand on them
    • TPM/ DRM and Terminator seeds - similiar in coding against replication, different in that seeds self-replicate whereas DRM'd files need other code to replicate them, just as genes need proteins to replicate them
    • free code development communities - variety of scales and types, 'rough consensus and running code'  = 'rough consensus and growing stuff'
    • Stallman and Raymond (Perens? O'Reilly) - Mollison and Holmgren (Hopkins and Green Wizard guy?)
    • licensing and certification - differences: software licenses are more technical (what you can and can't do with the code), food certification is more descriptive (how the food was and wasn't grown), software licensing is a hack on copyright, food certification is a hack on public health and hygiene regulations 
    • source banks (Sourceforge, Savannah, GitHub etc () seed banks (Koanga Gardens)

  • Holmgren's 12 permaculture design principles (from Principles and Pathways Beyond Sustainability) applied to computing, software, internet
    • Observe and interact - By taking time to engage with nature we can design solutions that suit our particular situation.
      • agile development?
    • Catch and store energy - By developing systems that collect resources at peak abundance, we can use them in times of need.
    • Obtain a yield - Ensure that you are getting truly useful rewards as part of the work that you are doing.
    • Apply self-regulation and accept feedback - We need to discourage inappropriate activity to ensure that systems can continue to function well.
    • Use and value renewable resources and services - Make the best use of nature's abundance to reduce our consumptive behaviour and dependence on non-renewable resources.
    • Produce no waste - By valuing and making use of all the resources that are available to us, nothing goes to waste.
    • Design from patterns to details - By stepping back, we can observe patterns in nature and society. These can form the backbone of our designs, with the details filled in as we go.
    • Integrate rather than segregate - By putting the right things in the right place, relationships develop between those things and they work together to support each other.
    • Use small and slow solutions - Small and slow systems are easier to maintain than big ones, making better use of local resources and producing more sustainable outcomes.
    • Use and value diversity - Diversity reduces vulnerability to a variety of threats and takes advantage of the unique nature of the environment in which it resides.
    • Use edges and value the marginal - The interface between things is where the most interesting events take place. These are often the most valuable, diverse and productive elements in the system.
    • Creatively use and respond to change - We can have a positive impact on inevitable change by carefully observing, and then intervening at the right time
  •  12 principles of agile software (from the Agile Manifesto) applied to food, fibre, fuel, housing
    • Our highest priority is to satisfy the customer
      through early and continuous delivery
      of valuable software.
    • Welcome changing requirements, even late in
      development. Agile processes harness change for
      the customer's competitive advantage.
    • Deliver working software frequently, from a
      couple of weeks to a couple of months, with a
      preference to the shorter timescale.
    • Business people and developers must work
      together daily throughout the project.
    • Build projects around motivated individuals.
      Give them the environment and support they need,
      and trust them to get the job done.
    • The most efficient and effective method of
      conveying information to and within a development
      team is face-to-face conversation.
    • Working software is the primary measure of progress.
    • Agile processes promote sustainable development.
      The sponsors, developers, and users should be able
      to maintain a constant pace indefinitely.
    • Continuous attention to technical excellence
      and good design enhances agility.
    • Simplicity--the art of maximizing the amount
      of work not done--is essential.
    • The best architectures, requirements, and designs
      emerge from self-organizing teams.
    • At regular intervals, the team reflects on how
      to become more effective, then tunes and adjusts
      its behavior accordingly.

  • 3 permaculture ethics (also from Principles and Pathways) applied to computering, software, internet
    • people care
    • earth care
    • fair share

  • Stallman's four freedoms applied to food, fibre, fuel, housing
    • The freedom to run the program, for any purpose (freedom 0).
    • The freedom to study how the program works, and change it to make it do what you wish (freedom 1). Access to the source code is a precondition for this.
    • The freedom to redistribute copies so you can help your neighbor (freedom 2).
    • The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

  • Another risk area to explore, permaculture and free culture approaches to economics
    • both tend to to rely on gift labour or artisan labour, rather than wage labour
    • both tend to value reasonably flat networks of collaboration, rather than heirarchical chains of command
    • green groups have been exploring community economics with co-ops. LETs, time banking, credit unions, and genuine wealth systems
    • free culture groups are responding with ideas like crowdsourcing investment (eg KickStarter)
    • differences local vs global trade focus - this is sensible as greens are more often trading physical objects or in-person services, where free culture is more often trading digital artifacts and remote services
    • freecycle, skillsharing, couchsurfing, hospitality club, WWOOFing
    • ride-sharing sites
  • patents - software patents and life patents - arguments against each kind, similarities and differences
  • transition - Open Source, CreativeCommons, and TransitionTowns
    • how to get from where we are to a free culture/ permaculture future?
    • is it worth compromising principles in the short term for adoption gains in the long term, where do we draw the line?
    • what are core principles we must never compromise on, and which are more flexible, how do we tell the difference?
    • how do we work with people enmeshed in establishment structures; corporations, territorial (states, councils etc) or sectoral (multinational companies); political parties; standards bodies; NGOs; and community groups, liberal or conservative? 
  • distributed education - libre course materials and networked courses and qualifications based on the permaculture training model
  • collaboration -
    • the barn raising principle - in person working bees - hackfests and permablitzes
    • software development communities and sustainability research networks
    • bar camps and convergences 
  • law suits used to suppress independent innovation
    • Monsanto sues Canadian farmer Percy Shmeizer over Round-Up Ready Soy that has trespassed on his farm
    • SCO sues over claimed inclusion of copyrighted code in Linux kernel
    • RIAA and MPAA suing file-sharers
  • what permaculture can offer free culture
    • survival
    • food, fibre, fuel, shelter, medicine
  • what free culture can offer permaculture
    • wiki-development and online hosting of libre teaching materials
  • compromise between values and pragatism for the sake of adoption
    • slow food ethics/ permaculture ethics vs. corporate organic workflow (Pollan, 'Omnivores Dillema']
    • free software ethics/ agile ethics vs. corporate open source workflow (Open Cores, Apple use of FreeBSD to build Darwin, so it could build the proprietary MacOSx on top)
    • neccesity to set boundaries of unifying phrases like 'free software' or 'slow food' of unity becomes meaningless and therefore useless
  • Direct community involvement
    • commissioning software: Transition network software, Mycelium/ commissioning food: Community Supported Agriculture
    • volunteer tech collectives;,, Indymedia/ Community Gardens, co-opsFood Not Bombs
    • server Colo: Seattle Community Colocation Project/ food co-op: Piko Wholefoods 
  • Climate Camps/ Bar camps - inspiration for CrisisCamps