Merge branch 'main' into google-drive-blog-post

Reviewed-on: #67

.drone.yml

@@ -1,16 +1,39 @@
 ---
 kind: pipeline
-name: default
+name: deploy to swarm.autonomic.zone
 steps:
-  - name: Deploy Autonomic.zone with Dokku
-    image: appleboy/drone-git-push:0.2.0-linux-amd64
+  - name: bundle static
+    image: plugins/docker
     settings:
-      remote: ssh://dokku@dokku.autonomic.zone:222/autonomic.zone
-      ssh_key:
-        from_secret: drone_deploy_key
+      username:
+        from_secret: docker_reg_username
+      password:
+        from_secret: docker_reg_passwd
+      repo: decentral1se/autonomic.zone
+      tags: latest
+
+  - name: deployment
+    image: decentral1se/stack-ssh-deploy:latest
+    settings:
+      stack: jekyll
+      compose: docker-compose.prod.yml
+      deploy_key:
+        from_secret: drone_ssh_swarm.autonomic.zone
+
+  - name: notify rocket chat
+    image: plugins/slack
+    settings:
+      webhook:
+        from_secret: rc_builds_url
+      username: comradebritney
+      channel: "internal.builds"
+      template: "{{repo.owner}}/{{repo.name}} build failed: {{build.link}}"
+    when:
+      status:
+        - failure
 trigger:
   branch:
-    - master
+    - main
   event:
     exclude:
       - pull_request

CHECKS

@@ -1,5 +0,0 @@
-WAIT=3
-TIMEOUT=3
-ATTEMPTS=3
-
-/

CONTRIBUTING.md

@@ -13,24 +13,31 @@ with.
 [writing posts]: https://jekyllrb.com/docs/posts/
 [creating pages]: https://jekyllrb.com/docs/pages/
 
-## Deploy It
+## Development
 
