Kanthaus wiki - User contributions [en]

User:Doug/Kitchen renovation

2026-04-21T14:33:56Z

Doug: add unisexurinal link

This page is to plan for the future kitchen.

== Aim ==
To create a kitchen that will:

* enable preparing food for bigger numbers of people
* be more enjoyable to use
* be easier to clean and maintain
* allow for a higher level of hygiene

== Location ==

* Current: K20-1-2
* Proposed: K20-1-1 (currently Snack kitchen) + K20-1-1B (currently Snack kitchen "Kabuff")
** 👍 has water and waste water connections
** 👍 not a pass-through room
** 👍 quite central
** 👍 would be next to the proposed future snack kitchen
** 👎 on the smaller side
*** but no passage space!
(The plan to swap Kitchen and Snack kitchen locations is already kind of underway: the recent (late 2025) window exchange put a window-door in the K20-1-2, with the aim to eventually put a balcony there.)

== Plan ==

=== Preparation ===
Currently some plumbing runs through the room which is in active use in the [[Main bathroom]] and lower staircase toilet.

* ☐ move toilet in main bathroom K20-2-1 to "Kabuff" K20-2-1B (See Appendix) ❓
** ☐ 🧩 acquire "good" toilet (i.e. one that doesn't block, preferably with urine separation) or all-bodies-urinal (e.g. [https://finizio.de/shop/unisexurinal/ from Finizio])
** ☐ free up the left side of Kabuff
** ☐ drill necessary holes to upper-staircase toilet (~50 cm)
** ☐ water off!
** ☐ install toilet, cistern, bidet hose & connect everything up (!)
** ☐ reinstall the old door or a curtain
** ☐ remove old toilet, cap off the tube
* ☐ supply water to lower staircase toilet from upper staircase toilet (or wash kitchen)
** ☐ drill hole
** ☐ water off!
** ☐ switch connections

=== Temporary Snack kitchen ❓ ===
K20-1-1 will be unusable for the duration of works. It is possible the work will be done in a month, but maybe longer, so the "temporary" rearrangement should be good for at least 2 months. Options:

* if weather allows, set up a a temporary outdoor "main" kitchen and set up new Snack kitchen "permanently" in current Kitchen (i.e. k20-1-2)
** more work to begin, less at end, food preparation more distributed
* set up temporary Snack kitchen in Elephant room
** less work to begin, more at end, food preparation more concentrated

=== Stripping down ===
This phase of the work is about getting rid of unwanted things and getting the room to a stage where positive construction can begin.

* ☐ remove mobile items (microwave, glasses, oats, etc)
* ☐ water off!
* ☐ remove mounted items (cupboards, shelf, radiator, sink, tap, etc)
* ☐ power off!
* ☐ remove fake-wall (left side, behind sink)
** ℹ️ unknown tasks may hide behind wall!
* ☐ remove unnecessary plumbing
** ☐ remove sewage pipe in back-right corner
** ☐ remove water pipes leading to right side
* ☐ strip walls & ceiling
** ☐ remove all tiles
** ☐ remove all wallpaper (including ceiling)
*** ℹ️ needs to be done ''thoroughly'', no pieces of paper left (likely requires spiky roller/water spray)
** ☐ remove all hooks, plugs, clips, etc.
** ☐ break out any loose plaster
** ☐ sand walls, if necessary
* celebrate 🎉

=== Building up ===
This phase of the work is about positively constructing towards the desired end state. '''A lot of open questions still!'''

* ☐ prepare walls & ceiling (i.e. smooth, flat, stable)
** ☐ plaster any holes
** ☐ if necessary plastering or complete dry-walling (hopefully not! 🙏)
* ☐ electrics
** aim: no exposed wires, good number of sockets where useful
** ☐ main light switch
** ☐ ovens/stoves ❓
** ☐ lights ❓
** ☐ parapet trunking (power strip) along both sides ❓
* ☐ plumbing
** ☐ radiator or wall heating ❓
** ☐ reroute that pipe that sticks out on the "left" side
** ☐ prepare sink inlets & outlet ❓
*** preference: [https://img1.homary.com/mall/file/2021/10/29/26e43c4043c34e81aa7b31c84b70c12a.jpg wall-mounted hose-tap]
*** ℹ️ outlet location has a degree of flexibility, wall-mounted tap not
* ☐ windowsill
** A nice bit or marble?
* ☐ ventilation❓
* ☐ Kabuff wall ❓
** if removing (See Appendix), shelves to go all the way
** ℹ️ [https://hardwareheaven.ie/wp/wp-content/uploads/2023/11/sb108-2.jpg "London" style shelf brackets] have a low profile.
* ☐ dry-walling left side
** aim: to be able to have one, long stainless steel work surface without any corners, gaps or cut-outs
**from floor to head-height?
* ☐ ceiling and upper walls
** white paint that can deal with humidity ❓
* ☐ lower walls
** random saved tiles, 20 cm * 20 cm ❓
* ☐ flooring
** [https://m.media-amazon.com/images/I/71Jidl6CMFL.jpg coin stud rubber matting] ❓
* portal through the wall to the snack-kitchen ❓
* ... unknown unknowns 👻💀👹 ...
* Celebrate! 🎉🎉

=== Installation ===
Note that the specifics of most of these items need to be decided on ''before'' commencing the work at all

* ☐ sink
* ☐ tap
* ☐ tables
** consider differing height requirements
* ☐ overhead storage
* ☐ fridge ❓
* CelEbRat3!!! 🎉🎉🎉🎉

== Appendix ==

=== Advice ===
Who do we know who did a comparable kitchen renovation? How much did it cost, time did it take? Advice?
* ✅ Lebenstraum Gemeinschaft Janishausen - Doug contacted
** 2026-04-21 still no response

=== Sewage pipe ===
Remove it or keep it? Removing it permanently gains a little space for the kitchen, simplifies the room shape and infrastructural complexity. Removing also requires work... Options in my order of preference
* remove pipe, relocate bathroom toilet to Kabuff
** significant work
* keep pipe, box it off (drywall)
** moderate work
** long-term missed opportunity
* remove pipe, remove bathroom toilet with no replacement
** the toilet seems useful and used!
* keep pipe, no boxing
** least work
** looks ugly, traps dirt
** (I would not be motivated to help with renovation if this option were chosen)
* remove pipe, reroute sewage through wall to staircase toilets
** most work
** this would require over 2 meters of horizontal sewage routing and a major reorganizing of pipes in upper staircase toilet
** (I would not be motivated to help with renovation if this option were chosen)

=== '''Kabuff separation wall''' ===
Remove part/all of it?
* options:
** removing the "small" side towards the entrance would allow a/the shelf to extend all the way to the door, making better use of the space
** as above, but extending all the way up: would allow a/the shelf to extend vertically to roof
** all: unclear... my imagination overflows
* any removal would brings ''significant'' costs and would only make sense to do during main action
** would require architectural considerations, possibly building in supports
** dusty breakage
** significant plastering required
** permanent damage to original and pretty door-frame
** makes it necessary to make all shelving new
* To-do: drill into wall above door frame post: if it extends to the ceiling, it's probably supporting

=== Heating (or not) ===
Options and their drawbacks

* Keep radiator (status quo)
** takes space from room
** makes windowsill less accessible
** traps dirt
** increases wall complexity for tiling, etc
* Remove radiator, no replacement
** possibly too cold in winter
*** but likely fine given physical activity + heating from cooking
* Remove radiator, install wall-heating panel
** work: finding parts, mounting, plumbing and plastering

User:Doug/Kitchen renovation

2026-04-21T14:17:08Z

Doug: update post mini-meeting

This page is to plan for the future kitchen.

== Aim ==
To create a kitchen that will:

* enable preparing food for bigger numbers of people
* be more enjoyable to use
* be easier to clean and maintain
* allow for a higher level of hygiene

== Location ==

* Current: K20-1-2
* Proposed: K20-1-1 (currently Snack kitchen) + K20-1-1B (currently Snack kitchen "Kabuff")
** 👍 has water and waste water connections
** 👍 not a pass-through room
** 👍 quite central
** 👍 would be next to the proposed future snack kitchen
** 👎 on the smaller side
*** but no passage space!
(The plan to swap Kitchen and Snack kitchen locations is already kind of underway: the recent (late 2025) window exchange put a window-door in the K20-1-2, with the aim to eventually put a balcony there.)

== Plan ==

=== Preparation ===
Currently some plumbing runs through the room which is in active use in the [[Main bathroom]] and lower staircase toilet.

* ☐ move toilet in main bathroom K20-2-1 to "Kabuff" K20-2-1B (See Appendix) ❓
** ☐ 🧩 acquire "good" toilet (i.e. one that doesn't block, preferably with urine separation) or all-bodies-urinal
** ☐ free up the left side of Kabuff
** ☐ drill necessary holes to upper-staircase toilet (~50 cm)
** ☐ water off!
** ☐ install toilet, cistern, bidet hose & connect everything up (!)
** ☐ reinstall the old door or a curtain
** ☐ remove old toilet, cap off the tube
* ☐ supply water to lower staircase toilet from upper staircase toilet (or wash kitchen)
** ☐ drill hole
** ☐ water off!
** ☐ switch connections

=== Temporary Snack kitchen ❓ ===
K20-1-1 will be unusable for the duration of works. It is possible the work will be done in a month, but maybe longer, so the "temporary" rearrangement should be good for at least 2 months. Options:

* if weather allows, set up a a temporary outdoor "main" kitchen and set up new Snack kitchen "permanently" in current Kitchen (i.e. k20-1-2)
** more work to begin, less at end, food preparation more distributed
* set up temporary Snack kitchen in Elephant room
** less work to begin, more at end, food preparation more concentrated

=== Stripping down ===
This phase of the work is about getting rid of unwanted things and getting the room to a stage where positive construction can begin.

* ☐ remove mobile items (microwave, glasses, oats, etc)
* ☐ water off!
* ☐ remove mounted items (cupboards, shelf, radiator, sink, tap, etc)
* ☐ power off!
* ☐ remove fake-wall (left side, behind sink)
** ℹ️ unknown tasks may hide behind wall!
* ☐ remove unnecessary plumbing
** ☐ remove sewage pipe in back-right corner
** ☐ remove water pipes leading to right side
* ☐ strip walls & ceiling
** ☐ remove all tiles
** ☐ remove all wallpaper (including ceiling)
*** ℹ️ needs to be done ''thoroughly'', no pieces of paper left (likely requires spiky roller/water spray)
** ☐ remove all hooks, plugs, clips, etc.
** ☐ break out any loose plaster
** ☐ sand walls, if necessary
* celebrate 🎉

=== Building up ===
This phase of the work is about positively constructing towards the desired end state. '''A lot of open questions still!'''

* ☐ prepare walls & ceiling (i.e. smooth, flat, stable)
** ☐ plaster any holes
** ☐ if necessary plastering or complete dry-walling (hopefully not! 🙏)
* ☐ electrics
** aim: no exposed wires, good number of sockets where useful
** ☐ main light switch
** ☐ ovens/stoves ❓
** ☐ lights ❓
** ☐ parapet trunking (power strip) along both sides ❓
* ☐ plumbing
** ☐ radiator or wall heating ❓
** ☐ reroute that pipe that sticks out on the "left" side
** ☐ prepare sink inlets & outlet ❓
*** preference: [https://img1.homary.com/mall/file/2021/10/29/26e43c4043c34e81aa7b31c84b70c12a.jpg wall-mounted hose-tap]
*** ℹ️ outlet location has a degree of flexibility, wall-mounted tap not
* ☐ windowsill
** A nice bit or marble?
* ☐ ventilation❓
* ☐ Kabuff wall ❓
** if removing (See Appendix), shelves to go all the way
** ℹ️ [https://hardwareheaven.ie/wp/wp-content/uploads/2023/11/sb108-2.jpg "London" style shelf brackets] have a low profile.
* ☐ dry-walling left side
** aim: to be able to have one, long stainless steel work surface without any corners, gaps or cut-outs
**from floor to head-height?
* ☐ ceiling and upper walls
** white paint that can deal with humidity ❓
* ☐ lower walls
** random saved tiles, 20 cm * 20 cm ❓
* ☐ flooring
** [https://m.media-amazon.com/images/I/71Jidl6CMFL.jpg coin stud rubber matting] ❓
* portal through the wall to the snack-kitchen ❓
* ... unknown unknowns 👻💀👹 ...
* Celebrate! 🎉🎉

=== Installation ===
Note that the specifics of most of these items need to be decided on ''before'' commencing the work at all

* ☐ sink
* ☐ tap
* ☐ tables
** consider differing height requirements
* ☐ overhead storage
* ☐ fridge ❓
* CelEbRat3!!! 🎉🎉🎉🎉

== Appendix ==

=== Advice ===
Who do we know who did a comparable kitchen renovation? How much did it cost, time did it take? Advice?
* ✅ Lebenstraum Gemeinschaft Janishausen - Doug contacted
** 2026-04-21 still no response

=== Sewage pipe ===
Remove it or keep it? Removing it permanently gains a little space for the kitchen, simplifies the room shape and infrastructural complexity. Removing also requires work... Options in my order of preference
* remove pipe, relocate bathroom toilet to Kabuff
** significant work
* keep pipe, box it off (drywall)
** moderate work
** long-term missed opportunity
* remove pipe, remove bathroom toilet with no replacement
** the toilet seems useful and used!
* keep pipe, no boxing
** least work
** looks ugly, traps dirt
** (I would not be motivated to help with renovation if this option were chosen)
* remove pipe, reroute sewage through wall to staircase toilets
** most work
** this would require over 2 meters of horizontal sewage routing and a major reorganizing of pipes in upper staircase toilet
** (I would not be motivated to help with renovation if this option were chosen)

=== '''Kabuff separation wall''' ===
Remove part/all of it?
* options:
** removing the "small" side towards the entrance would allow a/the shelf to extend all the way to the door, making better use of the space
** as above, but extending all the way up: would allow a/the shelf to extend vertically to roof
** all: unclear... my imagination overflows
* any removal would brings ''significant'' costs and would only make sense to do during main action
** would require architectural considerations, possibly building in supports
** dusty breakage
** significant plastering required
** permanent damage to original and pretty door-frame
** makes it necessary to make all shelving new
* To-do: drill into wall above door frame post: if it extends to the ceiling, it's probably supporting

=== Heating (or not) ===
Options and their drawbacks

* Keep radiator (status quo)
** takes space from room
** makes windowsill less accessible
** traps dirt
** increases wall complexity for tiling, etc
* Remove radiator, no replacement
** possibly too cold in winter
*** but likely fine given physical activity + heating from cooking
* Remove radiator, install wall-heating panel
** work: finding parts, mounting, plumbing and plastering

User:Doug/Mindful, careful, powerful changes

2026-04-04T10:11:41Z

Doug: init

''(I posted the following in `~exchange` in Mattermost in March 2026. [https://chat.kanthaus.online/kanthaus/pl/s54q9esrrjy1trkptt3gg6qb7y Link])''

'''Summary of this long post:''' (physical) changes to Kanthaus which I perceive as mindless, careless or powerless bring up feelings of frustration, stress and sadness in me.
----This has been on my mind and heart for a while. It's not urgent, but every time it happens, it builds on suppressed negative feelings. It is not something that one person does, so please don't feel individually called out. (Indeed, I'm likely guilty too!) This is not meant as an attack piece, emotional blackmail or an attempt at domination. I want people to understand that this affects me and why it affects me.

== Specific observations ==

* recent name labels beside in hallway before dorm & white shelf in elephant room (labels not cut straight, corners not cut/rounded, nails sticking out and bent)
* curtain rail in sorano (was very bendy, I raised concerns, it fell apart soon after... but I think fixed now?)
* curtain rail in silent office (I raised concerns that string wasn't good enough, this was changed to a pole, but it isn't straight and one side gets caught)
* magnet closers in communal (unfitting magnets were ordered and mounted. I ended up ordering and mounting fitting magnets almost a year later)
* punching bag pulley in sports room (initial installation still required using a ladder at some point, someone made some improvement, but I had to spend another hour to get it working properly)
* plant shelves in dragon room windows (unstable, would have damaged windows long-term. I tasked someone to take them down.)

== What goes on in my head and heart ==
When I see these kind of changes, several stories come to my mind

# the person did not notice the issues with their change
# the person did notice issues with their change, but though it was OK
# the person did notice issues with their result, didn't think it was OK, but lacked the ability to do something about it

=== 1. Mindless → Mindful ===
Story 1 I'll describe as being ''mindless.'' This is about not actually perceiving issues in the first place. Perhaps you're stressed. Perhaps you're doing it for the first time, and your imagination is based on insufficient experience.

Being '''mindful''' - full of mind - is about being present with all your senses, emotions and thoughts. Our belongings and spaces are extensions of our physical bodies -otherwise we'd be naked under the sky. Do you see that any physical change to our shared belongings or spaces is therefore also in some way social? If there is an accepted design for what you are doing, are you copying it with attention to detail? Do you mentally model how your community members will likely engage with what you are doing? Do you ask them if you are unsure? Which leads to number 2

=== 2. Careless → Careful ===
Number 2 I'll describe as being ''careless.'' It's about knowing the issues with some change, but deciding it's good enough anyway. I've heard the following statements when I've confronted people who did things I felt were careless:

* "I just wanted to do something"
* "It was someone else's idea, I didn't really understand it"
* "I just wanted to get it finished"

Sure, there are times when a things really does need to get done ''now'' and function completely outweighs ergonomics or aesthetics. But this is only sometimes the case. Either way, it kicks work down the line: cleaning work, maintenance work and most importantly, social work. Reverting some change you made is some work, sure, but it is usually a lot of social work for someone to ask you to revert something and for you to accept this! (And come on, there is only one person in the house working part time right now, "I don't have the time" is surely not a valid excuse.)

Being '''careful''' - full of care - is about, well, love I guess? If you just want to do something, maybe not changes to shared belongings? If you can't be bothered finishing it now, ask someone else of put a WIP instead of rushing? If you need help, ask... which bring me to number 3

=== 3. Powerless → Powerful ===
Number 3 I'll describe as being ''powerless.'' It's about knowing there are issues, but not being able to do better. Perhaps you don't know how to do some building technique properly. Or perhaps you find the process of getting social approval overwhelming.

Being '''powerful''' - full of power - is about being able to do things well. This does not mean doing everything yourself, and is as much about construction techniques as it is social skills. Is there a skill someone else could show you? If you are not asking for it, why? What do need in order to feel in control of what you are doing? What could we be doing differently for you to feel more confident that no one will complain afterwards?
----If you read this far, thanks! It was therapeutic for me just writing it out. I admit that I am extra perceptive and sensitive to details, but I hope this can be seen as a skill, not me trying to be annoying 🙏

Kanthaus is not a squat. We put and continue to put a lot of effort into securing these buildings so that we have control and agency over them. Kanthaus is already a showcase for how ''good'' life can be with less resources, but I feel we can do more.

If you're feeling demotivated, I am sorry. That's not what I want.

I want to be in a place with people who are mindful, careful and powerful! And I want those qualities to be embodied and reflected in all dimensions.

Don't you?

Hosting

2026-04-03T21:54:03Z

Doug: hosting is (also) Volunteer onboarding, phrase some things as "considerations", copy-editing, re-move position stuff to 3rd week (since this is about the latest something needs to be done, eager people can do earlier)

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. For individual Visitors, hosting is not only about facilitating a good visit, but also gradually onboarding them until they become a Volunteer - no one knows for sure how long they will stay! This page collects recommendations about what should be covered by when for a good experience for all. It is written for hosts, but we welcome any curious visitors that may be reading! 😊

== Individuals ==

=== Before committing ===
For a visit to work well, it needs to work for the Host, the Visitor and the House. Don't let enthusiasm get in the the way of good judgement! For first-time Visitors, it is recommended to arrange a fixed time-frame (that could be prolonged later.) Considerations:

* Host (you) — can you be fully present for the first days and mostly present for the duration of the visit? Do you have sufficient energy and good will to get to know and care for someone new?
* House — fullness, mood, illness? Ask at CoMe or on [[Mattermost]] if not fully sure.
* Visitor — is there clarity and alignment of intentions and expectations? Do they understand the nature and unusual features of Kanthaus? Consider calling as a more expressive medium.

=== Before arrival ===

* 📜 [https://kanthaus.online/about/visiting Visiting page] (phancy physalis!)
* announce time of arrival and departure:
** in [[Calendar|digital calendar]] (<code>people</code>),
** on visitor board, and
** in [[Mattermost]] <code>~in-house</code> and/or at CoMe
* reserve a sleeping spot for the first two nights, private unless otherwise agreed

=== Upon arrival ===

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

=== First full day ===

* house tour (ca. 1-2h)
* show physical calendar, to-do board, responsibility board, [https://pad.kanthaus.online/visitorTaskList Visitor task list]
* encourage them to observe, read signs and ask questions — especially to you, their Host!
* everything communal unless labeled
* get set up (door access, plate shelf & other storage solutions, potentially office space)
=== 1st week ===

* join [[Mattermost]]
* help find an agreeable way to contribute
* sleeping place information & empowerment
* 📜 [https://kanthaus.online/en/governance/collectiveagreements Collective Agreements]
* [[Visitor check-in]] — an informal exchange of thoughts and feelings, with a focus on feedback. (You are advised to check-in with yourself too — you can and should ask others for support or to take over hosting if needed.)

=== 2nd week ===

* 📜 [[Meeting culture]]
* 📜 [[Additional norms]]
* Visitor check-in

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

=== Every additional week ===

* Visitor check-in
** At this point, the Visitor has the option to ask for an evaluation instead, with or without applying for Volunteer. Talk to the Visitor about their options, and consider consulting with the community members about their thoughts and feelings.

=== Before departure ===

* ask them to write in the guestbook
* tell them to 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

== 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-03-19T17:40:17Z

Doug: Opinionated abbreviation of section titles

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 recommendations about what should be covered by when for a good experience for all. It is written for hosts, but we welcome any curious visitors that may be reading! 😊

== Individuals ==

=== Before committing ===
For a visit to work well, it needs to work for the Host, the Visitor and the House. Don't let enthusiasm get in the the way of good judgement! Consider the following questions (not exclusive):

* Host
** can you be fully present at Kanthaus for at least the first 2 days and mostly present for at least the first week?
** do you have sufficient energy and good will to get to know and care for someone new?
* Visitor
** do they understand the nature and unusual features of Kanthaus?
** do they have clarity about their intentions and expectations?
* House
** fullness?
** illness?
** mood?

=== Before arrival ===

* 📜 [https://kanthaus.online/about/visiting Visiting page] (phancy physalis!)
* announce time of arrival:
** in [[Calendar|digital calendar]] (<code>people</code>),
** on visitor board, and
** in [[Mattermost]] <code>~in-house</code> and/or at CoMe
* reserve a sleeping spot for the first two nights, private unless otherwise agreed

=== Upon arrival ===

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

=== 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
* sleeping place information & empowerment
* 📜 [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 additional week ===

* Visitor check-in (with the option to instead have an evaluation and apply for 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

== 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-03-19T10:17:10Z

Doug: 1) worked on introduction to make target audience and page content clearer. 2) introduced "Before committing" section. It seemed missing when I looked at it again, and mixed in with "Before arrival".

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 recommendations about what should be covered by when for a good experience for all. It is written for hosts, but we welcome any curious visitors that may be reading! 😊

== Hosting individual Visitors ==

=== Before committing ===
For a visit to work well, it needs to work for the Host, the Visitor and the House. Don't let enthusiasm get in the the way of good judgement! Consider the following questions (not exclusive):

* Host
** can you be fully present at Kanthaus for at least the first 2 days and mostly present for at least the first week?
** do you have sufficient energy and good will to get to know and care for someone new?
* Visitor
** do they understand the nature and unusual features of Kanthaus?
** do they have clarity about their intentions and expectations?
* House
** fullness?
** illness?
** mood?

=== Before arrival ===

* 📜 [https://kanthaus.online/about/visiting Visiting page] (phancy physalis!)
* announce time of arrival:
** in [[Calendar|digital calendar]] (<code>people</code>),
** on visitor board, and
** in [[Mattermost]] <code>~in-house</code> and/or at CoMe
* reserve a sleeping spot for the first two nights, private unless otherwise agreed

=== Upon arrival ===

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

=== 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
* sleeping place information & empowerment
* 📜 [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 additional week ===

* Visitor check-in (with the option to instead have an evaluation and apply for 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-21T16:47:26Z

Doug: copy-editing, formatting

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 that it's 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 a sleeping spot for the first two nights, private unless other agreement

=== Upon arrival ===

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

=== 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
* sleeping place information & empowerment
* 📜 [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 additional 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]]

User:Doug/Orderliness

2026-02-13T14:52:13Z

Doug: inspirations from poster

On Tuesday 11th November 2025 I hosted a session on "Cleanliness and orderliness" in response to a perceived drop in standards. It was useful, interesting and the dining table has been ''a lot'' cleaner since then. (Also, Lena started a "general responsibilities" and "weekly tasks" board, which may have helped.) This page is for me to publicly organize my thoughts towards further improvements and making the current improvements stick.

== General advice ==
The classic, general advice is "leave things as good as you found them". This has limitations, since people have different perceptions of "good" and different observations of "how they found them". <blockquote>Philosophical side-note:

In wild places, the general advice is "leave no trace" or "leave only footprints" - the idea being that if you don't leave trash and don't take anything, the place will be conserved. But you still shed hair and skin and leave footprints: the weather and countless organisms clean up and reset things after you. This is not the case in human structures, like buildings, where we specifically keep out the weather and non-humans, so the humans responsible for all dirt and chaos inside them. Further, the structures themselves age and degrade thanks to weather and entropy. Therefore, it really is necessary to not only clean up after yourself, but do more. I have heard it formulated as "leave better trace" and "leave it (3%) better than you found it". </blockquote>

== Specific states ==
The following table aims to capture more specifically capture the state things should be left in and when:
{| class="wikitable"
|+
!Item/area...
!to be left in default state...
!when...
!with known exceptions
|-
|sinks
|clear, clean, sieve empty
|before leaving room
|
|-
|dining table
|clear and clean
|before leaving room
|items temporarily left for community benefit: festive decoration, important information, etc
|-
|other communal surfaces
|clear and clean
|before leaving room
|Works-in-progress marked with name and date
|-
|toilets
|clean; seat dry; used towelets in bucket; with towelettes, toilet paper and menstrual products for next person
|before leaving room
|
|-
|hallways
|clear
|A.S.A.P.
|big arrivals of communal stuff, temporary storage of private things (marked with name and date)
|-
|private rooms
|free of personal items, surfaces clean - nice for unknown next person
|before reservation ends
|
|-
|beds
|covered with usable sheets, free of debris and presentable
|before claim ends
|
|-
|personal desks
|personal items stored on or under desk, preferably enough free space for another person to be able to use temporarily
|when claim ends
|very small desks need not be usable by others
|-
|personal storage areas
|clear and clean; people with extra spaces to actively clear one as new people need
|when claim ends
|
|-
|couches/sofas
|free of debris and presentable
|when leaving couch/sofa
|
|}

User:Doug/Various

2025-12-15T16:18:24Z

Doug: add "minimal support at evaluation votes" section

== Purge ==
'''Event (annual)'''

In the film of the same name (that I didn't watch) everyone does all the bad stuff on one day in the year to get it over with. We have stuff which is not fun and has roughly an annual cadence, such as:

* renewing the digital waste calendar
** see [[Calendar#Adapting the KELL (waste disposal) calendar|calendar#Adapting the KELL (waste disposal)]]
** KELL calendar seems to be available at least from the beginning of December
* pinging absent people about stuff they have stored, and moving it to the [[Spitz storage room]]
** could also be beginning of December.... could offer to send stuff as Christmas presents lol
* obfuscating links
* rotating key tag secrets
* changing password manager password
* HKW & WaWü MV's
* checking fire extinguishers/alarms
* replacing the [[Ventilation]] filters
* deep cleaning
** cobwebs
** door handles/frames

Also, there is a wonderful [[Infrequent maintenance]] page.

== Moment of reflection ==
'''Facilitation practice'''

For many years we're had a sound bowl and used it for quiet moments before and during meetings. Yet the practice varies to the point that it is unclear what the purpose is.

For me, I always perceived such moments, with or without sound bowls, as an opportunity for internal calming / mindfulness meditation. Yet we've been calling them "moments of silence". "Silence" puts emphasis on people (and the carers of children!) to make no noise, which can be stressful if you need to change position, cough, etc. Additionally, silence is not possible due to cars driving outside, planes flying, food frying, etc — while we can reduce them, noises are always part of our environment.

I see the aim of these moments rather for us to quiet ourselves internally and engage with our sensations, emotions, thoughts and consciousness — together. (In contrast, runners in a race are silent before the starting gun, but their minds are poised for action... we have had "moments of silence" like this!) If we choose to move towards the mindfulness direction, I see the following changes being helpful:

* renaming "silence" to "reflection/mindfulness/calmness/etc"
* calm and consistent practice:
** moment facilitator makes announcement, waits for people to arrange themselves
** strikes bowl (padded side of striker)
** breaths slowly, listens to sound, and when it's completely gone, takes one more slow in- and out-breath
** strikes bowl (padded side of striker)
** stops sounds by pressing hand into side of bowl
** places striker to side of bowl
** takes one more slow in- and out-breath, looks into faces/eyes of people in room
** meeting facilitator begins calmly, without jokes or reference to moment

Getting another sound bowl for attic use would be nice, because improvised objects are invariably bad. (Humming is a much better alternative.)

== Minimal support at evaluation votes ==
'''Constitution change'''

The [https://kanthaus.online/en/governance/constitution#evaluation current procedure] states:<blockquote>if there are 3 or more times as many ‘support’ votes to ‘oppose’ votes, the person is adopted at their requested position

—Constitution, §6.5.1.</blockquote>This leaves ambiguity about what should happen if a person exclusively receives 'accept' votes. The practice until now has been to treat this as a successful application. I think this is not good, and when I was interrogated why privately wrote:<blockquote>...in my experience, it is actively bad to have a person in a group who everyone is "just OK" with. This leads to situations where they feel left out, because no one has a strong, positive connection (read: support) with them. This often means the barrier for receiving critical feedback is higher, and the person only gets feedback when it's already "too" late. Conversely, it is my experience that exclusion is much harder for both parties than delayed-inclusion: waiting until there is active enthusiasm reduces the risk of exclusion. Further, the act of excluding is hard social work that no one wants to do, and if no one felt responsible in the first place (i.e. no support) then the work of exclusion can just "float in the air" (dilution of responsibility → Tragedy of the Commons)</blockquote>My basic proposal would be to add the requirement that at least one 'support' is required, modifying the clause simply to:<blockquote>'''if there is at least 1 'support' vote, and''' ''3 or more times as many ‘support’ votes to ‘oppose’ votes, the person is adopted at their requested position''</blockquote>

User:Doug/Various

2025-12-15T16:02:34Z

Doug: Add "Moment of reflection" section

User:Doug/Various

2025-12-15T15:04:59Z

Doug: Reformulate "Purge" as one section

== Purge ==
In the film of the same name (that I didn't watch) everyone does all the bad stuff on one day in the year to get it over with. We have stuff which is not fun and has roughly an annual cadence, such as:

* renewing the digital waste calendar
** see [[Calendar#Adapting the KELL (waste disposal) calendar|calendar#Adapting the KELL (waste disposal)]]
** KELL calendar seems to be available at least from the beginning of December
* pinging absent people about stuff they have stored, and moving it to the [[Spitz storage room]]
** could also be beginning of December.... could offer to send stuff as Christmas presents lol
* obfuscating links
* rotating key tag secrets
* changing password manager password
* HKW & WaWü MV's
* checking fire extinguishers/alarms
* replacing the [[Ventilation]] filters
* deep cleaning
** cobwebs
** door handles/frames

Also, there is a wonderful [[Infrequent maintenance]] page.

User:Doug/Purge

2025-12-15T15:03:07Z

Doug: Doug moved page User:Doug/Purge to User:Doug/Various: Small page, will use as basis for various ideas

#REDIRECT [[User:Doug/Various]]

User:Doug/Various

2025-12-15T15:03:07Z

Doug: Doug moved page User:Doug/Purge to User:Doug/Various: Small page, will use as basis for various ideas

In the film of the same name (that I didn't watch) everyone does all the bad stuff on one day in the year to get it over with. We have stuff which is not fun and has roughly an annual cadence. This page is to gather those things, and see if there is a fitting day/period in which to do them.

== Possible actions ==

* renewing the digital waste calendar
** see [[Calendar#Adapting the KELL (waste disposal) calendar|calendar#Adapting the KELL (waste disposal)]]
** KELL calendar seems to be available at least from the beginning of December
* pinging absent people about stuff they have stored, and moving it to the [[Spitz storage room]]
** could also be beginning of December.... could offer to send stuff as Christmas presents lol
* obfuscating links
* rotating key tag secrets
* changing password manager password
* HKW & WaWü MV's
* checking fire extinguishers/alarms
* replacing the [[Ventilation]] filters
* deep cleaning
** cobwebs
** door handles/frames

I just rediscovered the wonderful [[Infrequent maintenance]] page.

User:Doug/Various

2025-12-15T15:02:36Z

Doug: details on purge points

Calendar

2025-12-15T14:54:52Z

Doug: /* Working with .ics 👹 */ Rename section to make it concrete, copyedit.

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

== Adapting the KELL (waste disposal) calendar ==
The waste disposal calendar from KELL shows the days when the bins are picked up. Sometimes those pick-ups are quite early, and the safer option is to put the bins out the day before. To move all the dates is not trivial. Here's how we did it towards the end of 2024:

* Downloaded the correct <code>.ics</code> from https://www.kell-gmbh.de/
* Converted <code>.ics</code> to <code>.tsv</code> using https://github.com/loteoo/icsp
* Opened new <code>.csv</code> with LibreOffice
* Deleted Schadstoffmobil entries (Since you need to go at the exact time for this)
* Ensured <code>DTSTART</code> and <code>DTEND</code> columns were set to <code>YYYY-MM-DD</code> format
* Made new <code>DTSTART</code> and <code>DTEND</code> columns for the adapted values
** Formula: <code>=<original>-1</code>
** Saved file, closed file, reopened again (to convert formula to data)
* Deleted original <code>DTSTART</code> and <code>DTEND</code> columns
* Made sure the <code>DESCRIPTION</code> and <code>SUMMARY</code> were 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.
* Converted <code>.tsv</code> to <code>.ics</code>
* Copied <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, downloaded just the Schadstoffmobil calendar and uploaded 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]]

Talk:Stuff

2025-12-15T14:42:31Z

Doug: /* what is this */ Reply

== what is this ==

This page looks sad right now and I don't think that there's a chance that this will change.

What do people think, does it make sense to list communal items in a page like this? [[User:Liou|Liou]] ([[User talk:Liou|talk]]) 21:36, 13 December 2025 (CET)

:I also don't think this page makes much sense the way it is. Making an itinerary of items is cool! But I think this is the wrong medium for it. I would be happy for deleting this page without replacement. [[User:Doug|Doug]] ([[User talk:Doug|talk]]) 15:42, 15 December 2025 (CET)

User:Doug/Kitchen renovation

2025-12-11T10:07:32Z

Doug: add ventilation

The plan to swap the main [[Kitchen]] and [[Snack kitchen]] is already underway: the recent (late 2025) window exchange put a window-door in the current kitchen, with the aim to eventually put a balcony there. This is an excellent opportunity to improve the kitchen.

== Aims ==
To create a kitchen that will:

* enable preparing food for bigger numbers of people
* be more enjoyable to use
* be easier to clean and maintain
* allow for a higher level of hygiene

== Scope ==

* k20-1-1 (currently Snack kitchen)
** ''possibly'' the Snack kitchen Kabuff

== Questions ==
Many questions are in the plan below marked with ❓ This section is mostly for bigger/more complex questions.
* who do we know that got a comparable kitchen renovation? How much did it cost, time did it take? Advice?
** ✅ Lebenstraum Gemeinschaft Janishausen - contacted
* '''sewage pipe''' - remove it or keep it? Removing it permanently gains a little space for the kitchen, simplifies the room shape and infrastructural complexity. Removing also requires work... Options in my order of preference
** remove pipe, relocate bathroom toilet to cupboard
*** significant work
*** move storage into the main room
*** connect sewage though the wall to the staircase toilets sewage pipe (~50 cm)
*** connect rain & tap water also from upper staircase toilet
*** since replacing toilet anyway, get one that doesn't block
** keep pipe, box it off (drywall)
*** moderate work
*** long-term missed opportunity
** remove pipe, remove bathroom toilet with no replacement
*** the toilet seems useful and used!
** keep pipe, no boxing
*** least work
*** looks ugly, dirt-trap...
*** (I would not be motivated to help with renovation if this option were chosen)
** remove pipe, reroute sewage through wall to staircase toilets
*** most work
*** this would require over 2 meters of horizontal sewage routing and a major reorganizing of pipes in upper staircase toilet
*** (I would not be motivated to help with renovation if this option were chosen)
** '''Kabuff separation wall''' - removing part/all of it?
*** options:
**** removing the "small" side towards the entrance would allow a/the shelf to extend all the way to the door, making better use of the space
**** as above, but extending all the way up: would allow a/the shelf to extend vertically to roof
**** all: unclear... my imagination overflows
*** any removal would brings ''significant'' costs and would only make sense to do during main action
**** would require architectural considerations, possibly building in supports
**** dusty breakage
**** significant plastering required
**** permanent damage to original and pretty door-frame
**** makes it necessary to make all shelving new

== Plan ==

=== Rerouting ===
Currently some plumbing runs through the room which is in active use in the [[Main bathroom]] and lower staircase toilet. '''This work should be done before starting actual kitchen renovation at all.'''

* ☐ move toilet in main bathroom to "Kabuff" ❓
** ☐ acquire "good" toilet (i.e. one that doesn't block, preferably with urine separation) (or all-bodies-urinal?)
** ☐ free up left side of Kabuff
** ☐ drill necessary holes to upper-staircase toilet
** ☐ water off!
** ☐ install toilet, cistern, bidet hose & connect everything up (!)
** ☐ reinstall the old door or a curtain
* ☐ supply water to lower staircase toilet from upper staircase toilet (or wash kitchen)
** ☐ drill hole
** ☐ water off!
** ☐ switch connections

=== Temporary Snack kitchen reorganization ❓ ===
The Snack kitchen (i.e. k20-1-1) will be unusable for the duration of works. It is possible the work will be done in a month, but maybe longer, so the "temporary" rearrangement should be good for at least 2 months. Options:

* if weather allows, set up a a temporary outdoor "main" kitchen and set up new Snack kitchen "permanently" in current Kitchen (i.e. k20-1-2)
** more work to begin, less at end, food preparation more distributed
* set up temporary Snack kitchen in Elephant room
** less work to begin, more at end, food preparation more concentrated

=== Stripping down ===
This phase of the work is about getting rid of unwanted things and getting the room to a stage where positive construction can begin.

* ☐ hang protective sheet in Kabuff
* ☐ remove all unmounted items
* ☐ water off!
* ☐ power off!
* ☐ remove all mounted items (cupboards, shelf, sink, tap, etc)
* ☐ remove fake-wall
** ℹ️ unknown tasks may hide behind wall!
* ☐ remove unnecessary plumbing
** ☐ remove sewage pipe
** ☐ remove water pipe leading to "back-right" corner
* ☐ strip walls & ceiling
** ☐ remove all tiles
** ☐ remove all wallpaper (including ceiling)
*** ℹ️ needs to be done ''thoroughly'', no pieces of paper left (likely requires spiky roller/water spray)
** ☐ remove all hooks, plugs, clips, etc.
** ☐ break out any loose plaster
** ☐ sand walls, if necessary
* celebrate 🎉

=== Building up ===
This phase of the work is about positively constructing towards the desired end state. '''A lot of open questions still!'''

* ☐ prepare walls & ceiling (i.e. smooth, flat, stable)
** ☐ plaster any holes
** ☐ if necessary plastering or complete dry-walling (hopefully not! 🙏)
* ☐ electrics
** aim: no exposed wires, good number of sockets where useful
** ☐ main light switch
** ☐ ovens/stoves ❓
** ☐ lights ❓
** ☐ parapet trunking (power strip) along both sides ❓
* ☐ plumbing
** ☐ radiator or wall heating ❓
** ☐ reroute that pipe that sticks out on the "left" side
** ☐ prepare sink inlets & outlet ❓
*** (preference: wall-mounted hose-tap)
*** ℹ️ outlet location has a degree of flexibility, wall-mounted tap not
* ☐ windowsill
** which material ❓
** installation/plastering
* ☐ ventilation ❓
* ☐ Kabuff wall ❓
** ℹ️ "London" style shelf brackets have a low profile.
* ☐ dry-walling
** ☐ "left" side (half-wall or whole❓)
* ☐ ceiling and upper walls
** which kind of paint ❓
** colour/style ❓
* ☐ lower walls
** panels or tiles ❓
*** (preference: tiles)
** colour/style ❓
* ☐ flooring
** tiles or lino ❓
*** (preference: tiles)
** colour/style ❓
* ... unknown unknowns 👻💀👹 ...
* Celebrate! 🎉🎉

=== Installation ===
Note that the specifics of most of these items need to be decided on ''before'' commencing the work at all

* ☐ sink
* ☐ tap
* ☐ tables
* ☐ overhead storage
* ☐ fridge ❓
* CelEbRat3!!! 🎉🎉🎉🎉

User:Doug/Orderliness

2025-12-11T09:59:21Z

Doug:

On Tuesday 11th November 2025 I hosted a session on "Cleanliness and orderliness" in response to a perceived drop in standards. It was useful, interesting and the dining table has been ''a lot'' cleaner since then. (Also, Lena started a "general responsibilities" and "weekly tasks" board, which may have helped.) This page is for me to publicly organize my thoughts towards further improvements and making the current improvements stick.

== General advice ==
The classic, general advice is "leave things as good as you found them". This has limitations, since people have different perceptions of "good" and different observations of "how they found them". <blockquote>Philosophical side-note:

In wild places, the general advice is "leave no trace" or "leave only footprints" - the idea being that if you don't leave trash and don't take anything, the place will be conserved. But you still shed hair and skin and leave footprints: the weather and countless organisms clean up and reset things after you. This is not the case in human structures, like buildings, where we specifically keep out the weather and non-humans, so the humans responsible for all dirt and chaos inside them. Further, the structures themselves age and degrade thanks to weather and entropy. Therefore, it really is necessary to not only clean up after yourself, but do more. I have heard it formulated as "leave better trace" and "leave it (3%) better than you found it". </blockquote>

== Specific states ==
The following table aims to capture more specifically capture the state things should be left in and when:
{| class="wikitable"
|+
!Thing
!Default state
!When
!Known exceptions
|-
|sinks
|clear, clean, sieve empty
|before leaving room
|
|-
|dining table
|clear and clean
|before leaving room
|items temporarily left for community benefit: festive decoration, important information, etc
|-
|toilets
|clean; seat dry; used towelets in bucket; refill towelets, toilet paper or menstrual products if empty
|before leaving room
|
|-
|hallways
|clear
|A.S.A.P.
|big arrivals of communal stuff, temporary storage of private things (marked with name and date)
|-
|private rooms
|free of personal items, surfaces clean
|before reservation ends
|
|-
|beds
|covered with usable sheets, free of debris and presentable
|before claim ends
|
|-
|personal desks
|personal items stored on or under, other people able to temporarily use
|before claim ends
|very small desks need not be usable by others
|}

User:Doug/Orderliness

2025-12-11T09:48:50Z

Doug: add notes on "leave no trace", expand specifics table

On Tuesday 11th November 2025 I hosted a session on "Cleanliness and orderliness" in response to perceived drop in standards. It was useful, interesting and the dining room table has been ''a lot'' cleaner since then. (Also, Lena starting "general responsibilities" and "weekly tasks" boards may have helped.) This page is for me to publicly organized my thoughts for cementing those gains.

== General ==
The general advice remains "leave things as good as you found them". This fails when people have different perceptions of "better" and "how they found them", which is often. <blockquote>'''Philosophical side-note'''

In wild places, the general advice is "leave no trace" or "leave only footprints" - the idea being that if you don't leave trash and don't take anything, the place will be conserved. But you still shed hair and skin and leave footprints: the weather and countless organisms clean up and reset things after you. This is not the case in human structures, like buildings, where we specifically keep out the weather and non-humans, so the humans responsible for all dirt and chaos inside them. Further, the structures themselves age and degrade thanks to weather and entropy. Therefore, it really is necessary to not only clean up after yourself, but do more. I have heard it formulated as "leave better trace" and "leave it (3%) better than you found it". </blockquote>

== Specific ==
The following table aims to capture more specifically capture the state things should be left in and when.
{| class="wikitable"
|+
!Thing
!Default state
!When
!Exceptions
|-
|sinks
|clear, clean, sieve empty
|before leaving room
|
|-
|dining table
|clear and clean
|before leaving room
|items temporarily left for community benefit: festive decoration, important information, etc
|-
|toilets
|clean; seat dry; used towelets in bucket; refill towelets, toilet paper or menstrual products if empty
|before leaving room
|
|-
|hallways
|clear
|A.S.A.P.
|big arrivals of communal stuff, temporary storage of private things (marked with name and date)
|-
|private rooms
|free of personal items, surfaces clean
|before reservation ends
|
|-
|beds
|covered with usable sheets, free of debris and presentable
|before claim ends
|
|-
|personal desks
|personal items stored on or under, other people able to temporarily use
|before claim ends
|very small desks need not be usable by others
|}

User:Doug/Orderliness

2025-12-11T09:24:43Z

Doug: init

User:Doug/Kitchen renovation

2025-12-10T17:33:51Z

Doug: review; reorder; emoji; add windowsill, installation, Kabuff wall points

The plan to swap the main [[Kitchen]] and [[Snack kitchen]] is already underway: the recent (late 2025) window exchange put a window-door in the current kitchen, with the aim to eventually put a balcony there. This is an excellent opportunity to improve the kitchen.

== Aims ==
To create a kitchen that will:

* enable preparing food for bigger numbers of people
* be more enjoyable to use
* be easier to clean and maintain
* allow for a higher level of hygiene

== Scope ==

* k20-1-1 (currently Snack kitchen)
** ''not'' the Snack kitchen cupboard

== Questions ==
Many questions are in the plan below marked with ❓ This section is mostly for bigger/more complex questions.
* who do we know that got a comparable kitchen renovation? How much did it cost, time did it take? Advice?
** ✅ Lebenstraum Gemeinschaft Janishausen contacted
* '''sewage pipe''' - remove it or keep it? Removing it permanently gains a little space for the kitchen, simplifies the room shape and infrastructural complexity. Removing also requires work... Options in my order of preference
** remove pipe, relocate bathroom toilet to cupboard
*** significant work
*** move storage into the main room
*** connect sewage though the wall to the staircase toilets sewage pipe (~50 cm)
*** connect rain & tap water also from upper staircase toilet
*** since replacing toilet anyway, get one that doesn't block
** keep pipe, box it off (drywall)
*** moderate work
*** long-term missed opportunity
** remove pipe, remove bathroom toilet with no replacement
*** the toilet seems useful and used!
** keep pipe, no boxing
*** least work
*** looks ugly, dirt-trap...
*** (I would not be motivated to help with renovation if this option were chosen)
** remove pipe, reroute sewage through wall to staircase toilets
*** most work
*** this would require over 2 meters of horizontal sewage routing and a major reorganizing of pipes in upper staircase toilet
*** (I would not be motivated to help with renovation if this option were chosen)
** '''Kabuff separation wall''' - removing part/all of it?
*** options:
**** removing the "small" side towards the entrance would allow a/the shelf to extend all the way to the door, making better use of the space
**** as above, but extending all the way up: would allow a/the shelf to extend vertically to roof
**** all: unclear... my imagination overflows
*** any removal would brings significant costs and would only make sense to do during main action
**** would require architectural considerations, most likely building in supports
**** dusty breakage
**** significant plastering required
**** permanent damage to original and pretty door-frame

== Plan ==

=== Rerouting ===
Currently some plumbing runs through the room which is in active use in the [[Main bathroom]] and lower staircase toilet. '''This work should be done before starting actual kitchen renovation at all.'''

* ☐ move toilet in main bathroom to "Kabuff" ❓
** ☐ acquire "good" toilet (i.e. one that doesn't block, preferably with urine separation) (or all-bodies-urinal?)
** ☐ free up left side of Kabuff
** ☐ drill necessary holes to upper-staircase toilet
** ☐ water off!
** ☐ install toilet, cistern, bidet hose & connect everything up (!)
** ☐ reinstall the old door or a curtain
* ☐ supply water to lower staircase toilet from upper staircase toilet (or wash kitchen)
** ☐ drill hole
** ☐ water off!
** ☐ switch connections

=== Temporary Snack kitchen reorganization ❓ ===
The Snack kitchen (i.e. k20-1-1) will be unusable for the duration of works. It is possible the work will be done in a month, but maybe longer, so the "temporary" rearrangement should be good for at least 2 months. Options:

* if weather allows, set up a a temporary outdoor "main" kitchen and set up new Snack kitchen "permanently" in current Kitchen (i.e. k20-1-2)
** more work to begin, less at end, food preparation more distributed
* set up temporary Snack kitchen in Elephant room
** less work to begin, more at end, food preparation more concentrated

=== Stripping down ===
This phase of the work is about getting rid of unwanted things and getting the room to a stage where positive construction can begin.

* ☐ hang protective sheet in Kabuff
* ☐ remove all unmounted items
* ☐ water off!
* ☐ power off!
* ☐ remove all mounted items (cupboards, shelf, sink, tap, etc)
* ☐ remove fake-wall
** ℹ️ unknown tasks may hide behind wall!
* ☐ remove unnecessary plumbing
** ☐ remove sewage pipe
** ☐ remove water pipe leading to "back-right" corner
* ☐ strip walls & ceiling
** ☐ remove all tiles
** ☐ remove all wallpaper (including ceiling)
*** ℹ️ needs to be done ''thoroughly'', no pieces of paper left (likely requires spiky roller/water spray)
** ☐ remove all hooks, plugs, clips, etc.
** ☐ break out any loose plaster
** ☐ sand walls, if necessary
* celebrate 🎉

=== Building up ===
This phase of the work is about positively constructing towards the desired end state. '''A lot of open questions still!'''

* ☐ prepare walls & ceiling (i.e. smooth, flat, stable)
** ☐ plaster any holes
** ☐ if necessary plastering or complete dry-walling (hopefully not! 🙏)
* ☐ electrics
** aim: no exposed wires, good number of sockets where useful
** ☐ main light switch
** ☐ ovens/stoves ❓
** ☐ lights ❓
** ☐ parapet trunking (power strip) along both sides ❓
* ☐ plumbing
** ☐ radiator or wall heating ❓
** ☐ reroute that pipe that sticks out on the "left" side
** ☐ prepare sink inlets & outlet ❓
*** (preference: wall-mounted hose-tap)
*** ℹ️ outlet location has a degree of flexibility, wall-mounted tap not
* ☐ windowsill
** which material ❓
** installation/plastering
* ☐ Kabuff wall ❓
* ☐ dry-walling
** ☐ "left" side (half-wall or whole❓)
* ☐ ceiling and upper walls
** which kind of paint ❓
** colour/style ❓
* ☐ lower walls
** panels or tiles ❓
*** (preference: tiles)
** colour/style ❓
* ☐ flooring
** tiles or lino ❓
*** (preference: tiles)
** colour/style ❓
* ... unknown unknowns 👻💀👹 ...
* Celebrate! 🎉🎉

=== Installation ===
Note that the specifics of most of these items need to be decided on ''before'' commencing the work at all

* ☐ sink
* ☐ tap
* ☐ tables
* ☐ overhead storage
* ☐ fridge ❓
* CelEbRat3!!! 🎉🎉🎉🎉

The Vortex

2025-12-10T15:23:41Z

Doug: Add history section, credit to Hackerdom

Located in the [[Intermediate|Intermediate Storage Room]] in K20-1-5, the Vortex is a physical space to dump and look through various items. It physically consists of two tables, the space under those tables and a cardboard box next to the window.

Alternative Names: The Vortex of Doom

== What is it for? ==
There are three major use cases for the vortex:

# '''Removing''' stuff from communal or your private inventory.
# '''Clearing''' a corner of the household.
# '''Adding''' stuff to the household.

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

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

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

== Vortex categories ==

=== Communal sorted out ===

* Please attach a sign to the item saying why you want it to leave Kanthaus.

* If you sort a labelled item back in, please inform the person who wanted to get rid off it.
* '''Full duration:''' items go through all phases

=== Found randomly ===

* For all items (communal, unknown, private) that have been in odd places.
* Items in communal spaces that are not labelled otherwise can be assumed to be communal. Consider using the "communal sorted out" if you want to get rid off it.
* '''Full duration:''' items go through all phases

=== Private sorted out ===

* For your personal items that you don't want to posess anymore
* '''Short duration:''' items get doomed after phase 1 or moved to phase 2 category of "communal sorted out"

=== Broken ===

* Put any broken items in here.
* '''Short duration:''' items get doomed after phase 1 or moved to phase 2 category of "communal sorted out"

== Taking things out of the Vortex ==

=== Phase 1 ===

* personal items to keep them private
* known or assumed communal things to return them to a fitting communal space
* anything from "short duration" categories to privatize or communalize

=== Phase 2 ===

* personal items to keep them private
* anything to communalize it

=== Phase 3 ===

* anything to privatize or communalize it

== Doom ==
As well as death, doom is part of life and should not be seen (too) negatively.

Dooming in Kanthaus terms means:

* removing an item from the Kanthaus resources by putting it to the freeshop or the trash
* repurposing an item as building, crafting or towelette material

Dooming happens after phase 3 (after phase 1 for short duration categories)

=== Dooming instructions ===
* Good but unneeded items go in the [[Freeshop storage|Free Shop Storage]]
* Trash is put away according to [[Waste management]]. You might use the box of doom next to the window.

== Shifting ==
‘Vortex shifting’ is a [[Power hour|Power Hour]] task, which means that it ideally happens every week, sometimes more seldom, never more often.

To make it possible for Kanthausians who are not currently in the space to also voice an opinion on the stuff in the vortex, it’s required to document vortex shifts on [[Mattermost]]. Feel free to use the communal phone which should be at the charging dock.

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

* Start on the back and doom phase 3.
** Make (a) box(es) with things for the Free Shop and bring it there
** Check things you believe might be there in error with people who might know.
** You can communalize things, but consider that they have been in Vortex for quite some time already
** Don’t be shy to use the trash bins!
* Move phase 2 into phase 3.
** Take pictures and make sure that the things are identifiable. You might add that things are free for everyone in phase 3.
* Check phase 1. Spend some energy to move items to their places in the house.
* Move phase 1
** Doom the "short duration" categories or communalize them to "communal sorted out"
** Move "full duration" categories to phase 2
** Take pictures and make sure the things are identifiable. You might add that things are free to communalize in phase 2 and people should be quick on getting back their personal stuff.
* Upload the pictures to ~stuff on Mattermost and add some descriptive words.

== History ==
[[File:Vortex of doom Tokyo Hackerspace 2013 .jpg|thumb|"Vortex of doom" from Tokyo Hackerspace, 2013]]
The Vortex was developed in response to having too much stuff. Although Kanthaus only came with toilets, radiators and wallpaper, many things were optimistically scavenged in the early days — too optimistically. Yet while people felt OK bringing things, people felt less OK getting rid of things, leading to accumulation. (At this time, the [[Lantern]] was completely filled with possibly-useful-stuff and was called "the crap room".)

Someone decided to look into how other communities deal with this issue. The issue is/was so prevalent in hackerspaces, that the [https://wiki.hackerspaces.org/The_Old_Hardware_Pattern "The Old Hardware Pattern"] was identified in the hackerspace design patterns published in 2007 by Ohlig and Weiler:
<blockquote>
'''Problem'''

You can’t bring in shiny new hardware, as there is no space left. Your space has become a hardware museum filled with junk.

'''Implementation'''

Create a '''pile/stack''' where you put that old, unused hardware on. Let everybody take from it. Anything left within a while '''should be thrown away'''. But make sure you '''announce that step''' not only once, but at least three times with an escalation system.</blockquote>
The 3-week, constant rotation model from the Tokyo Hackerspace (pictured) was more of less directly copied, using a table for each section instead of a box.
[[Category:Power hour]]
[[Category:Maintenance]]

File:Vortex of doom Tokyo Hackerspace 2013 .jpg

2025-12-10T15:19:05Z

Doug:

User:Doug/Kitchen renovation

2025-12-09T13:19:58Z

Doug: add conditional remove radiator to "stripping down"

User:Doug/Kitchen renovation

2025-12-09T13:08:23Z

Doug: initial draft

Hosting

2025-12-07T21:20:09Z

Doug: reduction of text to key points

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 to make it a personal experience 😊

== Hosting individual Visitors ==

=== Before arrival ===

* 📜 [https://kanthaus.online/about/visiting Visiting page] (phancy physalis!)
* establish intentions for visit
* talk about notable features of Kanthaus:
** functional living
** getting stuff without money
** relative coldness in winter...
* 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 at least 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 day ===

* house tour (ca. 1-2h)
* show physical calendar, to-do board, task 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 tag
** office space
** snack kitchen use
** plate shelf & other storage solutions

=== Check-ins ===
[[Visitor check-in|Visitor check-ins]] should happen once per week. (Remember, after 3 check-ins, a Visitor may apply to become a Volunteer.)

==== 1st check-in ====

* join [[Mattermost]]
* help find an agreeable way to contribute

* 📜 [https://kanthaus.online/en/governance/collectiveagreements#relevant-in-first-days Collective Agreements relevant in the first days]

===== 2nd check-in =====

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

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

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

2025-12-07T20:45:19Z

Doug: Reintroduce sections for first 3 check-ins

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 to make it a personal experience 😊

== Hosting individual Visitors ==

=== Before arrival ===

* make sure they've read the 📜 [https://kanthaus.online/about/visiting Visiting page on the website] (phancy physalis!)
* get an idea of their intentions for their visit
* talk about the weird and wonderful features of Kanthaus:
** functional living (i.e. more like a hostel + coworking + hackerspace + etc than a shared flat)
** how we get most of our food without spending money
** relative coldness in winter
** …
* agree on date (and time) of arrival (and maybe departure) where you can be present for first 2 days, then inform Kanthausians:
** put it in [[Calendar|digital calendar]] ("people"),
** write it on the visitor board, and
** announce on [[Mattermost]] and/or at CoMe
* reserve a sleeping spot for them for at least the first two nights, preferably a private room

=== Upon arrival ===

* be there to open the door and welcome them 😊
* help satisfy basic needs (water, food, where are toilets, etc)
* establish preferred name, pronouns
* help them store their things (shoes, jacket, bag)
* show them where they'll sleep that night
* tell them the [[Wifi]] password
* find out food requirements and preferences
* be available for a chat
* make it clear that it's cool to hang out in the communal spaces

=== First day ===

* do a house tour (ca. 1-2h)
* show the physical calendar and todo board, explain schedule for next 24 hours
* encourage them that the most useful thing they can do in the first couple days is to pay attention, read signs, figure out what they need, get introduced to people and ask questions
* point out that being criticized is not meant personally and happens to everyone here
* get set up:
** door tag
** office space
** snack kitchen use
** plate shelf & other storage solutions

=== Check-ins ===
[[Visitor check-in|Visitor check-ins]] should happen once per week. After 3 check-ins, a Visitor may apply to become a Volunteer.

==== 1st check-in ====

* join [[Mattermost]]
* show and explain the task distribution board (hanging next to the main office) and one-time tasks, see [https://pad.kanthaus.online/visitorTaskList Visitor task list]

* 📜 [https://kanthaus.online/en/governance/collectiveagreements#relevant-in-first-days Collective Agreements relevant in the first days]

===== 2nd check-in =====

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

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

=== Before departure ===

* invite to write in the guestbook
* remind them to check all the place they might have stored or left stuff:
** rooms they slept in
** offices they worked in
** towel + bathroom shelf
** plate shelf
** shoe rack
** other storage locations
** vortex
* ask them for their email address if they want to receive our newsletter in future

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

Talk:Hosting

2025-11-26T17:29:43Z

Doug: add "before volunteer evalution" section

== Splitting off group hosting? ==

Although some of individual hosting will be relevant for groups, it is significantly different. [[User:Doug|Doug]] ([[User talk:Doug|talk]]) 14:55, 25 August 2025 (CEST)

== Before volunteer evaluation ==

Hosting visitors is the beginning of onboarding, possibly continuing towards Volunteer and Member. Many things should be known by people ''before'' they become Volunteers in my opinion, including at least the content captured in:

* [https://kanthaus.online/en/governance/collectiveagreements#relevant-in-first-days Collective Agreements relevant in the first days]
* [https://kanthaus.online/en/governance/collectiveagreements#relevant-after-first-days Collective agreements relevant after the first days]
* [[Meeting culture]]
* [[Additional norms]]
* [https://cloud.kanthaus.online/f/921937 Emergency protocols]
* [[Position attributes table]]
* something like [[User:Doug/How to make changes]] (i.e. general advice on how to do stuff without annoying/being annoyed)

We could make understanding this stuff a hard or soft requirement for becoming a Volunteer. But if we only do that, we could (still) end up with 1) people spending a lot of time as a Visitor without knowing this information, and 2) people "cramming" before an evaluation.

My preference would be therefore to spread this stuff across the first 3 check-ins (after which point Volunteer technically possible) in some rational way, at least as recommendations.

[[User:Doug|Doug]] ([[User talk:Doug|talk]]) 18:09, 26 November 2025 (CET)

Talk:Hosting

2025-11-26T17:09:46Z

Doug: /* Before volunteer evaluation */ new section

Meeting culture

2025-11-26T16:59:55Z

Doug: Add "Setting" section

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

== Timing ==
We set clear starting and ending times for our collective meetings: [[CoMe]], [[PlaMe]], [[Social sauna]] & Project Updates. We ask attendees to be on time, which means being a little bit early. It can be nice to announce that a meeting is starting soon, but time-keeping is seen ultimately as an individual responsibility. Always feel empowered to start on time.

Everyone is late sometimes. If it is still worth attending, try to reduce disturbance. It is not necessary to apologize. Be aware that things have been said already and people may not wish to repeat them.

We expect meetings to end at the time set initially. Extensions are possible, but should be proposed and consented in the meeting.

== Setting ==
We take care to hold meetings in a way that allows everyone to focus. Time and place should be considered to avoid possible disturbance from and to non-participants. Participants are encouraged to be mindful of noise and movement they make that might disturb others, and take reasonable measures to reduce their impact: while eating is allowed, please avoid crunchy food, food preparation or using metal cutlery with porcelain; if fidgeting is helpful for you, find something that can be fidgeted silently before the meeting starts.

== Hand signals ==
[[File:HandSignals.jpg|thumb]]To make it possible to give silent feedback we use [https://www.collaborationsuperpowers.com/wp-content/uploads/2020/04/Handout-Hand-signals-for-remote-meeting-facilitation.pdf hand signals]. Their use is to ‘comment’ without disrupting the speaker. We mostly just use:
* 🙌 raised & wiggling ("jazz") hands: agree, sounds good, etc
* ✋ raised hand: I want to speak (next)
* '''T''' "t-shape": technical point (speaker volume, time, language, etc)

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

== Pads ==

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

Occupancy indicator

2025-11-26T13:17:19Z

Doug: Link to "Room reservation" in lede

The occupancy indicator is device used to indicate whether a room or bed is currently occupied or not. This page focuses on the device itself, its design and construction. For using rooms, see [[Room reservation]].

== Indicators for rooms ==
<gallery mode="packed" style="float:right;" caption="indicator states">
File:Occupancy indicator outside free .jpeg|"free" outside
File:Occupancy indicator inside free .jpeg|"free" inside
File:Occupancy indicator outside occupied .jpeg|"occupied" outside
File:Occupancy indicator inside occupied .jpeg|"occupied" inside
</gallery>This indicator is used to show whether a privatisable room is occupied or not. Pulling down the toggle on the inside of the door hides the "free" state and reveals the "occupied" state on the sign outside. When the toggle is pulled down and the door then closed, the cloth is clamped by the door frame, preserving the "occupied" state. When the door is opened, gravity pulls the block of wood down, automatically returning the sign to the "free" state.

=== Current design ===
The current design is the 3rd iteration:
* Old bike gear cable is used. It is freely available anywhere bikes are repaired and very durable. (Brake cable can be used, but it's much stiffer)
* Small wire clamps (bought) are used at end junctions and to limit the toggle distance for the "occupied" state.
* The cloth is a strip of denim. Made by getting an old pair of large jeans, cutting off one leg, opening up one of the seams, sewing it back together as a straight tube, cutting off a slice and punching holes at opposite sides of the slice.
* The cloth is tensioned at each end with a small metal rod with a "C"-shaped bend in the middle. Made by pressing an old bike spoke between an improvised form (i.e. large nut cut in half + fitting metal rod) in a vice. The "C"-shaped bends stick out of the holes punched in the cloth.
<gallery mode="packed" style="float:right;" caption="forming tensioner">
File:Occupancy indicator cloth tensioner start .jpeg|unformed spoke
File:Occupancy indicator cloth tensioner finish .jpeg|tensioner with "C"-shaped bend in middle
</gallery>
=== Previous designs ===
The initial design was simply a sign on the outside of the door with clothes peg, where people could move the peg from "free" to "occupied". While easy to implement, it had the disadvantage that people often forgot to move the peg back to "free" when leaving the room. This lead to multiple cases of a room being unused, sometimes for days at a time!
[[File:Occupancy indicator v2 .jpeg|thumb|200x200px|2nd design]]
The 2nd iteration moved to the gravity-assisted, door-as-a-clamp design seen in the current design. This design used string instead of cable + cloth. While easier to implement, it had several disadvantages:

* The string would wear out through the constant friction, leading to regular breakages.
* Before fully breaking, the string would often get longer, making it less clear which state the room was in.
* Because of low surface area, the string was hard to clamp, often requiring additional material to be added to the door frame.
* The string would wear out a channel in the door frame, accelerating the previous issue.

== See also ==

* [[Room reservation]]

Room reservation

2025-11-26T13:11:51Z

Doug: Link to "Occupancy indicator"

🐚 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:Sheet.jpg|thumb|''the reservation sheet of the Communal Sleeping Room'']]
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.

It is expected that when leaving for a few days or more, the reserved bed would be made available again for other people (by whipping the name from the reservation sheet), and cleared of all personal belongings.

=== 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 4 reservable private rooms: the [[Lantern]], the (original) [[Private]] the [[Hipster room|Hipster]], and the [[Cloud Room]].

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 (and the occupancy indicator should not be used when casually using a room during someone else's reservation).

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

It is expected that when leaving for a few days or more, at least the table space would be made temporarily usable for other people.
[[Category:Social]]
[[Category:Practicalities]]

Occupancy indicator

2025-11-26T13:10:22Z

Doug: See also "Room reservation"

The occupancy indicator is device used to indicate whether a room or bed is currently occupied or not.

== Indicators for rooms ==
<gallery mode="packed" style="float:right;" caption="indicator states">
File:Occupancy indicator outside free .jpeg|"free" outside
File:Occupancy indicator inside free .jpeg|"free" inside
File:Occupancy indicator outside occupied .jpeg|"occupied" outside
File:Occupancy indicator inside occupied .jpeg|"occupied" inside
</gallery>This indicator is used to show whether a privatisable room is occupied or not. Pulling down the toggle on the inside of the door hides the "free" state and reveals the "occupied" state on the sign outside. When the toggle is pulled down and the door then closed, the cloth is clamped by the door frame, preserving the "occupied" state. When the door is opened, gravity pulls the block of wood down, automatically returning the sign to the "free" state.

The current design is the 3rd iteration:
* Old bike gear cable is used. It is freely available anywhere bikes are repaired and very durable. (Brake cable can be used, but it's much stiffer)
* Small wire clamps (bought) are used at end junctions and to limit the toggle distance for the "occupied" state.
* The cloth is a strip of denim. Made by getting an old pair of large jeans, cutting off one leg, opening up one of the seams, sewing it back together as a straight "tube", cutting off a slice and punching holes at opposite sides of the slice.
* The cloth is tensioned at each end with a small metal rod with a "C"-shaped bend in the middle. Made by pressing an old bike spoke between an improvised form (i.e. large nut cut in half + fitting metal rod) in a vice. The "C"-shaped bends stick out of the holes punched in the cloth.
<gallery mode="packed" style="float:right;" caption="forming tensioner">
File:Occupancy indicator cloth tensioner start .jpeg|unformed spoke
File:Occupancy indicator cloth tensioner finish .jpeg|tensioner with "C"-shaped bend in middle
</gallery>
=== Previous designs ===
The initial design was simply a sign on the outside of the door with clothes peg, where people could move the peg from "free" to "occupied". While easy to implement, it had the disadvantage that people often forgot to move the peg back to "free" when leaving the room. This lead to multiple cases of a room being unused, sometimes for days at a time!
[[File:Occupancy indicator v2 .jpeg|thumb|200x200px|2nd design]]
The 2nd iteration moved to the gravity-assisted, door-as-a-clamp design seen in the current design. This design used string instead of cable + cloth. While easier to implement, it had several disadvantages:

* The string would wear out through the constant friction, leading to regular breakages.
* Before fully breaking, the string would often get longer, making it less clear which state the room was in.
* Because of low surface area, the string was hard to clamp, often requiring additional material to be added to the door frame.
* The string would wear out a channel in the door frame, accelerating the previous issue.

== See also ==

* [[Room reservation]]

Occupancy indicator

2025-11-26T13:06:11Z

Doug: Once again, move the tensioner gallery *le sigh"

Occupancy indicator

2025-11-26T13:05:17Z

Doug: copyedit

The occupancy indicator is device used to indicate whether a room or bed is currently occupied or not.

== Indicators for rooms ==
<gallery mode="packed" style="float:right;" caption="indicator states">
File:Occupancy indicator outside free .jpeg|"free" outside
File:Occupancy indicator inside free .jpeg|"free" inside
File:Occupancy indicator outside occupied .jpeg|"occupied" outside
File:Occupancy indicator inside occupied .jpeg|"occupied" inside
</gallery>This indicator is used to show whether a privatisable room is occupied or not. Pulling down the toggle on the inside of the door hides the "free" state and reveals the "occupied" state on the sign outside. When the toggle is pulled down and the door then closed, the cloth is clamped by the door frame, preserving the "occupied" state. When the door is opened, gravity pulls the block of wood down, automatically returning the sign to the "free" state.

The current design is the 3rd iteration:
* Old bike gear cable is used. It is freely available anywhere bikes are repaired and very durable. (Brake cable can be used, but it's much stiffer)
* Small wire clamps (bought) are used at end junctions and to limit the toggle distance for the "occupied" state.
* The cloth is a strip of denim. Made by getting an old pair of large jeans, cutting off one leg, opening up one of the seams, sewing it back together as a straight "tube", cutting off a slice and punching holes at opposite sides of the slice.
* The cloth is tensioned at each end with a small metal rod with a "C"-shaped bend in the middle. Made by pressing an old bike spoke between an improvised form (i.e. large nut cut in half + fitting metal rod) in a vice. The "C"-shaped bends stick out of the holes punched in the cloth.<gallery mode="packed" style="float:right;" caption="forming tensioner">
File:Occupancy indicator cloth tensioner start .jpeg|unformed spoke
File:Occupancy indicator cloth tensioner finish .jpeg|tensioner with "C"-shaped bend in middle
</gallery>
=== Previous designs ===
The initial design was simply a sign on the outside of the door with clothes peg, where people could move the peg from "free" to "occupied". While easy to implement, it had the disadvantage that people often forgot to move the peg back to "free" when leaving the room. This lead to multiple cases of a room being unused, sometimes for days at a time!
[[File:Occupancy indicator v2 .jpeg|thumb|200x200px|2nd design]]
The 2nd iteration moved to the gravity-assisted, door-as-a-clamp design seen in the current design. This design used string instead of cable + cloth. While easier to implement, it had several disadvantages:

* The string would wear out through the constant friction, leading to regular breakages.
* Before fully breaking, the string would often get longer, making it less clear which state the room was in.
* Because of low surface area, the string was hard to clamp, often requiring additional material to be added to the door frame.
* The string would wear out a channel in the door frame, accelerating the previous issue.

Occupancy indicator

2025-11-26T12:50:58Z

Doug: Add "previous designs"

The "occupancy indicator" is device used to indicate whether a room or bed is currently occupied or not.

== Indicators for rooms ==
<gallery mode="packed" style="float:right;" caption="indicator states">
File:Occupancy indicator outside free .jpeg|"free" outside
File:Occupancy indicator inside free .jpeg|"free" inside
File:Occupancy indicator outside occupied .jpeg|"occupied" outside
File:Occupancy indicator inside occupied .jpeg|"occupied" inside
</gallery>This indicator is used to show whether a privatisable room is occupied or not. Pulling down the toggle attached to the inside of the door hides the "free" state and reveals the "occupied" state on the sign outside. When the toggle is pulled down and the door then closed, the cloth is clamped in the door frame, preserving the "occupied" state. When the door is opened, gravity pulls the block of wood down, returning the sign to the "free" state.

The current design is a 3rd iteration:
* Old bike gear cable is used. It is freely available anywhere bikes are repaired and very durable. (Brake cable can be used, but much stiffer)
* Small wire clamps are used at end junction and to limit the toggle distance for the "occupied" state.
* The cloth is a strip of denim. Made by getting an old pair of large jeans, cutting off one leg, opening up one of the seams, sewing it back together as a straight "tube", cutting off slices and punching a hole at opposite sides of the slice.
* The cloth is tensioned with a a formed metal rod at each end. Made by pressing old spokes against an improvised form (i.e. large nut cut in half + fitting metal rod) in a vice.
<gallery mode="packed" style="float:right;" caption="forming tensioner">
File:Occupancy indicator cloth tensioner start .jpeg
File:Occupancy indicator cloth tensioner finish .jpeg
</gallery>

=== Previous designs ===
The initial design was simply a piece of paper and a clothes peg. People simply moved the peg from "free" to "occupied". While this was very simple to implement, it had the disadvantage that people often forgot to move the peg back to "free" when leaving the room! This lead to multiple instances of a room being unused since people assumed someone was in there, and didn't want to disturb by knocking.

The 2nd iteration moved to the gravity-assisted, door-as-a-clamp design currently used. This was done using string instead of cable + cloth. While easier to implement, it had several disadvantages:

* The string would wear out through the constant friction, leading to regular breakages.
* Before fully breaking, the string would often get longer, making it less clear which state the room was in.
* Because of low surface area, the string was hard to clamp, often requiring additional material to be added to the doorframe.
* The string would wear out a channel in the door frame, accelerating the previous issue.

File:Occupancy indicator v2 .jpeg

2025-11-26T12:45:29Z

Doug:

Occupancy indicator

2025-11-26T12:34:13Z

Doug: move tensioner gallery to end

Occupancy indicator

2025-11-26T12:33:29Z

Doug: change gallery class...

Occupancy indicator

2025-11-26T12:32:37Z

Doug: reformat tensioner gallery

Occupancy indicator

2025-11-26T12:31:54Z

Doug: Add tensioner gallery

Occupancy indicator

2025-11-26T12:22:34Z

Doug: Initial

File:Occupancy indicator cloth tensioner start .jpeg

2025-11-26T12:15:14Z

Doug:

File:Occupancy indicator cloth tensioner finish .jpeg

2025-11-26T12:14:54Z

Doug:

File:Occupancy indicator outside free .jpeg

2025-11-26T11:45:38Z

Doug:

File:Occupancy indicator outside occupied .jpeg

2025-11-26T11:45:11Z

Doug:

File:Occupancy indicator inside free .jpeg

2025-11-26T11:44:38Z

Doug:

File:Occupancy indicator inside occupied .jpeg

2025-11-26T11:44:05Z

Doug:

Labeling

2025-11-24T15:49:12Z

Doug: Add "Design" section, remove "Types" section.

Labels and signs are essential for Kanthaus to work. In this article the term "label" is used for smaller signs (e.g. on food containers) and "sign" for those which contain more (abstract) information.

== Application methods ==
'''TL:DR; use patafix—don't use masking tape'''
{| class="wikitable"
|+
! rowspan="2" |Method
! colspan="4" |Surface
! rowspan="2" |Method notes
|-
!Glass
!Plastic (PET/PE)
!Wood
!Wall(paper)
|-
|Thermal labeller
|Good
|Good
|OK
|Bad
|Text deteriorates with heat/light
|-
|Embossing labeller
|Good
|Good
|Bad
|Bad
|Limited character range
|-
|Permanent marker
|Good
|OK
|Bad
|Bad
|Quality depends on handwriting
|-
|Patafix + sign
|Good
|Good
|OK
|OK
|Most flexible
|-
|Sticky paper labels / masking tape
|OK
|Bad
|Bad
|Bad
|Adhesive often only removable with acetone, damaging many surfaces
|}
'''Key:'''
* Good: Label stays in place and can be removed from surface with minimal clean-up and without damage.
* OK: Label mostly stays in place, or removal requires clean-up or leaves visual trace.
* Bad: Label falls off, or removal requires extensive clean-up or damages surface.

== Attributes ==

=== Durability ===
Labels are more or less exposed to decay. They can get wet, oily, hot, sun-bleached and touched in various ways.

=== Informational value ===
The informational value is not only in the sign but is created with the person reading it. This means that there's signage which might contain zero information for members but a lot for visitors. Also vice versa. While creating a sign, it makes sense to think about who is mainly addressed.

== Design ==

=== Contrast ===
High contrast is important for readability and accessibility. The [https://legibility.info/contrast-calculator contrast checker by legibility.info] can help put this in perspective. Unless you have a good reason to do something else, '''black on white is recommended.'''

=== Handwriting vs Printing ===
Handwriting can be hard to read, even though it may add points on the personality scale. If it's important that everyone reads it, '''printing is recommended.'''

=== Case ===
Just write normally and properly. Add emphasis with '''bold''' or ''italic'', NOT BLOCK CAPS.
{{Information|Want to learn more? Check out [https://legibility.info/ legibility.info] offered by The German Federation of the Blind and Partially Sighted (DBSV) based on WCAG and DIN 1450!}}

== Tools ==

=== Printer ===
See [[Printing]] for information on setting the printer up.

Powerhour

2025-11-21T13:45:16Z

Doug: Add "reliability" point to analysis

✨ The weekly communal cleaning session.

== Time and place ==
'''Mondays immediately after [[CoMe]]''' (or at 11 am when there's no CoMe) we stay in the same room to distribute tasks. Then K20 and K22 will be cleaned for a maximum of 2 hours.

== Initial meeting ==
[[File:PowerHourTaskList2024.png|thumb|Power Hour Task List]]
There is a Power Hour Task List for the most relevant tasks.

The facilitator decides how to assign tasks to people.

Usually, it goes something like this:

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

This meeting should not take more than 10 minutes.

== General Info ==
Most cleaning supplies are stored in the [[Intermediate|Intermediate Storage Room]].

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

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

== History ==
In November 2015, during the pre-[[History|history of Kanthaus]] (yunity), several people stayed at the [https://sensor-magazin.de/so-wohnt-mainz-das-liebermenschhaus/ Liebermenschhaus] ("Lovely-people-house") in Mainz. This was a living collective formed by some people of the Livingutopia network. They organized a weekly "Putzparty" ("Cleaning party") which was horribly early on a Thursday (if memory correct) since it was the only time that all the residents where able to make. They would split tasks and clean for an hour or two as their main cleaning action of the week.

Many other experiences were made during the pre-history period, none of which seemed as good. The "Powerhour" was pretty much directly copied from the "Putzparty" and included in the Collective Agreements at the founding of Kanthaus, at 10:00 on Thursdays.

In mid-2023, the time of Powerhur was [https://git.kanthaus.online/kanthaus/kanthaus-governance/commit/75e0172d5c5096681e1268fb872c8b531c0a0564 changed] to after [[CoMe]] (i.e. 11:00 on Mondays) in an effort to "concentrate" Kanthaus activities, to leave people more time to focus on non-Kanthaus things.

== Analysis ==
The topic of communal cleaning is evergreen and there are many systems. The Powerhour has some advantages:

* simplicity: meet at a given time, get task, clean for an hour, done
* regularity: you can plan with/around it (i.e. when Powerhour happens & when house cleanest!)
* mutual-monitoring: everyone is there, everyone sees who gets what task
* reliability: people less likely to forget
* community: doing something together in time can be bonding

== Detailed description of tasks ==

=== [[Power Hour/Main Kitchen|Main Kitchen]] ===
=== [[Power hour/Snack Kitchen|Snack Kitchen]] ===
=== [[Power hour/Bathrooms K20|Bathrooms K20]] ===
=== [[Power hour/Bathrooms K22|Bathrooms K22]] ===
=== Vacuuming Central Rooms ===
* get a vacuum cleaner from the [[Intermediate|Intermediate Storage Room]]
* vacuum all of K20-1 and K22-1 except the staircases

=== Vacuuming Staircase K20 Plus ===
* get a vacuum cleaner from the [[Intermediate|Intermediate Storage Room]]
* vacuum the K20 staircase and whatever needs vacuuming in K20-0, K20-2 and/or K20-3
* skip the basement

=== Vacuuming Staircase K22 Plus ===
* get a vacuum cleaner from the [[2nd bathroom|2nd Bathroom]]
* vacuum the K22 staircase and whatever needs vacuuming in K22-0 and/or K22-2
* skip the basement and workshops

=== [[The Vortex|Vortex Shifting]] ===
=== [[Power hour/Indoor Plant Care|Indoor Plant Care]] ===

=== [[Power hour/Bin Emptying|Bin Emptying]] ===
=== [[Power Hour/Incoming Food Care|Incoming Food Care]] ===
=== [[Power hour/Existing food care|Existing Food Care]] ===
=== Communal Closet Sorting ===
* sort the clean communal clothes into the fitting spots in the closet
* mind the sizes!
* sort out ripped or torn clothes
* fold towels and put them into the closet in the Main Bathroom
* fold tea towels, put them in extra basket together with other kitchen things
* fold duvet covers inside out and in a way that one can read the size written on the bottom
* bring bed cloths, kitchen textiles, clean butt towels and sorted-out clothes to [[Intermediate storage|Intermediate Storage Room]]. Place them in designated boxes.

=== [[Power hour/Basic Workshop Clean-Up|Basic Workshop Clean-Up]] ===
=== Mopping Central Rooms + Main Bathroom ===
* wait for the vacuuming to be finished
* then get a mop and bucket from the [[Intermediate|Intermediate Storage Room]]
* mop the Main Kitchen, the Snack Kitchen, the Dining Room, the Elephant Room, the Main Bathroom
* mop where you think it should be mopped

=== Deep Clean Room of Choice ===
* name one room and give it all your love
* this includes moving furniture to clean underneath, dusting book shelves or anything that’s rarely done

=== [[Power hour/Glass and Pfand|Sort and Return Glass and Pfand]] ===
=== [[Power hour/Clean Sidewalks|Clean Sidewalks]] K18, K20, K22 ===
[[Category:Social]]
[[Category:Regular]]
[[Category:Maintenance]]
[[Category:Meeting]]
[[Category:Repro]]