-
Notifications
You must be signed in to change notification settings - Fork 4
/
running.html
156 lines (124 loc) · 14.7 KB
/
running.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
<!DOCTYPE html><!-- ================================================================
WELCOME TO THE WEBMAKER TEACHING KIT TEMPLATE!
Use this template to create your own teaching kit, lesson plan or educational resource.
Edit the HTML below to add your own content, links and images.
Code comments like these will help with hints and guides.
Need help? Start here: http://mzl.la/teachingkit-tips
================================================================ -->
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
<meta content="teach-kit" name="webmaker:tags">
<link href="style.css" media="all" rel="stylesheet" type="text/css">
<!-- =============================== -->
<!-- ADD YOUR TITLE HERE -->
<title>Mozilla Study Group Handbook</title>
<!-- =============================== -->
</head>
<body>
<div id="ribbon">Mozilla Study Groups</div>
<!-- =============================== -->
<!-- HEADER IMAGE -->
<!-- Just paste the URL for your image in the "src" attribute below -->
<header style="background-image:url(https://s3-us-west-2.amazonaws.com/webmaker-kits/learning%402x.jpg); margin-bottom: 2em;">
<!-- =============================== -->
<hgroup>
<!-- =============================== -->
<!-- TITLE AND SUMMARY -->
<h1>Running a Mozilla Study Group</h1>
<h2>In this chapter, we present some ideas for how to manage your Study Group, suggest events your Group can throw, and outline a suggested program for your first few events.</h2>
<!-- =============================== -->
<!-- Add your name here -->
<h3 id="made-by">Made by the <a href="http://mozillascience.org/">Mozilla Science Lab</a></h3>
<!-- =============================== -->
</hgroup>
</header>
<div class="wrapper">
<div class="row">
<main>
<!-- =============================== -->
<!-- INTRO -->
<h1 id='events'>Managing Your Group</h1>
<p>In what follows, we discuss how to plan and run your Study Group, and describe some possible event types. A few key points to begin with:</p>
<div class='well' style='background-color:#FFF2CC'>
<ul>
<li><strong>Let the community lead.</strong> At every opportunity, ask the attendees what they'd like to see at a future event - and invite them to lead. The more people have a hand in designing and throwing events, the more diverse, useful and community-driven your Study Group will be.</li>
<li><strong>Plan a few months at a time.</strong> Choose a natural rhythm for your group - semesters, terms, or quarters - and try to sketch out a rough plan at the beginning of the period by asking for input from your community, and spreading ideas out.</li>
<li><strong>Communicate clearly.</strong> This means making sure all event listing and emails include time, place (with link to a map) and a short description of what the event is about, and reminding people a couple of times to come on out.</li>
<li><strong>Use your Code of Conduct.</strong> Your Code is there to make sure people feel welcome and are included; don't be afraid to emphasize it and enforce it when the need arises.</li>
<li><strong>Stick to it!</strong> It might take an event or two for people to tell their friends and word to spread; don't be discouraged if only a few people come to your first couple of events. Stick to it, and you'll have a thriving community soon enough.</li>
</ul>
</div>
<h1 id='planning'>Planning Events</h1>
<p>Now that you have a team assembled and a few mailing lists in your community to help spread the word, it's time to start planning and throwing events! Here are a few ideas to keep things running as smoothly as possible.</p>
<h2>Pace Yourself</h2>
<p>Many Study Groups enjoy a ton of excitement and energy when they first get going - events happen every week, attendance is high, and lots of people step up to lead sessions. But, after burning hot and bright for a few months, it can get hard to find a steady stream of content to keep momentum going. Follow these steps to keep a steady pace that's easy to maintain and manage.</p>
<ul>
<li><strong>Choose a natural rhythm</strong> for your community - terms, semesters, or quarters.</li>
<li><strong>Do a big advertising push</strong> at the beginning of each of these periods, letting people know about Study Group, and asking them what sessions they'd like to see or lead. Here are two template emails and surveys to send out: an <a href="https://github.com/mozillascience/studyGroupHandbook/blob/gh-pages/templates/startOfTermLetter1.md">an initial push</a>, and a <a href="https://github.com/mozillascience/studyGroupHandbook/blob/gh-pages/templates/startOfTermLetter2.md">reminder & request for session leaders</a>.</li>
<li>Take the most popular suggestions from your advertising push, and <strong>spread them out evenly</strong> over the term, one every two weeks.</li>
<li>In the free weeks, book events like <a href="event-types.html#coworking">coworking sessions</a>, or other ideas that come up through the term.</li>
<li>Throw in a <a href="event-types.html#hackyhour">hacky hour</a> once a month.</li>
<li><strong>End the period with a get together</strong> for the whole community, to thank them for participating and ask them what they'd like to do next term; this can be as simple as another hacky hour, with a particularly loud advertising push. Also take this opportunity to discuss with the organizing team what worked this term, and what needs improvement.</li>
</ul>
<!--p>Many Study Groups enjoy a ton of excitement and energy when they first get going - events happen every week, attendance is high, and lots of people step up to lead sessions. But, after burning hot and bright for a few months, it can get hard to find a steady stream of content to keep momentum going.</p>
<p>In order to avoid this, it's important to <strong>plan around the right cadence</strong> for your group; for most institutions, this will be terms, semesters, or quarters - whatever the natural division of time is in your community that splits the year up into three or four parts. At the beginning of terms, people's schedules change - some people will become unavailable, and others will find themselves newly able to attend, which makes this the perfect time to do a big push to advertise your group as widely and loudly as possible.</p>
<p>As you advertise at the beginning of each term, ask people to suggest topics for lessons; ask them what they're working on, what they'd be interested in leading a session on, and what they'd like to learn about.</p>
<p>Once responses come in, take the most popular ones and spread them out throughout the term, ideally one every two weeks; that way, both you and your community will have a clear calendar of what to look forward to for the next few months, and you'll save yourself the stress of constantly worrying about what to do next week.</p>
<p>On the off weeks, add in events like <a href="event-types.html#coworking">coworking sessions</a>, or throw in new lessons or event ideas as they come up, and once a month do a <a href="event-types.html#hackyhour">hacky hour</a> to help new people come meet the community.</p>
<p> Finally, at the end of the term, take the opportunity to get everyone together to thank them for participating, and ask them what they'd like to see in future. Also, get together in private with the organizing team to discuss how the term went; what events were the most popular? What didn't go as planned? How diverse across gender, culture and scientific discipline were your attendees? How can you reach an even wider audience next term? At this point, huge congratulations are in order - you delivered a whole term of learning, building and community bonding! Jot down some lessons learned, and next term will be even better. </p-->
<h2>Communicating Events</h2>
<p>Nobody will come to your events if you don't let people know about them! Follow these steps to effectively communicate about each individual event.</p>
<ul>
<li><strong>As early as possible</strong> and at least one week in advance, <a href="https://github.com/mozillascience/studyGroup#how-to-launch-a-new-event">list your event on your website</a>. Detailed instructions are in the README.md in your repo - basically, make an issue that includes the time, date, place (with a map), topic, and preparation instructions, and add a listing on your website.</li>
<li><strong>Focus on the issue tracker.</strong> There can be a lot of links and information for an event - location, lesson notes, examples to download - stay organized by putting all the relevant information in the first post for the issue in the issue tracker, and direct all attention to this issue in subsequent communications.</li>
<li><strong>At the start of the week</strong>, send a reminder email to all the mailing lists you have access to, pointing out the events happening that week (remember to include links to the issues describing the events, as well as a link to your Code of Conduct, and tell people to bring their friends!).</li>
<li><strong>The morning of the event</strong>, comment on the issue describing the event - even a simple 'Looking forward to this today!' is enough, since that will send a notification to everyone watching your repo.</li>
<li><strong>Consider webcasting</strong> your demos, so people can participate remotely. The easiest way to go about this is using <a href="http://www.google.com/+/learnmore/hangouts/onair.html">Google Hangouts on Air</a>, which directly streams your webcast to YouTube.</li>
</ul>
<p>Also, don't forget to ask people to watch your github repo - that way, they'll get updates about everything your Study Group is doing.</p>
<h1 id='reporting'>Reporting Back</h1>
<p>By starting a Study Group, you are joining a worldwide community of like-minded folks, trying to bring their local communities together. The next step, is to help plug your Study Group into the rest of this worldwide network by taking a few simple steps:</p>
<ul>
<li><strong>Ask your demo leaders to post their notes</strong> in their own GitHub repo. Then, <a href="mailto:sciencelab@mozillafoundation.org">send us an email</a> so we can add that lesson to our <a href="https://github.com/mozillascience/studyGroupLessons">collection</a> of lessons from around the world. Of course, this collection flows both ways - feel free to grab lessons from here to deliver at your own group! Also, add a link to the notes repo to the issue created for the corresponding event, and add a <a href="https://github.com/minisciencegirl/studyGroup/blob/gh-pages/lessons/dplyr/lesson.md">stub</a> in your '/lessons' directory in your main Study Group repo.</li>
<li><strong>Let us know about your webcasts</strong> by opening an issue <a href="https://github.com/mozillascience/studyGroupLessons/issues">in the lessons repo</a>. We'll add it to the <a href="https://www.youtube.com/playlist?list=PLyfPqolZyFtyE8zx2Dbm4uqZYQIeL9D9Z">playlist</a> for everyone to see.</li>
<li><strong>Get in touch</strong> with the Science Lab by <a href="mailto:sciencelab@mozillafoundation.org">emailing us</a>, and letting us know what you're up to - we'd love to schedule a monthly catch-up video call with you, to find out what you're up to and answer any questions you may have. </li>
<li><strong>Join in the Study Group Leader's Call</strong>: once a month, we'll be hosting a google hangout for Study Group organizers to share what they've been up to and trade ideas for events and strategies; get in touch with the Science Lab above, and we'll send you the details to join in.</li>
</ul>
<div class='well'>
<h2>A note on Licensing</h2>
<p>In order to share our lesson notes and webcasts most effectively, it's important to license them correctly. The easiest way to do this for a lesson on GitHub is to include a <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC-0</a> or <a href="https://creativecommons.org/licenses/by/3.0/">CC-BY</a> license in a file called LICENSE in the repository; if the repository is mostly example code, consider an <a href="http://opensource.org/licenses/MIT">MIT license</a>. Other open licenses are acceptable, but these are the simplest, and in our opinion, the most effective.</p>
<p>For webcasts on YouTube, it's best if the speaker records & distributes their own webcast on their own YouTube channel. If you want to record webcasts of others on your own channel, you will need the presenter to sign a recording release form, which the Science Lab can help you with. <strong>Never distribute a recording of another person without their written consent.</strong></p>
</div>
<h2>You're good to go!</h2>
<p>After working through the setup and planning in the last two chapters, you are all set to start running a Mozilla Study Group! Remember, this group is for your community - always feel free to remix, reimagine and reinvent anything you like in order to make Study Group what your community wants it to be. The only rule is to always try to include as many different people as possible. Remember to <a href="mailto:sciencelab@mozillafoundation.org">email us</a> as you get started, and never hesitate to make suggestions or ask for help; we look forward to hearing from you!</p>
<p>In the appendices of this Handbook, you'll find a <a href="event-types.html">list of event ideas</a>, and a collection of links to <a href="lessons.html">lessons</a> you can reuse in your own Study Group; as always, please feel free to suggest additions and new ideas!</p>
</main>
<aside>
<!-- =============================== -->
<!-- Contents -->
<section class="teach-list">
<h2>Chapters</h2>
<ol>
<li><a href='index.html'>Introduction</a></li>
<li><a href="setting-up.html">Setting Up a Mozilla Study Group</a></li>
<li><a href="running.html">Running a Mozilla Study Group</a></li>
<li><a href="event-types.html">Appendix: Event Ideas</a></li>
<li><a href="lessons.html">Appendix: Lesson Ideas</a></li>
</ol>
</section>
<section class="teach-list">
<h2>Subsections in this Chapter</h2>
<ol>
<li><a href='#events'>Managing Your Group</a></li>
<li><a href="#planning">Planning Events</a></li>
<li><a href='#reporting'>Reporting Back</a></li>
</ol>
</section>
</aside>
</div>
</div>
<script src="main.min.js"></script>
</body>
</html>