Kanthaus wiki - User contributions [en]

Yoga room

2024-10-15T10:56:41Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :hibiscus: Yoga Room (or K22-2-4) =

Space to move your body.

=== Purposes ===

* exercise
* meditate
* play
* store some communal sports stuff

=== Specials ===

* 4 hooks on the ceiling
* mats covering the floor
* big mirror on the wall
* fancy indirect light

The Workshop

2024-10-15T10:56:40Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :wrench: General Purpose Workshop (or K22-0-4) =

The place to build and repair things.

=== Purposes ===

* build something
* repair something
* store tools and material
* store ongoing projects

=== Specials ===

* [[technical/compressedair.md|compressed air]]

-----

=== Note ===

The General Purpose Workshop was inaugurated as an Open Workshop for public use on the 16th of April 2024.

For the moment people can make appointments by mail at werkstatt@kanthaus.online or messaging apps at +4915126370301

We also plan to organize special events like bicycle repairs, knife sharpening parties, etc. This aims to also make it a social space for exchange, mutual help, skillsharing and other forms of collaboration.

Windows

2024-10-15T10:56:39Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= Windows =

Most Kanthaus windows are from the DDR: these are basically old-school, wood-frame-and-glass windows, but doubled. You can seperate them by carefully unscrewing the two slit-screws facing inwards on the frame.

== DDR window repair ==

=== Glass replacement ===

* '''replacement glass:''' Wagner Fenster @ Jacobsplatz are nice and might have some old windows you can negotiate for. Transport glass in frame, much less likely to break. Otherwise Baumarkt? Our windows our surprisingly large: see the Dorm window for how to make do with smaller bit of glass.
* '''clear frame:''' Knock out old glass, scrape away old kit and nails so you have bare, clean wood all the way around. Use gloves and be careful!
* '''cutting glass:''' We have a glass cutter and instructions in the workshop, in a small plastic container, on the shelf above the screws. Please read the instructions thoroughly and ensure you can reliably make a long, straight cut before trying on your final piece! Glass should be ~2mm smaller than frame on every side.
* '''fit glass:''' carefully place cut glass in empty frame. Fix roughly in place with window nails: there is a bag of them in the white ‘goo’ cupboard at the bottom, at the back. Push them in using a spatula using only horizontal force. One every 10-15cm.
* '''grout glass:'''
** traditional: get a bag of fenster kit, warm it up. Using a spatula, grout it in as a 45 degree wedge (see any other window). The window can now be remounted. The kit should be painted over after ~1 week, once the kit has developed a ‘skin’, with linseed oil paint. Paint should go over and onto the window glass and frame ~2mm — the paint acts as an oxygen barrier, keeping the kit flexible and long-lasting.
** modern: use silicone gun and nylon wedges. Shouldn’t need painting… but please use white silicone :)

Wifi

2024-10-15T10:56:32Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :signal_strength: Wi-Fi =

To cover as many different needs as possible, we have different Wi-Fi networks:

== <code>kanthaus</code>: most secure, faster, printing, … and recommended! ==

* Ask for the password
* requires up to date devices. If it doesn’t work for you use <code>kanthaus-unsecure</code>

== <code>kanthaus-insecure</code>: less secure, but more flexible ==

* Ask for the password
* Only here devices are allowed to see each other

Water usage tracking

2024-10-15T10:56:31Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :droplet: Water usage tracking =

We log our water usage over time in [[../digital/grafana.md|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:../images/water_meter_reader.jpg|thumb|none|alt=Overview of the water meter reader|Overview of the water meter reader]]

== 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].

Washing room

2024-10-15T10:56:30Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :cyclone: Washing Room / Dumpster Kitchen (or K20-0-1) =

A room for sorting and cleaning clothes and food.

=== Purposes ===

* wash and dry potentially dirty saved food
* wash laundry
* storage for green boxes, big plastic bags and bike bags for dumpster diving
* storage for categorized dirty laundry

=== Specials ===

* waching machine can operate with rain water
* waterproof screen and sound system provide entertainment while washing food

-----

=== Laundry ===

We have a pretty elaborate idea of how communal laundry should be done. Please refer to the [[practicalities/laundry.md|laundry page]] for further details.

=== Food ===

You may find saved food in here which needs cleaning and sorting. Saving food is one of the main tasks in our house. [[practicalities/savingfood.md|Here’s the guide]] to do it properly.

Volunteer induction

2024-10-15T10:56:29Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :beginner: Volunteer Induction =