-1. Push your changes to master and Dokku will try to automatically release
-1. See the [Drone dashboard to see the build](https://drone.autonomic.zone/autonomic-cooperative/autonomic.zone/)
+The prerequisites are [Docker](https://www.docker.com/) and [Docker-compose](https://docs.docker.com/compose/).
 
-## Hack On It
+If you're on Debian, installing is easy.
 
-The only prerequisite is [Docker](https://www.docker.com/). If you're on Debian, installing is easy.
+Install Docker.
 
 ```bash
 $ curl -fsSL https://get.docker.com -o get-docker.sh  # have a look if you want
-$ sh get-docker.sh
+$ CHANNEL=stable sh get-docker.sh
 ```
 
-Fire up the container with the following.
+Install Docker-compose.
 
 ```bash
-$ make dockerserver
+$ cd autonomic.zone
+$ python3 -m venv .venv
+$ pip3 install -r requirements.txt
+```
+
+Then fire up the container with the following.
+
+```bash
+$ docker-compose up
 ```
 
 Then visit the locally running website.
@@ -39,9 +46,8 @@ Then visit the locally running website.
 
 Then you can edit the files as normal and reload the page.
 
-## Notes
+To stop the container when you're done, you can run:
 
-1. For configuration, please note, we now use a `dev` environment config file:
-   `_config_dev.yml`. Hence if you edit one `_config*` file and you also want
-   that change to be reflected in the other environment ("dev", "prod") then
-   edit the other file as well!
+```bash
+$ docker-compose stop
+```

Dockerfile

@@ -1,15 +1,17 @@
-FROM decentral1se/jekyll:4
+FROM ruby:2.7.3-alpine
 
 EXPOSE 4000
 
-WORKDIR /usr/src/app
+RUN apk --no-cache add \
+  bash \
+  curl \
+  g++ \
+  git \
+  make
+
+RUN gem install bundler -v 2.1.4
+RUN gem install jekyll -v 4.0.0
 
 COPY . ${WORKDIR}
 
-COPY sbin/* /sbin/
-
-RUN bundle config --global frozen 1
-
 RUN bundle install
-
-ENTRYPOINT ["/sbin/entrypoint.sh"]

Gemfile

@@ -1,4 +1,7 @@
 source "https://rubygems.org"
-ruby '2.6.5'
+
+ruby "2.7.3"
+
 gemspec
-gem 'jekyll-feed'
+
+gem "jekyll-feed"

Gemfile.lock

@@ -40,7 +40,8 @@ GEM
       sassc (> 2.0.1, < 3.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    kramdown (2.1.0)
+    kramdown (2.2.1)
+      rexml
     kramdown-parser-gfm (1.1.0)
       kramdown (~> 2.0)
     liquid (4.0.3)
@@ -50,13 +51,14 @@ GEM
     mercenary (0.3.6)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (4.0.3)
-    rb-fsevent (0.10.3)
+    public_suffix (4.0.4)
+    rb-fsevent (0.10.4)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
-    rouge (3.17.0)
+    rexml (3.2.3)
+    rouge (3.18.0)
     safe_yaml (1.0.5)
-    sassc (2.2.1)
+    sassc (2.3.0)
       ffi (~> 1.9)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
@@ -72,7 +74,7 @@ DEPENDENCIES
   jekyll-feed
 
 RUBY VERSION
-   ruby 2.6.5p114
+   ruby 2.7.3p183
 
 BUNDLED WITH
    2.1.4

Makefile

@@ -1,14 +0,0 @@
-dockerbuild:
-	@docker build -t autonomic/autonomic.zone:testing .
-.PHONY: dockerbuild
-
-dockerserver: dockerbuild
-	@docker run \
-		-e JEKYLL_PORT=4000 \
-		-e JEKYLL_HOST=0.0.0.0 \
-		-e JEKYLL_CONFIG=_config_dev.yml \
-		-v $$(pwd):/usr/src/app \
-		-p 4000:4000 \
-		-d \
-		autonomic/autonomic.zone:testing
-.PHONY: dockerserver

_config.yml

@@ -9,8 +9,7 @@ destination: dist
 sass:
   sass_dir: ./assets/styles
 featured-image-source:
-500px_url:
-github_url:
+include: ["src/.well-known", "src/.nojekyll"]
 mastodon_url: https://sunbeam.city/@autonomic
 twitter_url: https://twitter.com/autonomiccoop
 gitea_url: https://git.autonomic.zone/autonomic-cooperative/

_config_dev.yml

@@ -1,30 +0,0 @@
----
-title: Autonomic Co-operative
-email: helo@autonomic.zone
-description: Sustainability, Transparency, Privacy
-baseurl: ""
-url: ""
-source: src
-destination: dist
-sass:
-  sass_dir: ./assets/styles
-featured-image-source:
-500px_url:
-github_url:
-mastodon_url: https://sunbeam.city/@autonomic
-twitter_url: https://twitter.com/autonomiccoop
-gitea_url: https://git.autonomic.zone/autonomic-cooperative/
-markdown: kramdown
-permalink: pretty
-collections:
-  posts:
-    output: true
-    permalink: /blog/:title/
-  clients:
-    output: false
-exclude:
-  - vendor
-  - Gemfile
-  - Gemfile.lock
-plugins:
-  - jekyll-feed

autonomic.gemspec

@@ -2,13 +2,13 @@
 
 Gem::Specification.new do |spec|
   spec.name        = "autonomic"
-  spec.version     = '0.0.0'
-  spec.date        = '2017-09-24'
+  spec.version     = "0.0.0"
+  spec.date        = "2017-09-24"
   spec.summary     = ""
   spec.description = ""
-  spec.authors     = ['autonomic co-operative']
-  spec.email       = 'autonomic.posteo.net'
-  spec.files       = 'README.md'
+  spec.authors     = ["autonomic co-operative"]
+  spec.email       = "autonomic.posteo.net"
+  spec.files       = "README.md"
 
   spec.add_development_dependency "jekyll", ">= 4"
   spec.add_development_dependency "bundler", ">= 2.1.4"

deploy.d/config.yml

@@ -1,11 +0,0 @@
----
-vars:
-  port: "4000"
-  domain: "autonomic.zone"
-
-env:
-  DOKKU_LETSENCRYPT_EMAIL: "helo@autonomic.zone"
-  JEKYLL_CONFIG: "_config_prod.yml"
-  JEKYLL_ENV: "production"
-  JEKYLL_HOST: "0.0.0.0"
-  JEKYLL_PORT: "4000"

docker-compose.prod.yml

@@ -0,0 +1,35 @@
+---
+version: "3.8"
+
+services:
+  jekyll:
+    image: decentral1se/autonomic.zone:latest
+    command: |
+      bundle exec
+        jekyll serve --host 0.0.0.0 --trace
+    environment:
+      JEKYLL_ENV: production
+    networks:
+      - proxy
+    healthcheck:
+      test: ["CMD", "curl", "-f", "http://localhost:4000"]
+      interval: 15s
+      timeout: 10s
+      retries: 10
+      start_period: 20s
+    deploy:
+      update_config:
+        failure_action: rollback
+        order: start-first
+      labels:
+        - "traefik.enable=true"
+        - "traefik.http.services.jekyll.loadbalancer.server.port=4000"
+        - "traefik.http.routers.jekyll.rule=Host(`autonomic.zone`)"
+        - "traefik.http.routers.jekyll.entrypoints=web-secure"
+        - "traefik.http.routers.jekyll.tls.certresolver=production"
+        - "traefik.http.routers.jekyll.tls.options=default@file"
+        - "traefik.http.routers.jekyll.middlewares=security@file"
+
+networks:
+  proxy:
+    external: true

docker-compose.yml

@@ -0,0 +1,13 @@
+---
+version: "3.8"
+
+services:
+  jekyll:
+    image: decentral1se/autonomic.zone:latest
+    command: |
+      bundle exec
+        jekyll serve --watch --host 0.0.0.0 --force_polling --trace
+    volumes:
+      - ".:/srv/jekyll"
+    ports:
+      - "4000:4000"

renovate.json

@@ -0,0 +1,6 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "config:base"
+  ]
+}

requirements.txt

@@ -0,0 +1 @@
+docker-compose==1.29.1

sbin/entrypoint.sh

@@ -1,24 +0,0 @@
-#!/bin/bash
-
-set -eu -o pipefail
-
-# Fire up Jekyll with the right configuration
-run_jekyll() {
-  set -eu
-
-  bundle exec jekyll serve \
-    --config "$JEKYLL_CONFIG" \
-    --host "$JEKYLL_HOST" \
-    --port "$JEKYLL_PORT" \
-    --trace \
-    --verbose
-}
-
-# Main entrypoint
-main() {
-  set -eu
-
-  run_jekyll
-}
-
-main

src/.well-known/autonomic.zone/matrix/server

@@ -0,0 +1,3 @@
+{ 
+"m.server": "matrix.autonomic.zone:443" 
+}

src/_includes/footer.html

@@ -7,9 +7,15 @@
         Contact us to discuss your project's needs and arrange a consultation:</br>
         <b><a href="mailto:helo@autonomic.zone">helo@autonomic.zone</a></b></br></br>
         <b><a href="{{ '/assets/pgp/autonomic-key.asc' | relative_url }}">Download PGP key</a></b></br>
-        <a href= "https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/src/branch/master/src/assets/pgp"> Verify fingerprint:</a><code id="fingerprint">82FC 87C5 1A71 902F DC10 2CF5 4F90 D55B B24B 1147</code>
+        <a href= "https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/src/branch/main/src/assets/pgp"> Verify fingerprint:</a><code id="fingerprint">82FC 87C5 1A71 902F DC10 2CF5 4F90 D55B B24B 1147</code>
 
       <ul class="icons" style="margin-bottom: 0; padding-top: 1em">
+        <li>
+          <a title="RSS Feed" rel="me" href="{{ '/feed.xml' | absolute_url }}" style="border-bottom: none">
+            <!-- This SVG needs to be changed if you change the colour scheme as it is a massive hack. -->
+            <img alt="rss" style="height: 2rem;color: #fff" src="{{ '/assets/svg/rss-square-solid.svg' | absolute_url }}">
+          </a>
+        </li>
         <li>
           <a title="Twitter" rel="noopener" href="{{ site.twitter_url }}" style="border-bottom: none">
             <img alt="twitter" style="height: 2rem;" src="{{ '/assets/svg/twitter-brands.svg' | absolute_url }}">
@@ -48,7 +54,11 @@
         </address></br>
           We are a Co-operative Society registered with the <a href="https://mutuals.fca.org.uk/Search/Society/30380">FCA</a>. 
           <b>Registration Number: 4597 </b>
+          </br></br>
       </div>
+     <div style="vertical-align: bottom;">
+     <a href="{{ '/privacy' | relative_url }}">Privacy Policy</a> - <a href="{{ '/terms' | relative_url }}">Terms of Service</a> - <a href="{{ '/gdpr' | relative_url }}">GDPR</a>
+     </div>
     </div>
   </div>
 </footer>

src/_includes/services.html

@@ -14,7 +14,7 @@
         <div>
           <h3>Websites</h3>
           <p>
-            We offer <a href="https://wordpress.com/">Wordpress</a> and static sites. Either managed or unmanaged with frictionless tools for editing and publishing that empower users. <a href="https://matomo.org/">Matamo</a> provides ethical analytics to measure impact. 
+            We offer <a href="https://wordpress.com/">Wordpress</a> and static sites. Either managed or unmanaged with frictionless tools for editing and publishing that empower users. <a href="https://matomo.org/">Matomo</a> provides ethical analytics to measure impact. 
           </p>
           </div>
       </li>

src/_posts/2020-04-23-dat-py.md

@@ -0,0 +1,52 @@
+---
+layout: post
+title: Hyperpy, the punk-to-punk protocol in Python
+description: A new Python implementation of the Hypercore protocol is cooking at Autonomic
+image: 2020-04-23-dat-protocol.png
+category: technology, peer-to-peer, hypercore-protocol
+date: 2020-04-23
+---
+
+# Hyperpy, the punk-to-punk protocol in Python
+
+We're quite excited by the new wave of community-developed peer-to-peer
+technology. [Scuttlebutt], [Cabal], [Mapeo] and [Beaker browser] are inspiring
+examples of software which show that technology can be built to operate without
+running on centralised commercially-owned infrastructure (e.g. WhatsApp).
+
+One of the underlying innovations for these technologies is the [Hypercore
+protocol], which is a way of describing how two computers can send information
+to each other directly.
+
+Today, the reference implementation of the Hypercore protocol is written in
+Javascript. The Javascript ecosystem has proved to be remarkably flexible for
+advancing this next generation of tools. Simple methods of publishing (npm
+publish), well-established distribution channels (the browser) and a
+[philosophy of modularity] have enabled so many to get started with building
+peer-to-peer technology.
+
+However, there is a great need for other languages and ecosystems to benefit
+from the tools and concepts that are being developed based on the reference
+implementation. People from all walks of life need a working implementation in
+their preferred language of choice. In response to this, we are seeing projects
+like [Datrs] and [Datcxx] emerge (please note, the Hypercore protocol was once
+called the Dat protocol, see [this blog post] for more information).
+
+Alongside these efforts, a member of Autonomic has begun to work on Hyperpy, a
+Python-based implementation of the Hypercore protocol. The project proposes a
+roadmap but offers no deadlines and receives no funding at current status.
+
+However slowly, things are moving along. Further progress updates will be
+posted on this blog as they come in. All development is taking place on
+[git.autonomic.zone/hyperpy].
+
+[scuttlebutt]: https://scuttlebutt.nz/
+[cabal]: https://cabal.chat/
+[mapeo]: https://www.digital-democracy.org/mapeo/
+[beaker browser]: https://beakerbrowser.com/
+[hypercore protocol]: https://hypercore-protocol.org/
+[philosophy of modularity]: https://mafinto.sh/blog/pragmatic-modularity.html
+[datrs]: https://github.com/datrs/
+[datcxx]: https://datcxx.github.io/
+[git.autonomic.zone/hyperpy]: https://git.autonomic.zone/hyperpy/
+[this blog post]: https://blog.datproject.org/2020/05/15/dat-protocol-renamed-hypercore-protocol/

src/_posts/2021-01-25-how-we-make-decisions.md

@@ -0,0 +1,72 @@
+---
+layout: post
+title: How we make decisions
+description: Our collective's horizontal decision making process
+image: trees.jpg
+category: decision making, democracy
+date: 2021-01-21
+---
+
+# How we make decisions
+In Autonomic, we make decisions collectively, while also attempting to empower autonomous action by individual workers. 
+
+We designed our decision making process using decision making tools we had experienced through participation in various horizontal organisations. We hope this tool is useful to others in the struggle for a better world.
+
+Our decisions can be split intro three categories: **Small, Medium and Large**.
+
+## 1) Small - Get on and do the thing
+- No one cares.
+- Made by an individual within the co-op.
+- Could be in any area.
+- Up to individual co-op members to decide if they should just make the decision, or share it with the rest of the co-op to seek consensus.
+
+## 2) Medium - Consensus pending objections
+- About admin and infrastructure.
+- Doesn't have an effect on the direction or operation of the co-op.
+- Give a deadline: unless anyone objects or asks for more time by then, it goes ahead.
+- The deadline must reasonable (a week by default).
+- If any member of the co-op thinks it's a Large decision, achieve Maximum Consensus™ (see below).
+
+## 3) Large - Maximum Consensus™
+- Important decisions affecting the operation, direction, working conditions and finances of the co-op.
+- Consensus voting: addressing any concerns.
+- Can be requested by any member of the co-op for any decision.
+- Input from every co-op member.
+- Whoever proposes Large decisions is responsible for chasing up members for votes.
+- Votes can be in favour, against, abstain (stand aside) or block.
+- One member, one vote.
+
+## Process
+For Medium and Large decisions:
+
+ 1. Write up a proposal in a [HedgeDoc pad](https://hedgedoc.org/).
+ 2. Link to the proposal on the proposals page on our wiki.
+ 3. Announce the decision in the #announcements channel of our internal chat.
+ 4. List the decision on the Decisions page on our wiki.
+ 4. Announce the result in #announcements and record it on the Decisions
+    page of our wiki.
+
+## Proposal format
+(For Medium and Large decisions).
+
+- What you want to change.
+- Who it affects.
+- Size (Medium / Large).
+- Deadline.
+- What chat channel you want discussion to happen in.
+
+## Example proposal
+> @all I'd like to propose (Medium|Large) decision XXX, to write our name as
+"aUtOnOmIc cöööpERATIVE" in all our public communications.
+> 
+> Deadline for votes is DEADLINE – let me know if you need more time to vote than that.
+>
+> Please send absolutely any and all replies in #CHANNEL, not here 🙏
+>
+> 👍 this message for "enthusiastic consent", 🤷 for "stand aside" or 👎 if you need to indicate your extreme disagreement with this idea.
+>
+> 👇 VOTES HERE
+
+## Further resources
+Extra information about decision making processes in co-operatives can be found on the [Seeds for Change website](https://seedsforchange.org.uk/resources).
+

src/_posts/2021-02-11-google-drive.md

@@ -0,0 +1,25 @@
+---
+layout: post
+title: Escaping the Google silo
+description: Opening up your Google Drive and Docs files using open source software
+image: 
+category: technology
+date: 2021-02-11
+---
+
+At Autonomic we always promote using [libre software](https://en.wikipedia.org/wiki/Free_software) whereever possible but we understand that many clients have committed to using [propietary software](https://en.wikipedia.org/wiki/Proprietary_software) either due to legacy decision or because the non-libre solutions are simply more effective and mature.
+
+The Google Workspace set of tools including Google Drive and Google Docs is one such solution. Once your organisation has deployed and is using these Google services, it's extremly difficult to migrate away. Google Docs files are not easy to extract from their propietary format and users are strongly encouragaged to only interact with the documents via the Google Workspace web apps.
+
+This is problematic for organisations that want to approach their data storage with a stratergy that suits them, rather than the Google™️ mandated workflow. 
+There are also [so many criticims](https://en.wikipedia.org/wiki/Criticism_of_Google) that could be made of Google in so many areas (as a [worker's co-operative of privacy advocates](/our-founding-principles), we're of course very biased).
+
+There is also the question of [Google outages](https://en.wikipedia.org/wiki/2020_Google_services_outages) which happened multiple times in 2020. Of course, service outages can and do happen at any scale but it is interesting to note that they are even fairly regular occurance at many of the largest technology companies. When it comes to critical services, offering reduncancy and decentralisation is very difficult to do at the monolithic scale of the tech ginats.
+
+We have been working on a solution for a client to try and make it easier for organisatons to in the short term keep non-Google hosted copies of their data and in the long term, be in a better position to migrate away from Google Workspace all together. Luckily, there is an extensive [Drive](https://developers.google.com/drive/) and [Docs API](https://developers.google.com/docs/api/) which is well documentated and relativley stable.
+
+Our system is designed to pull all of your data out of the Google [walled garden](https://en.wikipedia.org/wiki/Closed_platform) and directly into your control. We host a server for you which runs our code to extract all of your files from Google Drive and covert all of your Google Docs into open document formats (.odt .docx etc.). The files are then made available to your organisation as standard filesystem on your own [Nextcloud](https://nextcloud.com/) instance and then you can do what you want with them. You'll also be able to draw up a support contract with us that suits your needs for both maintaining the server and supporting your users.
+
+We intend to release the source code for our system under a libre license as soon whens we feel it's ready but it still needs some cleaning up and documentation which takes time. When it's released, you'll be able to find on our [Gitea instance](https://git.autonomic.zone/autonomic-cooperative).
+
+If you're interested in hosting this solution for your organsation, feel free to [get in touch](mailto:helo@autonomic.zone).

src/_posts/2021-02-16-co-op-cloud.md

@@ -0,0 +1,99 @@
+---
+layout: post
+title: The Co-operative Cloud
+description: Libre software infrastructure without re-inventing the wheel
+image: coop-cloud.png
+category: coop, co-op, cloud, docker, swarm, libre-software, hosting,
+date: 2021-03-01
+---
+
+Running [libre software] apps and infrastructure for ourselves and our clients is central to what we do at Autonomic. Now, after a year of work, we're stoked to share our "Co-op Cloud" project with the world. We want to make it easier for others to join the party, ditch corporate spyware, and make their tools [sustainable, transparent and private].
+
+## Why a new tool?
+
+We started out using [Cloudron], which provides a very simple-to-use web interface for deploying libre software apps like Nextcloud, Mediawiki, and Rocket.chat with only a few clicks.
+
+Cloudron allowed us to radically reduce our initial and ongoing server costs. We didn't need to maintain a separate server for each service and clients apps could share computing resources whilst containerisation was still allowing us meeting their data privacy needs. Consequently, we've been able to take on many more "solidarity clients", people doing important work, but on a shoestring budget.
+
+As time has gone on, though, we've had a few moments when we questioned our reliance on Cloudron, and whether it was a sustainable choice for us and for our clients. We came to realise:
+
+- Core parts of the system officially [became proprietary] software. This rang alarm bells for us about its long-term future.
+
+- The work to package the available apps is done [entirely by the Cloudron team itself] and doesn't re-use the existing rich ecosystem of libre software packaging work that's already being done. This seems like a big risk. If Cloudron UG, the company behind Cloudron, goes under, someone or some entity would need to take on that laborious, technically specific and non-transferable packaging work or we'd quickly be leaving ourselves and our clients running outdated and unmaintained software.
+
+- Some aspects of Cloudron's architecture were causing problems. Requiring each app to be a single Docker image makes common application deployment configurations impossible (as far as we know, nobody has yet managed to get Mediawiki's visual editor working in Cloudron, for example).
+
+- Not being able to delegate user management to specific groups has made it hard for us to use Cloudron's Single Sign On system with groups who manage their own users.
+
+- Cloudron's central paradigm is focussed on "non-technical" users with the nice web front end for managing apps. However, we found our clients don't actually need to know what "domain name" or "storage volumes" are. That's why they pay us for support. They want it to "just work". Using an interface designed for non-technical users is not suitable for technical users and adds a lot of bloat.
+
+- Cloudron is a bit of a [black box](https://en.wikipedia.org/wiki/Black_box). When something breaks, it breaks hard and requires technical users to respond and investigate and then fix the issues.
+
+- Cloudron doesn't encourage collective and public collaboration on configuration files.
+
+- We have a general fear of centralising so much of our core business on a commercial entity, which could change its prices at any time and have a massive effect on our ability to operate.
+
+## A New Hope
+
+So, around the end of 2019, we tried to map out a few core principles of a system which might work a lot like Cloudron, but give us more guarantees that we can depend on. We started calling the new project Co-op Cloud. Here are some of the principles we identified:
+
+- Always be available under [copyleft licenses] to retain the shared work as part of the [commons](https://en.wikipedia.org/wiki/Commons). We shouldn't rely on creating [artificial scarcity](https://en.wikipedia.org/wiki/Artificial_scarcity) as a business model.
+
+- Work with existing libre software communities who are already packaging and publishing their software (Nextcloud, Gitea, Mediawiki, Rocket.chat, the list goes on and on...). We want to be involved in their community spaces and build bridges between infrastructure, software development and end-users.
+
+- Based on standardised technologies. Any new tools we write should only add a thin layer of usability on top of existing solutions.
+
+- Place democratic governance at the core of the project. We want to collaborate as much as possible with other co-operatives to build up effective decision-making structures so we can all rely on this project far into the future.
+
+- Focus on meeting the needs of small hosting providers with technical workers in order to provide a solid service for their clients.
+
+- Encourage the creation of a configuration commons. Innovations based on Co-op Cloud can easily be shared and worked on collectively.
+
+In our spare time (partly funded by income from working for our wonderful clients 😀) we've been putting the pieces together; and after a year of work (including two "back to the drawing board" moments), we're ready to launch an [alpha version](https://en.wikipedia.org/wiki/Software_release_life_cycle) of Co-op Cloud to the public.
+
+## Co-op Cloud public alpha
+
+Co-op Cloud is a simple packaging format using existing [open standards] to build a catalogue of apps, and a command-line client to read the catalogue and deploy those apps.
+
+If you'd like to learn more about Co-op Cloud, please read [our documentation], where we explain the decisions we've made so far in more depth. What technologies we're using, how we fit into the existing ecosystem, ways to contribute, what apps are available and so on.
+
+We've already been deploying Co-op Cloud as part of "dual power" strategy. We use Co-op Cloud to run some of our own and our clients' infrastructure while continuing with Cloudron and other strategies for the time being. We're seeing promising stability and it's been a joy to work with.
+
+## Enter the configuration commons
+
+You can also dive straight in by installing [`abra`, Co-op Cloud's command-line tool].
+
+You can use Co-op Cloud right now to deploy any of our [30+ apps] to your own physical server or virtual server. These include [Nextcloud](https://nextcloud.com/) (for file, calendar, contacts etc) [Rocket.chat](https://rocket.chat/) for instant messaging, [Keycloak](https://www.keycloak.org/) for Single Sign-On, [Statping](https://statping.com/) for service monitoring, and websites using [Wordpress](https://wordpress.org/), [Pelican](https://blog.getpelican.com/), [Jekyll](https://jekyllrb.com/), or static HTML. See the [app catalogue](https://docs.cloud.autonomic.zone/apps/) for more.
+
+Apps deployed via Co-op Cloud have automatic SSL certificates, and many come with pre-configured e-mail, backups, or Single Sign-On options.
+
+See the [getting started guide](https://docs.cloud.autonomic.zone/overview/) to get moving fast.
+
+## Packaging for Co-op Cloud
+
+Packaging new apps for Co-op Cloud is straightforward in most cases: you can re-use an application's own Docker image (or even `docker-compose.yml` file) with minimal changes. We managed to [make a Co-op Cloud version of the Matomo web analytics platform in about 20 minutes]. This standardised architecture also means that nobody using Co-op Cloud is dependent on Autonomic for updates. When a new Wordpress update comes out, you can easily install it yourself or automatically without waiting for us to update some arcane custom Docker image.
+
+## Next steps
+
+At this point, we'd like to invite other worker co-operatives or democratic collectives to take a look at what we're working on and have a chat with us. We have a public matrix room at `#coopcloud:autonomic.zone`. We think a common platform for hosting libre software infrastructure could make a big difference in terms of what we're able to offer as a movement.
+
+If you're interested in getting involved with Co-op Cloud development, or if you'd like help trying out Co-op Cloud hosted services for yourself or your organisation, please [get in touch].
+
+## Links
+
+- [Documentation](https://cloud.autonomic.zone/)
+- [Source code](https://git.autonomic.zone/coop-cloud)
+- [Public Matrix chat](https://matrix.to/#/#coopcloud:autonomic.zone?via=autonomic.zone)
+
+[libre software]: http://wikieducator.org/Libre
+[sustainable, transparent and private]: /#core-values
+[cloudron]: https://cloudron.io/
+[became proprietary]: https://forum.cloudron.io/topic/2862/why-not-make-cloudron-fully-open-source-again
+[entirely by the cloudron team itself]: https://git.cloudron.io/cloudron
+[our documentation]: https://docs.cloud.autonomic.zone
+[`abra`, co-op cloud's command-line tool]: https://git.autonomic.zone/coop-cloud/abra/
+[30+ apps]: https://git.autonomic.zone/coop-cloud/
+[get in touch]: mailto:helo@autonomic.zone
+[copyleft licenses]: https://www.gnu.org/licenses/copyleft.en.html
+[open standards]: https://compose-spec.io/
+[make a co-op cloud version of the matomo web analytics platform in about 20 minutes]: https://docs.cloud.autonomic.zone/package/

src/assets/svg/rss-square-solid.svg

@@ -0,0 +1 @@
+<svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="rss-square" class="svg-inline--fa fa-rss-square fa-w-14" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><path fill="#ffffff" d="M400 32H48C21.49 32 0 53.49 0 80v352c0 26.51 21.49 48 48 48h352c26.51 0 48-21.49 48-48V80c0-26.51-21.49-48-48-48zM112 416c-26.51 0-48-21.49-48-48s21.49-48 48-48 48 21.49 48 48-21.49 48-48 48zm157.533 0h-34.335c-6.011 0-11.051-4.636-11.442-10.634-5.214-80.05-69.243-143.92-149.123-149.123-5.997-.39-10.633-5.431-10.633-11.441v-34.335c0-6.535 5.468-11.777 11.994-11.425 110.546 5.974 198.997 94.536 204.964 204.964.352 6.526-4.89 11.994-11.425 11.994zm103.027 0h-34.334c-6.161 0-11.175-4.882-11.427-11.038-5.598-136.535-115.204-246.161-251.76-251.76C68.882 152.949 64 147.935 64 141.774V107.44c0-6.454 5.338-11.664 11.787-11.432 167.83 6.025 302.21 141.191 308.205 308.205.232 6.449-4.978 11.787-11.432 11.787z"></path></svg>

src/gdpr.md

@@ -0,0 +1,47 @@
+---
+layout: page
+title: Privacy Policy
+description: Privacy policy for Autonomic Co-operative Limited
+meta_description: This is the privacy policy for Autonomic Co-operative Limited.
+---
+
+# Autonomic Cooperative Limited Data Protection Act 2018 (GDPR) privacy Notice.
+
+> [The Data Protection Act 2018](https://www.gov.uk/data-protection) is the UK’s implementation of the General Data Protection Regulation (GDPR).
+
+## Summary
+Our purpose is to provide secure services for socially responsible and progressive groups and individuals. We seek to minimise data collection where possible and follow best security practices.
+
+To get in touch with Autonomic Cooperative Limited about any GPDR related issues please email [helo@autonomic.zone](helo@autonomic.zone). Our Secretary will act as contact for these matters. 
+
+## Data Protection Officer
+We do not have or believe we require a Data Protection Officer, as we do not process sensitive data, nor do our core activities require large scale systemic tracking of individuals. See the [Information Commissioner’s Office (ICO) guidance](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/accountability-and-governance/data-protection-officers/) on this.
+
+## Data Collection
+If you use our services, we may act as data processor for you. We provide information about how our systems and procedures allow you to use our service securely in our information security policy.
+
+We process data to provide Internet services. We collect names, addresses, email addresses, phone numbers of our customers so we can charge them for services and communicate with them information regarding the availability and status of their services. This processing is necessary for the performance of our contracts with them.
+
+## Logging and tracking
+Our services are configured to collect statistics including IP addresses via web server log files as is standard practice. The log files are kept for 28 days or less and are then deleted. We recommend you use [Tor Browser](https://www.torproject.org/) if you require greater anonymity.
+
+Our servers may collect web usage statistics via our private [Matamo](https://matomo.org/) analytics servers. You may opt out of Matamo tracking, the best way to do this is to set the [Do Not Track header](https://en.wikipedia.org/wiki/Do_Not_Track) in your browser or use the browser extensions [ublock origin](https://github.com/gorhill/uBlock/) and/or [Privacy Badger](https://privacybadger.org/).
+
+Occasionally our users may run alternative analytics software. This is outside of our control.
+
+## Data Storage
+This data is processed by our staff and only stored in the EU. We do not share data with 3rd parties unless this is required for the implementation of a specific service. For example, to a Domain Name Registrar to complete the whois information for a domain name. The requirement to share with 3rd parties will be clearly communicated to you, and only done with explicit consent.
+
+We are required under UK tax law to keep your basic personal data (name, address, contact details) for a minimum of 6 years after which time it will be destroyed.
+
+## Incorrect Information
+If at any point you believe the information we process on you is incorrect you request to see this information and even have it corrected or deleted. If you wish to raise a complaint on how we have handled your personal data, you can contact our Secretary via email on [helo@autonomic.zone](mailto:helo@autonomic.zone) who will then investigate the matter.
+
+See also our [Website Privacy Policy](/privacy) and  [Terms of Service](/terms).
+
+## Third Party Services
+We use servers hosted by [Webarchitects](https://www.webarch.net/privacy-notice), [Hetzner](https://www.hetzner.com/rechtliches/datenschutz) and [Digital Ocean](https://www.digitalocean.com/legal/gdpr/) and [Gandi](https://contract.gandi.net/v5/contracts/36637/Privacy_Policy_SAS_1.1_en.pdf) for Domain names, DNS and Email, so their Data Processing Agreements may also apply.
+
+## Contact us
+If you are not satisfied with our response or believe we are processing your personal data in a way that is not in accordance with the law you can complain to the [Information Commissioner’s Office (ICO)](https://ico.org.uk/).
+ 

src/privacy.md

@@ -0,0 +1,18 @@
+---
+layout: page
+title: Website Privacy Policy
+description: Privacy policy for autonomic.zone
+meta_description: This is the privacy policy for the website of Autonomic co-operative.
+---
+
+# Website Privacy Policy
+
+## The Autonomic Co-operative Limited website privacy policy
+
+Our Privacy Notice contains information regarding our [Data Protection Act 2018 (GDPR)](https://www.gov.uk/data-protection) compliance.
+
+This site does not set cookies.
+
+This site is configured to collect statistics including IP addresses via web server log files as is standard practice. The log files are kept for 28 days or less and are then deleted. We recommend you use [Tor Browser](https://www.torproject.org/) if you require greater anonymity. This site remains functional without [Javascript](https://en.wikipedia.org/wiki/JavaScript) enabled.
+
+The source code for this website can be found [here](https://git.autonomic.zone/autonomic-cooperative/autonomic.zone).

src/terms.md

@@ -0,0 +1,62 @@
+---
+layout: page
+title: Terms of Service
+description: Terms of Service for autonomic.zone
+meta_description: This is the Terms of Service for Autonomic Co-operative Limited.
+---
+
+# Terms of service
+This document describes what activities are allowed, under what conditions we may terminate your account, and asserts our limited liability. It applies to all interactions with Autonomic Cooperative Limited. Your use of Autonomic Cooperative Limited's services constitutes your agreement to these Terms of Service.
+
+## Summary
+If you do anything truly evil, we will terminate your account. We are not liable for any damages related to the use of these services. You agree to hold patience in your heart for the hard work we do.
+
+## Privacy policies
+We ask that you review our [Privacy Policy](/gdpr), so that you are aware of how we collect and use your information.
+
+## Ownership of and responsibility for content
+All Content, whether publicly posted or privately transmitted, is the sole responsibility of the person who originated such Content. We may not monitor or control the Content posted via the Services and we cannot take responsibility for such Content. 
+
+Any use or reliance on any Content or materials posted via the Services or obtained by you through the Services is at your own risk. You are responsible for your use of the Services, for any Content you provide, and for any consequences thereof.
+
+### Refraining from certain activities
+You may not engage in the following activities through the services provided by Autonomic Cooperative Limited:
+
+- Harassing or abusing others by engaging in threats, stalking or sending spam. This includes usernames, aliases or using any of our resources for this purpose.
+- Misuse of services by distributing viruses or malware, engaging in a denial of service attack, or attempting to gain unauthorised access to any computer system, including this one.
+- Contributing to the abuse of others by distributing material where the production process created violence or sexual assault against persons.
+
+## Account Termination
+Autonomic Cooperative Limited may terminate your service at any time for any reason.
+
+## Limitation on Liability
+You agree that Autonomic Cooperative Limited is not liable to you or to any other party for any direct, indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data, or other intangible losses, regardless of whether we were advised of the possibility of such damage. 
+
+In the case that applicable law may not allow the limitation or exclusion of liability or incidental or consequential damages, the above limitation or exclusion may not apply to you, although our liability will be limited to the fullest extent permitted by applicable law.
+
+### Choice of Forum and Law
+You agree that these Terms of Service and your use of Autonomic Cooperative Limited is governed by the law of United Kingdom.
+
+### Policy regarding copyright infringement - DMCA
+Autonomic Cooperative Limited complies with the Digital Millennium Copyright Act’s notice and take-down procedures. DMCA complaints should be addressed to:
+
+```
+Autonomic Cooperative Limited
+1539 Pershore Road
+Birmingham
+B30 2JH
+United Kingdom
+```
+
+Or via email: [helo@autonomic.zone](mailto:helo@autonomic.zone)
+
+Please note that it is Autonomic Cooperative Limited’s policy to take reasonable steps, within our power, to terminate the accounts of users who are repeat infringers in appropriate circumstances.
+
+### No Warranty
+You understand and agree that Autonomic Cooperative Limited provides online services “as is” and without any warranty, express, implied, or statutory. 
+
+We specifically disclaim any implied warranties of title, merchant-ability, fitness for a particularly purpose and non-infringement. We make no warranty as to the reliability, accessibility, or quality of our services. You agree that the use of our services is at your sole and exclusive risk.
+
+### Changes to this policy
+We reserve the right to change this policy. If we make major changes, we will notify our users in a clear and prominent manner.
+