Kanthaus wiki - User contributions [en]

Waste management

2025-08-09T05:33:53Z

Antonin: /* Waste management */ typo

== Waste management ==
We all know that lots of things which are considered waste can be very valuable. It's great to learn and teach about repairing and upcycling. But there comes the point where we have to get rid of some of the potential in order to give our souls some rest.

This page wants to inform about how different materials are handled and where they are stored. Also there's information on recycling places and landfills and guides on what to put in which bin.

== Different kinds of materials ==

=== Old textiles ===

* pure cotton things can be turned into butt towels
* textile without holes can go to Free Shop first
* with holes/sorted out/broken: old textile containers in the city or at Wertstoffhof Kell
* oily rags and similar: black bin

=== Paper/cardboard ===

* Paper could be sold at TIAx but is probably not worth the effort. Off to the blue bin!
* Cardboard should get folded and put in the blue bin
* banana boxes are nice so consider keeping them

=== Bottles and Jars ===

* size 77 jars and lids are being kept
* the rest gets collected in K20-basement
* empty bottles and jars go into the recycling containers that are around the town (Lidl parking lot)
* deposit (Pfand) can be returned best at Rewe

=== Organic ===

* everything organic, can be accompanied by some paper
* messy egg boxes

=== Compost ===

* most organic stuff
* no: cooked things, meat, citrus

=== Construction waste ===

* tiles, bricks, stone, concrete, ceramics, porcellain
* depending on the place it's more or less important to have purely mineral waste

=== Wood ===

* there are 4 categories of Altholz and it can be quite expensive to dispose of

=== Metal ===

* we keep some things out of metal for building and soldering in K18 basement
* most things can be collected and sold at TIAx, alternatively people like to come by and collect it for free

=== Electric devices ===

* to do: find out if TIAx also takes it

=== Batteries ===

* non-rechargables can be brought to any supermarket from time to time
* rechargables and devices containing rechargables are stored waterproof outside, can be brought to Kell from time to time

=== Paint ===

* let it dry in the sun, as soon as the surface cracks it can be put into the black bin

=== Hazardous stuff ===

* this is a quite wide variety. Generelly store outside and rainsafe.
* Schadstoffmobil takes some stuff but by far not everything
* ZAW Cröbern probably takes most stuff

== Black bin ==

* Each emptying costs 10€. Please consider some things when using it.

=== Yes ===

* small amounts of broken porcellain and mixed construction waste
* smaller sized glued or painted wood
* dry paint
* floor sweepings
* old dirty rags

=== No ===

* bulky stuff
* metal (better collect and sell)
* stuff that can also go in other bins
* textile that's not super destroyed

== Yellow bin ==

* Packaging material (styrofoam, plastic, tin, containers, plastic bags, wrapping foil, to-go-cups)
* some sources say that it's okay to put small amounts of hard plastics in the yellow bin

== Blue bin ==

* Paper
* Folded cardboard
* If they're too full, you can climb in and trample the contents down

== Construction waste ==

