Cookbook: Difference between revisions

From OpenHatch wiki
Content added Content deleted
imported>Aldeka
imported>Aldeka
No edit summary
Line 6: Line 6:
=== Project Nights ===
=== Project Nights ===


Project nights are open "hack" nights typically run by a programming user group.
⚫
A simple way to bring new people into your local tech meetup group (e.g. a Python user's group) is to run a project night. All you need is a venue (preferably with food), a few experienced developers who are willing to answer questions and mentor newcomers, a sign to mark part of the venue your "Beginner's Corner", and friendly verbiage in the marketing copy for the event (we've found that many people find "project nights" less intimidating and macho than "hack nights"). Here is a [https://openhatch.org/blog/2012/the-steps-boston-ruby-is-taking-to-become-friendly-to-beginners/ blog post] describing Boston Ruby's successful replication of Boston Python's project nights.


* Goal of the event: Help newcomers and old hats work on programming projects, while also enabling newcomers through lightweight mentorship

* Photo of one (if available): (TODO)
⚫
* How to run it: A simple way to bring new people into your local tech meetup group (e.g. a Python user's group) is to run a project night. All you need is a venue (preferably with food), a few experienced developers who are willing to answer questions and mentor newcomers, a sign to mark part of the venue your "Beginner's Corner", and friendly verbiage in the marketing copy for the event (we've found that many people find "project nights" less intimidating and macho than "hack nights").
* How OpenHatch usually helps: (TODO)
* Links to blog posts etc. of past instances of the event: [https://openhatch.org/blog/2012/the-steps-boston-ruby-is-taking-to-become-friendly-to-beginners/ Boston Ruby's blog post]
* Links to resources they'll find useful when organizing: N/A


=== Free Software Contribution Workshops for Students ===
=== Free Software Contribution Workshops for Students ===

[http://campus.openhatch.org/ Open Source Comes to Campus]
* Goal of the event: Introduce undergraduate students to the process of contributing to free software and connect them to communities that can mentor them

* Photo of one (if available): (TODO) [https://openhatch.org/blog/2010/photos-from-penn/]
* How to run it: (TODO)
* How OpenHatch usually helps: (TODO)
* Links to blog posts etc. of past instances of the event: [https://openhatch.org/blog/2010/photos-from-penn/]
* Links to resources they'll find useful when organizing: [http://campus.openhatch.org/ Open Source Comes to Campus], [http://penn.openhatch.org/ UPenn's instance of the workshop]


=== Newcomer Inclusion Contests ===
=== Newcomer Inclusion Contests ===

⚫
* [[Starling|Starling bounties]]
* Goal of the event: Bring in new contributors to a FOSS project by highlighting specific, needed tasks
⚫
* [http://mairin.wordpress.com/category/fedora-design-bounty/ Fedora Design Bounties]

* Photo of one:
* How to run it:
* How OpenHatch usually helps:
⚫
* Links to blog posts etc. of past instances: [http://mairin.wordpress.com/category/fedora-design-bounty/ Fedora Design Bounties]
⚫
* Links to useful resources: [[Starling|Starling bounties]]


=== Build-It Days ===
=== Build-It Days ===
* [[Build it]]


* Goal of the event: Bring in new contributors by setting aside time to help them get devel installs of your project set up.
* Playtest your docs


* Photo of one:
* Make a screencast of somebody setting up a devel install of your project and put the video on your Get Involved page!
* How to run it:
* How OpenHatch usually helps:
* Links to blog posts etc. of past instances: [http://mairin.wordpress.com/category/fedora-design-bounty/ Fedora Design Bounties]
* Links to useful resources: [[Build it]], (TODO: docs playtesting guide, devel install screencast guide)


=== Bitesize Bugs ===
=== Bitesize Bugs ===


* Goal: Make it easy for new contributors to find bugs appropriate for their level of experience and familiarity with the project.
⚫
=== Community Metrics ===


* Photo of one:
[http://communityleadershipsummit.wikia.com/wiki/Metrics Notes] from a CLS 2012 session on community metrics, including a [https://dl.dropbox.com/u/6302680/Community%20Metrics.pdf mind map of all (?) the community metrics one might track]
* How to run it:
* How OpenHatch usually helps:
* Links to blog posts etc. of past instances:
* Links to useful resources:


⚫
=== Community Metrics ===
Ubuntu's three-column Trello workflow for tracking package uploaders


* Goal: Know whether or not your FOSS project community is meeting your goals and learn what may be inhibiting community growth
[http://communityleadershipsummit.wikia.com/wiki/Entrance_and_exit_Surveys Notes from Asheesh's session on running surveys]


* Photo of one:
[http://redmonk.com/dberkholz/2012/07/10/how-to-recruit-open-source-contributors/ Gentoo tracking GSoC student retention] using a spreadsheet plus regular check-ins with mentors
* How to run it:

* How OpenHatch usually helps:
[http://meta.wikimedia.org/wiki/Template_A/B_testing A/B testing of Wikipedia revert messaging] to avoid discouraging new contributors
* Links to blog posts etc. of past instances: [http://meta.wikimedia.org/wiki/Template_A/B_testing A/B testing of Wikipedia revert messaging] to avoid discouraging new contributors
* Links to useful resources: (TODO: Ubuntu's three-column Trello workflow for tracking package uploaders), [http://communityleadershipsummit.wikia.com/wiki/Metrics Notes] from a CLS 2012 session on community metrics, including a [https://dl.dropbox.com/u/6302680/Community%20Metrics.pdf mind map of all (?) the community metrics one might track, [http://communityleadershipsummit.wikia.com/wiki/Entrance_and_exit_Surveys Notes from Asheesh's session on running surveys], [http://redmonk.com/dberkholz/2012/07/10/how-to-recruit-open-source-contributors/ Gentoo tracking GSoC student retention] using a spreadsheet plus regular check-ins with mentors


=== Automated Learning Tools ===
=== Automated Learning Tools ===

* (TODO: trypython/tryruby/codecademy/codingbat/etc)
* Goal: Learn programming languages or common FOSS tools without embarrassing yourself or demanding unnecessarily repeated effort from overworked mentors
*[http://openhatch.org/missions/ OpenHatch Training missions]

* [[Mission suggestions]]
* Photo of one:
* How to run it:
* How OpenHatch usually helps:
* Links to blog posts etc. of past instances: [https://openhatch.org/blog/2012/1137-people-have-learned-free-software-skills-with-the-help-of-openhatchs-training-missions/]
* Links to useful resources: (TODO: trypython/tryruby/codecademy/codingbat/etc), [http://openhatch.org/missions/ OpenHatch Training missions], [[Mission suggestions]]


=== Diversity Statements and Codes of Conduct ===
=== Diversity Statements and Codes of Conduct ===


* Goal: Make sure your messaging and community behavior is welcoming, not hostile
* [http://www.dreamwidth.org/legal/diversity Dreamwidth's diversity statement]

⚫
* [https://github.com/ginatrapani/ThinkUp/wiki/Developer-Guide ThinkUp's developer guide]: "Welcome! You are a programmer! The ThinkUp project eagerly welcomes new contributors from all communities, even if you don’t think of yourself as a programmer. (Yet!)"
* Photo of one:
* [http://geekfeminism.wikia.com/index.php?title=Conference_anti-harassment_policy Geek Feminism Wiki's example Code of Conduct for conferences]
* How to do it:
* How OpenHatch usually helps:
* Links to blog posts etc. of past instances:
⚫
* Links to useful resources: [http://www.dreamwidth.org/legal/diversity Dreamwidth's diversity statement], [https://github.com/ginatrapani/ThinkUp/wiki/Developer-Guide ThinkUp's developer guide]: "Welcome! You are a programmer! The ThinkUp project eagerly welcomes new contributors from all communities, even if you don’t think of yourself as a programmer. (Yet!)", [http://geekfeminism.wikia.com/index.php?title=Conference_anti-harassment_policy Geek Feminism Wiki's example Code of Conduct for conferences]


If you have any questions on how to run a successful event or use these materials effectively, or are otherwise interested in open tech community outreach, please sign up for the OpenHatch [http://lists.openhatch.org/mailman/listinfo/events Events mailing list].
If you have any questions on how to run a successful event or use these materials effectively, or are otherwise interested in open tech community outreach, please sign up for the OpenHatch [http://lists.openhatch.org/mailman/listinfo/events Events mailing list].

Revision as of 17:19, 18 July 2012

This is the OpenHatch cookbook -- a catalog of tools and events that we have found useful for growing and improving tech meetups and open source software projects, with materials and instructions for how you can replicate and adapt them for your community!

Introductory Programming Workshops

Curriculum for running an introductory programming workshop for women and their friends. Primary materials are for teaching Python, but we also have resources for Ruby on Rails (via Railsbridge) and Scala (forthcoming).

Project Nights

Project nights are open "hack" nights typically run by a programming user group.


  • Goal of the event: Help newcomers and old hats work on programming projects, while also enabling newcomers through lightweight mentorship
  • Photo of one (if available): (TODO)
  • How to run it: A simple way to bring new people into your local tech meetup group (e.g. a Python user's group) is to run a project night. All you need is a venue (preferably with food), a few experienced developers who are willing to answer questions and mentor newcomers, a sign to mark part of the venue your "Beginner's Corner", and friendly verbiage in the marketing copy for the event (we've found that many people find "project nights" less intimidating and macho than "hack nights").
  • How OpenHatch usually helps: (TODO)
  • Links to blog posts etc. of past instances of the event: Boston Ruby's blog post
  • Links to resources they'll find useful when organizing: N/A

Free Software Contribution Workshops for Students

  • Goal of the event: Introduce undergraduate students to the process of contributing to free software and connect them to communities that can mentor them

Newcomer Inclusion Contests

  • Goal of the event: Bring in new contributors to a FOSS project by highlighting specific, needed tasks

Build-It Days

  • Goal of the event: Bring in new contributors by setting aside time to help them get devel installs of your project set up.
  • Photo of one:
  • How to run it:
  • How OpenHatch usually helps:
  • Links to blog posts etc. of past instances: Fedora Design Bounties
  • Links to useful resources: Build it, (TODO: docs playtesting guide, devel install screencast guide)

Bitesize Bugs

  • Goal: Make it easy for new contributors to find bugs appropriate for their level of experience and familiarity with the project.
  • Photo of one:
  • How to run it:
  • How OpenHatch usually helps:
  • Links to blog posts etc. of past instances:
  • Links to useful resources:

Community Metrics

  • Goal: Know whether or not your FOSS project community is meeting your goals and learn what may be inhibiting community growth

Automated Learning Tools

  • Goal: Learn programming languages or common FOSS tools without embarrassing yourself or demanding unnecessarily repeated effort from overworked mentors

Diversity Statements and Codes of Conduct

  • Goal: Make sure your messaging and community behavior is welcoming, not hostile

If you have any questions on how to run a successful event or use these materials effectively, or are otherwise interested in open tech community outreach, please sign up for the OpenHatch Events mailing list.

All of these materials are both free as in beer and free as in speech to use. If you do use them, though, we at OpenHatch would love to hear about how it goes, either on the Events mailing list or a guest post on our blog!

Retrieved from "https://wiki.openhatch.org/wiki/Cookbook?oldid=9805"