Tweaked decision making blog post

.drone.yml

@@ -19,21 +19,9 @@ steps:
       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:
-    - main
+    - master
 event:
   exclude:
     - pull_request

Dockerfile

@@ -1,4 +1,4 @@
-FROM ruby:2.7.4-alpine3.12
+FROM ruby:2.7.2-alpine
 
 EXPOSE 4000
 

Gemfile

@@ -1,6 +1,6 @@
 source "https://rubygems.org"
 
-ruby "2.7.4"
+ruby "2.7.2"
 
 gemspec
 

Gemfile.lock

@@ -74,7 +74,7 @@ DEPENDENCIES
   jekyll-feed
 
 RUBY VERSION
-   ruby 2.7.3p183
+   ruby 2.7.2p137
 
 BUNDLED WITH
    2.1.4

docker-compose.prod.yml

@@ -4,9 +4,7 @@ version: "3.8"
 services:
   jekyll:
     image: decentral1se/autonomic.zone:latest
-    command: |
-      bundle exec
-        jekyll serve --host 0.0.0.0 --trace
+    command: bundle exec jekyll serve --host 0.0.0.0 --trace
     environment:
       JEKYLL_ENV: production
     networks:

docker-compose.yml

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

requirements.txt

@@ -1 +1 @@
-docker-compose==1.29.2
+docker-compose==1.28.0

src/_includes/footer.html

@@ -7,7 +7,7 @@
         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/main/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/master/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>

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

@@ -22,8 +22,8 @@ Our decisions can be split intro three categories: **Small, Medium and Large**.
 
 ## 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.
+- Don't have an effect on the direction or operation of the co-op.
+- Give a deadline. Unless anyone objects or asks for more time then it passes.
 - 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).
 

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

@@ -1,99 +0,0 @@
----
-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/_posts/2021-07-05-new-coop-cloud-blog-and-socials.md

@@ -1,10 +0,0 @@
----
-layout: post
-title: New Co-op Cloud blog, socials and updates
-description: Co-op Cloud project blog, socials and monthly updates
-image: ccblog.png
-category: coop, co-op, cloud, docker, swarm, libre-software, hosting,
-date: 2021-07-07
----
-
-The Co-op Cloud is starting to come into its own and we've decided to move our posts over to a dedicated [new and shiny blog](https://coopcloud.tech/blog/). We are working on opening up shared ownership of the project and want to create digital spaces where Autonomic is not implicitly having some sort of gate keeping role. We'll be writing regularly about our progress over there. We've also made new [Twitter](https://twitter.com/Coop_Cloud) and [Mastodon](https://social.coop/@coopcloud) which can you can follow along. That's all for now!

src/_posts/2021-08-16-website-priority-guide.md

@@ -1,61 +0,0 @@
----
-layout: post
-title: Content Priority Guides for Websites
-description: What is a Content Priority Guide and how to use it for web development
-image:
-category: autonomic, content, priority, guide, web, development, design, copywriting
-date: 2021-08-16
----
-
-A Content Priority Guide (CPG) are a simpler and faster version of [wireframes](https://en.wikipedia.org/wiki/Website_wireframe) that isn't focussed on design or the actual and encourage a client to not get bogged down in details. We found this exercise, gives the client and ourselves a clear and concise map of what the site is going to look like at an earliest stages of the project as possible. This is especially useful for smaller projects where there isn't budget or the client isn't very experienced with commissioning web development work.
-
-The content itself can then be worked on referencing the structure and hierarchy laid out in the CPG and if appropriate, the design team and front-end development team will also use the CPG in their work. The common consensus on the site layout created by the CPG allows for a "multi-threaded" approach to the project where different teams are able to work on their respective specialities simultaneously. The CPG can be updated as the project proceeds as long as all teams are aware of the changes.
-
-If a client's budget allows, Autonomic will also do more in depth collaborative processes with our clients but making a CPG together is a great starting point and requires no specialist tools or knowledge.
-
-Below is a sample Content Priority Guide. It was inspired by this [blog post](https://seesparkbox.com/foundry/content_priority_guide) and this [article](https://www.smashingmagazine.com/2012/05/design-process-responsive-age/).
-
-## Sample priority guide
-### The audience
-- Who are your audiences?
-- Can you list your audiences in order of priority?
-- What are the accessibility needs of your audiences?
-- What devices are your audiences primarily accessing the site on?
-
-### Page 1 - Homepage
-1. Heading
-2. Hero image 
-3. About Us copy (3-4 sentences)
-4. Our demands section
-	- Section Title
-	- Bullet point list of demands
-5. What we do section
-	- Section title
-	- Image
-	- What we do (A few sentences describing our activities)
-	- How we do it (A few sentences that include our principles)
-	- Our outcomes (A few paragraphs that talk about what we have achieved)
-
-### Page 2 - Projects
-1. Heading
-2. Sub-heading
-3. 6-8 items displayed in chronological order
-	- Project Title
-	- Image or Headline (if an image is provided, that will display. If there is no image, the headline will display)
-	- Project Description (2-4 sentences about the project)
-	- Link to read project details entry
-
-### Page 3 -  Blog
-1. Heading
-2. List of 6-8 blog posts
-	- Blog title
-	- Blog post publish date
-	- Blog post tags
-	- Pagination navigation links
-3. Archive blog posts drop down selectable by month
-
-### Page 4 - Contact
-1. Headline
-2. Email contact form
-3. Follow us on social media subheading and icons with links to social media pages
-

src/cookies.md

@@ -1,48 +0,0 @@
----
-layout: page
-title: Cookies Policy
-description: Cookies policy for Autonomic Co-operative Limited
-meta_description: This is the cookies policy for Autonomic Co-operative Limited.
----
-
-# Autonomic Co-operative Limited - General Cookies Policy
-This General Cookies Policy was last revised on: 2022-08-18
-
-The websites and online platforms we build and maintain may store data in a ‘cookie’. This is a tiny element of data that our sites can send to your browser, which is then stored on your hard drive for a limited duration before being automatically deleted.
-
-We use cookies in websites and web services to improve users’ experience, present customised information to fit each user’s needs, and enable the platform’s features and services to function properly. 
-
-All cookies we use will be implemented in a manner that complies with data protection law.
-
-Where we use cookies, they will be for the following purposes:
-    • Strictly necessary cookies – meaning that they are strictly necessary for the platform’s functionality and security. 
-    • Functionality cookies / session cookies — these cookies allow a website to remember your past user settings and preferences (e.g., language and display preferences), or to allow you to automatically log in to a website that is secured by a username and password, after an initial successfully authenticated login. These almost always also count as strictly necessary cookies, as they enable website functionality and a smooth and convenient browsing experience.
-    • Statistics / analytics / performance cookies — these cookies collect information about how you use a website, like which pages you visit and which links you click on. None of this information can be used to identify you. It is all aggregated and, therefore, anonymized. Their sole purpose is to improve website functions. 
-
-We normally use (Matomo)[https://matomo.org/] ethical analytics for analytics and performance purposes that we host on our own infrastructure, which means that:
-        ◦ visitors can’t be tracked across different days within the same website.
-        ◦ user profiles cannot be generated when cookies are disabled.
-        ◦ the data is not used for any other purpose than analytics.
-        ◦ we don’t track any personal data and have enabled cookie-less tracking.
-
-As a default policy, we will strive to only use essential cookies. We understand essential here as meaning that a cookie is either strictly necessary for the platform’s functionality and security, or for the Data Controller to fulfil their legal or contractual obligations or to pursue their legitimate interests in processing your data (please see the section titled Why we collect and process your personal data for further details about legal and contractual obligations or legitimate interests as legal bases for processing personal data.)
-
-Where we use analytics, performance or tracking cookies or systems, we will only ever use cookies/systems controlled directly by us or the Data Controller for whom we work as a Data Processor, for the exclusive use of the Data Controller.
-
-As a default policy, the cookies we use do not track your web browsing outside the websites and web services we build and maintain for our own purposes or for our customers and service users. Likewise, as a default policy we do not use marketing or ad-serving cookies.
-
-Our cookies will not usually contain the substantive contents of personal information that you give us (or that has been shared with us by a Data Controller or any third-party), unless this is strictly necessary to ensure the platform’s functionality or for the Data Controller to fulfil their legal or contractual obligations or pursue their legitimate interests in processing your data.
-
-Our cookies will not read, collect, or store any of your private information contained in files that you may have stored on your devices, nor any personal information that you may have posted or uploaded on the web.
-
-Where strictly necessary, our cookies may contain identification labels that can be used indirectly to personally identify you, so our web services recognise you as a unique user.
-
-Some of the websites or web services we maintain may collect technical information about the type of browser and device you are using, and store that information in the website’s server or in cookies on your device, so that the site can function and display properly for you.
-
-Some of our platforms’ cookies may also contain personally identifiable information in an indirect way, by storing a unique identification label that allows the website to indirectly identify you as an individual user by cross-reference with labelled data we hold about you in the website server, thus allowing the website to function properly by presenting the correct information to you. This type of cookie is usually necessary for platforms where users need to login with a password to access the platform’s services.
-
-You can prevent the setting of cookies by adjusting the settings on your browser (see your browser Help for how to do this). Be aware that disabling cookies will affect the functionality, and sometimes disable certain features, of the websites we maintain, and many other websites that you visit. Therefore, it is recommended that you do not disable cookies.
-
-In rare cases where we use non-essential cookies on our websites, or where our customer requests that we build/maintain a website for them using non-essential cookies, we will implement a website popup notifying the user about those cookies and to obtain their consent, giving them the opportunity to opt-in or otherwise be opted-out by default.
-
-We will never consider cookies used for marketing / direct marketing purposes as essential, even if direct marketing can reasonably be considered as falling under the Data Controller’s legitimate interests or contractual obligations.