This page lists knowledge and accesses we give to new [[positionsandevaluations.md|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
- [ ] send them an introductory message (see https://handbook.kanthaus.online/social/volunteerinduction.html#template-for-introductory-message)
- [ ] update the Slack user group
- [ ] invite to the Signal group
- [ ] 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://handbook.kanthaus.online/digital/nextcloud.html)
- [ ] show keepass
- [ ] 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://handbook.kanthaus.online/digital/email.html#for-administrators)
- [ ] show the handbook (at https://handbook.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 handbook
- [ ] introduce to any more complex house task (sysadmin, finances, you name it)</pre>
== Link collection ==

* https://pad.kanthaus.online/come
* https://pad.kanthaus.online/plame
* https://kanthaus.online/public
* https://cloud.kanthaus.online
* https://handbook.kanthaus.online
* https://pad.kanthaus.online/groupHosting#
* https://git.kanthaus.online/

== Template for introductory message ==

<pre>hey!
now that you're a volunteer there's some private slack channels you gain access to. I already invited you to
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's a bunch of other channels you could check out 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 (I can explain you more about that, it's a software version control system that we also use to store some data like the residency record)
* #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. it's sometimes used for specific purposes and/or by people who don't have Slack on their phones. I can add you there if you give me your phone number. :slightly_smiling_face:</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.

Ventilation

2024-10-15T10:56:27Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :wind_chime: Ventilation =

Kanthaus has a [https://en.wikipedia.org/wiki/Heat_recovery_ventilation central heat-recovery ventilation system], consisting of a [https://shop.systemair.com/de-DE/save--vtc--700--l--wrg--geraet/p609989 Systemair SAVE VTC 700] ventilation unit in the K22 attic and an extended system of pipes in valves to the majority of the rooms.

The ventilation unit supplies fresh air to the house, pre-warmed by the stale air it extracts from the house. Both air flows do not mix, they just transfer the heat inside the heat exchanger.

The system automatically adjusts the fan speed to maintain a consistent relative indoor humidity, thereby saving electric power.

== Air flow schema ==

[[File:/images/ventilation-plan.png]]

There are exceptions between floors: - [[rooms/silentoffice.md|Silent Office]] has supply instead of intake - K22-0 just has one intake in the [[rooms/freeshopstorage.md|Free Shop Storage]], but no supply - it pulls fresh air from the hallway and through the [[rooms/freeshoplounge.md|Free Shop Lounge]]

Also, ventilation piping is work-in-progress and will be extended as the house evolves.

== Statistics ==

You can get some statistics about the ventilation system in [[../digital/grafana.html|Grafana]]. Those statistics are pulled from the ventilation unit via [https://git.kanthaus.online/kanthaus/ventilation-watcher an ESP32 device communicating with it via Modbus].

== Maintenance ==

* Intake filters in the rooms: change and wash every 1-3 months when heating is running
* Central filters in the attic: replace and buy new filter every 12 months, ideally before winter
* Heat exchanger in the attic: wash every 1-2 years, maybe?

=== Change and wash intake filters ===

They are located in all rooms where air is sucked into the pipe, to prevent the pipe from getting dirty. Especially when radiators are running, a lot of dust is kicked up in the air and ends in the filters.

To check if a change is necessary, measure the air flow into the intake with an air flow meter (currently in K22-1-1). It doesn’t hurt to replace the filters more often.

You can take the filters out by simply pulling out the valve.

Fresh filters are in a box, currently in the Ex-food-storage (K22-1-1) as of 2023-02-23. Put the new filter on the outside of the pipe and insert the valve again. It’s a bit tricky to prevent the filter from getting pushed too far into the pipe.

You can wash the filters with a lot of water and dry them. Then they can be reused a few times, until holes appear.

=== Central filters in the attic ===

The SAVE VTC 700 ventilation devices has two filters, one for fresh air and one for used air. It’s important to replace the fresh air filter every 12 months, because it gets filled with dust and dirt from outside air. Especially spring and summer add a lot of pollution. When the filter gets full, the air supply can get smelly and the ventilation system doesn’t provide as much air. Hence, it’s good to replace the fresh air filter in autumn.

The used air filter doesn’t need to replaced regularly, as we have to filters on the intakes in the room (see section above).

First, buy a new fitting F7 filter, like those: - https://www.as-luftfilter.de/Ersatzflter-Lueftungsgeraete/Systemair/VTC-700/Ersatzfilter-passend-fuer-Systemair-VTC-700—Gueteklasse-F7.html - https://rt-handel.de/Ersatzfilter-Lueftung/Systemair/VTC-700/Ersatzfilter-passend-fuer-Systemair-VTC-700-Filterklasse-F7

Then turn off the ventilation device, open the main cover and unscrew the left panel. Slide out the old filter and take a picture to show it to interested people ;) Insert the new filter, carefully screw the panel on, close the main cover and turn on ventilation again.

=== Wash heat exchanger ===

We didn’t do this so far, but the heat exchanger can be rinsed with water to get rid of fine dust. This should increase its efficiency.

Ukuvota

2024-10-15T10:56:26Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :dart: Ukuvota =

Our small and simple score voting tool.

== Access ==

* to the [https://legacy.ukuvota.world/#/ tool]
* to the [https://gitlab.com/yunity/ukuvota code]

== Features ==

* Create score votings in the range of -3 to +3 with public link.
* Specify the times for proposal and voting phase.
* Specify an additional weight for negative scores.
* Fully transparent results view.

== Usage ==

We use ukuvota for all important decision-making: - Constitutional changes - Changes to the Collective Agreements - any questions with sufficiently high complexity and/or weight

In the past it was also used in more fun ways, like collect proposals for naming humans (in this case the decision of the crowd was never binding of course… :wink:).

Travel

2024-10-15T10:56:25Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :train: Travel =

As much as you love Kanthaus, you should get out now and then!

=== Public transport ===

:information_source: Beginning 01 Jan 2023, the 49 € ticket should be in action! This will allow you to take all buses, trams and non-ICE trains (e.g. S-Bahn, RE) across Germany for 49 € per month! :information_source:

:information_source: If you fancy a bit of direct action, you can ride illegally-but-supported with the [https://9eurofonds.de 9eurofonds.de] campaign on buses, trams and S-Bahn for a 9 € / month contribution to the fines-fund :information_source:

Wurzen, Leipzig, Halle, Merseburg and Oschatz all lie within the [https://www.mdv.de/ Mitteldeutscher Verkehrsverbund] (MDV). There is a nice map of the whole zone and subzones [https://www.mdv.de/site/uploads/tarifzonenplan.pdf here]. A lot of us really like the [https://oeffi.schildbach.de/ Öffi] transport app for journey plannning which is free and open-source, available on F-Droid and Google Play.

==== To Leipzig ====

The train is most convenient, with the station only 200 m from Kanthaus with 3 connections per hour. The S3 leaves at xx:18 and xx:48 and normally takes 45 minutes to the main station. The RE 50 leaves at xx:31 and takes ~20 minutes. If you would to go to the eastern districts of Leipzig, it might be quicker to take the S3 (to L. Anger Crottendorf or L. Stötteritz, ~25 minutes). The following tickets are valid for both trains.

:warning: You may get fined if your ticket is not “entwertet”. If your ticket doesn’t have a date-time, you need to punch it into one of the stamp-machines :warning:

The '''MDV Einzelfahrkarte''' is a one-way ticket that can be bought at any time, online or at the machines, for '''7,10 €'''. - This fare can be reduced using the [https://www.bahn.com/en/offers/bahncard/bahncard_25-conditions BahnCard 25] to a '''Normalpreis mit BahnCard-Rabatt Einfach''' for '''5,85 €'''. The BahnCard 25 discount card costs 56.90 € for one year. - This fare can be reduced using the [https://abo.l.de/ABO_beantragen ABO Flex] to an '''MDV Einzelfahrkarte ABO Flex''' for '''4,80 €'''. The ABO Flex discount card costs 6,90 € / month, with a minimum period of 6 months. - The discounts can’t be combined.

Alternatively, the '''MDV Hoppertickets''' are '''only available online''' via the [https://bahn.de bahn.de] website or app, or the [https://www.moovme.de/ MOOVME]. They are only available between '''09:00 - 04:00''' on weekdays, no restrictions on the weekend. - '''MDV Hopperticket Einzelfahrt: 6,70 €''' (one-way) - '''MDV Hopperticket Hin- und Rückfahrt: 11,00 €''' (return: the return journey must be made before 04:00 the next day) - These tickets are unaffected by BahnCards or ABO Flex’s

The fares are cheaper from Bennewitz Bhf which is ~3.3 Km ([https://www.qwant.com/maps/routes/?mode=cycling&destination=osm%3Anode%3A2299420210%40Bennewitz&pt=true&origin=osm%3Away%3A982897065%40Kanthaus&selected=0#map=14.44/51.3621209/12.7247490 ~19 minutes bike ride]) from Kanthaus, with the MDV Einzelfahrkarte costing 5,40 € and the MDV Einzelfahrkarte ABO Flex: 3,20 €. The Hopper ticket isn’t any cheaper :shrug:

There also seems to be a bus which goes from Wurzen to Leipzig Sommerfeld, the 691, but the times going [https://www.mdv.de/site/uploads/fahrplaene/rl/220829_rl_691_h.pdf there] and [https://www.mdv.de/site/uploads/fahrplaene/rl/220829_rl_691_r.pdf back] are quite irregular, Sommerfeld is far from the center and the price is unknown—not recommendable.

The private

2024-10-15T10:56:24Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :sunflower: The Private (or K20-2-5) =

The very 1st private room that existed in Kanthaus.

=== Purposes ===

* retreat to a [[practicalities/roomreservation.md|private]] room

=== Specials ===

* close to two toilets

Task lottery

2024-10-15T10:56:23Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :ticket: Task Lottery =

A small online tool for task distribution.

== Access ==

* to the [https://kanthaus.gitlab.io/task-lottery/ tool]
* to the [https://gitlab.com/kanthaus/task-lottery code]

== Features ==

* Tasks that contain slots can be created. Every task can have a name and multiple slots.
* Participants with names can be created.
* A button starts the random distribution of participants to tasks.
* A signature melody plays during the assignment process.

== Usage ==

During [[social/come.md|CoMe]] we use the task lottery to distribute dinner shifts and the opening of the free shop. In times of house fullness we might add lunch to the lottery.

Thanks to [https://maxlath.eu Maxime’s] custom coding the sections of the [https://codi.kanthaus.online/come CoMe pad] in which people specify their unavailabilities or volunteer for a certain shift, are automatically imported.

Processes to manage stuff

2024-10-15T10:56:22Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :package: Processes to manage stuff =

<img src="/images/underConstruction.jpg" alt="under construction yeah" style="width:150px;"/>

‘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 ==

Located in the [[rooms/intermediate.md|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: 1. '''Removing''' stuff from the household. 1. '''Clearing''' a corner of the household. 1. '''Adding''' stuff to the household.

# 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 [[rooms/freeshop.md|Free Shop]].

=== How does it work? ===

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

==== Phase 1 (0-7 days) ====

* All new items go here.
* If you have a certain reason for sorting out something (e.g. broken, we have too much of this, etc.), please add a note so others can understand your thoughts.
* The shift should always happen in [[social/powerhour.md|Power Hour]] before other things are added to phase 1.
** This means depending on when an item is added to the vortex, it might only stay in phase 1 for a very short time before it is shifted to the next phase.

'''Which items can be saved back from the vortex at this stage?''' Only your own personal items.

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

* Items from phase 1 are shifted here during [[social/powerhour.md|Power Hour]].

'''Which items can be saved back from the vortex at this stage?''' Your own personal items. Items you know to be communal.

==== Phase 3 (7 days) ====

* Items from phase 2 are shifted here during [[social/powerhour.md|Power Hour]].

'''Which items can be saved back from the vortex at this stage?''' Your own personal items. Items you know to be communal. Items that might have been private before can now be communalized. Items that might have been communal before can now be privatized.

==== Doom ====

* Items from phase 3 are doomed during Power Hour, this means:
** items that make sense to communalize are sorted into fitting communal locations
** trash is put into bins accordingly
** good but unneeded items go in the [[rooms/freeshopstorage.md|Free Shop Storage]]

'''Which items can be saved back from the vortex at this stage?''' Privatize whatever you want. Only (re-)communalize stuff if you’re really sure about it and know a good location for it!

==== Details of the shifting ====

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 [[digital/slack.md|Slack]].

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 [[rooms/freeshop.md|Free Shop]] - 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. - 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 [[social/powerhour.md|Power Hour]] to phase 1. - Upload the pictures to #kanthaus-stuff on [[digital/slack.md|Slack]] and add some descriptive words.

== Decluttering actions ==

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

=== Communal stuff decluttering ===

On example for communal stuff decluttering is the K20 entrance with its communal shoe and jacket shelf. Let’s say we want to declutter 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 [[rooms/dragonroom.md|Dragon Room]] or [[rooms/elephantroom.md|Elephant Room]] tables.
# Specify a time frame for the event and communicate it on site (the shelf itself, the sorting area and on [[digital/slack.md|Slack]]). 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 decluttering ===

Basically the same as the communal stuff decluttering, private stuff decluttering 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 [[rooms/spitzstorageroom.md|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 [[social/positionsandevaluations.md|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 ==

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

[[File:/images/maximeStuffRequest.jpg|Request to privatize]] ''Example of someone asking to privatize communal items''

Spitz storage room

2024-10-15T10:56:20Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :package: Spitz Storage Room (or K20-4) =

For storage of items that do not need to be frequently accessed.

=== Purposes ===

* store communal stuff in an organized way
* store personal stuff

=== Specials ===

* fancy fairy lights
* banana box storage

-----

=== Personal stuff storage allowance ===

Up to 3 stacked banana boxes (or equivalent volume), per person. Non volunteers and members need to update the Last Date Accessed (LDA) on their boxes at least once a year (by crossing over the previous date on the label of the box, and adding the current one). If their stuff is found to be over a year since the LDA, then the stuff can be [[social/stuffprocesses.md|vortexed]], and the owner notified (if known and possible). Adding contact information could be a good idea.

Ideally nobody should need to move other people’s stuff to access their own.

=== Order for communal items ===

Ideally we would circumscribe the storage to certain general categories of stuff, to easily assess if a wanted item could be found there or not. Stuff that is not readily obvious should be clearly labeled, with as much useful information as possible (i.e.: responsible/knowledgeable person/s, status or condition, amounts, instructions, etc).

=== Notes ===

* The marked corridor should be free of stuff standing or poking into, this way it is easier and safer to move around carrying stuff.
* Banana boxes can easily be sourced by going to supermarkets and asking employees for them.
* There is a long purple ethernet cable under the ventilation pipes cover.
* There is no ventilation in this room.
* Do not forget to turn off the light when leaving. The red witness light in the switch is on when the light is on.

Sorano

2024-10-15T10:56:19Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :european_castle: Sorano (or K22-1-1) =

Communal sleeping room with 3-4 sleeping spots.

=== Purposes ===

* sleep in [[practicalities/roomreservation.md|communal]] room
* store some personal things

=== Specials ===

* probably the coldest sleeping room in Winter

Social sauna

2024-10-15T10:56:18Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :foggy: Social Sauna =

<img src="/images/underConstruction.jpg" alt="under construction yeah" style="width:150px;"/>

The monthly meeting for Volunteers and Members to talk about social tensions specifically and emotions generally.

Snack kitchen

2024-10-15T10:56:16Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :bread: Snack Kitchen (or K20-1-1) =

The place to find quick snacks and drinks.

=== Purposes ===

* prepare bread, oats, convenience food
* make tea or coffee
* [[practicalities/dishwashing.md|use the dishwasher]]

=== Specials ===

* the fridge

-----

=== Jar norm ===

To have only matching lids to jars, we decided to keep one kind of jars: The 77 jar (meaning 77mm diameter of the lid).

[[File:/images/jarNorm.jpeg|Jar norm]] ''The system proved very useful!''

Mattermost

2024-10-15T10:56:15Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :family: Slack =

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.

Silent office

2024-10-15T10:56:14Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :computer: Silent Office (or K20-0-2) =

The silent office is a space for silent office work on your own projects. It provides desk space for 5 people, including a few monitors, keyboards and mice.

=== Purposes ===

* work on a (claimed) desk
* store some personal items at claimed desks

=== Specials ===

* quiet environment by default

Server

2024-10-15T10:56:12Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :star: Kanthaus server =

We have a server running locally that provides a few services to residents as well as guests.

== File sharing services ==

The server provides the possibility to store and exchange data. Some services are publically available (e.g. connecting with an anonymous user), for others you need a user account with some privileges. All file services are only available in the <code>full</code> [[../technical/wifi.md|network]] and served via [Samba](https://en.wikipedia.org/wiki/Samba_(software)). Use your computers file manager to browse the available network computers and locate the server as <code>KANTHAUS-SERVER</code>. If this doesn’t show up in your file manager or the link is broken, you can try entering <code>smb://kanthaus-server/</code> directly into your file managers adress bar. This should work on most linux environments.

=== Getting a user account ===

To get a user account, speak to an admin (e.g. Antonin or Tilmann). The admin will add you to the ansible user configuration and ask you to set a temporary password using your account. You can change the password yourself, e.g. via <code>smbpasswd -r kanthaus-server -U yourusername</code>.

Actually, you have two passwords: * System user account: Used for local access and SSH access. Change password using <code>passwd</code> when logged in * Samba account: Used for accessing the samba network shares. Change password using command above remotely or using <code>smbpasswd</code> when logged in.

==== Kanthaus cloud copy ====

* The share <code>kanthaus-public</code> offers an anonymously usable read only copy of the public part of the kanthaus cloud.
* The share <code>cloud.kanthaus.online</code> offers a read only copy of the whole kanthaus cloud. You need to have a user with the permissions class <code>kanthaus</code>.

The cloud copy is synchronized from the kanthaus cloud once every minute.

==== Internal cloud ====

The share <code>internalcloud</code> stores some data which should only be available from inside Kanthaus (e.g. financial data) and is only available to users with the permissions class <code>internal</code>. Please make sure to only put security sensitive stuff in here and also make sure to not leak your user credentials or the contents of this folder, when you have access to it.

This folder is part of the daily backup.

==== Home folder ====

Every user account also has their personal <code>home</code> folder available as the <code>homes</code> storage. All data you put here is only available to yourself. Inside the home folder, there is a directory called <code>storage</code>. This folder lies on an easily expandable, cheap harddisk storage. It is slower to access but suitable to store lots of data (e.g. backups of your computer).

Your home folder is part of a daily backup. Please put files called <code>.nobackup</code> into folders that you don’t want to be backed up (e.g. to save storage space). The <code>storage</code> folder is '''not''' part of the backup, but the harddisks have a raid configuration to tolerate the loss of one harddisk.

== Shell access ==

When you have a user account, you can also use SSH to connect to the server and use it for computing tasks. To set an initial password, ask an admin. When you already have file sharing access, you can add your SSH public key to the <code>homes/.ssh/authorized_keys</code> and use that for logging in. Same as above: In your home directory there is a symlinked folder called <code>storage</code> which is on spinning disks, whereby the rest of your home folder is on limited SSD space.

== SFTP Access ==

You can use software like FileZilla to access your home folder through <code>sftp://kanthaus-server</code> providing your username. See the Shell Access section above for other details.

==== How to unlock the encrypted <code>kanthaus-server</code> via network ====

* be in <code>kh-admin</code>
* <code>ssh -p 2222 root@192.168.178.249</code>
** your key must be stored on the server in <code>/etc/dropbear-initramfs/authorized_keys</code> -> <code>update-initramfs -u</code>
** ED25519 key fingerprint: <code>SHA256:mvCVYx8D/Fv/qYq+a/H4MoRAcfExAUsAFW3L2NVHnD0</code>
* enter password (stored in keepass -> Server)

== System specs ==

System is designed to save power but still have some computing resources. * CPU: Intel Core i5-4670 (4x 3.4 GHz) * Ram: 8 GB DDR3L (If there is the need we have 16 GB available, just needs more power) * SSD: 1 TB Samsung 860 Evo as root file system * HDD: BTRFS pool with 3 disks, 1 redundant. Current usable size ~3.5 TB

== Backups ==

Backups are done using borgmatic. The backup target is the local harddisk storage, so it does not safe us against fire or theft of the computer. We might think about adding a remote backup as well.

== Other services ==

* Foodsharing Gitlab CI runner (dockerized)
* House bus services
** local Web interface (dockerized)
** Logging daemon to externally hosted influxdb
* Virtual machines (kvm/libvirt)

Saving food

2024-10-15T10:56:11Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :pear: Saving food =

Almost all the food we eat is saved. Here you can find out how that works.

=== Getting the food ===

The first step is, of course, to get the food into the house. We have two main ways of doing so:

# foodsharing pickups

Officially agreed-on cooperations with stores are the best way to save food. There are cooperations with different kinds of stores in the area. [https://foodsharing.network foodsharing] is not exclusive to Kanthaus and signing up for a pickup requires being a verified foodsaver on aforementioned page. If you’re interested but need help, talk to Janina.

<ol start="2" style="list-style-type: decimal;">
<li>Dumpster-diving</li></ol>

We also save food from dumpsters of supermarkets. We have several good spots we usually visit by ebike. If you want to see the true extent of food waste for yourself, you should really join in and take a look into a dumpster! Talk to anyone in the house to get involved.

When you come back from a successful food haul, you’ll have crates and bags full of very ripe fruit, partly foul veggies and potentially soiled packaged food. Leave those crates and bags on the floor of the K20 entrance to be found by people in the morning.

=== Sorting and cleaning the food ===

Everybody will be thankful to people who clean and sort food! Here’s how you go about it:

(tbc)

Room reservation

2024-10-15T10:56:05Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :shell: Room reservation =

Kanthaus offers different levels of privatization for rooms, beds and desks. Some can be reserved for a limited amount of time and some can be claimed until they are unclaimed again by their user.

=== Different levels of sleeping spot privatization ===

Sleeping spots come in three different variants: - claimed bed in communal sleeping room - claimed bed in multi-purpose room - claimed private room with bed

==== Claimed bed in communal sleeping room: communal ====

In communal sleeping rooms like the [[rooms/dorm.md|Dorm]], the (original) [[rooms/communalsleeping.md|Communal Sleeping Room]], the [[rooms/catplanedreambasket.md|Cat Plane Dream Basket]] and the [[rooms/sorano.md|Sorano]], you can claim your bed using the sheet on the outside of the door. There is no time limit on your claim. You can leave reasonable amounts of private items in and around the bed, as long as they don’t interfere with others.

[[File:/images/catPlaneDreamBasket_reservation.png|communal reservation]] ''the reservation sheet of the Cat Plane Dream Basket''

==== Claimed bed in multi-purpose room: semi-private ====

There are just two multi-purpose rooms: the [[rooms/fansipan.md|Fansipan]] and the [[rooms/intermediate.md|Intermediate Storage Room]]. Both have one big bed each and additional features which make it necessary for the room to stay accessible (e.g. claimable desks and the [[social/stuffprocesses.md|vortex]]). The beds in these rooms count as semi-private since in reality people usually don’t get disturbed during the night, even though the theoretical possibility exists.

On the beds you can find a weekly reservation sheet in which you can reserve it for a specifc time frame up to 1 week (although it is best practice to only reserve for 2-3 nights at once to give others the possibility of signing in, too). Leaving personal items in and around the bed is only permitted during the time of your reservation. The week sheet is cleared every Monday as task handed out during [[social/come.md|CoMe]].

[[File:/images/reservationWeekSheet_2.png|weekly reservation sheet]] ''Time-based reservations that can be as short as 1 hour.''

Multi-purpose rooms have an additional card system on the outside of the door to indicate if the bed is already in use or not. This is to be understood along the lines of ‘If you’re looking for a sleeping spot, no need to look in here’ and not like a prohibition to enter!

==== Claimed private room with bed: private ====

Kanthaus has 3 reservable private rooms: the Lantern, the (original) Private and the Hipster. In times of need the Cloud Room can be used as an additional private.

On the outside of the doors you can find a reservation sheet in which you can reserve the room for a specifc time frame up to 1 week (although it is best practice to only reserve for 2-3 nights at once to give others the possibility of signing in, too). Leaving personal items in the room is only permitted during the time of your reservation. The week sheet is cleared every Monday as task handed out during [[social/come.md|CoMe]].

Next to the reservation sheet on the door you can find the occupancy indicator. It allows to show that the room is in actual use and noone is invited in. This is important because private rooms which are reserved but empty can still be used spontaneously by someone else as long as they’re freed immediately when the person who did the reservation wants to use them.

[[File:/images/occupancyIndicator.jpg|occupancy indicator]] ''Occupancy indicator, rules sign and week sheet on the door of a private room.''

=== Desks ===

In the Main Office, the Silent Office and the Fansipan people can claim desks. Desk claims are without time limit and include the right to store personal items, as well as creating more storage space in and around the desk, as long as it doesn’t disturb anybody.

[[File:/images/privateDesk.jpg|claimed desk]] ''Claimed desk in a slightly messy Silent Office.''

Room numbering

2024-10-15T10:56:04Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :1234: Room Numbering =

As the Kanthaus consist of two houses with multiple levels per house and multiple rooms per level, there is the need for a systemic numbering approach. The numbering is split up into different sections for each part:

* House
* Level
* Room

This makes up for a reference like <code>K20-0-2</code> for the [[rooms/silentoffice.md|Silent Office]] or <code>K22-1-1</code> for the [[rooms/sorano.md|Sorano]]

=== Houses ===

The houses are identified as:

* K20
* K22

=== Floors ===

The floor you enter a building on from the street or courtyard is called '''ground floor''' or numbered 0.

* B: Basement
* 0: Ground floor
* 1: Floor directly above ground floor
* 2: Top regular floor
* 3: Attic
* 4: Spitzboden

=== Rooms ===

Individual rooms in the specified section are identified by numbering them '''counter-clockwise''' starting from the point where you enter the floor’s hallway to the right with 1.

The room numbering is individual for most floors but generally is in the range from 1 to 5.

=== Exceptions ===

* Hallways: Don’t have numbers. Referenced as (e.g.) <code>K20-1 hallway</code>
* Staircase: Don’t have numbers. Reference as (e.g.) <code>K20 staircase</code>
* Half-Floor rooms in staircases: <code>K20-0#</code> is the room halfway between <code>K20-0</code> and <code>K20-1</code>
* The small “rooms” behind the old K20 bathrooms are not numbered and instead interpreted as belonging to the bigger rooms

Residence record

2024-10-15T10:56:03Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :memo: Residence record =

In the residence record, we record the residents of Kanthaus on a daily basis. The file is stored in a private [[git.md|git repository]] on [[server.md|our server]].

=== Why are people recorded? ===

* Because of our [[../social/positionsandevaluations.html|positions system]], which requires us to know how much time individuals spend at the space.
* We love data. That’s why we collect a lot of that, also on people.

=== How and when are people recorded? ===

* Whoever spent a night in Kanthaus will be recorded for the following day.
* People are listed chronologically. That means if Lisa and Bob arrive on the same day, but Bob comes at 5pm and Lisa at 8pm, Bob is recorded before Lisa.
* Many names are quite common, so we add a suffix. Whoever records a person first can decide on the suffix and if it is even needed. Common suffixation patterns are: first letters of last name or abbreviation of context organization.
* If you record someone with a frequent name make sure there has not been someone else recorded without a suffix already!
* Adding suffixes to past records is completely fine. What counts is reliable data.
* The residence record ideally is updated every day to avoid making mistakes.

=== What if I don’t want to be recorded? ===

* You can provide us with a consistent pseudonym, that we will use instead of your name.

Repro orga

2024-10-15T10:56:01Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :sparkling_heart: Repro orga =

How we organize our reproductive work.

== Repro what? ==

Reproductive work is the work that needs to be done to keep things running. It’s the underlying foundation that people need to focus on something else. It’s about food, cleaning, tidyness and social care. Or to say it with wikipedia:

<blockquote>Reproductive labor or work is often associated with care giving and domestic housework roles including cleaning, cooking, child care, and the unpaid domestic labor force. ''[https://en.wikipedia.org/wiki/Reproductive_labor Wikipedia]''
</blockquote>
We recognize this kind of work as extremely important and make structures to try and distribute it on as many shoulders as reasonably possible.

== Systems we use ==

We have come up with different systems for different use cases. These systems are by no means exhaustive and they are always a work in progress.

=== Power Hour ===

The weekly time of communal cleaning is meant to establish basic cleanliness and include every resident. It’s a well tested and often improved structure of ours that deserves its’ own page: [[social/powerhour.md|Power Hour page]]

=== Task lottery ===

Just like the name suggests this is a lottery for tasks. In this case it’s an online toll custom made for us but adaptable to many cases (and important enough to have its’ own page: [[digital/tasklottery.md|Task Lottery page]]). We mainly use it for communal food preparation shifts.

=== Repro Sheet ===

The repro sheet exists in many different versions in a variety of places. It’s simplicity is what makes it so attractive and versatile: You just make a table, put tasks to each day and let people fill themselves in.

This is very useful for times of heightened organization levels, like building weeks when we invite external people to help us with construction work. The influx of new people and the focus on joint efforts results in frequent (maybe even daily) meetings, which can also be used to make sure the repro sheet gets filled.

[[File:/images/reproSheet.png|repro sheet]] ''Example of a repro sheet''

== Repro work that is not covered ==

We are fully aware that not all the necessary repro work is covered by our systems and that it never will be. Things like emotional care work can not be pressed into a system. Sure, there are ways to try like e.g. appointing a person that can be approched, but who’s to say that people who have a problem will open up to this exact person? There will always be work done that is not part of a system. We have accepted it and try to incorporate this understanding most productively.

=== Laundry ===

Since the perfect moment for doing laundry depends heavily on the weather (solar power, drying space and rain water available) we do not subject it to any system for now. Tilmann is especially motivated to run washing machines when the time is right. He will often do huge amounts of laundry on sunny days and then leave baskets of clean wet laundry in the K20 entrance. If you see one, feel very much invited to put it up somewhere. :) More on laundry on its’ own page: [[laundry.md|Laundry page]]

=== Food on the weekends ===

The weekends are a structure-free time. People can make food if they feel like it, but nobody is expecting to get fed. Often people just eat small meals in small groups or someone spontaneously prepares something.

=== Cleaning of central area ===

The [[rooms/kitchen.md|Main Kitchen]], the [[rooms/snackkitchen.md|Snack Kitchen]] and the [[rooms/diningroom.md|Dining Room]] are used especially much, which naturally results in more need for cleaning. Although we expect everyone to tidy up behind themselves and sometimes do the extra effort of wiping a table or washing some pots, it is obvious that some people do more of this than others.

Usually it goes in waves: - Someone takes extra care and everything looks neat. - That person doesn’t feel like doing this service anymore and/or gets annoyed. - They bring it up or just stop doing it. - If nobody takes over it gets messier, to a point where more people complain. - Everybody becomes more aware and puts in more effort. - Things look neat again. - Over time most people stop putting in extra effort. - And we’re back to the beginning.

So far there was never intense frustration and bringing up the topic actually works. But only for a while. And maybe that’s also okay..?

=== Everything out of the ordinary ===

Irregular cleaning, sorting, organizing and maintaining is always dependent on the initiative of individuals. If they want to make a big communal action out of it, it might work. How it usually goes, though, is that someone sees a task, feels motivation, gets started and maybe someone else joins in.

Printing

2024-10-15T10:55:59Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :fax: Printing and Scanning =

-----

'''On this page''' - [[#printer-details|Printer details]] - Printing - [[#general-information|General information]] - Manual installation - [[#linux|Linux]] - [[#windows|Windows]] - [[#automatic|Automatic]] - Scanning - [[#to-usb|To USB]] - [[#to-network|To network]]

-----

== Printer details ==

* Model: Canon imageRunner Advance C2025i
* Location: Office (K20-1-4)
* Type: Laser
* Color: CMYK
* Paper size: A4 (Tray 2), A3 (Tray 1), Custom (Manual Feed)
* Duplex: Yes
* Scanning: Duplex ADF, to network share or USB

== Printing ==

=== General information ===

* You need to be in the <code>kanthaus</code> network to print.
* If you use a VPN, you’ll need to switch it off for printing.
* The printer consumes ~15W on standby. It may be left on during the day; it should be switched off at night. The power switch is on the right, vertical edge as you face the printer.
* On startup the printer may ask for the paper size of a paper tray: choose ''“A4 - plain paper”''.
* Sometimes the printer doesn’t wake up from sleep for printing: wake it by pressing the ‘power’ button on top panel.
* Pressing the ‘eye’ button 👁 let’s you view the current print job(s) and adjust the paper size.
* Often pages are printed in ''“US Letter”'' format accidentally - but there is only A4 and A3 paper in the printer, so these jobs are rejected with the ''“Load paper”'' instruction.
* Printing a booklet? Install the easy-to-use [https://kjo.herbesfolles.org/bookletimposer/ bookletimposer] (e.g. <code>sudo apt install bookletimposer</code>) to convert a linear PDF into booklet format. The default settings are probably what you want (i.e. print 2 pages side by side on A4 -> A5 booklet when folded and stapled)

=== Manual installation ===

''A bit tedious, but reliable''

==== Linux ====

# Install the Canon CQue driver:
#* Arch/Manjaro: <code>yay -S canon-cque</code>
#* Debian/Ubuntu: download and install the [https://www.canon-europe.com/support/business/products/office-printers/imagerunner/advance/imagerunner-advance-c2025i.html CQue DEB Driver].
# Add printer:
#* via system settings:
#*# ''“Settings”'' → ''“Printers”'' → ''“Additional Printer Settings…”'' → ''“+ Add”'' → ''“Network Printer”'' → ''“AppSocket/HP JetDirect”''
#*# For ''“Host”'' give <code>192.168.4.153</code> → ''“Forward”''
#*# Pick the driver
#*#* In ''“Makes”'' select ''“Canon”'' → ''“Forward”''
#*#* In ''“Models”'' choose ''“iR-ADV C2025i”'' and in ''“Drivers”'' choose ''“Canon iR-ADV C2025i PCL”'' → ''“Forward”''
#*#** if not available, choose ''“iR-ADV C2025 UFR II”'' or ''“iR-ADV C2025i PXL”''
#*# For all further options you can keep the default
#* via CUPS:
#*# Open CUPS interface: http://localhost:631
#*# ''“Administration”'' → ''“Printers”'' → ''“Add Printer”'' (You may be asked for your user (sudo) credentials)
#*# ''“Add Printer”'' → ''“AppSocket/HP JetDirect”'' → ''“Continue”''
#*# For ''“Connection”'' give <code>socket://192.168.4.153:9100</code> → ''“Continue”''
#*# Provide ''“Name”'' of your choice. ''“Description”'' and ''“Location”'' can be left empty → ''“Continue”''
#*# For ''“Make”'' select ''“Canon”'' → ''Continue''
#*# For ''“Model”'' select ''“Canon iR-ADV C2025i PCL”'' → ''“Add Printer”''
# Ensure ''“Media Size”'' is ''“A4”'' in the printer settings.

==== Windows ====

# Download and extract the [https://www.canon-europe.com/support/business/products/office-printers/imagerunner/advance/imagerunner-advance-c2025i.html [Windows 32bit & 64bit] Generic Plus PCL6 Printer Driver]
#* Make sure you know where the driver is extracted to. It may be in the same folder as the <code>.zip</code>, or it might have been cleverly put somewhere by your system. If unsure, try to extract the <code>.zip</code> again: it will complain that it’s already been extracted, and show you the path where it’s being extracted to.
# Add printer
#* Windows 10
#*# ''“Start”'' → ''“Settings: Printers and Scanners”'' → ''“Add a printer or scanner”'' Ignore auto-detected printers, click ''“The printer that I want isn’t listed”'' that will appear in some moments.
#*# In ''“Find a printer by other options”'' select ''“Add a local printer or network printer with manual settings”'' → ''“Next”''
#*# In ''“Choose a printer port”'' select ''“Create a new port”'', and in ''“Type of port”'' select ''“Standard TCP/IP Port”'' → ''“Next”''
#*# In ''“Type a printer hostname or IP address”'', for ''“Hostname or IP address”'' give <code>192.168.4.153</code>. ''“Port name”'' will auto-fill as you write, leave it as is. Make sure ''“Query the printer and automatically select the driver to use”'' is selected → ''“Next”''
#*# In ''“Additional port information required”'' leave the ''“Device Type”'' as ''“Standard: Generic Network Card”'', → ''“Next”''
#*# In ''“Install the printer driver”'', select ''“Canon Generic Plus PCL6”'' either through the options list, or by navigating via ''“Have Disk…”'' → ''“Next”''
#*#* If you use ''“Have Disk…”'' the path will start with the folder you extracted to (see <code>1.</code>) and end with <code>GPlus_PCL6_Driver_V290_32_64_00\x64\Driver\CNP60MA64.INF</code> or similar.
#*# If you get to ''“Which version of the driver to you want to use?”'' leave the selection as ''“Use the driver that is currently installed (recommended)”''
#*# In ''“Type a printer name”'', give the printer a meaningful name for you → ''“Next”''
#*# In ''“Printer Sharing”'', leave ''“Do not share this printer”'' selected → ''“Next”''
#*# In ''“You’ve successfully added [name]”'' → ''“Finish”''
# Ensure ''“Page Size”'' is set to ''“A4”''
#* Windows 10
#*# ''“Start”'' → ''“Settings: Printers and Scanners”'' → click on the printer you just added → ''“Manage”''
#*# In the new window, click ''“Printing Preferences”'' from the left-side menu
#*# In the new window, set ''“Page Size”'' to ''“A4”'' → ''“Apply”'' → ''“OK”''
#*# Now try printing the test page.

=== Automatic ===

''Buggy! Manual installation (above) recommended.''

If you are logged into <code>kanthaus</code> or <code>kanthaus-insecure</code>, the printer should automatically appear in your print dialogues as <code>Kanthaus_CanonC2025_...</code>. (The printer is ''not'' accessible from <code>kanthaus-gast</code>.)

If you don’t see the printer, check your system has [https://en.wikipedia.org/wiki/Multicast_DNS MDNS] For linux, this means having <code>avahi-daemon</code> installed and running, which should be the default on most distibutions.

This method prints via the virtual printer installed on the kanthaus server. While this should normally work, you might consider installing the printer manually on your system to avoid any potential problems and have a more direct relationship to the printer.

== Scanning ==

=== To USB ===

Insert a USB stick into the printer (slot to the right of the control panel). Press the power button on top to wake printer if sleeping, then press the ''“Scan & Store”'' button on the top of the screen and select the USB Memory Media.

Select options as desired, then press big, green button to scan. Press ''“Start storing”'' to transfer the scan, and finally eject USB stick via small, green button on the bottom-right corner.

<blockquote>'''Note:''' The USB stick needs to be formatted with the Windows file system FAT to be recognised by the printer/scanner-combination.
</blockquote>
=== To network ===

After turning the printer on, press the ''“Scan & Store”'' button on the top of the screen and select the KH-Server location.

After scanning, you will find your files in the [smb://kanthaus-server/scan Scan] share on kanthaus-server. Use the file manager of your system and browse for <code>windows/samba/network shares</code> or directly enter the address: <code>smb://kanthaus-server/scan</code>. If you are asked for any credentials, you can login anonymously.

For Windows 10, you may additionally need to: 1. enable SMB1.0 - in settings, go to ''“Windows Features”'' → tick options starting ''“SMB”'' → click ''“OK”'' 2. map network drive - open file explorer → go to ''“This PC”'' → click ''“Map network drive”'' (top menu bar) - in the pop-up: - for ''“Drive”'', choose a drive letter (any unused letter, default should be OK) - for ''“Folder”'', give <code>\\kanthaus-server\scan</code> → ''“Finish”''

<blockquote>'''Note:''' Remove your files after scanning: they are accessible to anyone without authentication from all networks except <code>kanthaus-gast</code>.
</blockquote>
== Maintenance/repair ==

* 2024-06: A4 paper was printing with Magenta and Yellow ‘haze’ on both sides. This issue persisted despite some deep cleaning of the toner cartridges (minimal improvement). The issue magically disappeared after some time.
* 2024-08: A3 predictably jamming - unresolved.

Powerhour

2024-10-15T10:55:57Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :sparkles: Power Hour =

The weekly communal cleaning session.

=== Time and place ===

'''Mondays at 11 am''' we meet in the [[rooms/diningroom.md|dining room]] to distribute tasks. Then all of our houses will be cleaned for a maximum of 2 hours.

=== Initial meeting ===

There is a Power Hour Task List for the most relevant tasks.

[[File:/images/powerHourTaskList2024.png|thumb|none|alt=Power Hour Task List|Power Hour Task List]]

The facilitator goes through the tasks briefly to find out which ones are of priority this week. Visitors are given tasks first so that they can be paired with more experienced Kanthausians easily. Then there is a round in which people can grab their preferred task. The facilitator makes sure that no important task is left and that everybody has something to do in the end.

This meeting should not take more than 10 minutes.

=== General Info ===

Most cleaning supplies are stored in the [[rooms/intermediate.md|Intermediate Storage Room]].

If the layout of the house is not clear to you, please refer to the [https://kanthaus.gitlab.io/expfloorer/ expfloorer].

If you can’t clean immediately after the Power Hour meeting, please do it in the next 2-3 days.

=== Detailed description of tasks ===

==== Main Kitchen ====

* clear the rack of clean dishes
* do all the dishes
* clean the sink
* clear and clean all surfaces
* clean the stoves
* if necessary exchange the towels and/or sponges
* do what you think should be done additionally

==== Snack Kitchen ====

* empty and fill the [[practicalities/dishwashing.md|dishwasher]]
* clear and clean all surfaces
* clean the sink and mirror
* clean the microwave, mini oven and toaster
* if necessary exchange the towels
* do what you think should be done additionally

==== Bathrooms K20 ====

This is about all bathrooms and toilets in K20: The [[rooms/mainbathroom.md|Main Bathroom]], the upper and lower staircase toilets. - clean the toilet - clean the sink and mirror - empty the bucket of used butt towels - refill clean butt towels and toilet paper - if necessary exchange the hand towel - in the Main Bathroom: clean the bathtub - do what you think should be done additionally

==== Bathrooms K22 ====

This is about all bathrooms and toilets in K22: The [[rooms/2ndbathroom.md|2nd Bathroom]], the [[rooms/babybathroom.md|Baby Bathroom]], the [[technical/composttoilet.md|Compost Toilet]]. - clean the toilet - clean the sink and mirror - empty the bucket of used butt towels - refill clean butt towels and toilet paper - if necessary exchange the hand towel - bonus task: clean the sink in the [[rooms/electroworkshop.md|Electronics Workshop]] and exchange the hand towel - do what you think should be done additionally

==== Vacuuming Central Rooms ====

* get a vacuum cleaner from the [[rooms/intermediate.md|Intermediate Storage Room]]
* vacuum all of K20-1 and K22-1 except the staircases

==== Vaccuuming Staircase K20 Plus ====

* get a vacuum cleaner from the [[rooms/intermediate.md|Intermediate Storage Room]]
* vacuum the K20 staircase and whatever needs vacuuming in K20-0, K20-2 and/or K20-3

==== Vaccuuming Staircase K22 Plus ====

* get a vacuum cleaner from the [[rooms/2ndbathroom.md|2nd Bathroom]]
* vacuum the K22 staircase and whatever needs vacuuming in K22-0 and/or K22-2

==== Vortex Shifting ====

* go to the [[rooms/intermediate.md|Intermediate Storage Room]]
* follow the [[social/stuffprocesses.md|instructions about the vortex]]

==== Indoor Plant Care ====

* take a watering can from the [[rooms/intermediate.md|Intermediate Storage Room]]
* walk through all of K20 and K22 looking for plants
* only water plants which are actually dry!
* make sure not to flood the surroundings!
* already flooded plants need to have their excess water removed instead of adding more
* also look at pieces of plants in glasses of water and maybe exchange or refill the liquid
* do what you think should be done additionally

==== Bin Emptying ====

* the big bins are in the garden next to the K22 back door
* [https://germanyinusa.com/2020/08/26/recycling-in-germany-2/ some general advice on German recycling]
* empty the bins in the Main Kitchen
* bring glass and Pfand from the Main Kitchen into the K20 basement
* empty the bins in the Snack Kitchen
* empty the bins in the Main Office
* empty the bins in the Intermediate Storage Room
* empty the bins in the Main Bathroom
* if necessary empty the small bins in all the toilets

==== Incoming Food Care ====

* look through the boxes of incoming food in K20-0 entrance
* seperate food that needs immediate care (e.g. berries, broken packagings, unfrozen things)
* seperate clean from dirty food
* clean and dry long-lasting food goes to the food storage in K20-B (make sure packaging is not damaged!)
* clean and dry fruits and vegetables go into the food shelves in K20-1
* clean everything that needs cleaning in the [[rooms/washingroom.md|Washing Room]]
* clean and wet food can sit there until it’s dry
* more detailed instructions can be foun in the section about [[practicalities/savingfood.md|saving food]]

==== Existing Food Care ====

* look through the food shelves in K20-1
* throw away rotting food
* sort the food by kind when it still lasts
* make a ‘needs urgent attention’-box and tell the cooking team of the day
* look through the fridge
* bonus task: look through the food storage in K20-B

==== Communal Closet Sorting ====

* sort the clean communal clothes into the fitting spots in the closet
* mind the sizes!
* match socks, leftover single socks can stay in a basket under the [[rooms/communalcloset.md|clothes 4 future]] rail
* sort out ripped or torn clothes
* fold towels and put them into the closet in the Main Bathroom
* fold tea towels, put them in extra basket together with other kitchen things
* fold duvet covers inside out and in a way that one can read the size written on the bottom
* bring bed cloths, kitchen textiles, clean butt towels and sorted-out clothes to Intermediate Storage Room

==== Basic Workshop Clean-Up ====

* clear and clean the surfaces
* do what you think should be done to make the room inviting

==== Mopping Central Rooms + Main Bathroom ====

* wait for the vacuuming to be finished
* then get a mop and bucket from the [[rooms/intermediate.md|Intermediate Storage Room]]
* mop the Main Kitchen, the Snack Kitchen, the Dining Room, the Elephant Room, the Main Bathroom
* mop where you think it should be mopped

==== Deep Clean Room of Choice ====

* name one room and give it all your love
* this includes moving furniture to clean below, dusting book shelves or anything that’s seldomly done

==== Sort and Return Glass and Pfand ====

* go to the big room in K20-B
* seperate Pfand that yields money when returned to a supermarket and glass waste
* bring Pfand to a supermarket
* bring glass to a glass container
* don’t hesitate to ask for directions!

==== Clean Sidewalks K18, K20, K22 ====

* remove dog poop, glass shards, cigarette butts and other trash from sidewalk and window sills
* if necessary remove weeds

Positions and evaluations

2024-10-15T10:55:56Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :+1: Positions and Evaluations =

This document is meant to give an overview about the structure of social hierarchy at Kanthaus.

== Positions ==

There are 3 positions at Kanthaus, in ascending level of responsibility ''and'' power they are: Visitor, Volunteer and Member. These Positions reflect and regulate the actual responsibility and power people hold. People move between Positions based on '''evaluation.'''

===

== Evaluation ==

Everyone at Kanthaus gets evaluated—it’s normal! Evaluation is a formal opportunity for you and the rest of the Kanthaus community to honestly inspect how that relationship is going and which Position suits you at this time: the whole thing lasts for ~1,5 hours. This document is a more human-readable version of the formal agreements located in the [https://kanthaus.online/governance/constitution Constitution].

=== 1. Meeting with Kanthaus Volunteers and Members (~75 minutes) ===

When it is time for your evaluation, a meeting will be arranged with you in which you and existing Kanthaus Members and Volunteers are invited. This will probably be done during a Coordination Meeting. No official notes will be taken, although you are welcome to take notes if you want, and an informal summary will be shared with the other Volunteers and Members afterwards. The only question that needs to be answered is whether you want to apply to continue at your current Position (e.g. Visitor) or progress to the next Position (e.g. Volunteer); aside from that the discussion is open and you are warmly invited to ask anything you want an answer to. Questions to consider include—

* What project-work are you doing for Kanthaus, Wurzen or elsewhere?
* Where do you see your role in Kanthaus?
* What do you see as your strengths/allowable weaknesses?
* What have you enjoyed/disliked about your time so far?
* How do you prefer to receive critical feedback?
* Do you have any outstanding conflicts with people involved at Kanthaus?
* Do you have allergies, dietary requirements or medical conditions you want to tell us about?
* What are your plans for the future?

=== 2. Kanthaus Members and Volunteers meet privately (~15 minutes) ===

After meeting with you, the Kanthaus Members and Volunteers will meet without you to decide which Position they find appropriate for you at this time. This meeting has three stages—

'''2.1. ‘Mock’ vote''' Before any discussion takes place, the question will be asked, ''“Do you support, accept or oppose (your name) becoming/remaining as a (Position you apllied for) at this point in time?”'' The participants will vote anonymously and see the predictive result.

'''2.2. Discussion''' The participants will talk personally about the result and any personal opinions they have. There is no particular format.

'''2.3. Vote''' Again the question will be asked, ''“Do you support, accept or oppose (your name) becoming/remaining as a (Position you applied for) at this point in time?”'' and again the participants will vote anonymously. A successful outcome occurs when there are 3 or more times as many ‘support’ votes to ‘oppose’ votes (e.g. 4 ‘support’, 2 ‘accept’ and 1 ‘oppose’.) If unsuccessful, the procedure will be repeated at the lower position, for example: if you requested to become Volunteer and it was unsuccessful, the process would be repeated as if you’d applied to remain as a Visitor. Only the result of the vote, not the individual votes, are recorded.

=== 3. Position outcome and feedback (~5 minutes) ===

You will receive feedback immediately regarding which Position you are offered and further feedback if you weren’t offered the Position you applied for.

-----

''The following flowchart visualizes the positions at Kanthaus as defined in the [https://kanthaus.online/governance/collectiveagreements/ Collective Agreements] (Visitors) and the [https://kanthaus.online/governance/constitution Constitution] (Volunteers and Members.)''

PlaMe

2024-10-15T10:55:55Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :clipboard: Planning Meeting =

<img src="/images/underConstruction.jpg" alt="under construction yeah" style="width:150px;"/>

The monthly meeting to discuss bigger topics relevant to the house as a whole. Decisions can be made and participation of Volunteers and Members is expected if they are around.

Piano room

2024-10-15T10:55:54Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :musical_keyboard: Piano Room (or K22-1-4) =

Like the living room of Kanthaus.

=== Purposes ===

* relax
* socialize
* watch something on a projector together
* play with the kids

=== Specials ===

* musical instruments such as a piano
* well curated bookshelves

-----

=== Bookshelves ===

The books in the piano room are for everybody to read, so feel free to use them! Please make sure the order doesn’t get disrupted. If you want to have a glimpse of some of the things you can find there, have a look on [https://inventaire.io/groups/kanthaus inventaire]! (The list on there is far from being comprehensive though.)

Office

2024-10-15T10:55:53Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :fax: Main Office (or K20-1-4) =

Office space in the center of the house.

=== Purposes ===

* work on a (claimed) desk
* store some personal items at claimed desks
* store communal office items

=== Specials ===

* a big [[technical/printing.md|printer/scanner]] combination
* inbox for physical mail
* communal laptops

Nextcloud

2024-10-15T10:55:51Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :cloud: Nextcloud =

We have our own instance of Nextcloud hosted on [[server.md|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].

Network

2024-10-15T10:55:49Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :ghost: Network setup =

This page should document some bits of the network infrastructure of kanthaus. Please maintain so people with a bit of network knowledge can understand and maintain the network.

== Overview ==

[[File:/images/network-topology.svg|Network topology]] 

== TRUNK network ==

the backbone of our network, connecting all Access Points and the central firewall, carries all the different networks via VLAN:

{|
!align="right" width="17%"| VLAN-ID
!width="33%"| IP Range
!width="26%"| Name
!width="22%"| Purpose / Devices
|-
|align="right"| untagged
| 192.168.178.x
| ADMIN
| configuration tnterfaces of all AP’s & Switches
|-
|align="right"| 4
| 192.168.4.x
| PRINTER
| connection between print server (kanthaus-server) and printer
|-
|align="right"| 5
| 192.168.5.x
| IOT ''(former SMA)''
| only access to kanthaus-server and potentially whitelisted internet IP’s + isolated clients¹
|-
|align="right"| 100
| 192.168.100.x
| RESTRICTED
| normal internet access + isolated clients¹
|-
|align="right"| 101
| 192.168.101.x
| VPN
| tunneled to VPN (currently NL)
|-
|align="right"| 102
| 192.168.102.x
| UNSECURE
| normal internet access
|}

¹ client isolation does not work between LAN <-> LAN clients

== Wifi’s ==

{|
! SSID
! Network
!align="center"| Encrypt.
!align="center"| 802.11r
!align="center"| 802.11w
!align="center"| Isolation
! Comment
|-
| <code>kanthaus</code>
| RESTRICTED
|align="center"| WPA3
|align="center"| -¹
|align="center"| required
|align="center"| on
|
|-
| <code>kanthaus-insecure</code>
| INSECURE
|align="center"| WPA2
|align="center"| -
|align="center"| -
|align="center"| -
| unsupported drivers, LAN parties, etc.
|-
| <code>kanthaus-gast</code>
| VPN
|align="center"| -
|align="center"| -
|align="center"| -
|align="center"| on
|
|-
| <code>kh-admin</code>
| ADMIN
|align="center"| WPA3
|align="center"| -
|align="center"| required
|align="center"| -
|
|-
| <code>kh-iot</code>
| IOT
|align="center"| WPA2
|align="center"| -
|align="center"| -
|align="center"| on
|
|}

'''802.11r:''' Fast Roaming '''802.11w''': Management Frame Protection

¹ would be cool to have it on, but eventually led to issues. let’s reevaluate in a few months

== Device list ==

{|
!width="15%"| Type
!width="18%"| Name
!width="19%"| Admin-IP
!width="18%"| Location
!width="20%"| Hardware
!width="8%"| Comments
|-
| Router
| <code>fritz.box</code>
| 192.168.200.1
| K20-1 hallway
| FritzBox 7530
| DSL termination (on main network), telephone
|-
| Router
| <code>firewall</code>
| 192.168.178.1
| K20-B rack
|
| central router / firewall
|-
| AP
| <code>dragon-k20-0</code>
| 192.168.178.207
| K20-0 hallway
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k20-1</code>
| 192.168.178.201
| K20-1 hallway
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k20-3</code>
| 192.168.178.208
| K20-3 center
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k20-B</code>
| 192.168.178.206
| K20-B water room
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k22-0</code>
| 192.168.178.204
| K22-0 side hallway
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k22-1</code>
| 192.168.178.202
| K22-1-4 piano room
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k22-2</code>
| 192.168.178.203
| K22-2 hallway
| Archer C5 v1.2
|
|-
| AP
| <code>dragon-k20-outside</code>
| 192.168.178.205
| K20-0-2 window
| Archer C5 v1.2
| provides uplink for flat
|-
| <s>DECT base</s>
| <s><code>dect-k20-1</code></s>
| <s>192.168.178.3</s>
| <s>K20-1 hallway</s>
| <s>fritz!box 7330</s>
| <s>currently only used by one ohone for testing</s>
|-
| Managed Switch
| k20 firewall switch
| 192.168.178.9
| K20-B rack
| TL-SG108E
|
|-
| Managed Switch
| k22 trunk switch
| 192.168.178.10
| K22-B stairs
| GS108E v3
|
|-
| Switch
| k20 trunk switch
| -
| K20-B Rack
|
| provides PoE for some AP’s in K20
|-
| Server
| <code>kanthaus-server</code>
| 192.168.*.2
| K20-0 hallway
| Server, i5-2500K, 16GB Ram
| file storage, nextcloud, foodsharing gitlab CI Server, housebus logging & time/sunset provider (see [https://git.kanthaus.online/kanthaus/kanthaus-server-services/ Repo])
|-
| Main water meter reader
| <code>mainwatermeter</code>
| 192.168.5.37
| K20 basement (former heating room)
| ESP32-CAM
| see [[./water.html|Water usage tracking]]
|-
| Warm water meter reader
| <code>warmwatermeter</code>
| 192.168.5.38
| K20 basement (rainwater room)
| ESP32-CAM
| see [[./water.html|Water usage tracking]]
|-
| Ventilation watcher
| <code>ventilation</code>
| 192.168.5.39
| K20 attic
| ESP32-WROOM
| see [https://git.kanthaus.online/kanthaus/ventilation-watcher docs]
|-
| K20 door
| <code>k20-door</code>
| 192.168.5.40
| K20 hallway
| ESP32-CAM
| see [https://git.kanthaus.online/kanthaus/door-esp32 docs]
|}

== Firewall / Router ==

central point of all subnets, routes between them - runs OPNSense - due to lack of ports on firewall, a VLAN switch added, bound to the firewall, also connecting to the fritz!box - Features: * VPN client * DNS Server * DHCP Server

== Access Points ==

* see Device list
* so far all Archer C5 v1.2
* centrally configured by OpenWISP: https://openwisp.im.kanthaus.online (only reachable inside the <code>ADMIN</code> net)
* starting point for other ethernet cables on that floor
* in K20 all powered by PoE (802.3af) from the switch in the basement

== Printer (Canon C2025i) ==

* Printer is in its own subnet together with the kanthaus-server
* On the kanthaus-server, there is ''CUPS'' running with printer sharing and auto discovery in the networks via avahi-daemon
* In <code>RESTRICTED</code> and <code>UNSECURE</code> the printer is also reachable directly via 192.168.4.153:9100

== kanthaus-server ==

* Most of the services are running inside a docker-compose setup
** Repo: https://git.kanthaus.online/kanthaus/kanthaus-server-services
** in <code>/opt/kh-services</code>
** checking state: <code>docker-compose ps</code>
** starting everything: <code>docker-compose up -d</code>
** logs: <code>docker-compose logs -f --tail=20</code>
* BTRFS raid for HDD’s under <code>/data</code>

== Random notes ==

=== Building customized OpenWRT for Archer C5 ===

<source lang="sh">ssh kanthaus-server
sudo -iu openwrt-builder
cd openwrt
make
ls -l bin/targets/ath79/generic/</source>
===== included changes =====

* root password
* default IP <code>192.168.178.200</code> in ADMIN range
* switch: all ports in ADMIN net
* disabled DNS rebind protection
* wireless interface names
* additional packages
** openwisp-config
** prometheus-node-exporter-lu
** luci-ssl (for https)
** ebtables (for [https://blog.matthias-larisch.de/openwrt_client_isolation/ effective client isolation])
** tcpdump (for easier debugging)

=== Upgrading customized OpenWRT ===

Documentation: https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem

<source lang="sh">ssh kanthaus-server
sudo -iu openwrt-builder
cd openwrt
git pull
git checkout v23.05.2</source>
Edit <code>feeds.conf</code> to change the branch for each feed to the new version, e.g. <code>...;openwrt-23.05</code>

<source lang="sh">./scripts/feeds update -a
./scripts/feeds install -a
make -j4 defconfig download clean world
ls -l bin/targets/ath79/generic/</source>
Errors during <code>make world</code> are to be expected, usually the set of default packages changed and dependency conflicts are happening. Investigate generated the <code>.config</code> file and compare with the official ones at https://downloads.openwrt.org/releases/23.05.2/targets/ath79/generic/config.buildinfo

=== How to update OPNsense ===

There is a short downtime involved during the two reboots, usually 2 minutes each.

# Join the <code>kanthaus-admin</code> wifi network and log in to 192.168.178.1 (user <code>root</code>, password in keepass). Export the configuration to make a backup.
# Check if updates are available (System->Firmware->Updates)
# In case of minor updates, just use the button to perform
# If there is a major update (2x per year), download the newest version from https://opnsense.org/download/, unzip and flash to any USB stick
# Take a VGA monitor, a USB keyboard and the USB stick to the K20 basement big room, open the rack box and connect the devices to the small computer (HP)
# Log in with the USB keyboard (same credentials as above) and trigger a reboot. It should now boot from the USB stick.
# Press any key when it prompts to run the “Importer”. Now it will boot up a live environment and read the configuration file. If successful, network services should run as before.
# If all looks good, it’s time to install to disk. Run <code>opnsense-installer</code> from the shell (either on local keyboard or via ssh), choose ZFS and let the installer do its job.
# Remove the USB stick and reboot again.
# Check if the system came up good.
# Perform any last updates from the web UI.
# Delete the configuration backup again, it can contain secrets.

=== Pitfalls ===

* We use 802.1q VLAN tagging. All switches everywhere need to have at least passive passthrough support, otherwise the Vlans disappear at that switch. I don’t know of any gigabit switch that does not support this.
* Again Vlan: Managed switches normally need to have all VLANs that should be forwarded (also tagged -> tagged forward) defined in them.
* Again Vlan: Some Access Points like WDR841 v7/v8 cannot handle tagged and untagged vlan on the same port at the same time. So far, we don’t have any equipment like that and likely we will never have, but just to know…
* Again Vlan: fritz boxes have their switch in managed vlan mode and don’t forward any tagged vlan

Meeting culture

2024-10-15T10:55:47Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :busts_in_silhouette: General meeting culture =

<img src="/images/underConstruction.jpg" alt="under construction yeah" style="width:150px;"/>

Kanthaus wants to be efficient and respectful of people’s time. We acknowledge the fact that in-person meetings are not the best format for all kinds of work and try to be accessible also to people who are physically distant.

== Meeting frames ==

* We specify clear start and end times.
* We start on time and don’t wait for late people.
* We watch the time and don’t drag out the meeting.
* We have a facilitator who guides through the meeting.

== Hand signals ==

To make it possible to give silent feedback we use [https://www.collaborationsuperpowers.com/wp-content/uploads/2020/04/Handout-Hand-signals-for-remote-meeting-facilitation.pdf hand signals].

[[File:../images/handSignals.jpg|hand signals]] ''More can be seen in the linked pdf.''

Their use is to ‘comment’ without disrupting the speaker, to facilitate the order of vocal contributions as well as pointing out technical or language points.

Additionally to the list above we sometimes use the so-called ‘temperature check’ to get an understanding of the feeling of the group towards a certain issue. To achieve that one person asks the group for said temperature check and then everybody wiggles their hands either downward (cold, no support, maybe even resistance), upward (hot, big support, enthusiasm) or somewhere in the middle.

== Pads ==

Our main meetings (like [[come.md|CoMe]] or [[plame.md|PlaMe]]) usually are backed up by corresponding online pads which contain the procedure and topics visible and editable for everyone. This means that people often bring laptops or phones to follow what’s going on. Facilitators in turn usually don’t readout everything or explain the format in the beginning, since it’s technically available already.

Main bathroom

2024-10-15T10:55:46Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :bathtub: Main Bathroom (or K20-2-1) =

The place to clean yourself.

=== Purposes ===

* shower or take a bath
* use the sink
* pee in the toilet
* store communal bathroom items
* store private bathroom items
* collect communal laundry

=== Specials ===

* low light with motion sensor, bright light with button
* electric heater to be used while in the shower

-----

=== Door ===

Using the door of this room is quite loud, which is especially disturbing when people are already sleeping in the rooms around. If you want to close it for having privacy in the room, please try to do so silently (e.g. slow or by pushing the door slightly orthogonally to the moving direction).

=== Preventing wet floors ===

When you shower, make sure that the shower curtain is hanging inside the shower, so the water does not run on the floor.

Also, please either dry yourself inside the shower or use the towel laying on the chair or radiator (or even a new one if there is none) to put on the floor in front of the shower.

[[File:/images/bathroom-wet-floor.jpg|Don’t: Wet floor because somebody did not dry inside the shower AND did not use a foot towel]] ''Example of a wet floor. Walking on this with slightly dirty shoes/feet/socks will spread a lot of dirt everywhere!''

=== Heating ===

This room is not verywell heatable, but we need to heat it in winter for mold prevention. To feel more warmth while in the shower, you can switch on the electric heater by pulling the string. It is basically a toaster that will radiate heat onto your skin. It consumes a lot of energy when left on, so please make sure to switch it off when you leave!

During the heating period it’s also very important to keep the door shut.

Laundry

2024-10-15T10:55:44Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :dress: Laundry =

Everything concerning laundry - be it dirty or clean.

=== Communal clothing ===

Since everything in Kanthaus is communal by default, this is the main section.

==== Dirty laundry sorting ====

Dirty laundry can be put into the laundry containers in the [[rooms/mainbathroom.md|Main Bathroom]] (K20-2-1b). When those are full they go to the fitting sections in the [[rooms/washingroom.md|Washing Room]] K20-0-1b.

The categories are as follows: - 40°C: Standard laundry (e.g. most clothes) - 60°C: Hygiene laundry (e.g. underwear, socks, tissues, bedsheets, towels) - 90°C: Kill-everything laundry (e.g. kitchen towels, butt towels)

==== Wet laundry ====

Spaces to dry laundry are: - the outside clothes lines - the [[rooms/2ndbathroom.md|2nd Bathroom]] in K22-2-2 - if need be more mobile drying racks can be put up in ventilated rooms

==== Dry laundry ====

Clothes baskets can be found in the [[rooms/washingroom.md|Washing Room]]. Often they are also left right beside the drying rack and can be used to take down the laundry when dry. Dry communal laundry goes into the [[rooms/communalcloset.md|Communal Closet]]. Just leave the basket on the floor, sorting it in can be done during [[social/powerhour.md|Power Hour]].

=== Private clothing ===

If you stay only for a short time or have clothes which you don’t want to share, you should not put them in the laundry baskets - chances are high that you won’t find you stuff again in a reasonable amount of time. Simply run a machine yourself; it should be adequatly labeled to make it doable. Please make sure that you have enough things to wash, so that the machine is full, or add some Kanthaus pieces.

When drying your private clothing make sure you somehow label them as yours. Otherwise they might end up in the [[rooms/communalcloset.md|Communal Closet]] after all.

Lantern

2024-10-15T10:55:43Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :izakaya_lantern: Lantern (or K22-1-3) =

The room in which you can read a book at night without turning the light on.

=== Purposes ===

* retreat to a [[practicalities/roomreservation.md|private]] room

=== Specials ===

* one of the prettier rooms in Kanthaus, fully redone in 2023

Kitchen

2024-10-15T10:55:42Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :stew: Main Kitchen (or K20-1-2) =

The room for preparing and serving (communal) meals.

=== Purposes ===

* cook and bake
* store kitchenware, dishes and cutlery
* [[practicalities/dishwashing.md|do dishes]]
* serve food

=== Specials ===

* the most central room of the house in both function and location
* a solar power monitor with forecast

Kanthaus.online

2024-10-15T10:55:41Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= kanthaus.online =

<img src="/images/underConstruction.jpg" alt="under construction yeah" style="width:150px;"/>

The website of Kanthaus.

== Contents and scope ==

[https://kanthaus.online kanthaus.online] is a place to present our projects and Kanthaus itself. It’s where people can find our [[social/documents.md|core documents]], the list of current Volunteers and Members, our [https://kanthaus.online/governance/minutes meeting minutes], the list of people’s projects on the landing page and more.

=== Website vs. handbook ===

The target audience is similar to this handbook: - people who are just interested in Kanthaus - people who want to visit Kanthaus

But in contrast to the handbook, which is about providing detailed guides and instructions, the website is much more about presenting and inviting.

K20 attic

2024-10-15T10:55:39Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :package: K20 Attic (or K20-3) =

The biggest ‘room’ in Kanthaus.

=== Purposes ===

* store things

=== Specials ===

* swing chair

Intermediate storage

2024-10-15T10:55:38Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :gift: Intermediate Storage Room (or K20-1-5) =

Home of the vortex.

=== Purposes ===

* process communal stuff in the [[social/stuffprocesses.md|vortex]]
* sleep in a [[practicalities/roomreservation.md|semi-private]] room
* store communal stuff like cleaning utensils, clean food buckets and bed linen

=== Specials ===

* probably most purposes in one room

Housebus

2024-10-15T10:55:37Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :zap: House Bus System =

<blockquote>===== Outdated =====

* most of the house bus network got changed / new cables added
</blockquote>
The house bus system is a project initiated by Matthias with the idea to collect data, access sensors and use actors in the house. This ranges from measuring the temperature over managing the grey water system up to operating the door bell.

See the [https://github.com/NerdyProjects/HouseBusNode Hardware/Firmware Github repository] and the [https://github.com/yunity/uavcan-influxdb-writer Logging helper Github repository] for further details.

=== Topology ===

The house bus is operated via a 4-wire connection that is passed from one node to another. It is physically a [https://en.wikipedia.org/wiki/CAN_bus CAN Bus] using 12..20 V supply voltage and the [https://en.wikipedia.org/wiki/UAVCAN UAVCAN protocol]. It is operated at 125 kBps and should work with a total bus length of ~200m where deviations from the ideal linear bus are allowed up to 30 m stubs.

==== CAN Termination ====

The CAN bus needs to be terminated at both ends. Currently, the termination resistors are in K20-2# (Greywatertank) as well as K20-B-2 (Rainwater tanks).

=== Physical access ===

Bus access is possible everywhere where the cable is. There should be a list of nodes where each physical split point / access point should be a top level list point and has all connections to other nodes as sublists. A sublist entry should mention all rooms the cable passes through.

* Node K20-2#
** to K20-1 hallway via K20-1# and K20-1-1
* K20-1 hallway
** to K20-2# (via see above)
** to K20-0 hallway
* K20-0 hallway
** to K20-1 hallway
** to K20-0-2
** to K20-B-4 (electricity main box room) via K20-B-3
* K20-0-2
** to K20-0 hallway
* K20-B-4
** to K20-B-2 (rainwatertanks)
** to K20-B-6 (heating room)
* K20-B-2
** to K20-B-4
* K20-B-6
** to K20-B-4

History

2024-10-15T10:55:36Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= History of Kanthaus =

<img src="/images/underConstruction.jpg" alt="under construction yeah" style="width:150px;"/>

How did Kanthaus start? What contexts did it emerge from and who were the people involved? Which ideas were important and how did they develop over time? This article tries to answer questions like these.

(tbc)

Hipster room

2024-10-15T10:55:35Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :sunglasses: Hipster Room (or K22-2-5) =

The room with the fancy wooden floor.

=== Purposes ===

* retreat to a [[practicalities/roomreservation.md|private]] room

=== Specials ===

* the bed is on window height

Heating

2024-10-15T10:55:33Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :volcano: Heating system =

Since beginning of Winter 2021, Kanthaus is powered by an air heat pump heating system, which means we heat fossil free only using electricity.

The outdoor unit is located in the garden outside of K20-0-1. Using a special liquid called refrigerant, it heats up water to send through our radiators, or domestic hot water (also called ‘DHW’) for showering and sinks.

The heat pump control panel is installed on the wall next to the Main Kitchen door in the hallway of K20-1.

== :exclamation: General info for users ==

Heat pumps work fundamentally different from gas heaters. (Here’s an [https://home.howstuffworks.com/home-improvement/heating-and-cooling/heat-pump.htm article about how they work in general].) While gas heaters usually send really hot water through the radiators, the heat pump heating system’s water temperature needs to be as low as possible. That means:

* You can not heat up a room quickly - expect a room to become pleasantly warm only 1-2 days after turning on the radiator
* Much of the temperature control is set centrally. Thus, turning the knobs on the radiators doesn’t do much more than switching on or off.
* The maximum reachable temperature is usually around 19.5 °C in Kanthaus. It slightly changes depending on the outdoor temperature though.
* It’s good for the system to run continuously rather than to be frequently switched on and off. Hence it is normal and wanted that the heatpump outside is working all the time.
* It needs a minimum water flow through the radiators to work at all. This means at least 6 radiators need to be turned on all the time.
* It can be very expensive if it doesn’t run efficient, so there is a lot of focus on keeping the efficiency of the system high.

=== :page_with_curl: Default settings ===

''as of 2024-01-10''

* heating water target temperature: between 30 and 40 °C
** consequence: the radiators can never be hotter than this
** more advanced mechanics regulate the exact heating water temperature automatically (see details below in ‘Advanced information’)
* between 7 am and 8 pm day mode is activated, then we heat to:
** 18.7 °C if the outside temperature is at or below -6 °C
** 20 °C if the outside temperature is at or above 10 °C
* between 8 pm and 7 am night mode is activated, then we heat to:
** 18.5 °C
* the target temperatures are evaluated using the Piano Room and the Main Office
** the mean temperature of both rooms combined over the last 5 minutes is the figure used
** conesquence: if (one of) those rooms get colder, the whole house will be heated more and the other way around

=== :house: Room heatability ===

We purposefully do not heat all rooms in Kanthaus.

The rooms which are warm by default in Winter are: - Snack Kitchen - Main Office - Main Kitchen - Dining Room - Elephant Room - Piano Room - Bathroom

Additionally, when there are enough people to justify it, we usually also heat: - Fansipan - Silent Office

If someone is in need of a warm private room, the best choice for that is definitely: - The Lantern

Also K-20-3 is very well heatable, but uses a completely decoupled heating solution.

-----

To keep the efficiency of the system high, we actively decided that badly heatable rooms stay cold(er). A room is badly heatable if: - the radiator is too small for the specific room - it is surrounded by cold walls (including floor and ceiling)

Here’s an incomplete list of those rooms: * The Private (6 cold walls) * Hipster Room (6 cold walls) * Sleep Kitchen (6 cold walls) * Ex Food Storage (6 cold walls) * Freeshop Lounge (6 cold walls) * Cloud Room (4 cold walls) * Dragon Room (5 cold walls)

To determine yourself if a room is well or badly heatable, please refer to the [https://kanthaus.gitlab.io/expfloorer/ expfloorer] and analyze the room’s location in the house. Keep in mind that K18 is completely cold, while WR9 is mostly heated.

=== :bath: Domestic hot water (aka DHW) ===

The heat pump is also responsible for domestic hot water (‘DHW’) being available in the Main Bathroom, the Main Kitchen and the Snack Kitchen. We have a DHW tank in K20-B water room for that purpose. When full and freshly heated, it holds 200 liters of 52°C water.

[[File:/images/heating-dhw-tank.jpg]] ''The heat is transferred without the two liquids touching.''

<div style="color:red;">

Heating up DHW and water for radiators is not possible at the same time!

</div>
Usually the heat pump switches to water mode once a day at some point when it’s sunny. If the hot water tank is empty, however, it immediately starts heating it up again.

The process of heating up DHW takes 30 to 90 minutes depending on how warm the water in the tank was to begin with.

==== Details of DHW heating ====

To heat the DHW, the heating water which otherwise would go through the radiators is redirected and its’ target temperature adapted. A DHW tank is specifically designed to have passages for heating water than can give off heat to the DHW without touching it.

When DHW is used, cold water flows into the tank from below. The hot water on top can still be used, because different temperature layers form in the tank. The thermometer to check the DHW’s temperature is on the upper side of the tank so that the reheating doesn’t start too early. When the temperature of the DHW falls below 39 °C on the top, then the heat pump will switch to water mode automatically and start heating the tank to the target temperature of 52 °C again.

The start of the heating process will mix the layers of different temperature water and first make it colder overall. Meaning: If you’re taking a shower and the hot water seems to not be so hot anymore, you better finish quickly.

==== Legionella ====

A known problem in domestic water systems are [https://en.wikipedia.org/wiki/Legionella legionella] bacteria which cause lung diseases. They only die above 60 - 70 °C, but there are other ways to get rid of them. To avoid chlorine, we went for physical removal, which means to create enough throughput of water to basically wash them away. When they don’t have the time to settle down and form bigger populations they’re nothing to worry about.

=== :question: Troubleshooting ===

==== A radiator is not getting warm, although the heating system should be running? ====

* Is it warm outside? Maybe the heating system turned off temporarily during nighttime?
* Try another radiator in another room, preferably on the other side of the house or in the other house
** If successful, a part of the heating system might be turned off at the valves in K20-B-old-heating-room or K22-b-event-storage. Find people who might be working on the heating system before turning it back on.

If both are not successful, go to the heating system control panel in K20-1 hallway.

* It does not show anything?
** Locate the heating systems fuse in the main electricity fuse box in the electricity room in the basement
** When you open the right panel of the heat pump outside (losen 4 screws, push it down, yes, push it down harder!) there are also 2 fuses at the top.
* It shows an error?
** H62: Too many radiators are turned off so the heat pump could not satisfy its minimum water flow. Turn on some more radiators and make sure that nobody can turn them off (e.g. by removing the thermostat to have it fully on)
** H70: Check the fuse “heater” in the main electricity box on the bottom right
** H74: Maybe the house bus node controlling the heating system had a problem? Press the “On” button and watch it for 5 minutes, if it reappears, disable “Optional PCB connectivity” in the installer menu to make it completely autonomous again.

==== I really want to heat a badly heatable/cold room/ I need to heat a room quickly. ====

* Use an electric space heater (“Heizlüfter”).
* Isn’t this very expensive?
** Yes (60 cents per hour), but adjusting the heating system so this is possible without the electric heater is more expensive all the time and this scenario should not occur often.

==== I would like to permanently use a badly heatable room. What do I need to do? ====

* Install fans underneath the raiator for better heat distribution
* Install a bigger radiator
* If this need is really there for many rooms, we might want to increase the whole heating systems temperatures, this increases the heating cost about 2.5 percent per degree (+ the increased heating cost for the rooms getting warmer of 6% per degree of room temperature)
* Generally it would be preferable to rather find a better heatable room instead.

==== The heat pump is annoyingly loud, can we do something? ====

* Depends. Is it a certain time or mode of operation? We can always have it operate on lower power for some hours, where it will then be more silent. Communicate your wish :-)

== :construction_worker: Advanced information ==

Our heat pump is a '''Panasonic Aquarea T-Cap 12 kW WH-MXC12H9E8'''. - [[assets/aquarea-service-manual.pdf|Service Manual]] - [[assets/aquarea-installation-manual.pdf|Planungs- und Installationsanleitung]]

=== :wrench: Required maintenance ===

In K20-B water room, there are two filters that should be cleaned regularly (e.g. at least once per heating season):

* Spirotap MB3 (The “big” thing in the return line on the bottom)
** Turn off the heat pump, so the pump is not running
** Pull down black magnetic cap
** Get a bucket, put it underneath the exhaust in the bottom
** Use the cap to turn the knob
** Leave it open for a second, it will immediately get rinsed
** '''Careful:''' water comes out with high pressure! Don’t let the cap slide off the knob!
** Put black magnetic cap back on, turn heat pump back on
* Superfilter (The ball valve with the black handle on the bottem)
** Turn black handle until it reaches closing position
** Unscrew cap and get the filter out
** It’s quite hidden inside, find it by feeling with your finger
** Take it out and rinse it, use a (tooth)brush to get it really clean
** Put it back in - no need to let it dry
** Close cap again and open black handle

The outside unit in the garden also has a filter, but it seems to be fine without maintenance after 2 winters.

=== :eyes: Additional layers of control ===

Because of some shortcomings in the controller of the heat pump itself, it is additionally monitored and controlled by a [https://github.com/NerdyProjects/HousebusNode_Heatpump House Bus node], a [https://github.com/Egyras/HeishaMon Heishamon] and a selfmade [https://git.kanthaus.online/kanthaus/heating_control heating controller script].

There is some unwanted redundancy, complexity and inflexibility in this setup that might be addressed at some point in the future, but for now it’s functional as it is.

If you want access to these additional layers because you are technically adept and interested in helping out with managing and improving the system, talk to Tilmann. He will be happy about it. :blush:

==== House Bus integration ====

The [[technical/housebus.md|House Bus]] node is a piece of hardware and software. The physical part is installed in K20-B water room and the digital part, which is running on it, is recorded in [https://github.com/NerdyProjects/HousebusNode_Heatpump Matthias’ github].

Its’ purpose is to allow reading all status from the heat pump, the heat meter and the electric counter, and to then write the data in InfluxDB. From there we can import it into (Grafana)[https://grafana.yunity.org/]. and use it to e.g. debug and understand the heat pump’s behaviour better.

The info made visible by the House Bus node is: - heating water temperature - power usage - heat generation - water flow - DHW mode or heating mode - outside temperature - compressor power consumption - many small details which not even Tilmann uses or understands

The House Bus node is a new generation coming from our other nodes as it uses upgraded uavcan v1 and an arduino base stack.

==== Heishamon interface ====

[https://github.com/Egyras/HeishaMon Heishamon] is a small piece of open-source software and hardware to monitor and control the heatpump. It is located in the K20-B water room and is connected to WiFi.

It also emulates the <code>Optional PCB</code> thus is able to set the SG ready signals and demand control.

Heishamon is used to adjust the water target temperatures, with the aim to keep room temperatures consistent and use more of our own solar power.

This probably is something the House Bus node is capable of, too, but at the time it seemed easier to set up a new system than to modify the existing one.

==== Script ====

A heating controller script called <code>heating-control.py</code> is running on the Kanthaus server. It is additionally stored in the git repo [https://git.kanthaus.online/kanthaus/heating_control heating_control], although the version in there might not be fully up-to-date.

It maintains comfortable temperatures in the house while minimizing energy usage. It does this by reading room temperature sensor data provided by the [[technical/housebus.md|House Bus system]] from InfluxDB and adjusting the heating water target temperature via Heishamon. Also, it can switch the heating on or off based on temperature thresholds.

Additionally, the program determines the amount of available solar power and makes use of it by raising temperatures to store heat in the house.

The program also triggers DHW re-heating if conditions are good, for example if the house is warm enough and there’s solar power available.

Grafana

2024-10-15T10:55:31Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :bar_chart: Grafana server =

We use a [https://grafana.com/ Grafana] instance to monitor various things in the house, which can be accessed at https://grafana.yunity.org/.

== Getting access ==

The Grafana board can be viewed by anyone. To modify it you need a [[nextcloud.md|Nextcloud]] account and need to be part of the Kanthaus group.

== Logging new quantities in Grafana ==

To track new metrics in Grafana you will need to store them in the underlying InfluxDB database, hosted at https://influxdb.kanthaus.online/. If you are writing from an IOT device running inside Kanthaus, running from the <code>192.168.5.*</code> subnet, then you cannot directly reach the internet: instead, you can point your device to <code>http://kanthaus-server:88/influxdb</code> which will proxy your requests to the outside.

You will need to supply credentials to be able to access InfluxDB: you can find those in our central password store. The InfluxDB database to use is <code>kanthaus</code>.

You can use [https://docs.influxdata.com/influxdb/v2.2/write-data/developer-tools/api/ InfluxDB’s API] to regularly write new values to the database. For instance, with <code>curl</code> this could look like this:

<pre>curl --request POST \
"http://kanthaus-server:88/influxdb/api/v2/write?bucket=kanthaus/" \
--header "Authorization: Basic YOUR_API_CREDENTIALS" \
--header "Content-Type: text/plain; charset=utf-8" \
--data-binary '
airSensors,sensor_id=TLM0201 temperature=73.97038159354763,humidity=35.23103248356096,co=0.48445310567793615 1630424257000000000
airSensors,sensor_id=TLM0202 temperature=75.30007505999716,humidity=35.651929918691714,co=0.5141876544505826 1630424257000000000
'</pre>
See [https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/ InfluxDB’s documentation about the line protocol] for details about the format of the data to post.

Once your quantity is logged in InfluxDB, you can create a new panel for it in Grafana. This can be done from Grafana’s web interface directly.

Glossary

2024-10-15T10:55:29Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :page_facing_up: Glossary =

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 CTRL+f (which lets you search for terms on the whole page through your browser).

=== CoMe ===

The weekly [[social/come.md|Coordination Meeting]]

=== PlaMe ===

The monthly [[social/plame.md|Planning Meeting]]

=== Power Hour ===

The weekly common cleaning. More info on [[social/powerhour.md|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 [[social/meetingculture.md|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.md|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 [[social/positionsandevaluations.md|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 [[social/positionsandevaluations.md|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 [[social/come.md|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 Slack 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 [[social/stuffprocesses.md|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 [[practicalities/travel.md|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 ===

A [https://kolalleipzig.de huge Solawi] in Sehlis, from which we sometimes save food.

-----

'''to be added''' - doocracy https://www.noisebridge.net/wiki/Do-ocracy - dragon dreaming - scrum - jitsi - bigbluebutton - nextcloud - nuudel - 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 - FLINTA* - 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 -

Git

2024-10-15T10:55:28Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :clipboard: Git =

We use Git to store mutable data. Our Git repositories are hosted with [https://forgejo.org Forgejo] on [[server.md|our own server]]. For immutable files we have a [[nextcloud.md|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 [[residencerecord.md|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>

Freeshop storage

2024-10-15T10:55:27Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :package: Free Shop Storage (or K22-0-2) =

The place to keep all the donations.

=== Purposes ===

* store free shop stuff in an orderly way

=== Specials ===

* if nobody takes care, it happens fast that the room overflows

Freeshop lounge

2024-10-15T10:55:25Z

HandbookMigration2024: "migration of handbook pages from https://git.kanthaus.online/kanthaus/handbook"

= :coffee: Free Shop Lounge (or K22-0-1) =

The 2nd room of the Free Shop.

=== Purposes ===

* sort free shop stuff
* host free shop customers and engage them further

=== Specials ===

* in the process of being changed (February 2024)