Copied over from Borderland: a template for responsibilities:

This description is meant to be changed by YOU.

### What is this responsibility?

Describe the responsibility. What is done, and why? Think about the need that is being fulfilled. How does this responsibility fulfill that need?

Give a summary of what this responsibility entails. Give links to Talk threads.

### Who could realize it?

What knowledge or skills does the Kiez Burner realizing this need to possess or learn? Are there any requirements? For example, the person driving the truck should probably have a license.

### What tasks are involved?

Note that a task and responsibility is not the same thing. A task can be finished but not all responsibilities are tasks that can be finished. Examples of responsibilities that is not a task are "Point of contact for authorities" and "Maintain Realities platform". Most responsibilities on Realities are not tasks. In that case, we list the tasks involved in the responsibility here in the description. There is no hard rule for when something should become its own Responsibility and when it should just be listed as a task for a responsibility. Use your own judgment, we're still experimenting with Realities.

* If there are tasks, list them like this

* List them in bullet points

* Lovely little bullet points

### What the hell are dependencies and deliberations

Delete this section, it's just a tutorial for you that created this responsibility.

* Right now, a Deliberation is just a link to anything. However, in the future Realities will automatically index all threads on Talk, and when you add a deliberation link to Talk, that Responsibility or Need will be shown alongside the thread on Talk.

*A dependency is something that this Responsibility depends on* in order for it to be realized. For example, a power grid depends on a placement map. In the future, this will use these dependencies when running advice processes. For example, someone who wants to make a decision about the placement map can see that the power grid depends on the placement map and that they should ask that realizer for advice. Very soon, Realities will also have email notifications to notify everyone who depends on something when that thing changes or loses its realizer. Pretty cool huh? So help us for the future of a brighter tomorrow, and add dependencies now, and making decisions will become much easier in the future.

### Post Mortem 2019: link

I edited the thread. It is very long now, but it is an important topic. Thanks for taking the lead @Veroca R. Sala !

I deleted 2 things where I am not sure what they mean:

• Makes sure The Talk threads of the previous year go to Archive ( this means not necessarily doing it but, opening a thread and see if someone is up to do that, make a follow up etc)

• Makes sure Talk Archive is added  to the Index of the General KB Guide.

I love the role of documentation lead (which is basically responsible for most of the Realities setup as well). Just please be aware that, if you are committed to making the guidelines per need, there will be a substantial portion of work needed from the documentation lead. Leads of previous years might communicate work done, but it will be up to the documentation lead to structure it.

Added the following needs:

• Guide "how we work together"

• Leadership succession

• Consent guidance

• Conflict resolution

• sound

• census

• Board & advisors

• Finance

reworded some of the needs to be a bit broader or clearer.

I would also suggest to add a need:
regulations: permits & inspections

• coordinate structures that need special permits

• event permit application

• fire safety protocols & evacuation plans

• onsite constructions inspection

• onsite inspection with the fire department

@Jan Thomas and @Alexxx does that regulation need & those responsibilites make sense to you?

@Jan Thomas perhaps when you do your documentation 2019 you could already separate all "permit" stuff related. would be great, so its easier for the person that would eventually take on Permit. =)

@Veroca R. Sala or @Christoph Völkl or @Keegan what do you think about presenting the current progress on Realities in the 1st Leads meeting?

Thread updated. Struggling with the marking down. If anyone Volunteers to make it look nicer, would be good, if not I thank only for reading this thread.🙂

Thread updated

I copy paste this comment from @waldo that was done on other thread cause i think it belongs here and I find interesting for next year.

"And btw, I would personally hope that Realities becomes a volunteer portal where things are self-explanatory for people. They choose what they are interested in and can find their way through the linked Talk threads and information present in Realities"

would it make sense to have a sort of a landing page before what we have now on Realities? A landing page where is explained different ways of volunteering as its said in the "How to volunteer" thread, perhaps better 😆 Or how do you envision this?

