Taking a break

[cameronmcefee]

Hi All,

For the last year and a half-ish, I've been seeing to the health of GitHub's CoderDojo, done most of the admin stuff, and have generally tried to lead the organization of things. Over the last few months we've taken on some awesome new mentors. With our last session we had more mentor involvement in the "process" of the dojo than ever before. Whereas in the early days I was concerned things wouldn't happen if I didn't push them, now I feel pretty comfortable that the show can go on without me. You guys are awesome.

Taking a break

I'd like to start phasing myself out of CoderDojo. It's been a great ride, but I'd like reduce my responsibility a bit so I can move on to new things. I still plan to be involved as a mentor here and there, but it's time I learn to not be the single point of failure for organization and admin.

I've mentioned it to a few of you at sessions but I won't be around for our next few sessions due to needing a break from things, as well as some family stuff that will have me out of town sporadically for the next few months.

Going forward, I'm hoping that you guys can self organize and keep things going. For now I'll leave things up to you, but if nothing starts up in the next few weeks I might bug a few of you to try taking on some responsibility to move things forward.

GitHub has officially moved offices, but the first floor where CoderDojo sessions will be held is still under construction. It will likely be completed in early October, so our next session could probably start late October/early November.

A plan

So that I don't leave everyone totally hanging, I figure I'd draft up a game plan that can be followed if you guys aren't sure where to start. Feel free to follow it or don't. It's your world now.

• I've created an admin repo that has log in details for our sites and a wiki for the admin side of running a dojo. If you'd like to help out with things like creating events and answering email, let me know and I'll add you to the repo.
• I'd suggest picking someone to that is the primary responsible person for the next event. This person doesn't necessarily have to run things, but their job is to make sure things are healthy. They'll probably start the discussions, organize the meetings, and make sure there are enough people/mentors/etc
• Create an issue in Lesson Plans to kick off the discussion.
• Meet up a couple times to sort out the main lesson concept, technology, teachers, and dates.
• A GitHubber doesn't need to be in charge of things. Our non-GitHub mentors are awesome people too.
• At least one GitHubber should be present at all sessions, to make sure people can get in, answer questions, etc.
• When new people express interest in being mentors, take them out to lunch first to make sure they're not creeps. If you're not comfortable with them or they aren't pleasant, then they're probably not a good fit.

  Fear not

I'm not totally checking out. I realize I haven't done a very good job of sharing institutional knowledge about the dojo process. I'm happy to answer questions if you ping me, and I'll do my best to flush out the admin repo wiki as we come across undocumented stuff.

I'm also around to help with the direct GitHub stuff like locking down dates so the office is available. Consider me a contact at this point rather than a direct contributor.

My hope is that — while this transition might be abrupt — it'll set our dojo on track to be mostly self sustaining. Hopefully we won't ever need a single leader but will be able to instead spread the responsibilities around. Once things in my life settle down a bit I'll be back to be a mentor and socialize with you fine people. It's awesome knowing that I can take a break like this and everything won't fall apart. You guys are rad.

cc @CoderDojoSF/mentors

[mikefowler]

Thanks for all the guidance, @cameronmcefee :P

I'm interested in helping out with the general running of things, please go ahead and add me to the admin repo.

[donjo]

Thanks for doing all that you've done in the last 18+ months @cameronmcefee and enjoy your well-deserved break. CoderDojoSF couldn't have taken off without you and the help that you and the :octocat: organization have provided has been invaluable. We'll keep the :ship: sailing while you're out.

[dgbeck]

Yes thanks Cameron. Your efforts are very much appreciated and have enabled much learning and growth all around.

I am interested in helping out with the lesson plans, will leave some feedback on the kids suggestions there shortly.

[marcyDel]

Hey Cameron. Great work to date!! I wouldn't have been able to start the Mountain View dojo without having you blaze the trail. Hope to see lots of great sessions up at the new GitHub location!

Also, if GitHub ever wants to get more parents invested in the program, I'd be happy to brainstorm or offer whatever help I can, even tough I am from the other planet, way down South.

For any of you curious about the goals for Coderdojo Silicon Valley, Mountain View read on…otherwise, hope to see you soon!

Mountain View plans:

1. Monthly intro to programming sessions at Microsoft. Focused on Scratch or Tynker. The goal of the session is to introduce beginners and parents to programming tools and resources.
2. Attain lead presenters for intermediate/advanced, small breakout, programming sessions on Python, HTML and mobile app development (Corona/SDK?).
3. Plan two all girls sessions in the winter and summer
4. Plan a programming science fair for next summer - maybe tie in with Ireland's Coolest Projects Awards
5. Attain a fiscal sponsor and/or a program owner to help raise funds for mentor and participant hospitality, as well as support special events
6. Find a team and lead to implement belts and badges. Simple implementation at first for attendance, youth mentor opportunities and social good.
7. Find middle and high school students who know Scratch or Tynker to mentor at monthly intro sessions. Assign community service credits for participation.
8. Assign 4 key organizer positions who agree to meet monthly to check in on goals, fundraising and memberships. Hold monthly drop in meetings for any interested members.
9. Set up GitHub as our main repository for projects and communication conduit for mentors.

On Aug 7, 2013, at 12:21 PM, David Beck notifications@github.com wrote:

Yes thanks Colin. Your efforts are very much appreciated and have enabled much learning and growth all around.

I am interested in helping out with the lesson plans, will leave some feedback on the kids suggestions there shortly.

— Reply to this email directly or view it on GitHub.

[marcyDel]

Oh, BTW, that last email was from Marcy. Keep forgetting, my email say "get2greg" ;-) Ugh.

Take care all!

Marcy

On Aug 7, 2013, at 12:21 PM, David Beck notifications@github.com wrote:

Yes thanks Colin. Your efforts are very much appreciated and have enabled much learning and growth all around.

I am interested in helping out with the lesson plans, will leave some feedback on the kids suggestions there shortly.

— Reply to this email directly or view it on GitHub.