* Kell Wertstoffhof takes it for 10€ per 100kg (not sure if this is true as there's old KH information saying 15€/ton)
* TiAx is offering containers (5,7,10m³), costs are about 130€ + 27,50€ per ton (source: phone call 6/25). Additionally needs [https://www.wurzen.de/buergerservice/dienstleistungen/containerstellung-900000049-0.html?myMedium=1 Antrag] to place container on the street.
* [https://www.dsb-degenhardt.de/kontakt DSB Degenhardt], Grube Lübschütz. Nice place and probably cheapest and easiest option for up until 1.5 tons. About 10€ per m³ (guess)
* ancient Kanthaus sources say Alba takes construction waste for 32,47€/ton

== Recycling places ==

=== Kell Wertstoffhof Wurzen ===

* public recycling place where they take a wide variety of stuff
* opening hours: tu-fr, 09:00-17:00
** also open @2nd saturday of each month, where they also take hazardous material (Schadstoffmobil)
* most services here are free for Wurzeners
** they could ask for a proof of residency
** there's a limit on how much bulky waste you can dump (something like 2 m³)

==== What they take and how they want you to seperate ====

*Bulky waste/Sperrmüll
**glued wood, pressboard panels, tapestry, bulky plastic stuff
*Electric waste/cable stuff without batteries or solar panels
*Batteries, accumulators
*Scrap Metal (better sell it at TiAx)
*Textiles
*Construction waste (10€ per 100 kg)

=== [https://tiax-recycling.de TIAx Transport und Recycling] ===

* place to sell mainly scrap metal (mixed and or sorted)
* they say prices are based on the daily value.
** mixed scrap metal: 128€ per ton (03/2025)
* opening hours: mo-fr, 07:00-12:00 & 13:00-16:00

=== [https://www.dsb-degenhardt.de/kontakt Grube Lübschütz, DSB Degenhardt] ===

* opening hours: mo-fr 7:00-16:00. from april to october until 17:00 and also on saturdays until 12:00
* [https://www.openstreetmap.org/node/4784787415 B107, 800 meters to Lübschütz coming from B6.] 7,5km from KH

=== [https://www.wev-sachsen.de/2025/06/10/fuer-unsere-kleinanlieferer-noch-einfacher-entsorgen-ab-1-juli-2025/ Zentraldeponie Cröbern] [https://www.zaw-sachsen.de/entsorgung/privatpersonen-und-kleingewerbe/ - Zweckverband Abfallwirtschaft Westsachsen] ===

* far away, only reasonable for some special stuff

* Am Westufer 3, 04463 Großpösna/OT Störmthal

* Telefon: 034299 705-0 ; E-Mail: info@zaw-sachsen.de
* Mo-Fr 16-19:00

=== [https://www.remondis-sachsen.de/standort-trebsen/ Remondis Recyclinghof Trebsen] ===

* similiar to Kell Wurzen

=== [https://sachsen.alba.info/unternehmen/standorte/detail/standort-wurzen/ Alba Wurzen] ===

* similiar to Kell Wurzen (probably)

== Things we keep which might be considered trash elsewhere ==
* Egg cartons
* candle butts
* soap bar remainings
* kitchen sponges

Water usage tracking

2025-07-06T05:29:44Z

Antonin: /* Updating the firmware */ fix markup

💧 We log our water usage over time in [[Grafana]]. To do so, we have two small devices next to our main water meter and warm water meter respectively. They periodically read the meter by taking a picture and recognizing digits in it (currently every 5 minutes). This page describes how those devices are set up, how to maintain them and how to install similar ones elsewhere.
[[File:Water meter reader.jpg|thumb]]

== Overview ==

The device is an ESP32-CAM board with an OV2640 camera module. It can be obtained from many suppliers (we use [https://arduino-projekte.info/produkt/esp32-cam-mit-ov2640-kamera-modul/ this one]). The software on the device is the [https://github.com/jomjol/AI-on-the-edge-device AI-on-the-edge-device] firmware, which does the digitization and upload to InfluxDB directly from the board itself. General documentation for this firmware is available on [https://github.com/jomjol/AI-on-the-edge-device/wiki its GitHub wiki], this document focuses on the Kanthaus-specific parts.

== Setting up the device ==

First, we need a power source (5V DC) for the board. We have plenty of such adapters in the electronics workshop, all that is needed is to solder the appropriate connectors to plug the power source to the board. The camera that comes with the device is set up for a focal length that is not adapted to this use, so we need to rotate the objective to obtain a sharp image of the meter at a close distance. This requires [https://github.com/jomjol/AI-on-the-edge-device/wiki/Installation removing the glue which holds the objective in place]. This step is quite fiddly, do not bring the lens too close to the sensor either or you could break the camera. The device comes with a default firmware which lets you stream from the camera over WiFi, which helps with checking the sharpness as you make changes. To do so, connect the device to a power source and connect to the WiFi network it creates. Then, go to <code>http://192.168.4.1/</code> and you are able to stream directly from the device’s camera.

The devices use by default an internal WiFi antenna which is not very strong. It is very advisable to use the external antenna instead, but that requires unsoldering a very small resistor and soldering it in another position, which requires some skill.

== Network settings ==

The devices are connected to the <code>kh-iot</code> WiFi network, which means it has limited network access. Their IP addresses are static:
* <code>192.168.5.37</code> for the main water meter
* <code>192.168.5.38</code> for the warm water meter

To access its web UI connect to the <code>kh-admin</code> network and go to <code>http://192.168.5.37/</code> (or <code>http://192.168.5.38/</code> for the warm water meter). If you are outside of Kanthaus, use SSH port forwarding via kanthaus-server, such as <code>ssh -L 8080:192.168.5.37:80 kanthaus-server</code>, and then point your browser to <code>http://localhost:8080/</code>.

The network settings for the device can be changed by taking out the SD card in it and modifying the <code>wlan.ini</code> file on the card.

== Updating the firmware ==

The firmware can be updated in two ways:
* either via the web interface
* or by flashing the device directly, using a USB-to-Serial adapter. We have one in the electronics workshop for this.

To flash via USB, the connections look like this: [[File:../images/water_meter_reader_ftdi.jpg|Connecting a FTDI adatper to flash the firmware]]

Flashing the device requires three binary files, which can be copied to device using <code>esptool.py</code> (which can be installed with <code>pip install esptool</code>):

<pre>esptool.py erase_flash
esptool.py write_flash 0x01000 bootloader.bin 0x08000 partitions.bin 0x10000 firmware.bin</pre>

== Training the digitizer ==

Before the device can read the meter, it needs to be calibrated. This would need to be done again for instance when our water meter is renewed. This can be done from the web UI directly. Refer to [https://github.com/jomjol/AI-on-the-edge-device/wiki/Graphical-configuration the official documentation] for more details about the process.

== Development environment ==

The [https://github.com/jomjol/AI-on-the-edge-device/wiki/Build-Instructions official documentation] recommends to use VSCode with the PlatformIO extension to develop, but sadly PlatformIO is not available for VSCodium at the time of writing this. Instead you can relatively easily work with a text editor, and install [https://platformio.org/ PlatformIO] in a Python virtualenv (from the <code>code/</code> subdirectory of the repository):

<pre>python3 -m venv .venv
source .venv/bin/activate
pip install platformio esptool</pre>
and then you can compile the firmware with

<pre>platformio run --environment esp32cam</pre>
This generates the three <code>.bin</code> files required for flashing in the <code>.pio/build/esp32cam</code> subdirectory.

For debugging purposes it is useful to use the USB-to-Serial adapter to see detailed logs. First, connect the adapter to the device (by crossing the RX/TX wires and connecting GND and +5V). Then, locate the USB-to-Serial adapter by listing the USB devices before and after plugging in. Once you have the path to the device, you can then open it with: <code>screen /dev/ttyUSB0 115200</code>. If screen terminates immediately you might need to add your user to the <code>dialout</code> group, see [https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/establish-serial-connection.html the detailed instructions for serial communication with ESP32].
[[Category:Technical]]

Water usage tracking

2025-07-06T05:29:18Z

Antonin: /* Network settings */ fix markup

💧 We log our water usage over time in [[Grafana]]. To do so, we have two small devices next to our main water meter and warm water meter respectively. They periodically read the meter by taking a picture and recognizing digits in it (currently every 5 minutes). This page describes how those devices are set up, how to maintain them and how to install similar ones elsewhere.
[[File:Water meter reader.jpg|thumb]]

== Overview ==

The device is an ESP32-CAM board with an OV2640 camera module. It can be obtained from many suppliers (we use [https://arduino-projekte.info/produkt/esp32-cam-mit-ov2640-kamera-modul/ this one]). The software on the device is the [https://github.com/jomjol/AI-on-the-edge-device AI-on-the-edge-device] firmware, which does the digitization and upload to InfluxDB directly from the board itself. General documentation for this firmware is available on [https://github.com/jomjol/AI-on-the-edge-device/wiki its GitHub wiki], this document focuses on the Kanthaus-specific parts.

== Setting up the device ==

First, we need a power source (5V DC) for the board. We have plenty of such adapters in the electronics workshop, all that is needed is to solder the appropriate connectors to plug the power source to the board. The camera that comes with the device is set up for a focal length that is not adapted to this use, so we need to rotate the objective to obtain a sharp image of the meter at a close distance. This requires [https://github.com/jomjol/AI-on-the-edge-device/wiki/Installation removing the glue which holds the objective in place]. This step is quite fiddly, do not bring the lens too close to the sensor either or you could break the camera. The device comes with a default firmware which lets you stream from the camera over WiFi, which helps with checking the sharpness as you make changes. To do so, connect the device to a power source and connect to the WiFi network it creates. Then, go to <code>http://192.168.4.1/</code> and you are able to stream directly from the device’s camera.

The devices use by default an internal WiFi antenna which is not very strong. It is very advisable to use the external antenna instead, but that requires unsoldering a very small resistor and soldering it in another position, which requires some skill.

== Network settings ==

The devices are connected to the <code>kh-iot</code> WiFi network, which means it has limited network access. Their IP addresses are static:
* <code>192.168.5.37</code> for the main water meter
* <code>192.168.5.38</code> for the warm water meter

To access its web UI connect to the <code>kh-admin</code> network and go to <code>http://192.168.5.37/</code> (or <code>http://192.168.5.38/</code> for the warm water meter). If you are outside of Kanthaus, use SSH port forwarding via kanthaus-server, such as <code>ssh -L 8080:192.168.5.37:80 kanthaus-server</code>, and then point your browser to <code>http://localhost:8080/</code>.

The network settings for the device can be changed by taking out the SD card in it and modifying the <code>wlan.ini</code> file on the card.

== Updating the firmware ==

The firmware can be updated in two ways: * either via the web interface * or by flashing the device directly, using a USB-to-Serial adapter. We have one in the electronics workshop for this.

To flash via USB, the connections look like this: [[File:../images/water_meter_reader_ftdi.jpg|Connecting a FTDI adatper to flash the firmware]]

Flashing the device requires three binary files, which can be copied to device using <code>esptool.py</code> (which can be installed with <code>pip install esptool</code>):

<pre>esptool.py erase_flash
esptool.py write_flash 0x01000 bootloader.bin 0x08000 partitions.bin 0x10000 firmware.bin</pre>
== Training the digitizer ==

Before the device can read the meter, it needs to be calibrated. This would need to be done again for instance when our water meter is renewed. This can be done from the web UI directly. Refer to [https://github.com/jomjol/AI-on-the-edge-device/wiki/Graphical-configuration the official documentation] for more details about the process.

== Development environment ==

The [https://github.com/jomjol/AI-on-the-edge-device/wiki/Build-Instructions official documentation] recommends to use VSCode with the PlatformIO extension to develop, but sadly PlatformIO is not available for VSCodium at the time of writing this. Instead you can relatively easily work with a text editor, and install [https://platformio.org/ PlatformIO] in a Python virtualenv (from the <code>code/</code> subdirectory of the repository):

<pre>python3 -m venv .venv
source .venv/bin/activate
pip install platformio esptool</pre>
and then you can compile the firmware with

<pre>platformio run --environment esp32cam</pre>
This generates the three <code>.bin</code> files required for flashing in the <code>.pio/build/esp32cam</code> subdirectory.

For debugging purposes it is useful to use the USB-to-Serial adapter to see detailed logs. First, connect the adapter to the device (by crossing the RX/TX wires and connecting GND and +5V). Then, locate the USB-to-Serial adapter by listing the USB devices before and after plugging in. Once you have the path to the device, you can then open it with: <code>screen /dev/ttyUSB0 115200</code>. If screen terminates immediately you might need to add your user to the <code>dialout</code> group, see [https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/establish-serial-connection.html the detailed instructions for serial communication with ESP32].
[[Category:Technical]]

Email

2025-02-04T19:29:07Z

Antonin: /* Giving access to Kanthaus email to a personal account */ fix imported markup :(

We have email accounts hosted on [https://uberspace.de/en/ uberspace.de]. 📨

== For users ==

Ask an existing volmem familiar with email administration to [[#for-administrators|create an account for you]]. We recommend using Thunderbird to access Kanthaus email, which will let you access Kanthaus email alongside your other email accounts, provide offline access to your emails and simplify the process of responding to Kanthaus emails.

=== Accessing Kanthaus email on the web ===

If you don’t want to use a client like Thunderbird, you can access the email online at https://webmail.uberspace.de/.

When replying to hello@ messages, remember to add the <code>hello</code> address in both Reply-to: and Cc:.

It is also worth configuring your account to display a name instead of just your email address. In the top right corner, click on the menu -> Settings. Then click on “Identity: <your-name>@kanthaus.online” and set a name there.

=== Setting up Kanthaus email in Thunderbird ===

Open up Thunderbird, go to “Tools -> Account settings”, and create a new account with your Kanthaus email address and password just created by an administrator for you:
[[File:1 basic configuration (Thunderbird tutorial) .png|none|thumb|Screenshot of initial configuration screen in Thunderbird]]

If Thunderbird fails to detect the settings automatically, you might have to adjust the settings as follows:

* Server (both for IMAP and SMTP): gehrels.uberspace.de
* Connection security: STARTTLS
* IMAP port: 143
* SMTP port: 587

[[File:2 detailed configuration (Thunderbird tutorial) .png|none|thumb|Screenshot of server settings configuration screen in Thunderbird]]

Once your account has been created, go to the settings:
[[File:3 account created (Thunderbird tutorial) .png|none|thumb|Screenshot of the link to account settings after account creation]]

Click the “Manage Identities…” button and click “Add” to create a new identity:
[[File:4 manage identities (Thunderbird tutorial) .png|none|thumb|Screenshot of the dialog to manage identities]]

Use the following settings:

* Your name: the same name as you would use on your normal account
* Email address: still the same address
* Reply-to address: the <code>hello</code> address (@kanthaus.online).
* Organization: Kanthaus
* Identity Label: Hello@Kanthaus (or anything else you want - but it cannot be left empty)
* Tick "Reply from this identity when delivery headers match and add the <code>hello</code> address there as well. '''Note''': this field is not immediately visible: you need to leave the dialog and edit the identity again for it to appear.

This will ensure that whenever you are replying to common email, you are telling your recipients to reply to the common address and not to you personally.
[[File:5 identity configuration (Thunderbird tutorial) .png|none|thumb|Screenshot of the identity settings]]

Then, go to the “Copies & Folders” tab and tick “Cc these email addresses” and add the <code>hello</code> address again. This will ensure that other Kanthausians are seeing your replies.
[[File:6 cc configuration (Thunderbird tutorial) .png|none|thumb|Screenshot of the copies and folders tab]]

That’s it! You can close the dialog with “OK”. You are now ready to reply to Kanthaus email. They are located in the “hello” folder under your account:
[[File:7 folders (Thunderbird tutorial) .png|none|thumb|Screenshot of the folders in a typical Kanthaus email account]]

When replying to Kanthaus email we recommend you will automatically have the <code>hello</code> address in Cc: and Reply-To:, so that further replies are visible for others. When that is not wished, you can remove those manually.
[[File:8 composing email (Thunderbird tutorial) .png|none|thumb|Screenshot of replying to an email with default settings]]

== For administrators ==

=== Creating a new personal email account ===

Login to Uberspace’s dashboard with Kanthaus’ account and go to [https://dashboard.uberspace.de/dashboard/mail the Email tab]. At the bottom of the page you will find “Virtual Mailboxes” section where you can add your own. Pick a fresh password for it.

=== Changing account password ===
Sadly, this can't be done by users themselves. You can change passwords through Uberspace, either though the web portal, or via the [https://manual.uberspace.de/mail-mailboxes/ ssh].

=== Giving access to Kanthaus email to a personal account ===

Once you have created a personal account, you can set it up so that it contains the general email received by Kanthaus (at the <code>hello</code> address) as a subfolder. You can set it up as follows:

* SSH into <code>gehrels.uberspace.de</code> (username <code>kanthaus</code>). This can be done by password or SSH key.
* Navigate to the email folder (<code>cd users/firstname</code> where <code>firstname</code> is the email user name)
* Create a symlink to the <code>hello</code> account with <code>ln -s ../hello/ .hello</code>
* Add the <code>hello</code> folder to the subscriptions: <code>echo hello >> subscriptions</code>

There are some other folders inside our mailbox that you could be interested in mirroring in the own account:
* the “Mailinglists” folder, which receives messages from mailing lists of befriended projects and other initiatives in the area.
* the “Spam” folder, in which spam gets sorted automatically (and therefore not always accurately).

To subscribe to those as well, you can do again <code>ln -s ../hello/.Spam/ .hello_spam</code> and <code>echo hello_spam >> subscriptions</code> for the Spam folder for instance.

Once that is done the person should have access to Kanthaus email in their email client.

== Email filtering ==

The Spam filtering we use is [https://manual.uberspace.de/mail-spam/ the default one offered by Uberspace].

On top of that, we have extra rules to sort messages into folders, for instance for mailing lists. Those filtering rules are managed by [https://manual.uberspace.de/mail-filters/ the Sieve system offered by Uberspace]. If you want to change those filters, here are some possible steps:

* First, get hold of the password for our hello@ email account. It is in our password store.
* Then, install [http://sieve.info/clients a ManageSieve client] and use it to connect to the hello@ address. You can pick from a wide range of clients. For instance, the <code>sieve-connect</code> command line interface is available on Ubuntu/Debian and works. The credentials required are:
** Server: gehrels.uberspace.de
** Port: 4190 (standard)
** Username: The email address
** The password for it
* Now you have access to the Sieve scripts available on the address and let you edit them.
[[Category:Digital]]

Git

2025-01-18T13:11:32Z

Antonin: /* Backing up Forgejo’s data */ fix botched markup

📋️ We use Git to store mutable data. Our Git repositories are hosted with [https://forgejo.org Forgejo] on [[Server|our own server]]. For immutable files we have a [[Nextcloud]] in the same location.

== What is Forgejo? ==
Forgejo is basically a social network built on top of the [https://git-scm.com/book/en/v2/Getting-Started-Git-Basics git technology] for version control. It is normally used for code, because it makes it easy to collaborate on common projects without breaking anything.

== Why did you decide to use this? ==
* We want to help people learn things and appreciate technology!
* Data that was put in git is extremely secure, because it’s stored on multiple people’s computers.
* If multiple people work on the same file it’s possible to tell who changed which exact character.
* It’s easy to put content from Forgejo onto our website.
* Everybody becomes a webmaster. 🙂
* The people who decided on this were already used to it… 😉

== What is stored where? ==
So far we have the following repositories: - [https://git.kanthaus.online/kanthaus/kanthaus.online kanthaus.online], where we store our website, https://kanthaus.online/. - [https://git.kanthaus.online/kanthaus/kanthaus-private kanthaus-private], where we store our [[residence record]], internal meeting minutes, financial plans and other stuff that contains personal information. Everything of relevance that consists of text and has pieces of confidential data should be put here. - [https://git.kanthaus.online/kanthaus/kanthaus-public kanthaus-public], which is publicly accessible as the name suggests. In this repository we do our task management via issues (which you can find [https://git.kanthaus.online/kanthaus/kanthaus-public/issues here]). This is especially important for our [[../social/roadmap.md|roadmap plannings]]. Other than that we have drafts, policies, signs, data on our water, electricity and gas usage and much more in here. - [https://git.kanthaus.online/kanthaus/kanthaus-ansible kanthaus-ansible] is for keeping our server tidy. Nothing you need to worry about, except you’re actually interested. In that case feel free to ask Matthias about it! - [https://git.kanthaus.online/kanthaus/handbook handbook] is where this handbook is stored. - [https://gitlab.com/kanthaus/expfloorer expfloorer] hosts a floorplan of Kanthaus.

== How to use it ==
Go to https://git.kanthaus.online and log in with your Nextcloud account. You will be automatically added to the “Kanthaus” organization in which our repositories are stored: https://git.kanthaus.online/kanthaus

You can modify the files there directly via your web browser.

== Cloning repositories on your machine ==
If you are working with local clones, you need to update those to point to Kanthaus Git instead of GitLab (which we were using before Forgejo).

On the page of each repository, such as https://git.kanthaus.online/kanthaus/handbook, copy the clone URL you prefer. For instance, for the handbook, they look like this: * HTTPS: <code>https://git.kanthaus.online/kanthaus/handbook.git</code> * SSH: <code>ssh://git@ssh.git.kanthaus.online:2222/kanthaus/handbook.git</code>

In your local clone, run:

<pre>git remote set-url origin <new-url></pre>
Note that if you want to use SSH URLs, you first need to [https://git.kanthaus.online/user/settings/keys add an SSH key].

== Instructions for administrators ==

We are running Forgejo via Docker inside our Docker-Compose deployment of services on the <code>kanthaus-server</code>.

=== Setting it up from scratch ===

After launching the service via Docker, the following manual steps need to be taken to configure the instance:
* Go to https://git.kanthaus.online/ where the set-up screen should display. Change the following settings:
* Site title: “Kanthaus Git”
* SMTP host: gehrels.uberspace.de
* SMTP port: 587
* Send email as: git@kanthaus.online
* SMTP user: git@kanthaus.online
* SMTP password: found in the Kanthaus keepass
* Tick “Enable email notifications”
* Tick “Disable Gravatar”
* Tick “Allow registration only via external services”
* Tick “Hide email addresses by default”
* Domain for hidden email addresses: <code>git.kanthaus.online</code>
* Set up an admin user with credentials you own: we will delete it later on
* After validating the sign-up form, go to https://git.kanthaus.online/org/create and create a “kanthaus” organization. You can prettify it a little, by adding a bit of metadata at https://git.kanthaus.online/org/kanthaus/settings and uploading a logo from https://kanthaus.online/pics/newLogo.png
* In Forgejo’s configuration file (<code>/data/services/forgejo/config/app.ini</code>), add the following lines at the end:

<pre>[oauth2_client]
USERNAME = userid
ENABLE_AUTO_REGISTRATION = true</pre>
You can also take this opportunity to add <code>LANDING_PAGE = /kanthaus</code> in the <code>[server]</code> section. And disable OpenID login:

<pre>[openid]
ENABLE_OPENID_SIGNIN = false
ENABLE_OPENID_SIGNUP = false</pre>
* Make sure our Nextcloud instance has the [https://apps.nextcloud.com/apps/oidc OIDC Identity Provider] app installed
* Go to [https://cloud.kanthaus.online/settings/admin/security Nextcloud’s security settings] (while logged in with an administrator account in NextCloud) and generate a new OpenID Connect client (if it does not exist yet), with the following details
** Name: Forgejo
** Redirection URI: https://git.kanthaus.online/user/oauth2/NextCloud/callback
* Go to [https://git.kanthaus.online/admin/auths Forgejo’s Authentication Sources] and click “Add an authentication source”, with the following settings:
** Authentication type: OAuth2
** Authentication name: “NextCloud”
** OAuth2 provider: OpenID Connect
** Client ID: the client ID produced at the previous step
** Client secret: the client secret produced at the previous step
** OpenID Connect Auto Discovery URL: https://cloud.kanthaus.online/.well-known/openid-configuration
** Additional scopes: <code>email</code>
** Claim name providing group names for this source: <code>roles</code>
** Group claim value for administrator users: <code>admin</code>
** Map claimed groups to Organization teams: <code>{"Kanthaus": {"kanthaus": ["Owners"]}}</code>
* Restart forgejo with <code>docker-compose restart forgejo</code> (in <code>/opt/kh-services</code>)

Note: this configuration relies on our NextCloud instance having the [https://docs.nextcloud.com/server/27/admin_manual/configuration_server/config_sample_php_parameters.html “clean URLs” option] enabled. Otherwise, the URLs need to be adapted to add <code>index.php</code> in them, such as <code>https://cloud.kanthaus.online/index.php/.well-known/openid-configuration</code>.

=== Setting up SSH access ===

To let users clone via SSH, we need to take some additional steps. In the configuration file (<code>/data/services/forgejo/config/app.ini</code>), set those settings (if not set already):

<pre>[server]
START_SSH_SERVER = true
SSH_PORT = 2222
SSH_LISTEN_PORT = 2222
SSH_LISTEN_HOST = 0.0.0.0
SSH_DOMAIN = ssh.git.kanthaus.online</pre>
Then, set up a port forwarding in OpenWISP. You need to be connected to the <code>kanthaus-admin</code> network for this and go to [https://192.168.178.1/firewall_nat.php the NAT Port Forward page]. Create a new rule: * Interface: WAN * TCP/IP version: IPv4+IPv6 * Protocol: TCP * Destination: WAN address * Destination port range: (other) 2222 to (other) 2222 * Redirect target port: 2222 * Description: git SSH access for Forgejo

The <code>ssh.git.kanthaus.online</code> should point to the Fritzbox (not kanthaus-server) so that it can take care of forwarding the port. If the domain points to kanthaus-server, connecting over IPv6 will likely fail.

=== Setting up the continuous integration ===

In the configuration file (<code>/data/services/forgejo/config/app.ini</code>), set those settings (if not set already):

<pre>[actions]
ENABLED = true</pre>
Then, go to the [https://git.kanthaus.online/user/settings/actions/runners Runners Management] page and click “Create new Runner”. Copy the registration token and put it in <code>/opt/kh-services/.env</code> as <code>FORGEJO_RUNNER_REGISTRATION_TOKEN</code>.

Delete <code>/data/services/forgejo_runner/.runner</code> if it is present.

Restart the runner with <code>docker-compose up -d</code> in <code>/opt/kh-services</code>.

The runner will register and should become visible [https://git.kanthaus.online/user/settings/actions/runners in Forgejo’s settings].

For each repository where you want to use the runner, you need to enable actions in the repository’s settings.

=== Backing up Forgejo’s data ===

You need to back up two things:
* the contents of <code>/data/services/forgejo</code>
* the Postgresql database.

To do so:
* First, find out the container id of the postgres instance with <code>docker ps | grep kh-services_postgres</code> and copy the first hash in the output to the second command, in place of <code><container-id></code>
* Run <code>docker exec -it <container-id> pg_dump -U postgres --clean forgejo | gzip > forgejo_database_dump.sql.gz</code>

To restore the backup, you need to:
* restore the contents of <code>/data/services/forgejo</code>
* restore the database similarly with: <code>cat forgejo_database_dump.sql.gz | gunzip | docker exec -i <container-id> psql -U postgres forgejo</code>

Git

2025-01-18T13:07:58Z

Antonin: /* Setting it up from scratch */

📋️ We use Git to store mutable data. Our Git repositories are hosted with [https://forgejo.org Forgejo] on [[Server|our own server]]. For immutable files we have a [[Nextcloud]] in the same location.

== What is Forgejo? ==
Forgejo is basically a social network built on top of the [https://git-scm.com/book/en/v2/Getting-Started-Git-Basics git technology] for version control. It is normally used for code, because it makes it easy to collaborate on common projects without breaking anything.

== Why did you decide to use this? ==
* We want to help people learn things and appreciate technology!
* Data that was put in git is extremely secure, because it’s stored on multiple people’s computers.
* If multiple people work on the same file it’s possible to tell who changed which exact character.
* It’s easy to put content from Forgejo onto our website.
* Everybody becomes a webmaster. 🙂
* The people who decided on this were already used to it… 😉

== What is stored where? ==
So far we have the following repositories: - [https://git.kanthaus.online/kanthaus/kanthaus.online kanthaus.online], where we store our website, https://kanthaus.online/. - [https://git.kanthaus.online/kanthaus/kanthaus-private kanthaus-private], where we store our [[residence record]], internal meeting minutes, financial plans and other stuff that contains personal information. Everything of relevance that consists of text and has pieces of confidential data should be put here. - [https://git.kanthaus.online/kanthaus/kanthaus-public kanthaus-public], which is publicly accessible as the name suggests. In this repository we do our task management via issues (which you can find [https://git.kanthaus.online/kanthaus/kanthaus-public/issues here]). This is especially important for our [[../social/roadmap.md|roadmap plannings]]. Other than that we have drafts, policies, signs, data on our water, electricity and gas usage and much more in here. - [https://git.kanthaus.online/kanthaus/kanthaus-ansible kanthaus-ansible] is for keeping our server tidy. Nothing you need to worry about, except you’re actually interested. In that case feel free to ask Matthias about it! - [https://git.kanthaus.online/kanthaus/handbook handbook] is where this handbook is stored. - [https://gitlab.com/kanthaus/expfloorer expfloorer] hosts a floorplan of Kanthaus.

== How to use it ==
Go to https://git.kanthaus.online and log in with your Nextcloud account. You will be automatically added to the “Kanthaus” organization in which our repositories are stored: https://git.kanthaus.online/kanthaus

You can modify the files there directly via your web browser.

== Cloning repositories on your machine ==
If you are working with local clones, you need to update those to point to Kanthaus Git instead of GitLab (which we were using before Forgejo).

On the page of each repository, such as https://git.kanthaus.online/kanthaus/handbook, copy the clone URL you prefer. For instance, for the handbook, they look like this: * HTTPS: <code>https://git.kanthaus.online/kanthaus/handbook.git</code> * SSH: <code>ssh://git@ssh.git.kanthaus.online:2222/kanthaus/handbook.git</code>

In your local clone, run:

<pre>git remote set-url origin <new-url></pre>
Note that if you want to use SSH URLs, you first need to [https://git.kanthaus.online/user/settings/keys add an SSH key].

== Instructions for administrators ==

We are running Forgejo via Docker inside our Docker-Compose deployment of services on the <code>kanthaus-server</code>.

=== Setting it up from scratch ===

After launching the service via Docker, the following manual steps need to be taken to configure the instance:
* Go to https://git.kanthaus.online/ where the set-up screen should display. Change the following settings:
* Site title: “Kanthaus Git”
* SMTP host: gehrels.uberspace.de
* SMTP port: 587
* Send email as: git@kanthaus.online
* SMTP user: git@kanthaus.online
* SMTP password: found in the Kanthaus keepass
* Tick “Enable email notifications”
* Tick “Disable Gravatar”
* Tick “Allow registration only via external services”
* Tick “Hide email addresses by default”
* Domain for hidden email addresses: <code>git.kanthaus.online</code>
* Set up an admin user with credentials you own: we will delete it later on
* After validating the sign-up form, go to https://git.kanthaus.online/org/create and create a “kanthaus” organization. You can prettify it a little, by adding a bit of metadata at https://git.kanthaus.online/org/kanthaus/settings and uploading a logo from https://kanthaus.online/pics/newLogo.png
* In Forgejo’s configuration file (<code>/data/services/forgejo/config/app.ini</code>), add the following lines at the end:

<pre>[oauth2_client]
USERNAME = userid
ENABLE_AUTO_REGISTRATION = true</pre>
You can also take this opportunity to add <code>LANDING_PAGE = /kanthaus</code> in the <code>[server]</code> section. And disable OpenID login:

<pre>[openid]
ENABLE_OPENID_SIGNIN = false
ENABLE_OPENID_SIGNUP = false</pre>
* Make sure our Nextcloud instance has the [https://apps.nextcloud.com/apps/oidc OIDC Identity Provider] app installed
* Go to [https://cloud.kanthaus.online/settings/admin/security Nextcloud’s security settings] (while logged in with an administrator account in NextCloud) and generate a new OpenID Connect client (if it does not exist yet), with the following details
** Name: Forgejo
** Redirection URI: https://git.kanthaus.online/user/oauth2/NextCloud/callback
* Go to [https://git.kanthaus.online/admin/auths Forgejo’s Authentication Sources] and click “Add an authentication source”, with the following settings:
** Authentication type: OAuth2
** Authentication name: “NextCloud”
** OAuth2 provider: OpenID Connect
** Client ID: the client ID produced at the previous step
** Client secret: the client secret produced at the previous step
** OpenID Connect Auto Discovery URL: https://cloud.kanthaus.online/.well-known/openid-configuration
** Additional scopes: <code>email</code>
** Claim name providing group names for this source: <code>roles</code>
** Group claim value for administrator users: <code>admin</code>
** Map claimed groups to Organization teams: <code>{"Kanthaus": {"kanthaus": ["Owners"]}}</code>
* Restart forgejo with <code>docker-compose restart forgejo</code> (in <code>/opt/kh-services</code>)

Note: this configuration relies on our NextCloud instance having the [https://docs.nextcloud.com/server/27/admin_manual/configuration_server/config_sample_php_parameters.html “clean URLs” option] enabled. Otherwise, the URLs need to be adapted to add <code>index.php</code> in them, such as <code>https://cloud.kanthaus.online/index.php/.well-known/openid-configuration</code>.

=== Setting up SSH access ===

To let users clone via SSH, we need to take some additional steps. In the configuration file (<code>/data/services/forgejo/config/app.ini</code>), set those settings (if not set already):

<pre>[server]
START_SSH_SERVER = true
SSH_PORT = 2222
SSH_LISTEN_PORT = 2222
SSH_LISTEN_HOST = 0.0.0.0
SSH_DOMAIN = ssh.git.kanthaus.online</pre>
Then, set up a port forwarding in OpenWISP. You need to be connected to the <code>kanthaus-admin</code> network for this and go to [https://192.168.178.1/firewall_nat.php the NAT Port Forward page]. Create a new rule: * Interface: WAN * TCP/IP version: IPv4+IPv6 * Protocol: TCP * Destination: WAN address * Destination port range: (other) 2222 to (other) 2222 * Redirect target port: 2222 * Description: git SSH access for Forgejo

The <code>ssh.git.kanthaus.online</code> should point to the Fritzbox (not kanthaus-server) so that it can take care of forwarding the port. If the domain points to kanthaus-server, connecting over IPv6 will likely fail.

=== Setting up the continuous integration ===

In the configuration file (<code>/data/services/forgejo/config/app.ini</code>), set those settings (if not set already):

<pre>[actions]
ENABLED = true</pre>
Then, go to the [https://git.kanthaus.online/user/settings/actions/runners Runners Management] page and click “Create new Runner”. Copy the registration token and put it in <code>/opt/kh-services/.env</code> as <code>FORGEJO_RUNNER_REGISTRATION_TOKEN</code>.

Delete <code>/data/services/forgejo_runner/.runner</code> if it is present.

Restart the runner with <code>docker-compose up -d</code> in <code>/opt/kh-services</code>.

The runner will register and should become visible [https://git.kanthaus.online/user/settings/actions/runners in Forgejo’s settings].

For each repository where you want to use the runner, you need to enable actions in the repository’s settings.

=== Backing up Forgejo’s data ===

You need to back up two things: * the contents of <code>/data/services/forgejo</code> * the Postgresql database. To do so: * First, find out the container id of the postgres instance with <code>docker ps | grep kh-services_postgres</code> and copy the first hash in the output to the second command, in place of <code><container-id></code> * Run <code>docker exec -it <container-id> pg_dump -U postgres --clean forgejo | gzip > forgejo_database_dump.sql.gz</code>

To restore the backup, you need to: * restore the contents of <code>/data/services/forgejo</code> * restore the database similarly with: <code>cat forgejo_database_dump.sql.gz | gunzip | docker exec -i <container-id> psql -U postgres forgejo</code>

Git

2025-01-18T13:07:36Z

Antonin: /* Instructions for administrators */ fix markup botched by the migration from the handbook :(

📋️ We use Git to store mutable data. Our Git repositories are hosted with [https://forgejo.org Forgejo] on [[Server|our own server]]. For immutable files we have a [[Nextcloud]] in the same location.

== What is Forgejo? ==
Forgejo is basically a social network built on top of the [https://git-scm.com/book/en/v2/Getting-Started-Git-Basics git technology] for version control. It is normally used for code, because it makes it easy to collaborate on common projects without breaking anything.

== Why did you decide to use this? ==
* We want to help people learn things and appreciate technology!
* Data that was put in git is extremely secure, because it’s stored on multiple people’s computers.
* If multiple people work on the same file it’s possible to tell who changed which exact character.
* It’s easy to put content from Forgejo onto our website.
* Everybody becomes a webmaster. 🙂
* The people who decided on this were already used to it… 😉

== What is stored where? ==
So far we have the following repositories: - [https://git.kanthaus.online/kanthaus/kanthaus.online kanthaus.online], where we store our website, https://kanthaus.online/. - [https://git.kanthaus.online/kanthaus/kanthaus-private kanthaus-private], where we store our [[residence record]], internal meeting minutes, financial plans and other stuff that contains personal information. Everything of relevance that consists of text and has pieces of confidential data should be put here. - [https://git.kanthaus.online/kanthaus/kanthaus-public kanthaus-public], which is publicly accessible as the name suggests. In this repository we do our task management via issues (which you can find [https://git.kanthaus.online/kanthaus/kanthaus-public/issues here]). This is especially important for our [[../social/roadmap.md|roadmap plannings]]. Other than that we have drafts, policies, signs, data on our water, electricity and gas usage and much more in here. - [https://git.kanthaus.online/kanthaus/kanthaus-ansible kanthaus-ansible] is for keeping our server tidy. Nothing you need to worry about, except you’re actually interested. In that case feel free to ask Matthias about it! - [https://git.kanthaus.online/kanthaus/handbook handbook] is where this handbook is stored. - [https://gitlab.com/kanthaus/expfloorer expfloorer] hosts a floorplan of Kanthaus.

== How to use it ==
Go to https://git.kanthaus.online and log in with your Nextcloud account. You will be automatically added to the “Kanthaus” organization in which our repositories are stored: https://git.kanthaus.online/kanthaus

You can modify the files there directly via your web browser.

== Cloning repositories on your machine ==
If you are working with local clones, you need to update those to point to Kanthaus Git instead of GitLab (which we were using before Forgejo).

On the page of each repository, such as https://git.kanthaus.online/kanthaus/handbook, copy the clone URL you prefer. For instance, for the handbook, they look like this: * HTTPS: <code>https://git.kanthaus.online/kanthaus/handbook.git</code> * SSH: <code>ssh://git@ssh.git.kanthaus.online:2222/kanthaus/handbook.git</code>

In your local clone, run:

<pre>git remote set-url origin <new-url></pre>
Note that if you want to use SSH URLs, you first need to [https://git.kanthaus.online/user/settings/keys add an SSH key].

== Instructions for administrators ==

We are running Forgejo via Docker inside our Docker-Compose deployment of services on the <code>kanthaus-server</code>.

=== Setting it up from scratch ===

After launching the service via Docker, the following manual steps need to be taken to configure the instance:
* Go to https://git.kanthaus.online/ where the set-up screen should display. Change the following settings:
* Site title: “Kanthaus Git”
* SMTP host: gehrels.uberspace.de
* SMTP port: 587
Send email as: git@kanthaus.online
* SMTP user: git@kanthaus.online
* SMTP password: found in the Kanthaus keepass
* Tick “Enable email notifications”
* Tick “Disable Gravatar”
* Tick “Allow registration only via external services”
* Tick “Hide email addresses by default”
* Domain for hidden email addresses: <code>git.kanthaus.online</code>
* Set up an admin user with credentials you own: we will delete it later on
* After validating the sign-up form, go to https://git.kanthaus.online/org/create and create a “kanthaus” organization. You can prettify it a little, by adding a bit of metadata at https://git.kanthaus.online/org/kanthaus/settings and uploading a logo from https://kanthaus.online/pics/newLogo.png
* In Forgejo’s configuration file (<code>/data/services/forgejo/config/app.ini</code>), add the following lines at the end:

<pre>[oauth2_client]
USERNAME = userid
ENABLE_AUTO_REGISTRATION = true</pre>
You can also take this opportunity to add <code>LANDING_PAGE = /kanthaus</code> in the <code>[server]</code> section. And disable OpenID login:

<pre>[openid]
ENABLE_OPENID_SIGNIN = false
ENABLE_OPENID_SIGNUP = false</pre>
* Make sure our Nextcloud instance has the [https://apps.nextcloud.com/apps/oidc OIDC Identity Provider] app installed
* Go to [https://cloud.kanthaus.online/settings/admin/security Nextcloud’s security settings] (while logged in with an administrator account in NextCloud) and generate a new OpenID Connect client (if it does not exist yet), with the following details
** Name: Forgejo
** Redirection URI: https://git.kanthaus.online/user/oauth2/NextCloud/callback
* Go to [https://git.kanthaus.online/admin/auths Forgejo’s Authentication Sources] and click “Add an authentication source”, with the following settings:
** Authentication type: OAuth2
** Authentication name: “NextCloud”
** OAuth2 provider: OpenID Connect
** Client ID: the client ID produced at the previous step
** Client secret: the client secret produced at the previous step
** OpenID Connect Auto Discovery URL: https://cloud.kanthaus.online/.well-known/openid-configuration
** Additional scopes: <code>email</code>
** Claim name providing group names for this source: <code>roles</code>
** Group claim value for administrator users: <code>admin</code>
** Map claimed groups to Organization teams: <code>{"Kanthaus": {"kanthaus": ["Owners"]}}</code>
* Restart forgejo with <code>docker-compose restart forgejo</code> (in <code>/opt/kh-services</code>)

Note: this configuration relies on our NextCloud instance having the [https://docs.nextcloud.com/server/27/admin_manual/configuration_server/config_sample_php_parameters.html “clean URLs” option] enabled. Otherwise, the URLs need to be adapted to add <code>index.php</code> in them, such as <code>https://cloud.kanthaus.online/index.php/.well-known/openid-configuration</code>.

=== Setting up SSH access ===

To let users clone via SSH, we need to take some additional steps. In the configuration file (<code>/data/services/forgejo/config/app.ini</code>), set those settings (if not set already):

<pre>[server]
START_SSH_SERVER = true
SSH_PORT = 2222
SSH_LISTEN_PORT = 2222
SSH_LISTEN_HOST = 0.0.0.0
SSH_DOMAIN = ssh.git.kanthaus.online</pre>
Then, set up a port forwarding in OpenWISP. You need to be connected to the <code>kanthaus-admin</code> network for this and go to [https://192.168.178.1/firewall_nat.php the NAT Port Forward page]. Create a new rule: * Interface: WAN * TCP/IP version: IPv4+IPv6 * Protocol: TCP * Destination: WAN address * Destination port range: (other) 2222 to (other) 2222 * Redirect target port: 2222 * Description: git SSH access for Forgejo

The <code>ssh.git.kanthaus.online</code> should point to the Fritzbox (not kanthaus-server) so that it can take care of forwarding the port. If the domain points to kanthaus-server, connecting over IPv6 will likely fail.

=== Setting up the continuous integration ===

In the configuration file (<code>/data/services/forgejo/config/app.ini</code>), set those settings (if not set already):

<pre>[actions]
ENABLED = true</pre>
Then, go to the [https://git.kanthaus.online/user/settings/actions/runners Runners Management] page and click “Create new Runner”. Copy the registration token and put it in <code>/opt/kh-services/.env</code> as <code>FORGEJO_RUNNER_REGISTRATION_TOKEN</code>.

Delete <code>/data/services/forgejo_runner/.runner</code> if it is present.

Restart the runner with <code>docker-compose up -d</code> in <code>/opt/kh-services</code>.

The runner will register and should become visible [https://git.kanthaus.online/user/settings/actions/runners in Forgejo’s settings].

For each repository where you want to use the runner, you need to enable actions in the repository’s settings.

=== Backing up Forgejo’s data ===

You need to back up two things: * the contents of <code>/data/services/forgejo</code> * the Postgresql database. To do so: * First, find out the container id of the postgres instance with <code>docker ps | grep kh-services_postgres</code> and copy the first hash in the output to the second command, in place of <code><container-id></code> * Run <code>docker exec -it <container-id> pg_dump -U postgres --clean forgejo | gzip > forgejo_database_dump.sql.gz</code>

To restore the backup, you need to: * restore the contents of <code>/data/services/forgejo</code> * restore the database similarly with: <code>cat forgejo_database_dump.sql.gz | gunzip | docker exec -i <container-id> psql -U postgres forgejo</code>

CoMe

2025-01-13T10:09:31Z

Antonin: migrate facilitation instructions here

✔️ The '''Co'''ordination '''Me'''eting is the only weekly meeting everyone is [https://kanthaus.online/en/governance/collectiveagreements recommended] to join. This makes it the main ‘real-life’ event we have for sharing information and ideas. We try and keep it short, and as relevant for the participants as possible. In consequence, it can be quite rapid: it’s not a good place for resolving emotional conflicts or making complex decisions.

== Time and place ==
The default is '''Monday 10 am''' in the [[dining room]]. The meeting lasts until 11 am maximum.

== Scope and importance ==
This is the most important meeting at Kanthaus. It takes place every week, we take notes which we [https://kanthaus.online/governance/minutes publish on our website] and we expect people to take part if they want to know what’s going on.

== Facilitation ==
A facilitator guides through the meeting, reads out the relevant informational sections and guides through the discussion points. Topics are collected before-hand in the [https://codi.kanthaus.online/come CoMe pad]. This document is then used as base for the meeting by the facilitator.

=== Requirements ===

* a Kanthaus [https://cloud.kanthaus.online nextcloud] account with membership of the <code>Kanthaus</code> group
* a [https://mattermost.kanthaus.online/ Kanthaus Mattermost] account with access to the private <code>kanthaus-residence</code> channel
* to know where the cash box is and how to open it


=== Preparation ===


==== Check dates ====

Ensure that both meta-data date and markup date are current.


==== Residence record ====

Check that the [https://git.kanthaus.online/kanthaus/kanthaus-private/src/branch/master/residenceRecord.csv residence record] is up to date.


==== Run the script ====

After you have updated the records, go to the [https://git.kanthaus.online/kanthaus/kanthaus-governance/actions?workflow=weekly_report.yaml&actor=0&status=0 Forgejo action], click on any run in the list and press “Re-run all jobs”. - After some minutes, the bot will post data to the <code>kanthaus-residence</code> channel. - Copy the contents in the gray ‘stats’ box to the <code>Previous week stats</code> CoMe section


==== Trash ====

Check the dates for trash pickups in the [https://cloud.kanthaus.online/apps/calendar/dayGridMonth/now Kanthaus calendar] and write them down in the <code>Schedule</code> section. Make sure to include any trash pickup on the next monday, as next CoMe will be to late to plan for it.


==== Money ====

Check the donation ‘shoe’ in the k20 hallway and deposit it in the cash box. List this sum plus any other donation in the last week in the <code>Income</code> CoMe section. If you’re feeling energetic, you can also check the donation box in the Verschenkeladen.


==== Evaluations ====

Included in the post you sent to <code>kanthaus-residence</code> earlier are any evaluation notices. Copy <code>Due for evaluation</code> and <code>Due for evaluation soon</code> entries to the <code>Evaluations and check-ins</code> CoMe section


=== During ===

There are no fixed rules, so feel free to add your own touch and do (small) experiments. Some general advice that seems to have worked so far: - Notify people 10 minutes before the meeting starts. - Start as close to 10:00 as possible. - Go through the ordered points in order, even if nothing has changed. - At the end of each section, ask people if they have anything add (and give them some moments to think!) - Do moderate discussion if off-topic or too detailed. You can always suggest a small group forms for special topics. - Try to finish the meeting before 11:00. If you think it really makes sense to extend it, announce that. - Try to leave the room as soon as CoMe has has ended. (This sends a signal to everyone else that they can also leave if they want to.)


=== Afterwards ===

‘Sanitize’ the CoMe pad by removing any data which shouldn’t be published. This includes anything marked <code>to be removed</code> or <code>tbr</code>, as well as any personal information about people who haven’t agreed to it.

Copy CoMe pad contents to the website. A graphical way of doing this can be done by: - Go to the [https://git.kanthaus.online/kanthaus/kanthaus.online/src/branch/master/user/pages/40.governance/90.minutes minutes] folder - Click <code>Add File</code> -> <code>New File</code> - As filename use <code>YYYY-MM-DD_CoMe/item.md</code> (e.g. <code>2023-05-15_CoMe/item.md</code>) - Copy the following metadata header (including the <code>---</code>) into this new document, and fix the date:

<pre>---
title: Coordination Meeting
date: "2023-MM-DD"
taxonomy:
tag: [come]
---</pre>
* Copy the CoMe pad content from the Edit mode/Bearbeiten Modus (black window) after the metadata header.
* Change the commit message to something like <code>add CoMe minutes for YYYY-MM-DD</code>
* Click <code>Commit changes</code>
* That´s it! After a few minutes the CoMe-minutes should appear on the website.

Prepare the CoMe pad for next week - clear all information that is no longer relevant (i.e. most of it except regular schedule events) - put forward the meta-data date and markup date to next CoMe

Then, finally, notify #kanthaus that the minutes are online and pad is cleared. ''Well done!''

== Adaptability ==
The CoMe pad is not subject to the [[Documents|core documents]] which means that facilitators can change it as they see fit and add or omit sections to their liking.

=== '''Sections which have been used reliably for a long time are (in chronological order):''' ===

==== '''Introduction & review of the week before''' ====
* a greeting
* a moment of silence
** to focus the attention
* a brief [https://medium.com/range/check-in-rounds-a7737012fed5 check-in round]
** to have heard everyone’s voice and be able to understand their current mode
* finding volunteers for the imminent meeting tasks
** meaning someone to take notes, someone to update the physical board, and someone for the digital calendar
** the volunteer to clear all [[Room reservation|weekly reservation sheets]] after the meeting is also found now
* an overview of resources used in the last week (e.g. water and electricity)
** to give people a feeling of how much we as a group consume
** the format has been changed many times and is still not satisfying
* irregular communal income and expenses
** for transparency
* a summary of things that happened in and around Kanthaus
** to celebrate achievements

==== Planning of the current week ====
* an overview of planned arrivals and departures this week
** to nurture and/or protect the community feeling
* the weather forcast
** to take into account for the schedule
* who is due to be [[Positions and evaluations|evaluated]] or have a visitor check-in
** to be able to schedule them
* '''the schedule for the week'''
** 1st main part of the meeting
** creates the communal week plan
* if someone wants to get/buy something
** to find out if buying is necessary and/or get approval from the group
* '''discussion and announcements'''
** 2nd main part of the meeting
** the space for people to raise points concerning the current week and/or near future
* [https://kanthaus.gitlab.io/task-lottery/ task lottery] and food planning
** to distribute communal dinner preparation and hosting of the free shop opening

==== Sections which are new, have been there in the past or are used only sometimes are: ====

* an selection of subjectively interesting world news
* a tiny version of [https://theanarchistlibrary.org/library/tekosina-anarsist-tekmil-a-tool-for-collective-reflection Tekmíl] or a space for potentially critical feedback to others present
* a to-do list for fixes and improvements around the house
* handing out responsibilities (like answering the phone or mails) for the whole week
* a list of who is actively hosting whom
* probably more that got forgotten over time…

Mattermost

2024-11-27T22:11:50Z

Antonin: start list of known issues

👪️ We use Mattermost to organize ourselves, at https://chat.kanthaus.online/

== Creating a personal account ==
You can get an account by following [https://chat.kanthaus.online/signup_user_complete/?id=7y1m51bwj3rmmmis573zyknofw&md=link&sbr=sa this link].

== Channels ==
Our main channel is <code>#kanthaus</code>. Many channels we use have been historically prefixed by <code>#kanthaus-</code> because they were in a Slack instance shared with other people.

Some of those channels are private, because they contain private or sensitive information. Those are reserved to Volunteers and Members.

== Known issues ==

This lists the issues we have encountered when using Mattermost:
* No email integration. We have built the [https://codeberg.org/mailmirror/mailmirror MailMirror plugin] for that, which could still be [https://codeberg.org/mailmirror/mailmirror/issues improved in many ways]
* No support for reminders of events (for instance stored in an ICS file)
* Not possible to fully rename the "Town Square" channel (the id will stay `~town-square`)

Glossary

2024-11-24T08:36:56Z

Antonin: /* Script (CoMe context) */ update for Mattermost

Kanthaus has many terms that might be confusing. This page is meant to help restore clarity. 📄

To make adding terms easier there is no order whatsoever. The best way to find what you’re looking for is probably <code>CTRL+f</code> (which lets you search for terms on the whole page through your browser).

== CoMe ==
The weekly [[CoMe|Coordination Meeting]]

== PlaMe ==
The monthly [[PlaMe|Planning Meeting]]

== Power Hour ==
The weekly common cleaning. More info on [[Powerhour|its own page]].

== Popcorn ==
In a round people speak (or pass on) one after the other, whereas a popcorn scenario means that people just speak up if they think of something. More info on [[meeting culture]]

== KMW ==
The van we owned until 2022. Abbreviation for its name ‘KeinMüllWagen’ (no trash wagon)

== HKW ==
The association that owns the house. Abbreviation for ‘Haus Kante Wurzen w.V.’

== WaWü ==
The charitable association that runs projects in the house and beyond. Abbreviation for ‘Wandel würzen e.V.’

== foodsharing ==
Big organization, community, [https://foodsharing.network online platform] and method to save and share food. Starting point of the history that led to Kanthaus.

== yunity ==
Project emerging from foodsharing to make a new online platform to save and share everything. Context in which the people who would later found Kanthaus met. More info on [[history]]

== Karrot ==
[https://karrot.world Online platform] for grassroots organizing of real-life activity. Over years co-developed by people in the house.

== Sociocracy ==
A governance system that uses small groups of people to make decisions based on consent and feedback loops. More info at [https://www.sociocracyforall.org/sociocracy/ Sociocracy for all]. Kanthaus is ''not'' organized sociocratically, but this, like other systems, was useful inspiration at many points.

== Score voting ==
A voting system where every options is rated individually on a scale and the option with the highest voting wins.

== Harzgerode/Freie Feldlage/FFL ==
Befriended project in the Harz mountains. More info on [https://freiefeldlage.de their website].

== K20/Salzderhelden ==
[https://k20-projekthaus.de/en/ K20] is one of the projects closest to Kanthaus conceptually. [https://utopisches-salzderhelden.de/en/ Salzderhelden] is the village around, which houses a multitude of other, related project spaces.

== Exchange logic ==
The logic of reciprocity, which expects something in return for everything. A valued utopian thought in Kanthaus (and elsewhere) is that overcoming exchange logic is necessary for authentic human connection. Friederike Habermann is a German scholar who is passionate about the topic. [https://wealthofthecommons.org/essay/we-are-not-born-egoists Here’s a nice little essay of hers].

== K20, K22 ==
Abbreviations for Kantstraße 20 and Kantstraße 22, the two houses that make up Kanthaus.

== Funkenhaus/Greene ==
[https://funken.haus/ Funkenhaus] is a self-organized seminar space. Greene is the surrounding village.

== Luftschlosserei ==
[https://luftschlosserei.org Luftschlosserei] is a nice commune south-west of Leipzig.

== Danni ==
Short for ‘Dannenröder Wald’, which housed a [https://waldstattasphalt.blackblogs.org/ big forest occupation] in (mainly) 2020.

== Spinnerei/Lausitz ==
[https://www.eine-spinnerei.de/ Eine Spinnerei] is a project in the Lausitz region that focuses on lignate extraction protest, consequently sustainable renovation and free ways of education.

== Evaluation ==
Meeting about a single person and their relationship to Kanthaus as a whole. More info on [[positions and evaluations]].

== Visitor/Volunteer/Member ==
The three positions a resident in Kanthaus can have. Residents can request a higher position at an evaluation. More info on [[positions and evaluations]].

== VolMems ==
Short for ‘Volunteers and Members’.

== ToI ==
Short for ‘Time of Introspection’, a time in which Kanthaus Volunteers and Members reflect on issues of the house. Usually once a year. There is no uniform format for this.

== MoC ==
Short for ‘Month of Calm’, a time in which no new Visitors are allowed to arrive so that residents don’t need to worry about presenting Kanthaus and integrating new people. Happens irregularly.

== Alumni ==
Term for people who have been Volunteers or Members in the past. No official position yet, but it still is a thing.

== FFJ ==
Time of self-organized learning in a group. Happens in Kanthaus in 2024. More info on [https://freiwilliges-freies-jahr.de/ffj-wurzen-2024/ the project’s website].

== BUND ==
[https://www.bund.net Bund für Umwelt und Naturschutz] is a huge German environmentalist NGO. We run the local branch in Wurzen.

== Bufdi/BFD ==
Government-funded volunteer jobs.

== Pad ==
Online text editor for collaborative use. At [https://pad.kanthaus.online pad.kanthaus.online] we run an instance of [https://hedgedoc.org/ HedgeDoc]. More info on pad usage in Kanthaus e.g. in [[CoMe]].

== Script (CoMe context) ==
The residence script that runs in preparation of Come calculates who is due for an evaluation and how many resources were used in the last week, and posts the outcomes in a dedicated [[Mattermost]] channel.

== Residence record ==
Manually updated data base for the CoMe script.

== Communalizing ==
The act of declaring an item communal property.

== Privatizing ==
The act of declaring an item private property.

== Vortexing ==
The act of placing an item in the vortex. More info on the vortex in [[Processes to manage stuff|stuff processes]].

== Open Tuesday ==
Opening time of the ground floor of K22 which contains the free shop, the foodsharing Fairteiler and (sometimes) the repair café / maker space. Default time is 3pm to 5pm.

== Free shop/Verschenkeladen ==
Room full of things to give away. Located in K22-0-3.

== Fairteiler ==
Foodsharing term for a publicly accessible shelf or fridge in which food can be shared between strangers. There is one in Wenceslaigasse in Wurzen.

== Workaway ==
[https://workaway.info Website] for people to find volunteer work all over the world. Kanthaus has a host profile on there.

== Projektverteiler ==
A mailing list for house projects and other alternative living concepts in and around Leipzig.

== HWR ==
[https://www.hwr-leipzig.org/ HWR] is short for ‘Haus- und Wagenrat e.V.’. An association that offers guidance to house projects and trailer sites. They helped us aquire the houses in Kantstraße.

== NDK/D5 ==
[https://www.ndk-wurzen.de/ NDK] is short for ‘Netzwerk für demokratische Kultur’, an association that has been doing work to counter the right-wing status quo in Wurzen for two decades now. [https://www.ndk-wurzen.de/unser-haus/kultur-und-buerger_innenzentrum-d5/ D5] are their headquarters at Domplatz 5.

== LADEN/Schweizerhaus Püchau ==
[https://schweizerhaus-puechau.jimdo.com/der-laden-wurzen/ The LADEN] is an open art space run by the association [https://schweizerhaus-puechau.jimdo.com/ Schweizerhaus Püchau] that has been doing art empowerment workshops in the region since 2010.

== Villa Klug ==
Something between house project and flat share with tons of space and nice people. Slightly south of Wurzen, right on the bank of the Mulde river.

== RE/S-Bahn ==
The two kinds of trains that go to Leipzig. RE is the fast one (~20 minutes) and S-Bahn the slow one (~40 minutes). More info on [[travel]].

== Phoenix ==
The red ebike. Usually lives in the communal bike shed.

== Lightning ==
The silver ebike. Usually lives in the communal bike shed.

== Daria ==
Bike trailer custom made for the base length of two green boxes. Usually stored on the wall of the communal bike shed.

== Nathanaël ==
Bike trailer custom made for the base length of four green boxes. Can also be used as a ladder. Usually stored standing outside of the communal bike shed under the roof.

== Carla (Cargo) ==
Heavy duty bike trailer. Inspired by [https://www.carlacargo.de/ Carla Cargo], built following the instructions provided by [https://pedalkreis.org/bauplaene/carlacargo/ Pedalkreis].

== Kids trailer ==
A boringly named bike trailer to transport two small children.

== Lollipop hitch ==
The kind of hitch to attach a trailer to a bike that is commonly used in Kanthaus. Like [https://www.cykelportalen.dk/wp-content/uploads/2017/08/CarryFreedomCity02.jpg this one].

== MCM ==
Short for ‘Mega/meta/master Coordination Meeting’. Format for longterm organizing that is not used anymore.

== Roadmap meetings ==
First longer term organizing format we came up with. Not used anymore.

== Sommerfest ==
Annual garden party in the warm season. With house tours, open free shop and Fairteiler, KüfA, drinks, music and more.

== KüfA ==
Short for ‘Küche für Alle’ or ‘kitchen for all’, an event where food is handed out for free or donation-based.

== KoLa ==
Short for "Kollaboratives Landwirtschaft" ("Collaborative agriculture"), [https://kolalleipzig.de huge Solawi] in Sehlis, from which we sometimes save food.

== FLINTA* ==
Stands for the German words "Frauen, Lesben, Inter*-Menschen, Nichtbinäre, trans*-Menschen und Agender-Menschen", which would be translated to women, lesbians, inter*-, nonbinary-, trans*- and agender people. In short, everyone who is not an endo-cis-man. The star tries to include anyone else who experiences discrimination by the patriarchy.

== nuudel ==
[https://nuudel.digitalcourage.de/ nuudel] is a non-tracking date finding tool operated by [https://digitalcourage.de/ digitalcourage]. It runs the open-source software [https://framagit.org/framasoft/framadate/framadate Framadate].
-----

'''to be added''' - doocracy https://www.noisebridge.net/wiki/Do-ocracy - dragon dreaming - scrum - jitsi - bigbluebutton - nextcloud - inventaire - open refine - blindspots - Jugendkommune - ROAW - collective governance directory - MSV - Kita - Bubis/Bubi/Mubi - communal - sharing circle - Fokusgruppe (Nachhaltigkeit)/FGNW - Wenceslaigassenfest - potato action - Auerworld - Acroyoga - GFK/NVC - Kommuja - GEN - Eurotopia - Awareness - Privilege - FTT - Kimchi - Tempeh - Landgut Nemt - Spidey - (ebay) Kleinanzeigen - (occupancy) indicator - Window holder - Sound bowl - Guest book - Expfloorer - House bus - Ventilation system - Heatpump - AC/air conditioning - Bike repair station -
[[Category:Social]]

Compost toilet

2024-11-24T08:36:25Z

Antonin: update after Mattermost migration

You can find the compost toilet in the K22 staircase, the room with the actual toilet is in between the ground floor and the first floor, the “tank room” where the material is composted is right below it on the ground floor, next to the garden door.

== General principle 🍂 ==

* Urine is separated and directed into the normal sewage system, the urine tube forms a siphon to prevent smell from the sewers
* The poop falls into a 800l plastic tank (which used to be an oil tank)
* The tank has a grid of metal bars on the bottom that allows for airflow and “harvesting” of the composted materials from below
* The tank also has a sewage connection on the very bottom in case there is ever an overflow or the material becomes too wet
* A 120mm 3W PC fan creates a slight vacuum throughout the tank and toilet and blows unwanted smells outside just below the roof

Details about the principle and instructions on how to build your own indoor compost toilet can be found in the brochure “Einfälle statt Abfälle” by Christian Kuhtz, which you can find in some KH bookshelf 😁

== Usage hints ==

* Because of the urine separation the material can get too dry. It might make sense to pee into the tank from time to time. Best have 1 or 2 people who use it regularly always pee beside the urine separation funnel (currently, 2022-07, Janina does this)
* Emptying the tank is necessary 1-4 times a year, depending on how much it is used
* If the material stacks up all the way to the ventilation outlet, its probably time to empty soon. You can buy some time by using the metal rod from the tank room, to push the hill of accumulated material down to the sides

== Emptying procedure ==

=== Prerequisites: ===

* approx. 1-2 hours of time
* tools (should be stored in the front area of the tank room):
** long metal rod, bend at the end
** some penny-bags (1-4)
** a shoveling device (one with short or no handle seems to work well)
* something to lay on, e.g. a camping mat (something that’s easy to clean or where it doesn’t matter if it gets dirty)
* a headlamp (can usually be found in the workshop, right when you enter to your left)
* maybe gloves (can also be found in the workshop)
* no arachnophobia :D yes, there will be spiders and other crawling insects
[[File:Comfortable compost toilet emptying position .jpg|thumb|Recommended emptying postition]]

=== Emptying ===
<ol style="list-style-type: decimal;">
<li>
Start with finding a comfortable position lying on your back.
</li>
<li>
Use the metal rod with bent tip to poke around between the bars of the grid, eventually you will have enough space to shift the material around in the tank and let it trickle down through the bars of the grid.
</li>
<li>If it does not work or it is too difficult, you can try to push a few of the bars to the sides (they are just loosely connected the the main carrying bars with some wire) to have more space to poke around with your rod.</li>
<li>If the material in the tank is to wet/heavy/dense it can help to poke into the tank from above (i.e. into the toilet) with the tip-bent rod.</li>
<li>After enough material has accumulated in the area below the rod-grid, use the shovel to move it to a penny bag other other container[[File:Compost toilet shit shovel .jpg|thumb|Shovel the <s>shit</s> compost]]</li>
<li>
Continue with step 1.
</li>
<li>Depending on how full the tank is and when it was last emptied, you can remove 2-6 penny bags. If the material changes from “feels like compost” to “feels like poop” you should stop :)</li>
<li>You can just empty the bags into the normal compost at the far corner of the garden, maybe try to mix it into the normal compost a bit with a shovel.</li>
<li>Don’t forget to clean up and wash your hands!</li></ol>

== General maintenance / bug fixing ==

* clogged fan: happens either when a piece of toilet paper or similar gets stuck in front of the fan from the inside, or the fan itself or the pipe behind it are filled with sawdust/flied
** remedy: go into the garden to what used to be the outside window of the “tank room” (you might have to move some trash bins), remove the piped leading out from the fan (the are all only loosely stuck together) and shake out the dust / use compressed air.
* broken fan / power adapter: I would expect the fan to only last a few years under this stress, if is breaks you should find a new one in the electronics workshop / salvage old PCs or power supplied. Power adapters you can also find in the electronics workshop, anything from 5-16V should work (but give you a more or less powerful fan)
* if you for some reason need to access the tank from above, or something with be toilet itself is broken (urine tube or “poop slide” made of cut-open buckets) the wooden chassis is not screwed or glued, only held in place by some wooden dowels. You can just lift the top off the sides, the urine tube and cut-open buckets will be in the way though as they are quite tightly connected, so you will need to lift the top wooden piece together with the toilet seat, urine-tube and buckets.

== Possible future improvements ==

* add a butt-shower (there still should be some in the workshop, ask Silvan)
* integrate the sawdust bin into the main wooden construction of the compost toilet, mainly to have more space in comfort when sitting on the toilet, and for optical reasons. Its a bit tricky but should be possible, maybe with a bin a bit smaller then the one used now. The bin should stay removable and you can use the cut-out wood as a lid. Ping Bodhi on Mattermost if you are interested!
[[Category:Rooms]]
[[Category:Toilets]]

Processes to manage stuff

2024-11-24T08:36:01Z

Antonin: /* Communal stuff de-cluttering */ update for Mattermost

📦️ "Stuff" is the term widely used in Kanthaus to refer to physical items that take up space in the house and are not food. Stuff can be useful or not, communal or private, a blessing or a curse. Managing stuff is a vital administrative task of the house, so we came up with several systems.

== [[The Vortex]] ==

== De-cluttering actions ==

Formerly known as ‘sales’ (based on the idea of doing an ‘internal yard sale’), which admittedly is an extremely confusing term, de-cluttering actions are events to clear out storage areas.

=== Communal stuff de-cluttering ===

On example for communal stuff de-cluttering is the K20 entrance with its communal shoe and jacket shelf. Let’s say we want to de-clutter the jacket shelf, the process is as follows:

# Empty the shelf and put all its contents to an accessible location. People need to be able to look through everything there. It should also not be in the way. Past locations were the [[Dragon room|Dragon Room]] or [[Elephantroom|Elephant Room]] tables.
# Specify a time frame for the event and communicate it on site (the shelf itself, the sorting area and on [[Mattermost]]). Past actions usually took 1-2 weeks maximum.
# During the event people are expected to take out the things they want to keep and hang them back onto the shelf.
# When the time is up everything that’s left will go through the vortex.

=== Private stuff de-cluttering ===

Basically the same as the communal stuff de-cluttering, private stuff de-cluttering are events to make sure we don’t have unnecessary items in public spaces for private items. This is only necessary in the entrance of K20 where we have space for private shoes and jackets ''without name tags''.

== Spitz Storage Room concepts ==

Since the [[Spitz storage room|Spitz Storage Room]] is the newest storage area, we this time, took good care to come up with a nice system ''before'' it is filled with stuff. The details are in the room page, but the general idea is as outlined below

=== Communal stuff in Spitz Storage Room ===

* clear categories of stuff
* clear labels
* only sorted boxes are allowed in the area

=== Private stuff in Spitz Storage Room ===

* everybody can have up to a stack of 3 banana boxes
* everything needs to be labeled with a name
* people who are neither [[Positions and evaluations|Volunteer or Member]] need to indicate when they last accessed the box (LDA = last date accessed) and remove it if this date is more than a year in the past

== Privatization of communal stuff ==
[[File:MaximeStuffRequest.jpg|thumb|''Example of someone asking to privatize communal items'']]
There is no perfectly choreographed process for privatization of communal stuff. However, there are best practices, which usually involve the following: - clearly identify the items you’d like to take, possibly with pictures - communicate your request online so that everybody has the chance to see it in time - formulate a deadline until which people are expected to react - be honestly open to other people’s potential claims on items and engage in productive discussion if necessary

The Vortex

2024-11-24T08:35:26Z

Antonin: update after Mattermost migration

Located in the [[Intermediate|Intermediate Storage Room]] in K20-1-5, the vortex is a physical space to regularly look through potentially unwanted communal items.

=== What is it for? ===

There are three major use cases for the vortex:

# '''Removing''' stuff from the household.
# '''Clearing''' a corner of the household.
# '''Adding''' stuff to the household.

The 1. Is probably the most relevant case: Someone thinks a certain item should not be part of the Kanthaus household anymore and wants to start the process of getting rid of it. The vortex gives others time to take it back and/or privatize it.

When someone tidies up a cluttered space they usually find stuff that is clearly (or maybe) not trash but still does not belong there. Needing to find a good new or the proper previous location os hard and blocks tidying up efforts, so putting these things in the vortex is an appropriate way to go.

Sometimes people find stuff that might be useful to the house or individuals, but they’re not really sure. Putting it in the vortex means leaving the decision to communalize or privatize the items to others and just giving them prioritized access before it ends up in the [[Freeshop|Free Shop]] or the trash.

=== How does it work? ===

There are three phases which the stuff - if not taken out - travels through. ‘Vortex shifting’ is a [[Power hour|Power Hour]] task, which means that it ideally happens every week, sometimes more seldom, never more often.

==== Phase 1 (0+ days) - New things ====

===== Put into this phase =====

* broken things which you don’t want to fix
* things you think we have too much of
* ‘lost’ personal property
* anything else you think should move (out) of the communal space in the house

Label things with the reason why you put them in. If you’d like people to talk to you about them, also write down your name. Pens and paper are on the shelf opposite the vortex, near the door.

===== Take out of this phase =====

* your personal things
* known communal things, to return them to communal space

==== Phase 2 (7+ days) ====

===== Put in =====
* Items from phase 1

===== Take out =====

* Your own personal items.
* Items you know to be communal.

==== Phase 3 (7+ days) - Last Chance ====

===== Put in =====
* Items from phase 2

===== Take out =====

* Anything you want to privatize
* Known communal things, to return them to their storage

==== Doom ====
Items from phase 3 are doomed at the next shift.

* Items that make sense to communalize are sorted into fitting communal locations. Remember that those items had 2 weeks to be sorted in already. Only return them if you're sure.
* good but unneeded items go in the [[Freeshop storage|Free Shop Storage]]
* trash is put into bins accordingly.

==== Details of the shifting ====
Shifting is one of the [[Power hour|Power Hour]] tasks.

To make it possible for Kanthausians who are not currently in the space to also voice an opinion on the stuff in the vortex, it’s required to document vortex shifts on [[Mattermost]].

Experience leads to the following best-practice of vortex shifting:

* Start on the back and empty phase 3.
* Make (a) box(es) with things for the Free Shop
* Check things you believe might be there in error with people who might know.
* If you feel like it, offer items to people outside Kanthaus - on Kleinanzeigen or to your friends.
* Don’t be shy to use the trash bins!
* Move phase 2 into phase 3.
* Take pictures and make sure that the things are identifiable.
* Feel free to also use the space below the table.
* If more space is needed than before, you can move the tape that marks the border between phase 2 and phase 3.
* Check phase 1. If there are items without a label explaining why they were vortexed, move them into their normal storage places. They are probably just lost.
* Move phase 1 into phase 2.
* Take pictures if you’re motivated, but the ‘phase 2 to phase 3’ pics are more important.
* Add stuff that came in during Power Hour to phase 1.
* Upload the pictures to #kanthaus-stuff on Mattermost and add some descriptive words.

Volunteer induction

2024-11-24T08:34:47Z

Antonin: update after Mattermost migration

🔰 This page lists knowledge and accesses we give to new [[Positions and evaluations|Volunteers]]. It is formatted as Markdown to make it easier to copy into a pad and tick boxes as the steps get done.

Evaluation facilitators don’t need to do all this work by themselves, they can share the pad with the group to spread the load.

<pre>### Immediately after evaluation
_to be done by the evaluation facilitator_
- [ ] invite to #kh_vol_and_mem and #kanthaus-mails
- [ ] invite to the Signal group
- [ ] send them the introductory message (see below)
- [ ] update the website (at https://git.kanthaus.online/kanthaus/kanthaus.online/src/branch/master/user/data/kanthausians.yaml)

### In the next days
- [ ] explain the hosting duties
- [ ] invite to Nextcloud (create their account at https://cloud.kanthaus.online/settings/users and add them to the "Kanthaus" group)
- [ ] show the cloud calendar and file system (see https://wiki.kanthaus.online/Nextcloud)
- [ ] show KeePassXC
- [ ] explain CoMe facilitation and mention git, CoMe script and records
- [ ] explain the email setup, offer access to hello@ and creation of personal kanthaus address (see https://wiki.kanthaus.online/Email)
- [ ] show the wiki (at https://wiki.kanthaus.online)
- [ ] explain the collective agreements changes with ukuvota
- [ ] share link collection
- [ ] give a door tag

### Eventually
- [ ] introduce to git with kanthaus.online to upload CoMe minutes
- [ ] introduce to git with kanthaus-private to update evaluation record

### By request or obvious interest
- [ ] show grafana (https://grafana.yunity.org)
- [ ] show the overview of kanthaus repositories on git (https://git.kanthaus.online)
- [ ] introduce to editing kanthaus.online
- [ ] introduce to editing the wiki
- [ ] introduce to any more complex house task (sysadmin, finances, you name it)</pre>
== Link collection ==

* https://kanthaus.online/public
* https://cloud.kanthaus.online
* https://handbook.kanthaus.online
* https://pad.kanthaus.online/groupHosting#
* https://git.kanthaus.online/
* https://premiumize.me

== Template for introductory message ==

<pre>Congratulations on becoming a Volunteer 🙂

(This message is copy-pasted from https://wiki.kanthaus.online/Volunteer_induction )

I have invited you to the private Mattermost channels
#kh_vol_and_mem (the channel for volunteers and members only) and
#kanthaus-mails (where all mails to hello@kanthaus.online get forwarded to), but there are other channels you could be invited to if you wanted, mostly automatically fed ones like:

* #kanthaus-konto-wawü that prints the charitable association's bank account activity
* #kanthaus-konto-hkw that prints the house owner association's bank account activity
* #kanthaus-residence that prints the results of the weekly script that is used for CoMe
* #kanthaus-git that prints activity on kanthaus-private and kanthaus.online git repositories
* #kanthaus-finances that is mainly (but rarely) used by the finances team

There also is a Signal group that serves as the only encrypted group communication for Kanthaus volunteers and members. I can add you there if you give me your phone number.</pre>
Feel free to point them to the pad where the other induction tasks are listed, so that they can prod other Volunteers and Members if they are interested in getting a specific access or knowledge.

Alternatives to Slack

2024-11-24T08:32:23Z

Antonin:

In the past we used Slack for internal coordination. We looked for alternatives and after [https://legacy.ukuvota.world/#/app/3ab61b88-572c-1b46-f597-1bd8a7262638/vote an ukuvota] we decided to migrate to Mattermost.
{| class="wikitable"
|+
!
! colspan="3" |sign up
! colspan="3" |app
!UI
|-
!
!email
!phone number
!Use nextcloud
account (SSO)
!web
!mobile
!desktop
!distinct levels
|-
|Slack
|yes
|no
|?
|'''yes'''
|yes
|yes
|'''3''' (workspace), channels, messages, replies
|-
|[https://mattermost.kanthaus.online/ Mattermost]
|yes
|no
|paid
|'''yes'''
|yes
|yes
|'''3''' (instance), channels, messages, replies
|-
|[https://kanthaus-test.zulipchat.com/ Zulip]
|yes
|no
| style="background:#9EFF9E" |'''yes'''
|'''yes'''
|yes
|yes
|'''3''' (instance), channels, topics, messages
|-
|Signal
|no
| style="background:#FFC7C7" |'''required'''
|no
|'''yes'''
| style="background:#FFC7C7" |'''required'''
|yes
|'''1''' (group), messages
|-
|Simplex
|no
|no
|no
|'''yes'''
| style="background:#FFC7C7" |'''required'''
|no
|'''1''' (group), messages
|-
|Discourse
|yes
|no
| style="background:#9EFF9E" |'''yes'''
|'''yes'''
|yes
|no
|'''2.5''' [forum] (instance), categories, topics, replies
'''2.5''' [chat] (instance), channels, messages, replies
|-
|Mailing lists
|yes
|no
|no
|'''yes'''
|yes
|yes
|'''?''' (list), messages & replies
|-
|Matrix
|yes
|no
|?
|'''yes'''
|yes
|yes
|'''4''' (instance), space, group, message, thread
|}

==External comparison resources==

*[https://www.messenger-matrix.de/messenger-matrix-en.html Kuketz-Blog Messenger Matrix]

Mattermost

2024-11-24T08:29:17Z

Antonin: update after Mattermost migration

👪️ We use Mattermost to organize ourselves, at https://mattermost.kanthaus.online/

== Creating a personal account ==
You can get an account by following [https://mattermost.kanthaus.online/signup_user_complete/?id=7y1m51bwj3rmmmis573zyknofw&md=link&sbr=sa this link].

== Channels ==
Our main channel is <code>#kanthaus</code>. Many channels we use have been historically prefixed by <code>#kanthaus-</code> because they were in a Slack instance shared with other people.

Some of those channels are private, because they contain private or sensitive information. Those are reserved to Volunteers and Members.

Slack

2024-11-24T08:08:22Z

Antonin: Antonin moved page Slack to Mattermost: migrating to mattermost

#REDIRECT [[Mattermost]]

Mattermost

2024-11-24T08:08:17Z

Antonin: Antonin moved page Slack to Mattermost: migrating to mattermost

👪️ We use a Slack workspace to organize ourselves, at https://yunity.slack.com/

== Creating a personal account ==
You can get an account by following [https://slackin.yunity.org/ this link].

== Channels ==
The Slack workspace we use is shared with other projects (notably the development of the foodsharing platform). Our main channel is <code>#kanthaus</code>. The other channels we use are mostly all prefixed by <code>#kanthaus-</code>.

Some of those channels are private, because they contain private or sensitive information. Those are reserved to Volunteers and Members.

== Migrating out of Slack ==
We are aware of Slack being a proprietary software made available by a for-profit company. We use it for historical reasons and are already preparing to migrate to another platform.

Nextcloud

2024-10-16T11:21:45Z

Antonin: list style fixes

<nowiki>:</nowiki>cloud: We have our own instance of Nextcloud hosted on [[Server|our server]] to store immutable data and our calendar.

== Who can reach it where? ==
The address is: https://cloud.kanthaus.online

You need to have an account to access the Nextcloud. Volunteers and Members are given accounts, others can access the <code>kanthaus-public</code> folder via https://kanthaus.online/public

== How to mount it as a shared directory on my machine? ==
Nextcloud is reachable via the WebDAV protocol. On many Linux variants, you can connect to it in your file manager via the following address (where <code>${my_username}</code> is replaced by your Nextcloud username):
* <code>davs://cloud.kanthaus.online/remote.php/dav/files/${my_username}/</code> for Gnome
* <code>webdav://cloud.kanthaus.online/remote.php/dav/files/${my_username}/</code> for KDE
* You can also mount it manually as a filesystem with [https://docs.nextcloud.com/server/13.0.0/user_manual/files/access_webdav.html#creating-webdav-mounts-on-the-linux-command-line davfs2]

More information about this setup is available in the [https://docs.nextcloud.com/server/13.0.0/user_manual/files/access_webdav.html#accessing-files-using-linux Nextcloud manual], including [https://docs.nextcloud.com/server/13.0.0/user_manual/files/access_webdav.html#accessing-files-using-macos instructions for MacOS] and [https://docs.nextcloud.com/server/13.0.0/user_manual/files/access_webdav.html#accessing-files-using-microsoft-windows Windows].