Add budget template to resolution 010

See coop-cloud/organising#454

Dockerfile

@@ -1,4 +1,4 @@
-FROM squidfunk/mkdocs-material:9.1.15
+FROM squidfunk/mkdocs-material:9.1.19
 
 EXPOSE 8000
 
@@ -8,4 +8,6 @@ WORKDIR /docs
 
 RUN apk add --no-cache curl
 
-RUN pip install mkdocs-awesome-pages-plugin mkdocs-material-extensions
+RUN pip install \
+  mkdocs-awesome-pages-plugin==2.9.1 \
+  mkdocs-material-extensions==1.1.1

custom_theme/partials/header.html

@@ -1,19 +1,61 @@
 {#-
   This file was copied from the Material theme
-  You can find the file in .venv/lib/python3.10/site-packages/material/partials/header.html
+  You can find the file in https://raw.githubusercontent.com/squidfunk/mkdocs-material/master/src/partials/header.html
 -#}
+<!--
+  Copyright (c) 2016-2023 Martin Donath <martin.donath@squidfunk.com>
+
+  Permission is hereby granted, free of charge, to any person obtaining a copy
+  of this software and associated documentation files (the "Software"), to
+  deal in the Software without restriction, including without limitation the
+  rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+  sell copies of the Software, and to permit persons to whom the Software is
+  furnished to do so, subject to the following conditions:
+
+  The above copyright notice and this permission notice shall be included in
+  all copies or substantial portions of the Software.
+
+  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+  FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE
+  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+  FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
+  IN THE SOFTWARE.
+-->
+
+<!-- Determine base classes -->
 {% set class = "md-header" %}
 {% if "navigation.tabs.sticky" in features %}
-  {% set class = class ~ " md-header--lifted" %}
+  {% set class = class ~ " md-header--shadow md-header--lifted" %}
+{% elif "navigation.tabs" not in features %}
+  {% set class = class ~ " md-header--shadow" %}
 {% endif %}
+
+<!-- Header -->
 <header class="{{ class }}" data-md-component="header">
-  <nav class="md-header__inner md-grid" aria-label="{{ lang.t('header.title') }}">
-    <a href="{{ config.extra.homepage | d(nav.homepage.url, true) | url }}" title="{{ config.site_name | e }}" class="md-header__button md-logo" aria-label="{{ config.site_name }}" data-md-component="logo">
+  <nav
+    class="md-header__inner md-grid"
+    aria-label="{{ lang.t('header') }}"
+  >
+
+    <!-- Link to home -->
+    <a
+      href="{{ config.extra.homepage | d(nav.homepage.url, true) | url }}"
+      title="{{ config.site_name | e }}"
+      class="md-header__button md-logo"
+      aria-label="{{ config.site_name }}"
+      data-md-component="logo"
+    >
       {% include "partials/logo.html" %}
     </a>
+
+    <!-- Button to open drawer -->
     <label class="md-header__button md-icon" for="__drawer">
       {% include ".icons/material/menu" ~ ".svg" %}
     </label>
+
+    <!-- Header title -->
     <div class="md-header__title" data-md-component="header-title">
       <div class="md-header__ellipsis">
         <div class="md-header__topic">
@@ -23,7 +65,7 @@
         </div>
         <div class="md-header__topic" data-md-component="header-topic">
           <span class="md-ellipsis">
-            {% if page and page.meta and page.meta.title %}
+            {% if page.meta and page.meta.title %}
               {{ page.meta.title }}
             {% else %}
               {{ page.title }}
@@ -32,53 +74,94 @@
         </div>
       </div>
     </div>
-    {% if not config.theme.palette is mapping %}
-      <form class="md-header__option" data-md-component="palette">
-        {% for option in config.theme.palette %}
-          {% set primary = option.primary | replace(" ", "-") | lower %}
-          {% set accent  = option.accent  | replace(" ", "-") | lower %}
-          <input class="md-option" data-md-color-media="{{ option.media }}" data-md-color-scheme="{{ option.scheme }}" data-md-color-primary="{{ primary }}" data-md-color-accent="{{ accent }}" {% if option.toggle %} aria-label="{{ option.toggle.name }}" {% else %} aria-hidden="true" {% endif %} type="radio" name="__palette" id="__palette_{{ loop.index }}">
-          {% if option.toggle %}
-            <label class="md-header__button md-icon" title="{{ option.toggle.name }}" for="__palette_{{ loop.index0 or loop.length }}" hidden>
-              {% include ".icons/" ~ option.toggle.icon ~ ".svg" %}
-            </label>
-          {% endif %}
-        {% endfor %}
-      </form>
+
+    <!-- Color palette -->
+    {% if config.theme.palette %}
+      {% if not config.theme.palette is mapping %}
+        <form class="md-header__option" data-md-component="palette">
+          {% for option in config.theme.palette %}
+            {% set scheme  = option.scheme  | d("default", true) %}
+            {% set primary = option.primary | d("indigo", true) %}
+            {% set accent  = option.accent  | d("indigo", true) %}
+            <input
+              class="md-option"
+              data-md-color-media="{{ option.media }}"
+              data-md-color-scheme="{{ scheme | replace(' ', '-') }}"
+              data-md-color-primary="{{ primary | replace(' ', '-') }}"
+              data-md-color-accent="{{ accent | replace(' ', '-') }}"
+              {% if option.toggle %}
+                aria-label="{{ option.toggle.name }}"
+              {% else  %}
+                aria-hidden="true"
+              {% endif %}
+              type="radio"
+              name="__palette"
+              id="__palette_{{ loop.index }}"
+            />
+            {% if option.toggle %}
+              <label
+                class="md-header__button md-icon"
+                title="{{ option.toggle.name }}"
+                for="__palette_{{ loop.index0 or loop.length }}"
+                hidden
+              >
+                {% include ".icons/" ~ option.toggle.icon ~ ".svg" %}
+              </label>
+            {% endif %}
+          {% endfor %}
+        </form>
+      {% endif %}
     {% endif %}
+
+    <!-- Site language selector -->
     {% if config.extra.alternate %}
       <div class="md-header__option">
         <div class="md-select">
           {% set icon = config.theme.icon.alternate or "material/translate" %}
-          <button class="md-header__button md-icon" aria-label="{{ lang.t('select.language.title') }}">
+          <button
+            class="md-header__button md-icon"
+            aria-label="{{ lang.t('select.language') }}"
+          >
             {% include ".icons/" ~ icon ~ ".svg" %}
           </button>
           <div class="md-select__inner">
             <ul class="md-select__list">
               {% for alt in config.extra.alternate %}
                 <li class="md-select__item">
-                  <a href="{{ alt.link | url }}" hreflang="{{ alt.lang }}" class="md-select__link">
+                  <a
+                    href="{{ alt.link | url }}"
+                    hreflang="{{ alt.lang }}"
+                    class="md-select__link"
+                  >
                     {{ alt.name }}
                   </a>
                 </li>
-                {% endfor %}
+              {% endfor %}
             </ul>
           </div>
         </div>
       </div>
     {% endif %}
+
+    <!-- Button to open search modal -->
+    {% if "material/search" in config.plugins %}
+      <label class="md-header__button md-icon" for="__search">
+        {% include ".icons/material/magnify.svg" %}
+      </label>
+
+      <!-- Search interface -->
+      {% include "partials/search.html" %}
+    {% endif %}
+
+    <!-- Repository information -->
     {% if config.repo_url %}
       <div class="md-header__source">
         {% include "partials/source.html" %}
       </div>
     {% endif %}
-    {% if "search" in config["plugins"] %}
-      <label class="md-header__button md-icon" for="__search">
-        {% include ".icons/material/magnify.svg" %}
-      </label>
-      {% include "partials/search.html" %}
-    {% endif %}
   </nav>
+
+  <!-- Navigation tabs (sticky) -->
   {% if "navigation.tabs.sticky" in features %}
     {% if "navigation.tabs" in features %}
       {% include "partials/tabs.html" %}

docs/federation/finance.md

@@ -5,9 +5,13 @@ title: Finance
 > If you have any questions or run into problems, please chat with us on
 > `#coopcloud-finance:autonomic.zone`
 
-### Overview of financial machinery
+## Agreeing to spend money (Budgets)
 
-It's slightly complicated because Money but here's how it works. There are two moving parts:
+
+
+## Sending and receiving money
+
+It's slightly complicated, because money is complicated, but here's how it works. There are two moving parts:
 
 * The Co-op Cloud Open Collective
 * The Autonomic Wise account
@@ -58,7 +62,7 @@ Finally, please let us know what your username/email is for your Open Collective
 
 ##### Where are the bank details of federation members?
 
-Please see the internal Federation wiki, `Finance.md`.
+Please see [`Finance.md` in the internal Federation Wiki](https://git.coopcloud.tech/Federation/organising/wiki/Finance)
 
 ##### What transfer type do we use for USD?
 

docs/federation/resolutions/in-progress/009.md

@@ -0,0 +1,22 @@
+---
+title: "Resolution 009: Federation common fund buffer - 2023-07-03"
+---
+
+## Resolution 009: Federation common fund buffer - 2023-07-03
+
+- Deadline: 2023-07-17
+- Size: Large
+
+### Summary
+
+The Co-op Cloud Federation has [a common fund](https://opencollective.com/coop-cloud#category-BUDGET) which can be used by federation members by proposing [budgets](https://docs.coopcloud.tech/federation/resolutions/passed/004/).
+
+With Resolution 009, we want to introduce the idea of a common fund buffer.
+
+This buffer is proposed to be set at 1,500 EUR. When the buffer is reached, no more budgets can be proposed. When the fund increases once more, budgets can resume.
+
+The buffer is in place to reserve funds for critical collective spending when we have limited income.
+
+### Details
+
+1,500 EUR is fairly arbitrarily chosen but seems to be a reasonable amount of money to cover situations where, e.g. we need to pay for servers, domains, mail accounts or other common critical infrastructure.

docs/federation/resolutions/in-progress/010.md

@@ -0,0 +1,41 @@
+---
+title: "Resolution 010: Budget 004: Critical fixes - 2023-07-03"
+---
+
+## Resolution 010: Budget 004: Critical fixes - 2023-07-03
+
+- Deadline: 2023-07-17
+- Size: Large
+
+### Summary
+
+We propose to have a standing budget of 10 hrs / month available for fixes in Abra, Co-op Cloud recipes and other critical tools (e.g. recipes.coopcloud.tech) in the Co-op Cloud ecosystem.
+
+A fix is deemed critial when it is listed on this coop-cloud/organising board:
+
+> https://git.coopcloud.tech/coop-cloud/organising/projects/24
+
+This board is collectively gardened by Co-op Cloud participants (both federation members and not). The process for adding a ticket to the board requires getting confirmation from at least one other member of the federation.
+
+This budget can be claimed by any volunteer who would like to develop the fix. If the volunteer is not a Co-op Cloud federation member, they must first be "vouched for" by a federation member. This is an informal process which can be arranged via the Matrix chat. This aims to assure agreement on timing and what the fix should contain beforehand.
+
+Fixes can be claimed by assiging yourself to the ticket. If within 1 week there is no updates on the ticket, another volunteer can propose to take over. This process is also informal: please @ the original volunteer and give some reasonable time for them to reply (suggested: 1 day).
+
+If the fix is urgent and things need to move faster, please state so on the ticket. Please consult with at least one other member of the federation to confirm that there is indeed agreement on the urgency of the fix.
+
+### Details (Budget 004)
+
+**Budget amount**: Any amount, until the common fund buffer is reached.
+
+**Who will implement this**: Self-organised volunteers.
+
+**When will the money be spent**: Any time until the common fund buffer is
+reached.
+
+**What is the money for**: Critical `abra` fixes.
+
+This budget stands open and available for use until the common fund buffer is reached. Please see Resolution 009 for further details on the buffer.
+
+Please see [Resolution 003](https://docs.coopcloud.tech/federation/resolutions/passed/003/) for details on the hourly rate for this work.
+
+Invoices can be submitted via the Co-op Cloud Open Collective. Please see [these docs](https://docs.coopcloud.tech/federation/finance/#how-to-get-paid-via-open-collective) for how to do that.

docs/federation/resolutions/in-progress/011.md

@@ -0,0 +1,22 @@
+---
+title: "Resolution 008: Budget 005: Backup improvements - 2023-07-23"
+---
+
+- Deadline: 2022-08-06
+- Size: Large
+
+### Summary
+
+Agree Budget 005, for up to 10 hours (€200) to implement changes to the Co-op Cloud backup system, including `abra`, and `backup-bot-two`. 
+
+More information, including background to the changes, and breakdown of the work, can be found here: https://pad.local-it.org/4chDYXkBQZywXKj0zs_Ymg#
+
+### Details (Budget 005)
+
+**Budget amount**: Up to EUR €200
+
+**Who will implement this**: Calix/3wc, decentral1se, Philipp and Moritz
+
+**When will the money be spent**: Before the end of August 2023.
+
+**What is the money for**: Improvements to Co-op Cloud backup tools

docs/federation/resolutions/index.md

@@ -14,5 +14,5 @@ title: Resolutions
 Who this affects, and what it does
 
 ### Details
-A narritive with details
+A narrative with details
 ```

docs/federation/resolutions/passed/006.md

@@ -1,4 +1,8 @@
-# Resolution 006: Budget 002: Resolution Writing-up 
+---
+title: "Resolution 006: Budget 002: Resolution Writing-up - 2023-05-29"
+---
+
+# Resolution 006: Budget 002: Resolution Writing-up - 2023-05-29
 
 - Deadline: 2022-06-12
 - Size: Large

docs/federation/resolutions/passed/007.md

@@ -0,0 +1,17 @@
+---
+title: "Resolution 007: 1 year dues waiver for Doop.coop - 2023-06-19"
+---
+
+- Deadline: 2023-07-03
+- Size: Medium
+
+### Summary
+
+Waive membership dues for Doop.coop for the first year of their membership, from July 2023 to June 2024.
+
+### Details
+
+Yusf said:
+
+> Hai! As our coop is a side gig, we've had a very low turnaround in the coop last fiscal. As such we've hadn't had the time to raise our revenue yet in this cycle so my question for the federation is:
+> Is it possible for us (already joined), Doop Coop, to apply for this solidarity free membership the first year after which we'll be able to put in the fee?

docs/federation/resolutions/passed/008.md

@@ -0,0 +1,24 @@
+---
+title: "Resolution 008: Budget 003: Paying invoices - 2023-06-19"
+---
+
+- Deadline: 2022-07-03
+- Size: Large
+
+### Summary
+
+Agree Budget 003, for up to €20/month for an Autonomic member to pay invoices submitted for Co-op Cloud Federation work.
+
+### Details (Budget 003)
+
+**Budget amount**: EUR €20/month
+
+**Who will implement this**: Autonomic
+
+**When will the money be spent**: Monthly
+
+**What is the money for**: Paying for the work involved in paying invoices submitted via OpenCollective.
+
+## A note about decentralisation
+
+Unfortunately, there doesn't seem to be a good way to open this task to other Co-op Cloud Federation members, until we get a dedicated bank account for the Federation, but if anyone has ideas about this, please let us know!

docs/get-involved/index.md

@@ -12,15 +12,11 @@ We are happy to have designers, critical thinkers, artists, hackers, documenters
 
 There are a number of "roles" such as "operator", "maintainer", "organiser" which we've tried to come up with to make it more clear how you can relate to the project and how you can find ways to be involved which suit your interests. If you don't fit one of these roles, that is fine.
 
-We have [a weekly check-in](/get-involved/#kite-flying-hours) for contributors of this project to let each other know what we're working on, how much time we've spent on it and how to coordinate further work.
+We have [an irregular online check-in](/organisers/handbook/#kite-flying-hours) for contributors of this project to let each other know what we're working on, how much time we've spent on it and how to coordinate further work.
 
 We have a [status page](/intro/bikemap) showing what we are aiming to achieve in the near future. That gives a good overview of where we're going together.
 
-From this status page, we use an [issue tracker](https://git.coopcloud.tech/coop-cloud/organising/issues) where we hold discussions about what we want to do. We categorise these issues according to the bike map using these [milestones](https://git.coopcloud.tech/coop-cloud/organising/milestones). Finally, use this [board](https://git.coopcloud.tech/coop-cloud/organising/projects/8) to keep track of what we're working on right now. We collectively review these things on a weekly/monthly basis to keep track of our time spent vs. budget available.
-
-Once you've found something to work on and are introduced, we'll give you an account on our [time tracking infrastructure](https://kimai.autonomic.zone) where you can log your times. This helps us reduce the burden of financial and time keeping admin falling on one person.
-
-We have received funding via [the ECF](https://culturalfoundation.eu/initiatives/culture-of-solidarity-fund) and can offer £16 hourly rate for your work. We've written more on why we think it is important to compensate all contributions for this project below.
+We use [issue trackers](https://git.coopcloud.tech/coop-cloud/organising/issues) and [project boards](https://git.coopcloud.tech/coop-cloud/organising/projects) to keep track of what we're working on right now. We collectively review these, to keep track of our time spent vs. budget available.
 
 ## Compensation
 

docs/intro/bikemap.md

@@ -6,4 +6,4 @@ title: Bike map
 
 - We are working towards a stable `1.0.0` release.
 
-- What we're currently working on is listed on this issue tracker: [`coop-cloud/organising`](https://git.autonomic.zone/coop-cloud/organising/issues).
+- What we're currently working on is listed on this issue tracker: [`coop-cloud/organising`](https://git.coopcloud.tech/coop-cloud/organising/issues).

docs/intro/faq.md

@@ -176,7 +176,7 @@ This means that we can patch our app containers directly in conversation with up
 
 We definitely recommend using best-in-class security auditing tools like [docker-bench-security](https://github.com/docker/docker-bench-security), IDS systems like [OSSEC](https://www.ossec.net/), security profiles like [Apparmor](https://docs.docker.com/engine/security/apparmor/) and hooking these into your existing monitoring, alert and update maintenance flows.
 
-It's up to how you want to arrange your system. For example, Co-op Cloud also allows you to compartmentalise different apps onto different servers. You could stack a bunch of apps on one big server or you could deploy one app per server.
+It's up to you how you want to arrange your system. For example, Co-op Cloud also allows you to compartmentalise different apps onto different servers. You could stack a bunch of apps on one big server or you could deploy one app per server.
 
 These are organisational concerns that Co-op Cloud can't solve for you which any software system will require. See this [additional question](/intro/faq/#what-is-important-to-consider-when-running-containers-in-production) for further information.
 
@@ -248,6 +248,18 @@ Yes! Horizontal scaling is one of the ways Co-op Cloud can really shine. `abra`
 
 ## Why only x86 support?
 
-We would love to do ARM support and hope to get there! We've been testing this and [ran into some issues](https://git.autonomic.zone/coop-cloud/organising/issues/25). The TLDR; is that a lot of upstream libre app developer communities are not publishing container builds that support ARM. If they are, there are typically subtle differences in the conventions used to build the image as they are mostly done by community members and not directly taken on by the upstream project themselves. Since one of the core goals is to coordinate and reuse upstream packaging work, we see that ARM support requires a lot of organising and community engagement. Perhaps projects themselves will not want to take on this burden? It is not the role of the Co-op Cloud to set up an entire ARM publishing work flow at this moment in time. We see the benefits of supporting ARM and if you've got ideas / thoughts / approaches for how to make progress here, [please get in touch](/intro/contact/).
+We would love to do ARM support and hope to get there! We've been testing this and [ran into some issues](https://git.coopcloud.tech/coop-cloud/organising/issues/25). The TLDR; is that a lot of upstream libre app developer communities are not publishing container builds that support ARM. If they are, there are typically subtle differences in the conventions used to build the image as they are mostly done by community members and not directly taken on by the upstream project themselves. Since one of the core goals is to coordinate and reuse upstream packaging work, we see that ARM support requires a lot of organising and community engagement. Perhaps projects themselves will not want to take on this burden? It is not the role of the Co-op Cloud to set up an entire ARM publishing work flow at this moment in time. We see the benefits of supporting ARM and if you've got ideas / thoughts / approaches for how to make progress here, [please get in touch](/intro/contact/).
 
 Update: [Can I run Co-op Cloud on ARM?](/operators/handbook/#can-i-run-co-op-cloud-on-arm)
+
+## Why would an activist group use Co-op Cloud infrastructure over private cloud infrastructure (e.g. AWS, Azure, GCP)?
+
+If your group is powerful enough to have generated opposition, it's not implausible that some law enforcement body may be trying to stymie your group's advances. To do this, law enforcement bodies may and probably will collaborate with big tech. Indeed, Big Tech has consistently shown a quick willingness to cooperate with Law Enforcement agencies (a la Snowden-revealed NSA subpoenas, [disallowing Signal to domain front](https://techcrunch.com/2018/05/02/signal-could-get-kicked-out-of-amazon-web-services/) and other such incidents where [Big Tech aided governments in hunting activists](http://discourse.leagueofconcernedusers.org/t/activist-infrastructures/69?u=themoonisblue)).
+
+If your group has ambitions that generate enough fury in your opposition, you should think twice about where you store your data and whose services you rely on to store your data.
+
+By using Co-op Cloud infrastructure over private cloud infrastructure, you create a few possibilities:
+
+- You may interact with a server provider that is more ethical than Big Tech. Although the server provider may still succumb to law enforcement, you might place more trust in some providers than in private cloud providers (e.g. AWS).
+
+- You may be able to situate your servers in locations that are relatively more impervious to law enforcement attempts to dismantle your infrastructure. Indeed, if you deployed your infrastructure in a relatively secure setting such as Switzerland, then you would weather a greater chance of keeping your infrastructure alive than if you deployed it in, say, the United States. Protonmail and [Extinction Rebellion (XR)](https://www.youtube.com/watch?v=I_O3zj3p52A) choose Switzerland for their servers, for reasons along these lines.

docs/operators/handbook.md

@@ -376,9 +376,9 @@ abra app run foo.bar.com db bash -c 'mysqldump -u root -p"$(cat /run/secrets/db_
 ## Can I deploy a recipe without `abra`?
 
 Yes! It's a design goal to keep the recipes not dependent on `abra` or any
-single tool that we develop. This means the configurationc commons can still be
-useful beyond this project. You can deploy a recipe with standard commands like
-so:
+single tool that we develop. This means that the configuration commons can
+still be useful beyond this project. You can deploy a recipe with standard
+commands like so:
 
 ```
 set -a
@@ -387,8 +387,7 @@ cd ~/.abra/recipes/myrecipe
 docker stack deploy -c compose.yml example_com
 ```
 
-`abra` makes all of this more cenvenient but other tooling could follow this
-approach.
+`abra` makes all of this more convenient.
 
 ## Proxying apps outside of Co-op Cloud with Traefik?
 

mkdocs.yml

@@ -2,6 +2,7 @@
 site_author: Co-op Cloud
 site_name: "Co-op Cloud: Public Interest Infrastructure"
 site_url: https://docs.coopcloud.tech
+use_directory_urls: true
 
 theme:
   name: material
@@ -20,7 +21,7 @@ theme:
   favicon: img/favicon.ico
   custom_dir: custom_theme/
 
-copyright: Copyleft 🄯 2022 Co-op Cloud
+copyright: Copyleft 2023 Co-op Cloud
 
 markdown_extensions:
   - meta
@@ -81,8 +82,11 @@ nav:
           - federation/resolutions/passed/003.md
           - federation/resolutions/passed/004.md
           - federation/resolutions/passed/005.md
+          - federation/resolutions/passed/006.md
         - "In progress":
           - federation/resolutions/in-progress/index.md
+          - federation/resolutions/in-progress/009.md
+          - federation/resolutions/in-progress/010.md
         - "Draft":
           - federation/resolutions/drafts/index.md
       - "Finance": federation/finance.md
@@ -96,8 +100,8 @@ nav:
     - glossary/index.md
 
 plugins:
-  - search
   - awesome-pages
+  - search
 
 repo_name: coop-cloud/docs.coopcloud.tech
 repo_url: https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/

requirements.txt

@@ -1,4 +1,4 @@
 mkdocs-awesome-pages-plugin==2.9.1
 mkdocs-material-extensions==1.1.1
-mkdocs-material==9.1.15
+mkdocs-material==9.1.19
 mkdocs==1.4.3