Compare commits

..

3 Commits

15 changed files with 110 additions and 240 deletions

View File

@ -24,7 +24,7 @@ services:
labels:
- "traefik.enable=true"
- "traefik.http.services.jekyll.loadbalancer.server.port=4000"
- "traefik.http.routers.jekyll.rule=Host(`old.autonomic.zone`) || Host(`www.old.autonomic.zone`)"
- "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"

View File

@ -0,0 +1,61 @@
---
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

View File

@ -1,63 +0,0 @@
---
layout: post
title: Come join the good ship Autonomic!
description: Hi do you want to work with the coolest anarchist tech workers co-operative?
image: robertmccall.jpg
category: decision making, democracy, meta
date: 2021-11-25
---
## Background
Autonomic is a worker-owned co-operative of queer comrade hackers dedicated to using technology to empower people making a positive difference in the world. Since 2017, weve been successfully delivering projects in a range of sectors including renewable energy, labour organising, independent media, feminist research, migrant solidarity activism, sustainable fashion, and arms trade abolition.
We are currently 12 worker-owners, located on four continents worldwide. We are a Co-operative Society, registered in the UK with the Financial Conduct Authority. Legally, we are a freelance consortium, which means that we operate as a group of self-employed contractors, and are responsible for our own individual income tax.
Autonomic aspires to follow the [7 co-operative principles as defined by the International Co-operative Alliance](https://www.ica.coop/en/cooperatives/cooperative-identity).
We're currently looking to build capacity in the co-op in key areas to help take us to the next level.
## Pay
We are currently paid £16 per hour for all work.
Everyone in the co-op will always be paid the same rate, which we decide on collectively and adjust according to how well we're doing.
## What we're looking for:
We are looking for folks who have expertise in the following areas:
### Required
- Care, communicatiton and compassion. Trust. Comradeship. Each according to their need.
- Available for around 10-20 hours per week **between 8am UTC and 3pm UTC**
### Skill areas
We are in need of people who have experience or interest in at least 2 of these areas:
- Project management: progress tracking and planning, budgeting and estimates.
- Client communications / relations / meeting, conflict resolution.
- Infrastrucure skills: Debian, Ansible, Git, Docker, Docker Swarm in the context of [Co-op Cloud](https://coopcloud.tech).
- Wordpress development (front end and back end): PHP, CSS, Composer, Docker.
- Finance administration: invoicing, tax, forecasting,
### Bonus/Nice to Have
- Wordpress plug-in development
- Drupal development
- New business development
## Process
People of color, women, genderqueer, non-binary and trans folks, neurodiverse and queer folks strongly encouraged to apply.
Email helo@autonomic.zone with your CV (doesn't have to be fancy, just a list of work) and a little bit about yourself and what you're looking for work wise.
If we think you might be suitable for these roles, you'll be invited for a few chats with members of the co-op who will show you more about the kinds of work we do and be able to answer any questions you have.
If we want to take you on, we'll then have a vote amongst our members and you can start working for us right away as a "potential member". After 100 hours of work you can be invited to join the co-op as a full member.
<hr>
_image by Robert McCall_

View File

@ -1,14 +0,0 @@
---
layout: post
title: The Co-op Cloud Federation Proposal
description:
image: ccforest.jpg
category: coop cloud, decision making, democracy
date: 2022-04-14
---
Following on in [the tradition](https://autonomic.zone/blog/new-coop-cloud-blog-and-socials/) of making [short blog posts](https://autonomic.zone/blog/co-op-cloud/) about [Co-op Cloud](https://coopcloud.tech) on this blog, here comes another one!
We're delighted to announce that we have finally published the Co-op Cloud federation proposal. It's a document which aims to formalise the organisation of the project, focusing on a democratic process. It's open for comments, feedback, critique & amendments.
Autonomic has had a central role in the organising of this project until now, but we'd like to step back and open up space for others. The proposal is part of formalising that and we're excited to see who will step in! You can find out more on the [Co-op Cloud blog](https://coopcloud.tech/blog/federation-proposal/) or jump straight to [the proposal](https://pad.autonomic.zone/s/MLafJE2jC).

View File

@ -1,36 +0,0 @@
---
layout: post
title: Publishing our Ansible roles
description:
image: infra.jpg
category: ansible, automation, infrastructure
date: 2022-05-30
---
We're delighted to announce that we're publishing our Ansible roles
into the open under [`git.autonomic.zone/autonomic-cooperative/...`](https://git.autonomic.zone/explore/repos?q=ansible&topic=1) at long last 🥳
They've always been licensed as libre software but due to the way we managed
our internal infrastructure configurations, they were embedded in a private
repository.
The roles are currently lacking documentation and written for very specific
Autonomic needs but they might be handy as a learning resource or a base to
fork from. We'd happily accept contributions to generalise them.
In particular, we've been relying on and running
[`autonomic.new-hetzner`](https://git.autonomic.zone/autonomic-cooperative/autonomic.new-hetzner)
for years, so it is battle tested. The role bootstraps a Hetzner VPS from
scratch and provisions it with a hardened SSH configuration, firewalls, user
accounts and some basic packages and a shiny MOTD.
All roles are CI tested on every commit with [Molecule](https://molecule.readthedocs.io/en/latest/) so things don't break.
[Expanding re-use with shared infrastructure](https://community.coops.tech/t/cotech-gathering-ansible-and-shared-infrastructure-session/1107)
is someting we've always been working on at Autonomic. We have an ongoing
critique of Ansible and the pros/cons of when it is a good choice to use. This
ultimately lead us to start projects like [Co-op
Cloud](https://coopcloud.tech/). However, we still think Ansible is pretty good
at handling more complicated server provisioning needs.
Happy Infra Hacking.

View File

@ -1,45 +0,0 @@
---
layout: post
title: Wireless Battle of the Mesh - Building Community Networks for Fun and Non-Profit
description: Autonomic members are aiming to attend. Here is our public endorsement!
image: bmesh.png
category: community, wireless, event
date: 2022-07-11
---
Autonomic Co-op supports this year's "Wireless Battle of the Mesh - Building
Community Networks for Fun and Non-Profit".
The event aims to bring together people from across the globe who are
interested in community networks, including wireless mesh network technologies,
fiber infrastructure, Do-It-Yourself Internet Access Providers, and more
generally how to create and maintain a thriving community of people involved in
building their own networks.
We envision 4 days of expert presentations, practical workshops, hacking
sessions, and fruitful discussions: whether you are a mesh networking
enthusiast, community networking activist, protocol developer, or have an
interest in networking in general, come and join the event!
The Battlemesh is free of charge and open for all.
This year, the event will take place from Monday 19th to Wednesday 22nd
of September, 2022 in Rome, Italy! It will be followed by the RomHack
Camp on September 23-25, also in Rome.
Check out more information [here](https://www.battlemesh.org/BattleMeshV14).
We are writing this post as part of a public endorsement and support for
"Wireless Battle of the Mesh - Building Community Networks for Fun and
Non-Profit" not only for the efforts made by its community to advance the field
of wireless mesh networking and foster the development of grass-roots community
networks, but for their contribution to digital freedom rights movement,
empowerment of peoples tech/net/media competency and a free and open civil
society.
We aim to support the event by:
- helping to promote it
- making it possible for our members to join the event
See you there hopefully!

View File

@ -1,61 +0,0 @@
---
layout: post
title: Come join the good ship Autonomic!
description: We (were) hiring again!
category: decision making, democracy, meta
date: 2022-10-10
---
> As of 8 November 2022, this round of recruitment is now closed. Thanks to those who got in touch, and stay tuned for the next time we're looking for new members.
## Background
Autonomic is a worker-owned co-operative of queer comrade hackers dedicated to using technology to empower people making a positive difference in the world. Since 2017, weve been successfully delivering projects in a range of sectors including renewable energy, labour organising, independent media, feminist research, migrant solidarity activism, sustainable fashion, and arms trade abolition.
We are currently 11 worker-owners, located in 6 countries. We are a Co-operative Society, registered in the UK with the Financial Conduct Authority. Legally, we are a freelance consortium, which means that we operate as a group of self-employed contractors, and are responsible for our own individual income tax.
Autonomic aspires to follow the [7 co-operative principles as defined by the International Co-operative Alliance](https://www.ica.coop/en/cooperatives/cooperative-identity).
## Pay
We are currently paid £20 per hour for all work.
Everyone in the co-op will always be paid the same rate, which we decide on collectively and adjust according to how well were doing.
## What were looking for
We are looking for folks who have expertise in the following areas:
### Required commitments
- Care, communication and compassion. Trust & responsibility. Comradeship. Each according to their need.
- Available for around 10-20 hours per week. We work in multiple timezones but mostly find that being available for at least 1-3 hours for checking in and co-working between 13:00 UTC - 15:00 UTC is the best.
### Required skills
We are in need of people who have experience or interest in front end development.
- Comfortable with front-end technologies: HTML / CSS / JS / PHP (any or all)
- Comfortable writing WordPress themes and templates and debugging obscurities
### Bonus/Nice to Have
- Wordpress plug-in development
- Experience with collective organising & consensus decision making
- Debian systems administration skills: Bash scripting, running system upgrades, handling SSH keys etc.
- Interest in collectively learning how to run a cooperative under capitalism
- Experience in running union, grassroots or community political campaigns
- New business development, chasing leads
- Finance administration: invoicing, tax, forecasting
- Client communications / relations / meeting, conflict resolution
- Project management: progress tracking and planning, budgeting and estimates
## Process
People of color, women, genderqueer, non-binary and trans folks, neurodiverse and queer folks are strongly encouraged to apply.
Email [hello@autonomic.zone](mailto:hello@autonomic.zone) with your CV (it really doesnt have to be fancy, just a list of work) and a little bit about yourself and what youre looking for work wise.
If we think you might be suitable for these roles, youll be invited for a few chats with members of the co-op who will show you more about the kinds of work we do and be able to answer any questions you have.
If we want to take you on, well then have a vote amongst our members and you can start working for us right away as a “potential member”. After ~100 hours of work you can be invited to join the co-op as a full member.

View File

@ -1,20 +0,0 @@
---
layout: post
title: NEoN x Autonomic - Digital Reforms
description: A brief update about our work with NEoN in the last months.
image: letsleave.png
category: coop-cloud, neon
date: 2022-12-18
---
> This year has seen many changes at NEoN, and we will have many more next year. We are committed to exploring new ways of working that help us develop and implement new strategies that emphasise collaborative, collective, and communal approaches.
>
> As part of our ongoing work on the [Counter Cloud Action Plan](https://neondigitalarts.com/counter-cloud/), [titipi.org](http://titipi.org/) introduced us to [Autonomic](https://autonomic.zone/) and its [Cooperative Cloud Infrastructure.](https://autonomic.zone/#services) Autonomic is a cooperative that is owned and run by its workers. They build technologies and infrastructure to empower users to impact the world positively. Their services reflect their commitment to their core values - sustainability, transparency and privacy.
>
> We commissioned [Autonomic](https://autonomic.zone/) to look over NEoN's digital infrastructure and help us to find a new sustainable way of working that supports one of its goals of DeGoogle-isation. Based on discussions and their past experiences working with other initiatives such as[ lumbug.space](https://lumbung.space/), [UTAW](https://utaw.tech/about/), VREC and [Comic Gewerkschaft](https://www.comicgewerkschaft.org/Uber-Uns), Autonomic has provided us with a plan of reforms, which we are delighted to share with you.
Read the full report [here](https://neondigitalarts.com/neon-digital-reforms/)!
Much love & solidarity to the good people at NEoN!
PS. Main Image Credit: "Let's leave planet GAFAM" by David Revoy from [degooglisons-internet.org](https://degooglisons-internet.org).

Binary file not shown.

Before

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 189 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.6 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 92 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 436 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 496 KiB

48
src/cookies.md Normal file
View File

@ -0,0 +1,48 @@
---
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 users needs, and enable the platforms 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 platforms 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 cant 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 dont 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 platforms 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 platforms 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 websites 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 platforms 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 Controllers legitimate interests or contractual obligations.