Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tips for co-organizers teams #30

Merged
merged 3 commits into from
Dec 3, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/acknowledgements.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Thanks to all contributors to R-Ladies guidance, here and in its previous homes.
_Grácias a todas las personas que contribuyeron al contenido de esta guía, aqui y en los sitios donde estaba antes._

* Current and former [global team members](https://rladies.org/about-us/team/): Alice Daish, Athanasia Monika Mowinckel, Bea Hernández, Chiin-Rui Tan, Christin Zasada, Claudia Vitolo, Erin LeDell, Florencia D’Andrea, Gabriela de Queiroz, Hannah Frick, Jennifer Thompson, Katherine Simeon, Laura Ación, Maëlle Salmon, Nadeja Sero, Noa Tamir, Page Piccinini, Patricia A. Loto, Rachel Kirkham, Saranjeet Kaur Bhogal, Sheila Saia, Sina Rüeger, Yanina Bellini Saibene.
* Thanks also to: Alice Walsh, Andrea Sánchez-Tapia, Denisse Fierro Arcos, Divya Seernani, Ines Teaca, Janani Ravi, Jen Richmond, Jonelle Villar, Julia Romanowska, L. Paloma Rojas-Saunero, Layla Bouzoubaa, Paola Corrales, Silvia Gutiérrez, Vilma Romero.
* Thanks also to: Alice Walsh, Andrea Sánchez-Tapia, Denisse Fierro Arcos, Divya Seernani, Ines Teaca, Janani Ravi, Jen Richmond, Jonelle Villar, Julia Romanowska, L. Paloma Rojas-Saunero, Layla Bouzoubaa, Paola Corrales, Liili Abuladze, Silvia Gutiérrez, Vilma Romero.

Thanks to the [R Consortium](https://www.r-consortium.org/) for funding this project.
_Grácias al [R Consortium](https://www.r-consortium.org/) por financiar este proyecto._
Expand Down
56 changes: 56 additions & 0 deletions content/organization/intro/co-organizers/index.en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
title: "Co-organizers"
menuTitle: "Co-organizers"
weight: 99
---

The more the merrier!
Recruiting co-organizers can also

* help you share the load
* let each organizer pick tasks they prefer (as opposed to one person having to do it all)

## Where and how to recruit co-organizers?

If you're lucky, a member of the chapter will volunteer on their own. :grin:
Sometimes, though, folks need more encouragement.

* If you have someone in mind, talk to them directly. Think of what being an organizer represents to you so that you can tell them that. :wink:

* Have a call to organizers e.g. at the beginning of events. Prepare materials (a slide?) and provide a process for interested folks to talk to current organizer(s) to better understand the commitment.

* If you have a form for asking questions to new members, ask them whether they'd consider becoming an organizer so that they at least know it's a possibility.

* Maybe you will randomly meet your co-organizers at a conference! (when in-person events are a thing again, or in the break-out rooms of an online conference)

{{< tweet 963861899040477200 >}}

* In all cases try to think of how to diversify your team. (We welcome tips!) It might come with diversifying who attends the meetups, by promoting events in different places than usual?


You can point people who hesitate to jump on board to the [intro chapter for organizers](/organization/intro/get-started/#chapter-organizer-why-and-what-efforts).

If some people are happy to help without committing, it's already a great progress for you.
Remind them regularly they could become an official organizer. :wink:

## How to onboard organizers?

* before a volunteer commits as an organizer, an idea might be to have them host (i.e. organize) one or a few meetups (be careful to acknowledge their work although they're not an official organizer (yet)!);

* after that, register them as organizers
* on meetup and
* [at the global level](https://github.com/rladies/rladiesguide/issues/18) (guidance in flux) to have them access your chapter email address; get invited to the organizers slack.
* Locally, make sure to give them access to the needed tools/services e.g. Tweetdeck access to Twitter.

* Point them to this guide (and tell them any feedback is welcome).

## How to organize team work?

* You might assign roles to organizers e.g. one would be in charge of social media for instance;
* Or task assignment can be more flexible. Organizers will probably volunteer to do things that play to their strenghts. You can have a rotation system for some tasks like Twitter and Meetup management.

## Chapter governance

There is no rule around the governance within your local chapter but we encourage you to be welcoming of other volunteers.

[R-Ladies NYC](http://www.rladiesnyc.org/) has a formal governance structure with a board.
6 changes: 2 additions & 4 deletions content/organization/intro/get-started/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,9 @@ Here's what will happen if you want to start a chapter...

If you want to become an organizer at your local chapter, get in touch with the current organizers.

## Chapter governance
## Co-organizers

There is no rule around the governance within your local chapter but we encourage you to be welcoming of other volunteers.

[R-Ladies NYC](http://www.rladiesnyc.org/) has a formal governance structure with a board.
Refer to [the dedicated chapter](/organization/intro/co-organizers)

## Reports by organizers

Expand Down