I see the Website is good for the whole, but i do think that Volunteering deserves more attention in regards of how do we pretend to get people involved. It need more clear and unified info, specially for the pre event.

Realities without an explanatory and also sensitive content about how to get involved, it ends up being only a cold organizational mapping.

Thread Updated

Realities needs a Description box to put above all the Needs and Responsibilities as well as a Landing page where to have it all explained in detail

In this Drive Doc we are working on the Realities Landing Page content and the Realities description for the platform itself.

I suggest adding in the description of all the Needs. As a task: "to open a thread on Talk" followed by a link to "I'm a Realizer, and now what" (btw The content on that thread needs some work and I would love your feedback @waldo ) and hopefully a link to the Talk code of conduct.

I think by adding this task on Realities we would save some effort on guiding and also making clear that to get involved and become a Realizer, also requires being active on Talk and making the process public to the community and other Realizers.

I perceive some fear from people to jump in actively on talk. This means volunteers might do ( at least in the beginning) most of their work out of Talk, which leads to miscommunication and I'm sure making them feel lonely in their role.

I personally had that feeling myself ( until you push me forward with this thread 🤗)

Concerning the fire safety, evacuation plans and first aid.

I think those 3 should be combined under one lead but if we do first aid on our own again it should have a sub lead, as it becomes quiet a lot to organize.

Alex as former fire lead and I had a talk already and I agreed to volunteer for fire safety as it is easy for me to liaison with the firedepartment and its my field of work anyway.

If I have contact to the former lead/creator of evacuation plans and protocol, I would be interested in taking lead for this field.

@waldo I like the idea of covering all these needs, and also breaking down some roles that are a bit heavy. Question is: based on what exactly do I create the description & responsibilities list of these new "roles" you suggest up there ?

If we put a nice explanation on top of realities, maybe with some visuals,realities could definitely be that pre-event volunteer portal,oder?Of course it could also be a landing page before that,which could be the website?

I see it was not very much clear. I meant the Documentation Lead would also:

• make sure the talk threads go Archive: its basically what you did a little while ago when you opened the Kiez Burn 2020 kick off.( i cant find that thread now or perhaps got modified). It meansTaking all the talk groups together and place them on a Archive Kiez Burn 2019 folder.

• About the documentation Lead: we should establish a timeline to do these tasks

1. reminding leads to write their documentation . (shortly after the event?)

2. clear up talk . (it cant be done straight away after the event, but in January?

• Also According to what i see in this thread, still we are not covering with the Documentation Lead the tasks of :

1. making sure realities is cleared up

2. setting up the new realities

• Now we have more "needs" on Realities. Th Doc. Lead this should be a role for a Lead and a Co-lead. Specially for structuring and reminding to get the documentation done. Although we wish to make it as easy as possible so Leads can do this themselves mainly. Hopefully, may be... we still dont count on that one... but we wishhhh 🤗

I like the idea of breaking "permit" out from "site liaison" as these can be nicely separated. I would however focus the role on

• event permit application

• coordinate structures that need special permits (as it's part of the permit process) - in Mecklenburg-Vorpommern this would have been any "fliegende bauten" ie tents etc. above 75 square metres of floor space

• onsite constructions inspection - if related to permits

The other aspects relating to fire seem to better fit with the existing "Fire Safety" need.

Also there could be a bit of overlap with the "Legal & safety" need, even though according to 2019 realities the better name for this would have been "Insurance". Might be worth deciding under which need things like checking the safety of what our participants build is situated? My gut would say to place that under "Legal & Safety"

The fire department tend to do their own onsite inspection at Freiland. But other locations might want a more hands-on approach for sure. Otherwise it makes sense from the fire side

@Holger Wessels perhaps has got an opinion regarding this?

I think it will be good. I'm hoping to come in remotely but not sure what my internet is going to be like so will see on the day if I can contribute much