Organizer checklist
Last updated on
14 February 2024
This documentation needs work. See "Help improve this page" in the sidebar.
Checklist for organizing a small contribution event
- Have signage so people know they are in the right location.
- Be really nice to new folks.
- Welcome each person who comes, introduce yourself, introduce everyone else. Say IRL (in real life) names and usernames. Write down names where people can all see them. Point them to the attendee checklist page.
- Tell people if there will be lunch. (Write it down where you are writing down other announcements cause people will come in late and they will be able to catch up.)
- Write down WiFi and password.
- Get people on Slack in #contribute (or another designated chat channel/platform for the event). Because, even when working in-person, Slack is handy to share links and use the bot. And remotely, you get to coordinate, get help, and joke with Drupalers. Also, when participants get used to Slack, then after the event they can continue to stay connected. Write down the Slack channels.
- Get to know the attendees, ask them questions, and then help them choose tasks that are good matches to them.
- Match participants with simple tasks. Especially their first task should be simple so they have success and give them confidence to stay engaged and keep trying.
- Tell participants when they begin to work on issues, to make a comment on the issue saying what they are about to do. This helps to avoid duplicate work.
- Advise participants to reload issue pages before making a comment to see if someone else has commented since the last time they loaded the page.
- Ask participants to paste links to issues they are going to start work on into Slack. (This helps communicate with people around the world, and also makes a record for the organizer of who is working on what.)
- Tell participants that it is encouraged make comments on Drupal.org issues to: ask questions, give intermediate results, etc.
- Have participants work in groups, it encourages collaboration in the community and can help mentors if there are many participants.
- Show participants their drupal.org profile page. Have them add information about themselves and their mentors. Show them their "dashboard" and how to turn on email notifications for issues they follow.
- Take pictures (ask permission), and write down who is there.
- Thank everyone. Celebrate successes, especially small ones.
Checklist for organizing a large contribution event
- Arrive early
- Locate supplies
- Place supplies and signs (make any missing signs)
- Mentors put on sticker name tags: use a thick marker to write your name and drupal.org username on a sticker name tag that can be placed on your shirt (the badges hang below the table edge, and people cannot see them)
- Pre-event mentor huddle
- Select people for workshop vs. mentored contribution room and greetings
- Begin event
- Have participants get sticker name tags (badges hang below the table edge and people cannot see them)
- Have each participant take a stack of all the task cards
- Announce to the whole room
- What will the day be like in general
- Tell folks to chat in Slack, Say hi to their mentor in #contribute
- Set expectations
- It might take a while to find an issue
- We want participants to do the finding, not be handed an issue and why
- Many people 3-5 working on one issue (bug, needs work or needs review) use tags (novice, topical)
- Explain the use of task cards (we should get words for this ahead of time.
- Take attendance. Record time, room, and attendance counts in the event signup Google spreadsheet. Tweet attendance and photo.
- Instruct photographers
- Remind to ask permission
- Get close ups with diverse and happy people (not all serious)
- Post to flickr, get their flickr profile ids of photographers
- Move people from the workshop to the core contribution room. Explain they have graduated from set-up and can now go to the other room to contribute to the project.
- Room announcement:
- Fill out profile
- Work together
- Announce when lunch will be
- Mentor huddle
- Confirm with the committer the estimated time of live commit (make a Google calendar invite)
- Check on participants
- Make sure they post a comment
- Encourage partial/WIP patches/reviews.
- Add RTBC candidates to Google spreadsheet
- Introduce the event sponsor so they can thank the participants and repeatedly mention their company name.
- Lunch
- Review RTBC candidate issues
- Mentor huddle
- Have the mentor and participants go to an experienced mentor and say what all they did (mentors hand out stickers)
- Triple check RTBC candidates
- Remind people to update their profile (with mentor info)
- Make sure people post their particular work, and make comments with questions (is ok to later make another comment answering own questions)
- Take attendance (again)
- Show participants their d.o dashboard
- Room announcement (repeat things that their table mentors have likely said or demonstrated):
- Review accomplishments (expectations, partial work)
- Update profile
- Post partial work
- Dashboard
- Going forward: extended contribution events, at home, set expectations for issues getting "fixed"
- Live commit
- Pick a live commit issue. Make sure at least one new contributor who worked on the issue will stay for the live commit
- Show live commit issue to committer 30 mins before live commit
- Announce in all the rooms there will be a live commit at XX:YY
- Hand out stickers
- at XX:YY re-announce and encourage people to move to live commit area
- Take mentor picture before live commit
- XX:YY live commit. get *all* participants in live commit issue on stage (new contributors, experienced contributors, mentors)
- Lots of folks will leave at this point. totally fine.
- The remaining participants and mentors go back to tables
- Introduce participants to topical tables/maintainers/experienced contributors
- Help people "finish"
- End. Ask people to leave the room. Check the room for power cords or other valuables.
- Break
- Dinner (mentor thank you dinner)
Help improve this page
Page status: Needs work
You can:
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion