Skip to content

Commit 0306cb7

Browse files
Community_roles (#1695)
* Community_roles * Update common-content/en/blocks/community-roles/index.md Co-authored-by: Daniel Wagner-Hall <daniel@codeyourfuture.io> * Update common-content/en/blocks/community-roles/index.md Co-authored-by: Daniel Wagner-Hall <daniel@codeyourfuture.io> * Update common-content/en/blocks/community-roles/index.md Co-authored-by: Daniel Wagner-Hall <daniel@codeyourfuture.io> * Update org-cyf-itp/content/welcome/day-plan/index.md Co-authored-by: Daniel Wagner-Hall <daniel@codeyourfuture.io> * update to 1 coordinator * wrap change --------- Co-authored-by: Daniel Wagner-Hall <daniel@codeyourfuture.io>
1 parent c7090a5 commit 0306cb7

File tree

3 files changed

+41
-2
lines changed

3 files changed

+41
-2
lines changed
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
+++
2+
title="Weekly tasks for your community"
3+
time=15
4+
hide_from_overview=true
5+
[build]
6+
render = 'never'
7+
list = 'local'
8+
publishResources = false
9+
10+
+++
11+
**Your local CodeYourFuture community is run by the trainees and volunteers**, who are together every Saturday. There are some tasks that must be done _weekly_, to ensure it all runs smoothly. Let's decide who's can help with what?
12+
13+
We need a Coordinator in the community responsible for finding people weekly to do the tasks.
14+
The person in this role should NOT be the one who does that tasks every week.
15+
We suggest changing the coordinator every month, but you can decide what works best.
16+
If the coordinator is no longer able to do this role, please identify someone else who can do it.
17+
18+
Steps:
19+
1. Understand what you should do as coordinator:
20+
- **Lunch**: choose someone for every week who will
21+
- make the list of food that is needed, checking leftovers (if applicable)
22+
- knowing the community's dietary requirements
23+
- choosing who will buy OR communicating with who will buy
24+
- choosing who will help on the day (setting up/clearing out)
25+
- **Energiser**: choosing who will do the energiser in the following week, ensuring it is done every week.
26+
- **Timekeep**: choosing who will time keep, ensure it happens so the class stays on track
27+
2. Share the coordinator name on your local Community Slack so everyone knows who they are
28+
3. Coordinator: identify volunteers for the next 1-2 weeks
29+
4. Repeat this whenever needed
30+
31+
The coordinator role and individual weekly roles are important ways to build a community based on trust and autonomy. But also helps each of you to practice some important **communication, planning and leadership skills**, which you will need for your future jobs in tech.

common-content/en/blocks/wrap/index.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,11 @@ time=20
77
publishResources = false
88
+++
99

10-
You are done for the day. Take a moment to reflect on what you have learned and achieved.
10+
You are done for the day.
11+
12+
Make sure to have assigned the community roles for the next week, if you haven't already.
13+
14+
Take a moment to reflect on what you have learned and achieved.
1115

1216
Stand in a circle and share:
1317

org-cyf-itp/content/welcome/day-plan/index.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,13 @@ time=75
4545
name="Afternoon break"
4646
src="blocks/afternoon-break"
4747
[[blocks]]
48+
name="Weekly tasks for your community"
49+
src="blocks/community-roles"
50+
time=15
51+
[[blocks]]
4852
name="Next Steps"
4953
src="module/fundamentals/next-steps"
50-
time=45
54+
time=30
5155
[[blocks]]
5256
name="Wrap"
5357
src="blocks/wrap"

0 commit comments

Comments
 (0)