Kanthaus wiki - User contributions [en]

Hosting

2026-02-19T10:37:25Z

Janina:

Visitors and groups require a Volunteer or Member to host them during their stay. Hosting is important work, with the host acting as the main connector between the visitor/group and the community. This page collects minimal recommendations for a good experience, but don't forget it is a personal experience 😊

== Hosting individual Visitors ==

=== Before arrival ===

* 📜 [https://kanthaus.online/about/visiting Visiting page] (phancy physalis!)
* establish intentions for visit
* agree on time of arrival (and maybe departure) — host should be present for at least first 2 days — then:
** put in [[Calendar|digital calendar]] (<code>people</code>),
** write on visitor board, and
** announce in [[Mattermost]] <code>~in-house</code> and/or at CoMe
* reserve sleeping spot for the first two nights, preferably private

=== Upon arrival ===

* be there to open the door and welcome 😊
* basic needs: water, food, toilets, etc
* establish preferred name, pronouns
* help them store their things (shoes, jacket, bag)
* show them sleeping place
* give [[Wifi]] password
* establish food requirements and preferences
* be generally available

=== First full day ===

* house tour (ca. 1-2h)
* show physical calendar, to-do board, [https://pad.kanthaus.online/visitorTaskList Visitor task list]
* most useful initial contribution: observing and asking questions
* everything communal unless labeled
* talk about culture around criticism
* get set up:
** door access
** plate shelf & other storage solutions
** potentially office space

=== 1st week ===

* join [[Mattermost]]
* help find an agreeable way to contribute
* empower to keep finding sleeping spots
* 📜 [https://kanthaus.online/en/governance/collectiveagreements#relevant-in-first-days Collective Agreements relevant in the first days]
* [[Visitor check-in]] after 7 days - an informal exchange about how people are feeling, with a focus on feedback in either direction. Should cover all points (above) not yet covered.

=== 2nd week ===

* 📜 [https://kanthaus.online/en/governance/collectiveagreements#relevant-after-first-days Collective agreements relevant after the first days]
* 📜 [[Meeting culture]]
* 📜 [[Additional norms]]
* Visitor check-in

=== 3rd week ===
* [[Position attributes table|📜 Position attributes table]]
* [[Positions and evaluations|📜 Positions and evaluations]]
* [https://cloud.kanthaus.online/f/921937 📜 Emergency protocols]
* Visitor check-in

=== Every subsequent week ===

* Visitor check-in (with the option to become Volunteer)

=== Before departure ===

* write in the guestbook
* check all places for personal things:
** sleeping rooms
** offices
** towel + bathroom shelf
** plate shelf
** shoe rack
** vortex
* ask for email address for potential future contact

== Hosting groups ==
(Doesn't work hosting at Kanthaus? See [[Other places for groups]])

=== Clarify the basics ===

* communicate and find out the following:
** what is it that they are doing?
** how many people are coming?
** when will they arrive (earliest) and leave (latest)?
** which room(s) will they be using for day-time activities?
** which room(s) will they be using for sleeping?
** (when) will they participate in dinner preparation?
** will they bring food or help us recover it?
* communicate to KH residents about the group coming
** make a Mattermost post in ~kanthaus and/or a CoMe point
** put it in the nextcloud calendar in the following format: <code>Group name (n ppl) [host]</code>

=== Before arrival ===

* reserve the room(s)
* keep KH residents posted about changes in group size, arrival time, room usage and/or duration of stay
* check the room(s) you offered them for usability, cleanliness and clean them if necessary

=== Upon arrival ===

* be there to open the door and welcome them :)
* show them where they can leave their stuff
* show them the room(s) they will be using
* invite them to use the rest of the house as well
* give them a key/tag and/or teach them the door code

=== During ===

* give a house tour if wanted
* regularly check in with them to make sure everything is fine
* be available for questions
* make them aware of the guest book and invite them to leave an entry

=== After ===

* check the room(s) and leave them in a usable state
* check privatizable storage areas and clear names if necessary
== Other information ==

=== Visitor task list ===
There's currently a [https://pad.kanthaus.online/visitorTaskList# pad] with potential things visitors could do while in Kanthaus. This list is meant to be comprised of tasks which can be done with little to no help from experienced residents. It’s things which are small, and accessible; not super urgent, but still useful. Some tasks have names next to them which can be read as an invitation to get in contact with residents.

=== Communal agreement ===
There was a communal agreement on hosting duties. It was removed after a constitutional change in July 2025.<blockquote>Hosts—Volunteers or Members which agree to host a Visitor—are responsible for taking care that their Visitor and the other residents have the best time possible. This responsibility includes tour-guiding, question answering, helping to avoid common problems and resolving tensions. Hosts are also responsible for organizing a check-in for the Visitor after the Visitor has spent ~7 days at Kanthaus. The check-in round is an informal chat in which the Visitor, their host and one or two Volunteers/Members see how things are going for the Visitor and other residents. Hosting Duty should be explicitly transferred if the current host leaves for more than 2 or 3 days.</blockquote>
[[Category:Social]]

Hosting

2026-02-19T10:28:09Z

Janina: rework individual visitor part

Visitors and groups require a Volunteer or Member to host them during their stay. Hosting is important work, with the host acting as the main connector between the visitor/group and the community. This page collects minimal recommendations for a good experience, but don't forget it is a personal experience 😊

== Hosting individual Visitors ==

=== Before arrival ===

* 📜 [https://kanthaus.online/about/visiting Visiting page] (phancy physalis!)
* establish intentions for visit
* agree on time of arrival (and maybe departure) — host should be present for at least first 2 days — then:
** put in [[Calendar|digital calendar]] (<code>people</code>),
** write on visitor board, and
** announce in [[Mattermost]] <code>~in-house</code> and/or at CoMe
* reserve sleeping spot for the first two nights, preferably private

=== Upon arrival ===

* be there to open the door and welcome 😊
* basic needs: water, food, toilets, etc
* establish preferred name, pronouns
* help them store their things (shoes, jacket, bag)
* show them sleeping place
* give [[Wifi]] password
* establish food requirements and preferences
* be generally available

=== First full day ===

* house tour (ca. 1-2h)
* show physical calendar, to-do board, [https://pad.kanthaus.online/visitorTaskList Visitor task list]
* most useful initial contribution: observing and asking questions
* everything communal unless labeled
* talk about culture around criticism
* get set up:
** door access
** plate shelf & other storage solutions
** potentially office space

=== 1st week ===

* join [[Mattermost]]
* help find an agreeable way to contribute
* empower to keep finding sleeping spots
* 📜 [https://kanthaus.online/en/governance/collectiveagreements#relevant-in-first-days Collective Agreements relevant in the first days]
* [[Visitor check-in]] after 7 days - an informal exchange about how people are feeling, with a focus on feedback in either direction. Should cover all points (above) not yet covered.

=== 2nd week ===

* 📜 [https://kanthaus.online/en/governance/collectiveagreements#relevant-after-first-days Collective agreements relevant after the first days]
* 📜 [[Meeting culture]]
* 📜 [[Additional norms]]
* Visitor check-in

=== 3rd week ==
* [[Position attributes table|📜 Position attributes table]]
* [[Positions and evaluations|📜 Positions and evaluations]]
* [https://cloud.kanthaus.online/f/921937 📜 Emergency protocols]
* Visitor check-in

=== Before departure ===

* write in the guestbook
* check all places for personal things:
** sleeping rooms
** offices
** towel + bathroom shelf
** plate shelf
** shoe rack
** vortex
* ask for email address for potential future contact

== Hosting groups ==
(Doesn't work hosting at Kanthaus? See [[Other places for groups]])

=== Clarify the basics ===

* communicate and find out the following:
** what is it that they are doing?
** how many people are coming?
** when will they arrive (earliest) and leave (latest)?
** which room(s) will they be using for day-time activities?
** which room(s) will they be using for sleeping?
** (when) will they participate in dinner preparation?
** will they bring food or help us recover it?
* communicate to KH residents about the group coming
** make a Mattermost post in ~kanthaus and/or a CoMe point
** put it in the nextcloud calendar in the following format: <code>Group name (n ppl) [host]</code>

=== Before arrival ===

* reserve the room(s)
* keep KH residents posted about changes in group size, arrival time, room usage and/or duration of stay
* check the room(s) you offered them for usability, cleanliness and clean them if necessary

=== Upon arrival ===

* be there to open the door and welcome them :)
* show them where they can leave their stuff
* show them the room(s) they will be using
* invite them to use the rest of the house as well
* give them a key/tag and/or teach them the door code

=== During ===

* give a house tour if wanted
* regularly check in with them to make sure everything is fine
* be available for questions
* make them aware of the guest book and invite them to leave an entry

=== After ===

* check the room(s) and leave them in a usable state
* check privatizable storage areas and clear names if necessary
== Other information ==

=== Visitor task list ===
There's currently a [https://pad.kanthaus.online/visitorTaskList# pad] with potential things visitors could do while in Kanthaus. This list is meant to be comprised of tasks which can be done with little to no help from experienced residents. It’s things which are small, and accessible; not super urgent, but still useful. Some tasks have names next to them which can be read as an invitation to get in contact with residents.

=== Communal agreement ===
There was a communal agreement on hosting duties. It was removed after a constitutional change in July 2025.<blockquote>Hosts—Volunteers or Members which agree to host a Visitor—are responsible for taking care that their Visitor and the other residents have the best time possible. This responsibility includes tour-guiding, question answering, helping to avoid common problems and resolving tensions. Hosts are also responsible for organizing a check-in for the Visitor after the Visitor has spent ~7 days at Kanthaus. The check-in round is an informal chat in which the Visitor, their host and one or two Volunteers/Members see how things are going for the Visitor and other residents. Hosting Duty should be explicitly transferred if the current host leaves for more than 2 or 3 days.</blockquote>
[[Category:Social]]

User:Janina/Effectiveness

2025-11-21T19:37:54Z

Janina: save effectiveness essay

I want to be effective and get things done. When Kanthaus started it was all about "helping people achieve their greatest potential". I'm not there at the moment. I think I could do more, be a better agent of change. I think we could be a better collective of change-makers. To arrive there, I believe we need to ask the painful questions: Are you spending your time wisely? Is your project reaching its goal? Should you re-evaluate the benefit your work has for the world?

To be able to ask these questions productively we need to all feel safe and secure as part of a community that is not judging to exclude, but evaluating to support growth. It must be clear that we live, work and criticize in solidarity. That we are in this together and want to get better collectively.

I want to have a big, common, political project that we focus all our energy on. I want to feel the connection and satisfaction it would bring. I want us to commit and to plan together. And of course not all plans would come to fruition, there will be challenges and changes on the way. I want people to feel able to become a part of this future project, even though they don't know how much physical and/or mental capacity they will have when it's due. That it's clear that they can take time off if they need to. But that they won't want to, because it's going to be such an awesome project with such amazing team dynamics, where everybody contributes as best as they can. :)

Until then I want to talk about personal projects. I want to find a good format to focus on each individual, their work, their aims for it and how these things relate. I want us to get comfortable admitting that we might not spend our time exactly as we want and to turn to the group to find ways for improvement together. And I also want us to be comfortable admitting needing time for personal issues we might have and to boldly plan that time into our schedule.

This is not about pressuring people into having more output, it's about helping people who ''want'' to have more output becoming able to. This is not about shaming people who sometimes have low capacity, it's about finding ways to wholeheartedly be okay with that. This is about love, change and growing closer. This is about clarity, commitment and focus. This is about being effective in the goals we set for ourselves.

I still want to change the world. Don't you, too?

Pressure cooker

2025-11-20T07:30:24Z

Janina: add potato details

The electric pressure cooker is a great rice cooker too!

It is stored in the [[Kitchen]], at the bottom of the shelf for personal storage of used dishes.

== Instructions ==

=== Rice ===
valid for jazmin or basmati, and between 1 and 1,5kg.

- wash the rice thoroughly, and drain it with mesh colander.
- Add rice and water.

Dryer steamy rice with a slight crisp on the bottom: 1 liter of water for 1 kg of rice

Well done and more wet rice: 1.2 liters of water for 1 kg of rice

- Select "Rice" with the menu button. Press Start. It will take some minutes to warm up, then a 10 min counter starts.

- When finished " bb " appears, it's keeping the rice warm. Press Cancel.

- Let the rice cool down and do not release the steam to speed it up! When the lid can be opened, done!

=== Potatoes ===
Prepare potatoes by cutting them to similar size. 5cm diameter is a good measurement.
- Fill pot, but be careful not to overfill beyond the lip of the pot. The valve on the lid should move freely.

- Add around 200ml of water. Using hot water from the electric kettle will noticeably speed up the process.

- Select steam program and increase time to 10 minutes. Press Start.

- When finished "bb" appears, it's in keep warm mode. Press Cancel.

- If you're in a rush you can release the steam, but it will make the potatoes mushy. To prevent that, just wait until the lid can be opened.

=== Beans ===
- Wash them and soak for many hours. Throw away the soaking water.
- Put in pressure cooker, cover with water, add salt and half a tea spoon of baking soda. Herbs, onion in quarters, garlic, are optional.
- Choose bean program.
For small beans soaked overnight it was too much. When 5 min left cancel the program. "bb" should be cancelled. too.

I'm less sure about beans yet, because too many variables. But it is around these lines.

=== Quinoa ===
It also works for Quinoa, with the same "Rice" program and 1:1 with water by weight.
[[Category:Practicalities]]

Laundry

2025-10-16T18:46:46Z

Janina: add winter smell precautions and start washing machine instructions

👗 Everything concerning laundry - be it dirty or clean.

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

=== Standard procedure ===

==== Dirty laundry sorting ====
Dirty laundry can be put into the laundry containers in the [[Main bathroom|Main Bathroom]] (K20-2-1b). When those are full they go to the fitting sections in the [[Washing room|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, bed sheets, towels)

* 90°C: Kill-everything laundry (e.g. kitchen towels, butt towels)

==== Starting the washing machine ====
''This section needs pictures for better understanding!''

We usually have two working washing machines that can run either on tap water or on rain water. Please use the detergent fitting to the kind of water you choose. The switch for the water is right on top of the machines, below the plexiglass. The detergent is in the tiny room above the dirty laundry baskets.

# Make sure the machine is reasonably full - not more than an extended hand should fit on top.
# Set the water source to 'rain'.
# Fill in detergent labeled with 'rain' and measured by the marked measuring cup.
# Set to 'Buntwäsche' and the degree matching the laundry you want to wash (see categories above).
# Reduce spin to 1000 .

==== Wet laundry ====
Spaces to dry laundry are:
* the outside clothes lines
* the [[2nd bathroom|2nd Bathroom]] in K22-2-2
* the attics
* K20 staircase ceiling-mounted rack (only if outdoor temperature is above 5°C, to prevent mold on the walls)
* K20-0 wash room ceiling-mounted rack
* if need be more mobile drying racks can be put up in ventilated rooms

==== Dry laundry ====
Clothes baskets can be found in the [[Washing room|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 [[Communal closet|Communal Closet]]. Just leave the basket on the floor, sorting it in can be done during [[Power hour|Power Hour]].

=== Winter adjustments to prevent or remove smell ===
In colder temperatures inside, the laundry dries slower and can develop smell. Especially the clothes washed at only 40°C are at risk, so in winter it should be spun with 1200 rpm (rounds per minute) to speed up the drying process.

==== Extra drying precautions ====

* hang in well-ventilated rooms, ideally exhaust rooms (bathrooms, attics, washroom)
* hang up soon after machine is complete, ideally less than 2 hours
* use a big fan to blow air into laundry in the first hours after hanging up
* hang cloths with many/thick layers with lots of space in between (e.g. trousers with pockets, hoodies, sweatpants)
* hang in garden on mobile rack, then move rack into staircase when it gets dark
* wash already smelly stuff at 60°C, this kills most bacteria

== 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 adequately 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 [[Communal closet|Communal Closet]] after all.
[[Category:Repro]]
[[Category:Practicalities]]

CoMe

2025-09-22T10:18:02Z

Janina: remove residence record and publishing to website instructions

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

== Time and place ==
The default is '''Monday 10 am''' in the [[dining room]]. The meeting lasts until 11 am maximum. Therefore time management to cover all sections is a crucial task for the Facilitator.

== Scope and importance ==
This is the most important meeting at Kanthaus. It takes place every week, we take notes which we publish in our Mattermost and we expect people to take part if they want to know what’s going on.

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

=== Requirements ===

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


=== Preparation ===


==== Check date ====

Ensure that the date is current.


==== Run the script ====

There is a scheduled job that automatically runs the script that feeds up-to-date information about stats and evaluations to the <code>kanthaus-residence</code> channel.

In case that does not work, you can go to the [https://git.kanthaus.online/kanthaus/kanthaus-governance/actions?workflow=weekly_report.yaml&actor=0&status=0 Forgejo action], click on any run in the list and press “Re-run all jobs”. - After some minutes, the bot will post data to the <code>kanthaus-residence</code> channel.


==== Stats ====

From the post in <code>kanthaus-residence</code>, copy the contents in the gray ‘stats’ box to the <code>Previous week stats</code> CoMe section


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


==== Trash ====

Check the dates for putting out trash cans in the [https://cloud.kanthaus.online/apps/calendar/dayGridMonth/now Kanthaus calendar] and write them down in the <code>Schedule</code> section.


==== Money ====

Check the donation container in the k20 hallway and deposit it in the cash box. List this sum plus any other donation in the last week in the <code>Income</code> CoMe section.


=== During ===

There are no fixed rules, so feel free to add your own touch and do (small) experiments. Some general advice that seems to have worked so far: - Notify people 10 minutes before the meeting starts. - Start as close to 10:00 as possible. - Go through the ordered points in order, even if nothing has changed. - At the end of each section, ask people if they have anything add (and give them some moments to think!) - Do moderate discussion if off-topic or too detailed. You can always suggest a small group forms for special topics. - Try to finish the meeting before 11:00. If you think it really makes sense to extend it, announce that. Make a clear announcement when the meeting is over, and if [[Powerhour|Power Hour]] assignments will be done right away.


=== Afterwards ===

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

Copy CoMe pad contents to the <code>minutes</code> channel on Mattermost.

Prepare the CoMe pad for next week - clear all information that is no longer relevant (i.e. most of it) - put forward the date and counter to next CoMe and add the name of the next facilitator.

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

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

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

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

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

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

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

User:Janina/Sommerfest-preparation

2025-09-10T06:15:29Z

Janina: start

Sommerfest is the most public event of the year: We want to present ourselves in a positive light and create a friendly and joyful atmosphere.

== Frame ==
Festive gathering mostly in the garden

Starting time: 2 pm

Door of K20 is as much open as possible

== To do on the day ==
We hold a meeting at 10 am to get the house in shape

=== Orderliness ===

* tidy up the garden
* tidy up the house
* make sure the lower staircase toilet and compost toilet are equipped and neat
* have someone responsible for toilets

=== Make garden festive ===

* decorate
* put up tables and benches
* put up a buffet
* put up stage area
* have someone responsible for music
* arrange fire corner
* (optional) hide ugly corners of the garden
* (optional) buy soft drinks

=== Make fest accessible ===

* decorate the door and put out a big sign
* put up signage towards toilets, free shop, whatever makes sense
* put up barriers to the non-public parts of the house
* clarify which areas will definitely not be part of the fest
* have someone responsible for awareness

=== Food ===

* have someone responsible for cake making
* have someone responsible for maintaining the buffet table
* have someone responsible for savory food

=== Program ===

* make a (rough) schedule and create a poster from it
* have people responsible for doing house tours
* have someone responsible for making announcements

=== Outreach ===

* clarify who feels responsible for approaching strangers and who doesn't

Volunteer induction

2025-08-29T09:32:20Z

Janina: /* Link collection */

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

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

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

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

### Eventually
- [ ] introduce to git with kanthaus.online to upload CoMe minutes
- [ ] introduce to git with kanthaus-private to update evaluation record
- [ ] show and go through https://wiki.kanthaus.online/Hosting_checklist

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

== Link collection ==

* https://kanthaus.online/public
* https://cloud.kanthaus.online
* https://wiki.kanthaus.online
* https://git.kanthaus.online/
* https://premiumize.me

== Template for introductory message ==

<pre>Congratulations on becoming a Volunteer 🙂

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

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

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

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

User:Janina/Symbol-based marking system for visitors

2025-08-15T12:38:51Z

Janina: inital

==== What problem to solve ====
- Visitors often don't know how much space they're meant to claim and how to do so

- Long-term residents get annoyed by unmarked or wrongly marked spaces

- Explaining different systems to each individual visitor is work and they might not remember everything at the right moment

==== General idea ====
Choose a set of clearly distinct symbols that are easy to recognize even when small. Define which spaces should or could be claimed by a visitor and create a set of labels/markers in which each location get a thingy. Make several sets to hand out to different visitors. Keep track of which visitor uses which symbol e.g. on the physical visitor board. Collect the markers when the visitors leave.

==== Which spaces to prepare for ====
- Towel rack (clothes peg)

- Used dishes shelf (magnet?)

- Private shoe shelf (magnet?)

- Private storage (could even be a new shelf with symbols permanently attached. but where?)

==== Which symbols to use ====
- star

- flower

- cloud

-

User:Janina/Coffee fishbowl

2025-05-14T10:14:41Z

Janina: add fishbowl link

Date: 2025-05-13

Present: Janina, Tilmann, Gwen, Pju, Astrid, Timber, Thomas, Marynia, Lena, Larissa, Matthias

Minutes: Janina

Frame: 1,5 hours, open [https://www.betterevaluation.org/methods-approaches/methods/fishbowl-technique fishbowl] with 4 chairs in the middle

=== Minutes ===
Pju: I personally don't drink coffee. It's not good for me. I do appreciate Thomas making coffee for the free shop. I wouldn't need that high quality for it though.

Tilmann: I was neutral towards coffee until I realized that many people are quite dependent on it. Like my parents, who drink coffee everyday on several occasions and they don't seem to be able to do without. That doesn't look like voluntary enjoyment to me, but rather like problematic addiction. I also perceived this in Kanthaus in the past: There were moments when we ran low on coffee and some people got really nervous. That's when it became clear to me that coffee is actually a quite potent drug, even though I myself don't react to it that strongly. I started to wonder if we are making this drug too readily available in Kanthaus and the recent developments did not help too ease my concerns in that direction. The freezer discussion for example showed very heated emotions.

Pju:The freezer thing was unfortunate. Maybe the amount of coffee beans frozen was just too big?

Tilmann: There was never such a strong reaction towards unfreezing meat or using it in 'the wrong way'.

Thomas: At the moment it's 8kg in the freezer and we use 1 kg per week.

Tilmann: Sounds crazy much...

Thomas: Well the freezer space will be available in summer, as you, Tilmann, said is needed.

Gwen: You, Thomas, said the coffee is communal, so can't we unfreeze it to make space for food if we judge that food is more important than coffee?

Timber: I was part of making the decision to take the coffee out and I stand by it. I doubt that it really needs to be frozen. The difference in taste is so marginal.

Pju: For me the amount makes a difference since it's a luxury good and many people don't have anything to do with it.

Thomas: There is also weed in the freezer which I have nothing to do with. But I don't want to speak about the freezer so much, I see it as a misunderstanding mainly.

Tilmann: We don't produce coffee ourselves, it doesn't even grow here. It's a colonialist product and by buying it we exploit other parts of the world.

Thomas: I don't buy shitty, exploitative coffee. I buy coffee from a cooperative, it's transported on a sailboat and the revenue is used to improve the lives of the people who grew it.

Tilmann: I think you're missing the point of self-sufficiency: If people grow coffee to export, they can't grow the food they need.

Thomas: It's people who need money and I'd rather buy their product than donate money to them as a charity. Helping them grow their business is much more sustainable.

Astrid: How do you, Thomas, feel now that you hear that not many people who live in this community really value coffee? Maybe you could just buy less for yourself and events.

Janina: I appreciate that Thomas makes coffee at events I organize, for me it also wouldn't need to be the highest quality coffee, but I value that Thomas buys the least exploitative beans.

Thomas: 2/3 of the coffee I use per week is for the free shop. To me it is gifting the people a nice experience. It's like a microcosm of how I perceive Kanthaus values: I do it completely consciously, with the least trash and waste possible, using ecologically produced, fairly traded beans that were transported emission free. And I want it to be the highest quality possible as to not make the gift smaller. I like to bring the people a moment of joy, of connection, of exchange. It builds trust and relationships that form a kind of community with the people of the town.

Janina: To me the two most essential and potentially controversial points are the question if we want to promote drugs and if buying a product to make a change for the better is a valid approach or not. On the drug point: People gather around drugs and I'm fine with using this to my advantage when organizing public events. We need to decide which battle to fight when to be effective. When it comes to in-house usage it could be good to put some emphasis on the awareness point that coffee is indeed a drug and that daily consumption, possibly several times, can be problematic. We're not a drug free house, so everyone should be free to consume things as long as they don't bother anyone, but we can and should talk about harmful tendencies. On the point about buying stuff to improve things: I really don't know. I think it's not my approach for sure, but I don't want to completely dismiss it either without good reasoning.

Once more the freezer:

Timber: When I took it out I honestly thought that someone who is not Thomas froze the coffee because they thought that it would mold otherwise. I thought I knew better and took it out.

Gwen: Also, Timber and Flori came home late after saving a lot of bread in Leipzig. There was not enough space and they were desperate.

Thomas: Tilmann put it back in on the next day. There was space.

Timber: I'm still amazed and don't understand how Tilmann did it.

Thomas: It could have been put it a styrofoam box with some cold packs and put back as soon as there is space again.

Janina: That's actually a good point that didn't even cross my mind. But I think the main problem about the whole freezer issue was the communication about it. You, Thomas, had a very strong reaction, so it obviously did something to you.

Thomas: I said it's fine. The coffee belongs to the community.

Marynia: But if you have such specific wishes on how to treat it maybe you should just keep the beans private and just share the coffee.

Janina: I think it would have been different if the coffee boxes had been labeled with 'Thomas'. Taking those out I would find extremely disrespectful, taking out communal items always is a judgement case.

Tilmann: I did take out some meat and the orange peels to make the coffee fit.

Janina: I still have a confusion. You, Thomas, say it's fine and the community can decide to unfreeze the coffee, but from your initial reaction I got the impression that you were quite angry. Were you?

Thomas: Yes I was angry.

Janina: Are you saying that you were angry but that way okay?

Thomas: Yes.

Marynia: Well, maybe then you shouldn't lash out at people.

(the discussion was not immediately over, but the 1,5 hours were and Janina had to leave)

User:Janina/Coffee fishbowl

2025-05-14T10:11:45Z

Janina: Created page with "Date: 2025-05-13 Present: Janina, Tilmann, Gwen, Pju, Astrid, Timber, Thomas, Marynia, Lena, Larissa, Matthias Minutes: Janina Frame: 1,5 hours, 4 chairs in the middle === Minutes === Pju: I personally don't drink coffee. It's not good for me. I do appreciate Thomas making coffee for the free shop. I wouldn't need that high quality for it though. Tilmann: I was neutral towards coffee until I realized that many people are quite dependent on it. Like my parents, who d..."

Date: 2025-05-13

Present: Janina, Tilmann, Gwen, Pju, Astrid, Timber, Thomas, Marynia, Lena, Larissa, Matthias

Minutes: Janina

Frame: 1,5 hours, 4 chairs in the middle

=== Minutes ===
Pju: I personally don't drink coffee. It's not good for me. I do appreciate Thomas making coffee for the free shop. I wouldn't need that high quality for it though.

Tilmann: I was neutral towards coffee until I realized that many people are quite dependent on it. Like my parents, who drink coffee everyday on several occasions and they don't seem to be able to do without. That doesn't look like voluntary enjoyment to me, but rather like problematic addiction. I also perceived this in Kanthaus in the past: There were moments when we ran low on coffee and some people got really nervous. That's when it became clear to me that coffee is actually a quite potent drug, even though I myself don't react to it that strongly. I started to wonder if we are making this drug too readily available in Kanthaus and the recent developments did not help too ease my concerns in that direction. The freezer discussion for example showed very heated emotions.

Pju:The freezer thing was unfortunate. Maybe the amount of coffee beans frozen was just too big?

Tilmann: There was never such a strong reaction towards unfreezing meat or using it in 'the wrong way'.

Thomas: At the moment it's 8kg in the freezer and we use 1 kg per week.

Tilmann: Sounds crazy much...

Thomas: Well the freezer space will be available in summer, as you, Tilmann, said is needed.

Gwen: You, Thomas, said the coffee is communal, so can't we unfreeze it to make space for food if we judge that food is more important than coffee?

Timber: I was part of making the decision to take the coffee out and I stand by it. I doubt that it really needs to be frozen. The difference in taste is so marginal.

Pju: For me the amount makes a difference since it's a luxury good and many people don't have anything to do with it.

Thomas: There is also weed in the freezer which I have nothing to do with. But I don't want to speak about the freezer so much, I see it as a misunderstanding mainly.

Tilmann: We don't produce coffee ourselves, it doesn't even grow here. It's a colonialist product and by buying it we exploit other parts of the world.

Thomas: I don't buy shitty, exploitative coffee. I buy coffee from a cooperative, it's transported on a sailboat and the revenue is used to improve the lives of the people who grew it.

Tilmann: I think you're missing the point of self-sufficiency: If people grow coffee to export, they can't grow the food they need.

Thomas: It's people who need money and I'd rather buy their product than donate money to them as a charity. Helping them grow their business is much more sustainable.

Astrid: How do you, Thomas, feel now that you hear that not many people who live in this community really value coffee? Maybe you could just buy less for yourself and events.

Janina: I appreciate that Thomas makes coffee at events I organize, for me it also wouldn't need to be the highest quality coffee, but I value that Thomas buys the least exploitative beans.

Thomas: 2/3 of the coffee I use per week is for the free shop. To me it is gifting the people a nice experience. It's like a microcosm of how I perceive Kanthaus values: I do it completely consciously, with the least trash and waste possible, using ecologically produced, fairly traded beans that were transported emission free. And I want it to be the highest quality possible as to not make the gift smaller. I like to bring the people a moment of joy, of connection, of exchange. It builds trust and relationships that form a kind of community with the people of the town.

Janina: To me the two most essential and potentially controversial points are the question if we want to promote drugs and if buying a product to make a change for the better is a valid approach or not. On the drug point: People gather around drugs and I'm fine with using this to my advantage when organizing public events. We need to decide which battle to fight when to be effective. When it comes to in-house usage it could be good to put some emphasis on the awareness point that coffee is indeed a drug and that daily consumption, possibly several times, can be problematic. We're not a drug free house, so everyone should be free to consume things as long as they don't bother anyone, but we can and should talk about harmful tendencies. On the point about buying stuff to improve things: I really don't know. I think it's not my approach for sure, but I don't want to completely dismiss it either without good reasoning.

Once more the freezer:

Timber: When I took it out I honestly thought that someone who is not Thomas froze the coffee because they thought that it would mold otherwise. I thought I knew better and took it out.

Gwen: Also, Timber and Flori came home late after saving a lot of bread in Leipzig. There was not enough space and they were desperate.

Thomas: Tilmann put it back in on the next day. There was space.

Timber: I'm still amazed and don't understand how Tilmann did it.

Thomas: It could have been put it a styrofoam box with some cold packs and put back as soon as there is space again.

Janina: That's actually a good point that didn't even cross my mind. But I think the main problem about the whole freezer issue was the communication about it. You, Thomas, had a very strong reaction, so it obviously did something to you.

Thomas: I said it's fine. The coffee belongs to the community.

Marynia: But if you have such specific wishes on how to treat it maybe you should just keep the beans private and just share the coffee.

Janina: I think it would have been different if the coffee boxes had been labeled with 'Thomas'. Taking those out I would find extremely disrespectful, taking out communal items always is a judgement case.

Tilmann: I did take out some meat and the orange peels to make the coffee fit.

Janina: I still have a confusion. You, Thomas, say it's fine and the community can decide to unfreeze the coffee, but from your initial reaction I got the impression that you were quite angry. Were you?

Thomas: Yes I was angry.

Janina: Are you saying that you were angry but that way okay?

Thomas: Yes.

Marynia: Well, maybe then you shouldn't lash out at people.

(the discussion was not immediately over, but the 1,5 hours were and Janina had to leave)

User:Janina

2025-04-15T08:11:24Z

Janina: add subpage template

Heyo!

Looking forward to working on this wiki with you! 😊

== Subpages ==
{{ListSubpagesOfThisUserpage}}

== Todo ==

* find a way to make nice category pages
* write a 'quick start guide' to kanthaus
* integrate glossary somewhere visible (main page? sidebar?)
* put more content into [[glossary]]
* put more content into [[bikes and trailers]]
* put more content into [[saving food]]
* write new pages
** food policy
** transformative justice
** heart-sharing
** group hosting guide
** visitor hosting guide

Bread machine

2025-03-11T10:06:58Z

Janina:

This page is about the [https://manuall.de/ambiano-bm21-08631-brotbackautomat/ Aldi Ambiano Brotbackautomat], which is (currently) the main machine used for making [[bread]].

== Recipe ==
The most tested recipe is the ''Brot-Grundrezept'', so basic bread recipe. For this we use (slightly different to the original recipe):

* 320ml water (= 320g)
* 4tbs oil (= 52g, typically sunflower seed oil)
* 2tsp salt (= 12g)
* 2.5tbs sugar (= 35g)
* 500g flour (typically a mixture of 405 and non-405 wheat flour)
* 1.75tsp yeast (= 5.25g)

== Device operation ==

* Remove the bread container (number 1 in the manual) from the machine
* Make sure the dough hook (number 2 in the manual) is inserted correctly in the bread container
* Put the ingredients in the bread container, using a scale if necessary. For measuring tsp / tbs we have a special spoon in the [[Kitchen|main kitchen]] (number 5 in the manual). Make sure the yeast is not getting wet in case you later increase the time
* Insert the bread container in the machine. You will need to insert it a bit diagonally and then twist it until it locks in
* Close the lid
* Plug in the bread machine
* The display should display a 1 to the left of the estimated time, indicating the first program (''GRUNDPROGRAMM''). If this is not the program you want, push the ''MENÜ'' button (number 14 in the manual) repeatedly. If you follow the basic recipe, leave it at 1
* Push the ''GEWICHT'' button (number 13 in the manual) until the little arrow points at ''1000g''
* Push the ''BRÄUNUNGSGRAD'' button (number 9 in the manual) until the little arrow points at ''DUNKEL''
* ''Optional'': If you want the device to be done later, e.g. because you want it to utilize solar energy and still be done at 7am in the morning, push the time button (number 12 / 11 in the manual) repeatedly until the time displayed is to your liking. The time displayed is the time the machine takes until the machine is done
* Wait until the time has passed and the machine is done
* Take out the bread container. Try not to burn your hands: It's very hot!
* Flip the bread container onto a plate, kicking the bread out of it
* Carefully remove the hook from the bread, utilizing a knife and/or another hook (number 6 in the manual)
* Let the bread cool down for some time
* Eat the bread
[[Category:Practicalities]]
[[Category:Technical]]

Bread

2025-03-11T10:06:19Z

Janina:

We eat a lot of bread in Kanthaus.

== Where to find bread ==
Unfrozen bread is typically stored in the [[Snack kitchen]], in the box under the bread cutting board. Frozen bread is in one of the [[Freezer|freezers]].

== Obtaining new bread ==
There are two main options for obtaining new bread: [[Saving food|Saving]] (either dumpster diving or foodsharing) or making it yourself, e.g. with the help of the [[Bread machine]].
[[Category:Practicalities]]

Hosting

2025-02-26T10:16:10Z

Janina: add category

Hosting individuals and groups in Kanthaus is a core task for all Volunteers and Members. To enable all to give a consistent hosting experience to Visitors and groups, this hosting checklist collects important points.

= Hosting Sheet for individual visitors =

== Before the visitor arrives ==

* communicate unusual features of Kanthaus however necessary
** functional living
** dumpster diving
** no close buddying
** relative coldness in winter
** …
* agree on date (and time) of arrival (and maybe departure)
* find a sleeping spot for them for the first two nights, preferably a private room
* find out if they have experience of being “an independent visitor/guest”
* inform other Kanthausians about the upcoming visit on Mattermost and in CoMe
* put it in the digital calendar
* tell them roughly how many people there will be in Kanthaus and give a short overview of how the situation will be

== Upon the visitor’s arrival ==

* be there to open the door and welcome them
* ask for urgent needs (toilet, water, food)
* help them store their things (bag, shoes, jacket)
* show them where they’ll sleep that night
* let them know where to find a toilet, a shower, food and water
* tell them about kanthaus-gast wifi
* ask about food preferences (allergies etc.)
* tell them if there’s any scheduled event the next day (like come, power hour)
* be available for a chat
* make it clear that it’s cool to hang out in the communal spaces

== The next day ==

* do a house tour (ca. 1-2h) with the visitor
* explain the week plan and the food tasks sheet in the dining room
* invite them to contribute to cooking and cleaning
* encourage them to ask questions and try out things
* point out that being criticized is not meant personally and happens to everyone here
* ask them if they would like to be “left” by themselves to explore and observe or if they would feel more comfortable with being actively invited to participate
* show how to open (and close!) the window in the kitchen
* demonstrate using the door code in K22 and/or hand them a door tag
* tell them about constitution and collective agreements

== Once a week during their stay ==

* schedule a longer check-in to give and receive feedback
* post a summary of said check-in in ~vol-and-mem on Mattermost

== Before they leave ==

* invite to write in the guestbook
* ask them for their email address if they want to receive our newsletter in future

= Group Hosting Checklist =

== Clarify the basics ==

* communicate and find out the following:
** what is it that they are doing?
** how many people are coming?
** when will they arrive (earliest) and leave (latest)?
** which room(s) will they be using for day-time activities?
** which room(s) will they be using for sleeping?
** (when) will they participate in dinner preparation?
** will they bring food or help us recover it?
* communicate to KH residents about the group coming
** make a Mattermost post in ~kanthaus and/or a CoMe point
** put it in the nextcloud calendar in the following format: <code>Group name (n ppl) [host]</code>

== Before they arrive ==

* reserve the room(s)
* keep KH residents posted about changes in group size, arrival time, room usage and/or duration of stay
* check the room(s) you offered them for usability, cleanliness and clean them if necessary

== Upon arrival ==

* be there to open the door and welcome them :)
* show them where they can leave their stuff
* show them the room(s) they will be using
* invite them to use the rest of the house as well
* give them a key/tag and/or teach them the door code

== During ==

* give a house tour if wanted
* regularly check in with them to make sure everything is fine
* be available for questions
* make them aware of the guest book and invite them to leave an entry

== After ==

* check the room(s) and leave them in a usable state
* check privatizable storage areas and clear names if necessary
[[Category:Social]]

User:Janina/Hosting checklist

2025-02-26T10:15:38Z

Janina: Janina moved page User:Janina/Hosting checklist to Hosting checklist: moved from wip stage to presentable

#REDIRECT [[Hosting checklist]]

Hosting

2025-02-26T10:15:38Z

Janina: Janina moved page User:Janina/Hosting checklist to Hosting checklist: moved from wip stage to presentable

Hosting

2025-02-26T10:15:03Z

Janina: add individual hosting sheet

Hosting

2025-02-26T10:04:39Z

Janina:

Hosting individuals and groups in Kanthaus is a core task for all Volunteers and Members. To enable all to give a consistent hosting experience to Visitors and groups, this hosting checklist collects important points.

= Group Hosting Checklist =

== Clarify the basics ==

* communicate and find out the following:
** what is it that they are doing?
** how many people are coming?
** when will they arrive (earliest) and leave (latest)?
** which room(s) will they be using for day-time activities?
** which room(s) will they be using for sleeping?
** (when) will they participate in dinner preparation?
** will they bring food or help us recover it?
* communicate to KH residents about the group coming
** make a Mattermost post in ~kanthaus and/or a CoMe point
** put it in the nextcloud calendar in the following format: <code>Group name (n ppl) [host]</code>

== Before they arrive ==

* reserve the room(s)
* keep KH residents posted about changes in group size, arrival time, room usage and/or duration of stay
* check the room(s) you offered them for usability, cleanliness and clean them if necessary

== Upon arrival ==

* be there to open the door and welcome them :)
* show them where they can leave their stuff
* show them the room(s) they will be using
* invite them to use the rest of the house as well
* give them a key/tag and/or teach them the door code

== During ==

* give a house tour if wanted
* regularly check in with them to make sure everything is fine
* be available for questions
* make them aware of the guest book and invite them to leave an entry

== After ==

* check the room(s) and leave them in a usable state
* check privatizable storage areas and clear names if necessary

Hosting

2025-02-26T10:02:16Z

Janina: fix formatting

= Group Hosting Checklist =

== Clarify the basics ==

* communicate and find out the following:
** what is it that they are doing?
** how many people are coming?
** when will they arrive (earliest) and leave (latest)?
** which room(s) will they be using for day-time activities?
** which room(s) will they be using for sleeping?
** (when) will they participate in dinner preparation?
** will they bring food or help us recover it?
* communicate to KH residents about the group coming
** make a Slack post (#kanthaus?) and/or a CoMe point
** put it in the nextcloud calendar in the following format: <code>Group name (n ppl) [host]</code>

== Before they arrive ==

* reserve the room(s)
* keep KH residents posted about changes in group size, arrival time, room usage and/or duration of stay
* check the room(s) you offered them for usability, cleanliness and clean them if necessary

== Upon arrival ==

* be there to open the door and welcome them :)
* show them where they can leave their stuff
* show them the room(s) they will be using
* invite them to use the rest of the house as well

== During ==

* give a house tour if wanted
* regularly check in with them to make sure everything is fine
* be available for questions
* make them aware of the guest book and invite them to leave an entry

== After ==

* check the room(s) and leave them in a usable state
* check privatizable storage areas and clear names if necessary

Hosting

2025-02-26T10:00:56Z

Janina: add group hosting checklist

Hosting individuals and groups in Kanthaus is a core task for all Volunteers and Members. To enable all to give a consistent hosting experience to Visitors and groups, this hosting checklist collects important points.

## Group Hosting Checklist

### Clarify the basics
- communicate and find out the following:
- what is it that they are doing?
- how many people are coming?
- when will they arrive (earliest) and leave (latest)?
- which room(s) will they be using for day-time activities?
- which room(s) will they be using for sleeping?
- (when) will they participate in dinner preparation?
- will they bring food or help us recover it?
- communicate to KH residents about the group coming
- make a Slack post (#kanthaus?) and/or a CoMe point
- put it in the nextcloud calendar in the following format: `Group name (n ppl) [host]`

### Before they arrive
- reserve the room(s)
- keep KH residents posted about changes in group size, arrival time, room usage and/or duration of stay
- check the room(s) you offered them for usability, cleanliness and clean them if necessary

### Upon arrival
- be there to open the door and welcome them :)
- show them where they can leave their stuff
- show them the room(s) they will be using
- invite them to use the rest of the house as well

### During
- give a house tour if wanted
- regularly check in with them to make sure everything is fine
- be available for questions
- make them aware of the guest book and invite them to leave an entry

### After
- check the room(s) and leave them in a usable state
- check privatizable storage areas and clear names if necessary

Hosting

2025-02-26T09:59:26Z

Janina: start hosting duties page

Bikes and trailers

2025-02-26T09:30:16Z

Janina:

🚲️ Kanthaus has a nice fleet of communal bikes and trailers, as well as some privately maintained vehicles.

== Overview ==
We have two sheds and a room for bike and trailer storage.

Two of our bikes are e-bikes: Phoenix and Lightning. They are meant to be used only for pulling trailers, or when someone needs to go far.

Visitors should get an intro to the bikes before borrowing one for the first time. And let their host know which one they are taking.

When taking a bicycle to Leipzig, a proper lock is needed. Consider a safer location for overnights.

In the communal bicycle shed we park the bikes at an angle, so the back of the room is more easily accessible.

Our trailers are all self made. Daria is the smallest, capable of carrying about 90kg. Nathaniel is convertible to a ladder, and can also carry 90kg. Carla cargo is the heavy duty one, and can carry up to 250kg. It has inertial independent brakes and a front wheel, and it is made of steel.

== Maintenance and repair ==
If you break something, fix it. If you don't feel able to, tell someone and do it together.

The Communal Bike Shed has all bicycle specific tools, spare parts, and a portable bike holder. The [[Mechanical workshop|Workshop]] carries general tools, hooks to hang bicycles from the ceiling, and compressed air.

Communal bike maintenance is very much appreciated [[Repro orga|repro]] work! If you want to get involved, please talk to us.

[[Category:Practicalities]]
[[Category:Technical]]
[[Category:Repair]]

Processes to manage stuff

2025-02-15T18:01:00Z

Janina: enlarge example pic

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

== [[The Vortex]] ==

== De-cluttering actions ==

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

=== Communal stuff de-cluttering ===

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

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

=== Private stuff de-cluttering ===

Basically the same as the communal stuff de-cluttering, private stuff de-cluttering are events to make sure we don’t have unnecessary items in public spaces for private items. This is only necessary in the entrance of K20 where we have space for private shoes and jackets ''without name tags''.
[[File:PrivateShoeSale.png|alt=Screenshot of a message|thumb|699x699px|Example of the start of a private shoe sale]]

== Spitz Storage Room concepts ==

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

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

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

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

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

== Privatization of communal stuff ==
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:MaximeStuffRequest.jpg|thumb|''Example of someone asking to privatize communal items''|695x695px]]

[[Category:Social]]
[[Category:Repro]]

Processes to manage stuff

2025-02-15T17:58:45Z

Janina: add shoe sale pic

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

== [[The Vortex]] ==

== De-cluttering actions ==

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

=== Communal stuff de-cluttering ===

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

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

=== Private stuff de-cluttering ===

Basically the same as the communal stuff de-cluttering, private stuff de-cluttering are events to make sure we don’t have unnecessary items in public spaces for private items. This is only necessary in the entrance of K20 where we have space for private shoes and jackets ''without name tags''.
[[File:PrivateShoeSale.png|alt=Screenshot of a message|thumb|699x699px|Example of the start of a private shoe sale]]

== Spitz Storage Room concepts ==

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

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

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

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

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

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

File:PrivateShoeSale.png

2025-02-15T17:57:25Z

Janina:

Screenshot of Larissa starting a private shoe sale

User:Janina/Food policy

2025-01-29T15:36:13Z

Janina: Created page with "Kanthaus as a project is very focused on a sustainable use of resources, especially food. == Why == Food production, packaging, transport and retail use massive amounts of energy, labor and water. At the same time they produce pollution and unavoidable waste. (add source and some numbers!) We need food to live and we appreciate its value, but in our abundant capitalist consumer society this value is too often reduced to a price tag that does not show the true cost of a..."

Kanthaus as a project is very focused on a sustainable use of resources, especially food.

== Why ==
Food production, packaging, transport and retail use massive amounts of energy, labor and water. At the same time they produce pollution and unavoidable waste. (add source and some numbers!)

We need food to live and we appreciate its value, but in our abundant capitalist consumer society this value is too often reduced to a price tag that does not show the true cost of an item.

The future might hold less abundance and could rather force us to do with as little as possible. In the spirit of resilience in case of collapse we should already train how to do that today, in the most joyful and creative way we can.

[very WIP!]

== How ==
thoughts when saving

thoughts when sorting

thoughts when cooking

User:Janina

2025-01-29T13:29:55Z

Janina:

Heyo!

Looking forward to working on this wiki with you! 😊

== Todo ==

* find a way to make nice category pages
* write a 'quick start guide' to kanthaus
* integrate glossary somewhere visible (main page? sidebar?)
* put more content into [[glossary]]
* put more content into [[bikes and trailers]]
* put more content into [[saving food]]
* write new pages
** food policy
** transformative justice
** heart-sharing
** group hosting guide
** visitor hosting guide

User:Janina

2025-01-29T11:17:44Z

Janina: Created page with "Heyo! Looking forward to working on this wiki with you! 😊 == Todo == * find a way to make nice category pages * write a 'quick start guide' to kanthaus * integrate glossary somewhere visible (main page? sidebar?) * put more content into glossary * put more content into bikes and trailers * put more content into saving food * write new pages ** food policy ** transformative justice ** heart-sharing ** group hosting guide"

Residence record

2025-01-29T11:08:11Z

Janina:

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

=== Why are people recorded? ===

* Because of our [[Positions and evaluations|position system]] which requires us to know how much time individuals spend at the space.

=== 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.
[[Category:Social]]
[[Category:Digital]]

Ukuvota

2025-01-29T11:05:58Z

Janina:

🎯 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… 😉).
[[Category:Digital]]
[[Category:Social]]

Task lottery

2025-01-29T11:04:56Z

Janina:

🎫 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 [[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.
[[Category:Digital]]
[[Category:Repro]]
[[Category:Social]]

Mattermost

2025-01-29T11:04:08Z

Janina:

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

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

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

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

== Known issues ==

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

Mattermost

2025-01-29T11:03:41Z

Janina:

Server

2025-01-29T11:02:24Z

Janina:

⭐️ 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 publicly 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> [[Wifi|network]] and served via [[wikipedia:Samba_(software)|Samba]]. 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 address 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 hard-disk 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 hard-disks have a raid configuration to tolerate the loss of one hard-disk.

== 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-2500K (4x 3.3 GHz)
* Ram: 16 GB DDR3L
* SSD: 1 TB Samsung 860 Evo as root file system
* HDD: BTRFS pool with 2 disks. Current usable size 3 TB

== Backups ==

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

== Tor Relay ==
We run a [https://metrics.torproject.org/rs.html#details/DB35C03124D5EC03BCFE2754078A48366133EE05 Tor middle/guard relay]. It was set up according to [https://community.torproject.org/relay/setup/guard/debian-ubuntu/ those instructions]. You can check its status with
sudo systemctl status tor@default
It (re)started successfully if the following line (with a different IP) appears in the journal (<code>sudo journalctl -xeu tor@default</code>):
Self-testing indicates your ORPort 84.184.31.103:9001 is reachable from the outside. Excellent. Publishing server descriptor.
However, you don't need to worry too much about it, since [https://chat.kanthaus.online/kanthaus/messages/@timber Timber] will get notified within 5 minutes of the Tor relay being down.

Also note that the Tor relay restarts every night something past 5 since our IP address changes around that time. This is expected behavior and nothing to worry about.

If you're very curious and want to see what happens on the server, you can check out <code>sudo nyx</code>, though be mindful to [https://community.torproject.org/relay/setup/post-install/ not share this data publicly], since it can endanger the anonymity of our users.

The keys of the relay lie in <code>/var/lib/tor/keys</code> and are included in <code>/opt/kh-services/configs/borgmatic.yml</code>, which ''should'' mean that they're being backed up.

== Other services ==

* Foodsharing Gitlab which CI runner (dockerized)
* House bus services
** local Web interface (dockerized)
** Logging daemon to externally hosted influxdb
* Virtual machines (kvm/libvirt)
[[Category:Technical]]
[[Category:Digital]]

Nextcloud

2025-01-29T11:01:47Z

Janina:

☁️ We have our own instance of Nextcloud hosted on [[Server|our server]] to store immutable data and our calendar.

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

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

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

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

Kanthaus.online

2025-01-29T11:00:53Z

Janina:

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 [[Documents|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. wiki ===

The target audience is similar to this wiki: people who are just interested in Kanthaus, people who want to visit Kanthaus, and people who already are in Kanthaus.

But in contrast to the wiki, which is about providing detailed guides and instructions, the website is much more about presenting and inviting.
[[Category:Digital]]

Grafana

2025-01-29T10:59:35Z

Janina:

📊 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]] 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.
[[Category:Digital]]

Git

2025-01-29T10:58:54Z

Janina:

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

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

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

== What is stored where? ==
Among other things we have the following repositories:

* [https://git.kanthaus.online/kanthaus/kanthaus.online kanthaus.online], where we store our website, https://kanthaus.online/.
* [https://git.kanthaus.online/kanthaus/kanthaus-private kanthaus-private], where we store our [[residence record]], internal meeting minutes, financial plans and other stuff that contains personal information. Everything of relevance that consists of text and has pieces of confidential data should be put here.
* [https://git.kanthaus.online/kanthaus/kanthaus-public kanthaus-public], which is publicly accessible as the name suggests. In this repository we do our task management via issues (which you can find [https://git.kanthaus.online/kanthaus/kanthaus-public/issues here]). This is especially important for our [[../social/roadmap.md|roadmap plannings]]. Other than that we have drafts, policies, signs, data on our water, electricity and gas usage and much more in here.
* [https://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>
[[Category:Digital]]

Git

2025-01-29T10:58:33Z

Janina:

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

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

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

== What is stored where? ==
Among other things we have the following repositories:

* - [https://git.kanthaus.online/kanthaus/kanthaus.online kanthaus.online], where we store our website, https://kanthaus.online/.
* - [https://git.kanthaus.online/kanthaus/kanthaus-private kanthaus-private], where we store our [[residence record]], internal meeting minutes, financial plans and other stuff that contains personal information. Everything of relevance that consists of text and has pieces of confidential data should be put here.
* - [https://git.kanthaus.online/kanthaus/kanthaus-public kanthaus-public], which is publicly accessible as the name suggests. In this repository we do our task management via issues (which you can find [https://git.kanthaus.online/kanthaus/kanthaus-public/issues here]). This is especially important for our [[../social/roadmap.md|roadmap plannings]]. Other than that we have drafts, policies, signs, data on our water, electricity and gas usage and much more in here.
* - [https://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>
[[Category:Digital]]

Evaluation record

2025-01-29T10:54:08Z

Janina:

📝 In the evaluation record, we record a summary of the [[Positions and evaluations|evaluations required by our positions system]]. The file is stored in [https://git.kanthaus.online/kanthaus/kanthaus-private kanthaus-private] (a [[Git|git repository]]). At the end of an evaluation, the facilitator is expected to record the evaluation in this table.

== Structure ==
The evaluation record is a table (written in CSV format), containing for each evaluation the following fields: - Date - Person being evaluated - Position before the evaluation - Position applied for - New position - People who got to vote on the position - Other non-voting people present at the evaluation - Notes, giving a broad summary of the topics of the evaluation and the general situation of the evaluee.

== Uses ==
In combination with the [[residence record]], this file is used to determine automatically who is due for evaluation before each [[CoMe]].

This file can also be consulted by Volunteers and Members who were unable to attend an evaluation, to get a gist of what was said.

Occasionally, this file is analyzed to gather statistics about our position system or attendance of evaluations.
[[Category:Social]]
[[Category:Digital]]

Expfloorer

2025-01-29T10:52:50Z

Janina:

🏡 The interactive digital map of Kanthaus, made in SVG with Inkscape.

== Access ==

* to the [https://kanthaus.gitlab.io/expfloorer/ map]
* to the [https://gitlab.com/kanthaus/expfloorer code]

== Features ==

The different floors are collapsible. Toggles for beds, toilets, food, measurements, doors and windows. More to be added in the future. More info in the repository.

== Extract and use SVG tutorial ==

The example case of making a sleeping spot reservation sheet.

=== Take svg from expfloorer ===
[[File:1 Expfloorer extract tutorial .jpg|thumb|Developer console in firefox: in this example we extract the shape of the sleep kitchen.]]
Every browser has a so-called ‘developer console’ that let’s you get more information from websites. Let’s use this feature to get a room shape. Go to [https://kanthaus.gitlab.io/expfloorer/ expfloorer] in your browser and press F12 to open the developer console. Now choose the inspector and inspect the element you want to extract.

All complex SVG objects have a so-called ‘d’ value, which contains all the information about the shape. When you click that value in the developer console you can copy it.

=== Insert svg into new file ===
[[File:2 Expfloorer extract tutorial .jpg|thumb|d value in inkscape xml editor: the d value in the XML editor is clickable.]]
Inkscape is the default SVG manipulation program for Linux, so we use it. To have a place to paste our d value we need to make a complex object and then change it. So we just make two overlapping circles or rectangles, select them and go for path->union. Now the two simple objects merged into one complex object. Now we open the XML editor, select the d value of our object and exchange the contents to what we copied from expfloorer.

It might look like you just have an empty sheet after copying in the new d, but when you zoom out enough you will find your new object. It just doesn’t appear in your previous viewport necessarily.

=== Creating something ===
[[File:3 Expfloorer extract tutorial .jpg|thumb|Finished reservation sheet. Pretty isn’t it? 😉]]
Now you can take the shape and do whatever you want with it. E.g. creating a sleeping spot reservation sheet like this one:

But since this isn’t an Inkscape tutorial we won’t get into how to do that now.
[[Category:Digital]]
[[Category:Practicalities]]

Calendar

2025-01-29T10:52:06Z

Janina:

We host our own (CalDAV) calendar on our Nextcloud instance: https://cloud.kanthaus.online/apps/calendar

== Calendars overview 📅 ==

* '''main''' - Kanthaus events of relevance to most residents
* '''people''' - for recording visitor visiting times
* '''müll''' - waste collection dates from [https://kell-gmbh.de/service/pdf-kalender/ KELL]
* '''festivals-events-etc''' - for external events that may be of interest to others
* '''Contact birthdays''' - automagically generated from birthdates in the ‘khontacts’ contact book

See [https://www.planlos-leipzig.org/ planlos-leipzig.org] for interesting events in Leipzig.

== Android/AOSP phone access ==

* Download [https://www.davx5.com/ Davx5]
** Recommended to download via [https://f-droid.org/packages/at.bitfire.davdroid/ F-droid]
* Open Davx5, add new account, select “Login with URL and user name”,
** Base URL: <code>https://cloud.kanthaus.online</code>
** User name: <yourNextcloudUserName>
** Password: <yourNextcloudPassword>
* Got to ‘Caldav’, select all calendars you want to sync

== Laptop/computers ==

* Your calendar app ''should'' already have Caldav capabilities
* Find ‘add calendar’ or equivalent
* Use the same details as for Android/AOSP

== Working with <code>.ics</code> 👹 ==
Concrete example: the waste disposal calendar from KELL shows the days when the bins are picked up. Sometimes those pick-ups are early, and the far safer option is put the bins out the day before. To move all the dates (except for the Schadstoffmobil!) is not trivial. Here's how we did it in towards the end of 2024:

* Download the correct <code>.ics</code> from https://www.kell-gmbh.de/ (without Schadstoffmobil!)
* Convert <code>.ics</code> to <code>.tsv</code> using https://github.com/loteoo/icsp
* Open new <code>.csv</code> with LibreOffice
* Ensure <code>DTSTART</code> and <code>DTEND</code> formats are set to date (YYYY-MM-DD) format
* Make new <code>DTSTART</code> and <code>DTEND</code>columns for the adapted values
** Formula: <code>=<original>-1</code>
** Save file, close file, reopen again (to convert formula to data)\
* Delete original <code>DTSTART</code> and <code>DTEND</code> columns
* Make sure the <code>DESCRIPTION</code> and <code>SUMMARY</code> are informative, an emoji at the beginning of the <code>SUMMARY</code> is especially nice! (e.g. ''"🟩 Put out Biotonne"''). Also, make sure that line lengths are under 75 characters long, or Nextcloud (Hub 9.0) will complain.
* Convert <code>.tsv</code> to <code>.ics</code>
* Copy <code>PRODID</code> and <code>VERSION</code> lines (2 & 3) from original <code>.ics</code> to between <code>BEGIN:VCALENDAR</code> and <code>BEGIN:VEVENT</code> (1 & 2)
* Additionally, download just the Schadstoffmobil calendar and upload as is

Watch out that you don't have any <code>UUID</code> clashes! (i.e. you will need to delete existing events if same events previously uploaded.)
[[Category:Digital]]
[[Category:Social]]

Processes to manage stuff

2025-01-29T10:49:46Z

Janina:

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

== [[The Vortex]] ==

== De-cluttering actions ==

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

=== Communal stuff de-cluttering ===

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

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

=== Private stuff de-cluttering ===

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

== Spitz Storage Room concepts ==

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

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

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

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

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

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

Stuff

2025-01-29T10:47:36Z

Janina:

This page describes items that we have but may not remember about them.

The items are listed next to places where they are normally expected to be found.

=== Office ===

* graphics tablet
* binoculars
* camera
* communal laptops
* blood pressure tester

=== Electronics workshop ===

* Screen protectors for Pixel 3a: handys box
* Huawei 4g router (×2?): big WiFi+DECT box
* 6× TP-Link 1200AC routers: big WiFi+DECT box
* a small Android tablet: desk
* many 1GiB switches: big WiFi + DECT box
* Small computer (5× Ethernet) (Fujitsu FUTRO S920): not sure where
[[Category:Practicalities]]

Documents

2025-01-29T10:44:41Z

Janina:

📎 '''Core documents of Kanthaus governance'''

We - that is mostly Doug - spend a lot of thought on how to organize ourselves. That led to a three layer system of governance, which is described in the following documents.

=== [https://kanthaus.online/en/governance/constitution The Constitution] ===

* The most important document that describes the basic structures of communal living and decision making.
* It is written in formal language on purpose to make it a legit and clear legal document.
* The more human-friendly version that contains explanations in casual language is [https://kanthaus.online/en/governance/governancefaq the FAQ]

=== [https://kanthaus.online/en/governance/collectiveagreements The Collective Agreements] ===

* The document that clarifies more practical questions of everyday life.
* The schedule of common activities and the preferences regarding certain practicalities are written down here.
[[Category:Social]]

Saving food

2025-01-29T10:43:24Z

Janina:

🍐 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:
[[Category:Repro]]
[[Category:Practicalities]]

Room reservation

2025-01-29T10:42:44Z

Janina:

🐚 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 ===
[[File:CatPlaneDreamBasket reservation.png|thumb|''the reservation sheet of the Cat Plane Dream Basket'']]
In communal sleeping rooms like the [[Dorm]], the (original) [[Communal sleeping room|Communal Sleeping Room]], the [[Cat plane dream basket|Cat Plane Dream Basket]] and the [[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.

=== Claimed bed in multi-purpose room: semi-private ===
There are just two multi-purpose rooms: the [[Fansipan]] and the [[Intermediate|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 [[Processes to manage stuff|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 specific 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 [[CoMe]].

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 ===
[[File:OccupancyIndicator.jpg|thumb|''Occupancy indicator, rules sign and week sheet on the door of a private room.'']]
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 specific 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 [[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 no-one 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.

== Desks ==
[[File:PrivateDesk.jpg|thumb|''Claimed desk in a slightly messy Silent Office.'']]
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.
[[Category:Social]]
[[Category:Practicalities]]

Door & window handling

2025-01-29T10:41:46Z

Janina:

This page describes doors and windows in the house with regards to

* why/when to open/close them
* physical handling (ToDo)

== Why and when to open and/or close doors? 🚪 ==
Opening and closing doors permits/restricts '''air flow''' as well as '''noise'''.

You want to have the most air flow when [[airing]], so open the doors for that. You don’t want to have air flow when heating, so keep doors to heated areas closed:

* Heat leaves the heated room -> it would get colder
* With the warm air, humidity leaves into a cold room where it is easy to start condensation/mold growth ([[Airing|See airing]])

You may want to close doors when you plan to be noisy in a room:

* Active conversation/discussion
* Working with tools that make noise
* Listening to music not knowing if people in neighbor rooms like that

== What does a closed door not mean? ==
The philosophy of Kanthaus focuses on openness, not isolation. When a door is closed, it is mostly because of the reasons listed above.

'''A closed door to a communal room should always be seen as an invitation to come in and close it behind yourself again'''

== Why and when to open/close a window? 🪟 ==
When it is colder inside than outside, we like to keep windows closed, especially when the [[Heating|heating system]] is running. [[Airing]] is not necessary, since we have a great [[Ventilation]] system in place. Please read the appropriate pages for details.

When it is warm outside, windows might be kept open when

* it is ensured that windows don’t flap because of wind (several windows already broke because of that)
* people inside don’t mind increased noise
* our music/noise/being loud does not disturb neighbors outside
[[Category:Structural]]
[[Category:Practicalities]]

Laundry

2025-01-29T10:35:00Z

Janina: add cats

👗 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 [[Main bathroom|Main Bathroom]] (K20-2-1b). When those are full they go to the fitting sections in the [[Washing room|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, bed sheets, towels)

* 90°C: Kill-everything laundry (e.g. kitchen towels, butt towels)

=== Wet laundry ===
Spaces to dry laundry are: - the outside clothes lines - the [[2nd bathroom|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 [[Washing room|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 [[Communal closet|Communal Closet]]. Just leave the basket on the floor, sorting it in can be done during [[Power hour|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 adequately 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 [[Communal closet|Communal Closet]] after all.
[[Category:Repro]]
[[Category:Practicalities]]