The OpenHatch blog is graciously powered by WordPress.
Entries (RSS) and Comments (RSS).

What OpenHatch has taught me

by Kyzz April 22nd, 2014

There’s a saying that goes something like this: “We are what we repeatedly do.  Excellence then, is not an act, but a habit” – Aristotle

 

In my opinion OpenHatch embodies this saying each time I dive deeper into the community.  Although I have yet to contribute much due to time constraints I still find the contributors delightful.  I found myself in the OpenHatch IRC channel asking questions about FOSS and trying to learn, and many people gladly take time out of their day to answer your questions and further your understanding of what you’re working on.  The most shocking part to me was how efficient OpenHatch is about getting people involved in the open source community –  from the ground up.  One of the more interesting workshops the folks over at OpenHatch have been working on is “Open Source Comes to Campus.”  Essentially, volunteers come to your college campus to teach practical skills needed to contribute to open source projects.

I think that open source software is very important to keep around and is a great place to start for people who want to learn.  You don’t even have to know how to code to be a part of something really special – as long as you have some sort of skill you can contribute.  I have yet to have a bad experience with anyone from this community, and thanks to everyone at OpenHatch who has sparked my interests in free software.  Personally, I try to welcome newcomers to the community and answer general questions that may come up.  I also keep up with a few OpenHatch mailing lists and when I have enough time I hope to contribute to the code base.

The biggest thing that I’ve learned from OpenHatch is that no matter how big or small your contribution matters, and it feels AWESOME to be a part of something that might help others.  The second biggest thing I’ve learned is to never be afraid to ask a question, but also don’t forget to listen.  Often times, when you are learning new things it’s hard to understand the first time around.  If you don’t understand, just ASK.  Everyone I have come in contact with in this community has a great humility to them, and they really do help.  To get involved just drop by the OpenHatch IRC channel on freenode!

Before I started frequenting OpenHatch I never found a community that was anything close to the awesome atmosphere for self and community growth.  The first time interacting with a new community online you would generally feel some apprehension.  You may be interested in how to contribute, and all those questions have been asked a million times, but it’s important that your voice is heard!  Although, one thing worth mentioning is that is it NEVER necessary to ask to ask a question – just ask away!

Teaching open source at Rutgers University

by Shauna April 17th, 2014

students at Rutgers OSCTC

On Monday, October 21st, we ran our seventeenth Open Source Comes to Campus event at Rutgers University.  We were invited to Rutgers by Sri Raga Velagapudi, who we met at Grace Hopper Open Source Day only two weeks before.  Myself, Sri, and Prachi Pendse, a CS graduate student, worked hard to pull off a great event on short notice.

This was our first weekday event, and unsurprisingly there were a lot of students coming and going as they fit the event in between classes. Despite being short-staffed (three staff and thirty students made for a 1:10 mentor:student ratio) we had little trouble keeping students caught up.  This was due in large part to the friendliness of the attendees, who often reached out to help students who were arriving late.  We also made use of the What You Missed wiki page.

The event was also shorter than average.  The time was mostly lost from our contributions workshop, the last activity of the day.  This meant that students were only able to get through the first steps of contributing, such as picking a project, and reading through an issue to understand it.  Students got a great deal out of these beginning steps, and did not seem to mind having to stop before they’d even decided what to work on.  This is an important lesson for events with longer workshops: students shouldn’t feel rushed or pushed to contribute, but encouraged to take their time familiarizing themselves the process.

We learned as much as our students did from this event!  We hope to return to Rutgers soon.

Teaching open source at UMass Amherst

by Shauna April 9th, 2014

 

Students working at Open Source Comes to Campus - UMass.

On Sunday, March 9th, we ran another Open Source Comes to Campus event at UMass Amherst.  We ran a first event at UMass last April, and hope to run another next year!  Many thanks to our wonderful in-person mentors Heidi Ellis, Karl Wurst, and Terri Yu, and to our remote mentors Marina Zhurakhinskaya, Sean Lip, Yana Malysheva, and Jacob Davis.

Contributions

  • The first contribution of the day came during the first hour!  One student noticed a mistake in our bug tracker activity and, with our encouragement, filed a bug.
  • During the contributions workshop, two students worked on issues in the Open Science Collaboration blog.  Both involved adding plug-ins to the blogging framework Pelican so the students were able to help each other with the process.  One student gave readers the ability to share individual blog posts via email and social media with the click of a button. Another student gave authors the ability to place parts of articles behind a cut.  Both enhancements have been merged into the project and are being used by the community.
  • One student attempted to work on the Open Science Collaboration blog, but had difficulty setting up Pelican on Windows.  Not to be deterred, she stayed an hour after the event was technically over working with a remote mentor to fix the problem.
  • Mentor Heidi Ellis led a small group of students interested in Mousetrap, a GNOME application that allows users with physical disabilities to move a mouse cursor.  Working together on a single machine, they found and reported a bug that was causing the program to crash.
  • Another student contributed to WelcomeBot, a small OpenHatch project which aims to welcome newcomers to our IRC channel even when no one else is there.  He implemented a vast improvement in how the bot recognizes when it’s being greeted or asked for help.

Notes

  • With deadlines for the Outreach Program for Women and Google Summer of Code coming up, we spent a lot of time talk about opportunities for students and how to pursue them. OPW organizer Marina Zhurakhinskaya talked with students over video chat during our career panel and mentored student applicants during the contributions workshop.  Several students remarked on how much they appreciated her help.  Although the focus we give to internships will vary based on proximity to application deadlines, we plan on highlighting these kinds of opportunities more prominently, and have made a wiki page on the topic to help us do so.
  • We tried out a new version of the Practicing Git activity. We aimed to retain the interactive elements of our typical activity while allowing the tutorial to be lead by a single presenter. The new activity also had the benefit of being not entirely a toy project.  The activity was generally well received, making it a good option for events where only a single mentor is comfortable teaching git.
  • The Contributions Workshop continues to improve.  All but one student stayed through the entirety of the workshop, with more than a third of students continuing past the official ending time.  Two student submitted pull requests to projects later that night.  At the same time, we did have some difficulty connecting students with our remote mentors.  We received a ton of useful feedback from the maintainers of our first OpenHatch-Affiliated Project, Oppia.  We hope that by introducing students to projects before the event, arranging for video-based introductions, and pairing remote mentors with local mentors, we can continue making the Contributions Workshop even more enjoyable.
  • UMass once again opened itself up to students from other schools, and once again Mt Holyoke was well represented.  Given the interest in open source from Mt Holyoke, we hope to run an event there soon!

OpenHatch newsletter, March 2014

by Mike Linksvayer March 31st, 2014

Welcome to OpenHatch newsletter number 20.

French translation of the OpenHatch In-Person Event Handbook.

SpinachCon Zero == A Huge Success! for free software user testing hackathon:

We also have some exciting plans for the future. As you may have guessed by where this blog’s been posted, OpenHatch is going to be the official organizational home for SpinachCon going forward. Once we’ve sorted through the data and suggestions we gathered at the first event, we’ll improve the tests and materials so they can be shared and used at other events. OpenHatch has long been interested in finding more ways for non-technical contributors to participate in the creation of free software, so this is a great fit! OpenHatch already hosts the very popular Open Source Comes to Campus events at schools around the country. We often get asked, “What can we do next?” and hosting a SpinachCon will soon be one of the answers we can give.

Two Open Source Comes to Campus events this month, at UMass-Amherst and City College of San Francisco. Blog posts coming soon. Coming up in April: George Mason University (April 19th), Northeastern Illinois University (April 26th) and MIT (April 26th and 27th). Contact us if you want to get involved!

List of Summer Internships for Open Source Enthusiasts. Still time to apply for several!

How we prepared an open source sprint that converted friends into new contributors. Scroll to the bottom for a bonus ASCII patch-review flow chart.

Two new wiki pages: Contributing to Python and Triaging Python tickets. (“Python has 800 patches stalling on a review. Want to help me review them? Great way to start contributing.“)

New projects in the OpenHatch volunteer opportunity finder

  • ProteanOS is a fully-free operating system distribution of binary packages, configurable for a wide variety of embedded systems. It invites newcomers to help with making and updating software packages, developing distribution tools, drafting technical documentation, and more.

OpenHatchy but not OpenHatch things around the web

Outreach Program for Women wins the Free Software Foundation’s Award for Projects of Social Benefit!

Selena Deckelmann’s slides and speaker notes on What Beginners Teach Us.

RIT launches first minor in free and open source software and free culture.

Introduction to Linux MOOC starting 3rd quarter 2014.

Open Sourcing Feminism: The Challenge of Collective Intelligence in 2014 by Vivien Maidaborn, one of two female founders of Loomio.

Ask HN: Best OSS Projects for Beginning Contributors

Knight News Challenge entry from Sandra Ordenez: Increasing Diversity in Open Source for a Better Internet.

Wikimedia series on Seeing through the eyes of new technical contributors.

Lukas Blakk, Project Ascend Kickoff:

I had an idea to create an open source version and specifically target participants who come from underemployed, LGBTQ, Latin@, and African American populations – aka: people who are terribly underrepresented in tech but also very much more so in Open Source. The idea was that instead of people paying to come learn to become developers in the capitalist, Startup-focused, feeding-frenzy the Silicon Valley promotes we could instead seed other towns, other communities with open source and create an in-depth technical contribution training program that more mirrored the experience I had with Dave Humphrey at Seneca College.

Opensource.com: Academic computer science education group puts focus on open source.

Also check out links submitted to /r/openhatch, and add your finds!

Get involved

You can help write this newsletter! The April newsletter in progress (preview). Join our publicity list or hop on #openhatch with suggestions and questions.

Thanks to Britta Gustafson and Shauna Gordon-McKeon for contributing to this edition!

Read previous newsletters.

Like +1, follow @openhatch at identi.ca or Twitter.

SpinachCon Zero == A Huge Success!

by freedeb March 27th, 2014

Sometimes your favorite free software has a piece of spinach in its teeth, and they need you to let them know.

small-GnashGnuSpinach

We had a really great group at the inaugural SpinachCon. Around 30 people participated in friendly user-testing, aka pointing out the “spinach” in free software. Four projects; Hyperkitty — a user-facing Mailman application, Inkscape — fantastic vector graphics editor, LibreOffice — a free office suite and MediaGoblin — a decentralized media-hosting platform, brought machines and tasks for users to test. We had a mix of people who were in town a bit early for LibrePlanet and locals from our awesome Boston/Cambridge area Desktop GNU/Linux Users group. The end result was a lot of great and varied user feedback for the participating projects over the course of the five hour event.

You might be wondering what kind of feedback we got. There’s a great write-up on what Hyperkitty got out of the event here. A lot of the MediaGoblin and LibreOffice feedback was procedural, which I think is probably some of the hardest stuff for developers to see for themselves. Examples included critiques; “I couldn’t find the search box” and “I thought it was going to confirm, but it didn’t” as well as positive comments like, “I liked the simplicity of the interface” and “The overall feel is nice.” All of the folks who brought projects in for user-testing said they were really glad they did.

As the person who asked everyone to participate, I have a ton of thank-you’s to dispense. Industry Lab was very gracious as we slowly sucked all their spare tables and chairs into the spacious room we took over for the day. MediaGoblin’s technical lead Chris Webber took time out from the middle of a busy funding campaign to set up some testing instances. Robinson Tryon took an incredibly early train down from Vermont to lead people through LibreOffice tasks. Máirín Duffy brought HyperKitty (and her tiny daughter) into the city so we could all see the new face of Mailman. Martin Owens also brought his small daughter in and took notes as people worked their way through Inkscape tutorials. We hit some small snags — not unexpected whenever you’re trying to do something new — so I’d especially like to thank all our attendees for being so patient and understanding. Lastly, thanks to the Open Invention Network for providing USB keys and buying us lunch; lots of spinach salad and plenty of pizza was eaten.

We also have some exciting plans for the future. As you may have guessed by where this blog’s been posted, OpenHatch is going to be the official organizational home for SpinachCon going forward. Once we’ve sorted through the data and suggestions we gathered at the first event, we’ll improve the tests and materials so they can be shared and used at other events. OpenHatch has long been interested in finding more ways for non-technical contributors to participate in the creation of free software, so this is a great fit! OpenHatch already hosts the very popular Open Source Comes to Campus events at schools around the country. We often get asked, “What can we do next?” and hosting a SpinachCon will soon be one of the answers we can give.

In the short-term, we’re looking to schedule another local event. In the spirit of meta-spinach finding, we’d love to hear your comments on how to make the second SpinachCon even better if you attended last Friday’s event. We’ll be announcing the next local iteration via the Boston Desktop GNU/Linux Users group.

Summer Internships for Open Source Enthusiasts

by Shauna March 19th, 2014

It’s the heart of internship application season, and we want to spread the word about opportunities to contribute to open source this summer. The following list of internships are all funded, open to (though not always limited to) students, and taking place over the summer.

Some of these internships are coming up very soon.  In an ideal world, this blog post would’ve been up a month ago.  Our apologies!  Please check the application deadlines first.

Multi-project Programs

The following programs support students working on multiple projects for several different organizations.

  • Google Summer of Code is the largest and best known program supporting student participation in open source.  This coding-focused internship funds thousands of students across the globe as they work on hundreds of open source projects.  The deadline this year is March 21st.
  • The GNOME Outreach Project for Women is like Google Summer of Code, but smaller, not exclusively focused on code contributions, and restricted to people assigned female at birth and/or identifying as a woman, genderqueer, genderfluid, or genderfree (regardless of assignment at birth).  It’s also not limited to students.  The deadline this year is March 31st.
  • Rails Girls Summer of Code is a relatively new program (this is their second year) sponsoring work on Rails and Ruby open source projects.  People who self-identify as female or have experience being socialized female are given preference during selection.  The program is not limited to students, but professional developers should not apply.  The deadline this year is May 2nd.
  • The DataONE summer internship program supports work on projects aligning with DataONE’s mission: “the foundation of new innovative environmental science through a distributed framework and sustainable cyberinfrastructure that meets the needs of science and society for open, persistent, robust, and secure access to well-described and easily discovered Earth observational data.”  Undergraduate and graduate students, as well as postgraduates of up to 5 years, are encouraged to apply.  The deadline this year is March 18th.

Single Project Programs

The following programs support students working within a single organization.

  • Wikimedia’s Individual Engagement Grants support “projects that provide opportunities to reach the Wikimedia movement’s goal of spreading participation in free culture across boundaries of language, gender, and geography. We seek out opportunities for growth in under-represented demographics, smaller and newer Wikimedia projects, and communities in the global south.”  These grants are ideal for people who are already involved in the Wikimedia community and have their own ideas about how to improve it!  The deadline this year is March 31st.
  • Khan Academy, the non-profit education website, is looking for software developer interns “to create a free virtual classroom for the world”.  Their website does not list an application deadline.
  • The Center for Open Science, a new non-profit focused on “improving the alignment between scientific values and scientific practices to improve the accumulation and application of knowledge” has closed their application for this year’s summer interns. Bookmark them for next year!

See something we’ve missed?  Leave a comment and/or add it to our Opportunities wiki page, and we’ll update this post.

Edited to add - Thanks to Ashwini Oruganti (Ashfall on Twitter), we have two more opportunities to list:

  • The X.Org Endless Vacation of Code is a program sponsoring students to work on the X Window System.  They encourage a broad range of proposals, especially technical documentation.  The program is not limited to the summer, and has no application deadline.
  • Summer of Code in Space (SOCIS) is run by the European Space Agency and offers students stipends “to write code for various space-related open source software projects.”  It’s limited to undergraduate and graduate students attending institutions based in specific European countries.  The deadline this year is May 15th.

 

(Written by Asheesh and Britta)

Photo

On Saturday January 4, eight OpenHatch volunteers, new and experienced, gathered in San Francisco to work together on improving the OpenHatch website. We took over a couple tables in a cafe with a sprawl of laptops, cords, huge salads, and people asking each other lots of questions.

To prepare for the event, Asheesh Laroia and Susan Tan followed the In-Person Event Handbook, a guide maintained by Shauna Gordon-McKeon. Susan sent pre-event announcements and acquired a generous food sponsorship from the Python Software Foundation. Asheesh worked on a list of tasks people might work on, and after the sprint ended, updated the list of tasks with their current status.

Out of nine sprinters (Susan, Ni, Nate, Meghan, Mark, Jack (remote), Britta, Becka, Asheesh), four were new or almost-new contributors to OpenHatch — exciting! Thanks to Susan for reaching out to the Hackbright community to help invite new contributors.

More about the structure

New contributors sometimes find themselves lost while trying to find some part of the project where they can make a difference. As part of pre-sprint prep, per the Defining tasks for attendees recommendations, we identified the following categories of useful things to do:

  • Reviewing pull requests that fix existing issues, and giving people feedback, or merging them
  • Fix technical issues that are obstacles for new contributors
  • Read documentation for clarity, and fix if possible
  • Fix high-priority technical issues that are obstacles for users

Within each section, we mentioned specific tasks, including:

  • A plain-English description of what to do
  • An estimate of how long it might take
  • Where to find more information, such as a bug report link
  • The skills and tools needed to achieve the task
  • Who, if anyone, in the room was working on it

You can see a snapshot of that document taken when the event ended.

To help attendees know what to expect, we sent an email to the OpenHatch development mailing list before the event began.

We think that spending time coming up with these categories, and naming specific tasks, helped people understand how they could best use their skills and interests. The plain-English descriptions helped people find something to work on. One person who cares passionately about Python web app deployment found a Heroku-related issue to address; another who loves copy-editing found a way to do that. Yet another person who had her own ideas got to work on them, successfully ignoring the list!

Most of all, since the list was already prepared when attendees arrived, we could focus our mentorship time on answering questions about how to do something, going beyond just what to do.

What we worked on

  • Meghan, a brand-new contributor to OpenHatch (and to open source projects!), tackled a mysterious and strange bug that had been lingering in the bug tracker for a long time: when searching the volunteer opportunity finder, and using voice input (such as on Android), the placeholder text in the search field wasn’t cleared properly. Neither she nor anyone else could reproduce the issue, so she simplified the implementation to use the HTML5 placeholder attribute rather than possibly error-prone Javascript. It’s always a great pleasure when new contributors’ first commits are a net removal of lines of code! Working on this in person supported lots of interactive question-answering, resulting in a stellar, well-tested pull request that was quickly merged.
  • Ni Mu, who had previously contributed to the design of The In-Person Event Handbook but hadn’t contributed much to Python projects before, evaluated a reported bug with the training mission teaching using diff and patch, and closed it as already resolved. Yay for clearing out bug tracker cruft!
  • Nate Aune, a new contributor to OpenHatch, improved documentation of how OpenHatch uses Heroku, and improved code to make the app’s migrations run properly on PostgreSQL, which is the database engine on Heroku. Asheesh merged these changes and added some commits on top to fix small formatting issues.
  • Becka (who first joined us at the 2013 PyCon sprints) read through pull requests, including this very pleasant one, and she learned more about setting up a local environment for working on OpenHatch.
  • Britta Gustafson, who has been a communications volunteer for a few months, wrote down suggestions for homepage improvements (Let’s link important things from the homepage and Let’s also put more social media on the homepage), and she made initial mockups and then discussed them with other contributors. It was pleasantly effective to have an in-person focused conversation about significant visual changes instead of just sharing screenshots via IRC and email. After the sprint, we iterated more on the mockups and Susan implemented the changes, and they are live. Britta also fixed some broken styling that was hiding text in a useful old blog post.
  • Susan Tan, who has been contributing to OpenHatch code for a few months, began the significant task of deleting a feature that hadn’t really worked well for a while — a map on the people search page — which is now successfully removed from the site. She also answered questions for new contributors. Additionally, before the event, she had sent announcement emails and worked with the Python Software Foundation to get food sponsorship.
  • Mark Holmquist (who was a first-time committer at an in-person sprint in May 2012) reviewed pull requests that fixed CSS and wording problems, and he reviewed the text on the Open Source Comes to Campus website, suggesting edits to improve clarity and consistency. These improvements are live.
  • Jack Grigg, a long-time contributor, reviewed some code-removal work first submitted at the Grace Hopper Conference Open Source Day; he revised the commits, and Asheesh pushed them. In the past, we used celery for background tasks; we’ve simplified our codebase to not use celery at all, and this removes all traces of celery from the app.
  • Asheesh, who had the most experience with the codebase, had prepared the list of tasks for new contributors to work on, and worked with attendees to answer questions or review code.
  • Post-sprint, John Morrissey (a long-time contributor who first joined us at PyCon sprints) asked on the email list for more guidelines on how to review code contributions with small issues. In response, Asheesh created an ASCII flow chart.

Thanks and follow-up

A couple things we forgot to prepare, to remind ourselves for next time: a specific plan to take a photo of everyone (our photo is missing a couple people!) and bringing name tags. After the sprint, we walked over to a nearby bar for beer and non-beer, and we chatted some more. (Interestingly, we sent out a post-sprint survey but most participants didn’t fill it out; the events mailing list later had a good discussion of how to get post-event feedback.)

If this sort of thing sounds like fun to you, join the Devel mailing list and stay tuned for the next sprint announcement!

Thanks to Susan Tan and Asheesh Laroia for all their pre- and post-sprint organizing work. Thanks too to all the attendees, in-person and remote.

We’re grateful to the Python Software Foundation for sponsoring food!

If you’re interested in running an event like this for your open source project, check out the Python Sprints website to learn more about food sponsorship, read the In-Person Event Handbook, and join the OpenHatch outreach event community to ask questions!

Bonus for those who scrolled this far

Please enjoy our new patch-review flow chart.


+--------------------------------------------------+
| Is the submitter sitting right in front of you? |
| (A presence in online chat, e.g. IRC, counts.)|
+--------------------------------------------------+
+ +++
yes | no
+ | +
| | +
| | |
v | |
+-------------------------------------+ | |
| Ask them to revise the submission, | | |
| after providing detailed review, | | |
| and make sure to help them resubmit | | |
| in case they have questions. | | |
+-----------+-------------------------+ | |
| | |
| | |
+-----------v-----------------------+ | |
| Did they finish revising the | | |
| submission to your satisfaction | | |
| before they left your presence? | | |
| | | |
+-----------------------------------+ | |
+ + | |
yes no | |
+ + | |
| +-----------------+ |
| |
v |
+-----------------------------+ |
| Merge it (and say thanks!) | |
+-----------------------------+ |
|
+-------+
+-----------------------v------------------------+
| Do you have a reasonable belief that |
| they will respond to feedback within a |
| short period (e.g., 2-3 days, tops)? You |
| might look at their responsiveness to past |
| comments to get a sense of that, and/or their |
| general tone on the pull request, e.g. their |
| degree of tiredness/frustratedness vs their |
| degree of eagerness. |
+------+-----------------------------------------+
+ +
yes no
+ +
v +--v------------------------------+
+--------------------------------------+ | Are they an experienced |
| Leave a comment indicating the | | contributor, whose last commits |
| code style issues you have, | | indicate that their concept of |
| preferably pointing to existing | | code style is similar to yours? |
| OpenHatch docs or mailing list | | (For first-timers, choose "no".)|
| posts about the style, and say that | +---------------------------------+
| you hope they'll get a chance to | + +
| make the desired changes, but even | yes no
| if not, you'll be happy to make them | + +
| yourself and merge it on or after |+-----v---------------+ |
| 3 days from now. Leave a note saying || Do like this, but | |
| if they want more than 3, just ask. || "a month" instead of| |
+--------------------------------------+| 3 days. | |
^ | | |
| +-----+---------------+ |
| | v
| | +----------------------------------------+
| | | Thank them for this |
| | | contribution, and leave |
+-----------------------------+ | a detailed review indicating |
| what changes you would make |
| and that you have pushed their |
| work, with those changes on top. |
+----------------------------------------+

OpenHatch newsletter, February 2014

by Mike Linksvayer February 28th, 2014

Welcome to OpenHatch newsletter number 19.

Our goals in 2014 for Open Source Comes to Campus.

Introducing setup sprints: getting project installation, documenation, and contribution process ready for contributions by newcomers, especially students at Open Source Comes to Campus events.

Things newcomers to open source rarely ask but often wonder, Shauna Gordon-McKeon writes at opensource.com.

In 2014, let’s make open source software more usable, Asheesh Laroia guest-posts on the Open Source Software & Usability blog.

Julie Pichon, [openstack-dev] Interested in attracting new contributors?

OpenHatch doesn’t spam, you get one email a week if one or more people
indicated they want to help. The initial effort is not time-consuming,
following OpenHatch’s advice [4] you can refine a nice “initial
contact” email that helps you get people started and understand what
they are interested in quickly. I don’t find the time commitment to be
too much so far, and it’s incredibly gratifying to see someone
submitting their first patch after you answered a couple of questions
or helped resolve a hairy git issue. I’m happy to chat about it more,
if you’re curious or have any questions.

In any case if you’d like to attract more contributors to your project,
and/or help newcomers get started in open-source, consider adding your
project to OpenHatch too!

OpenHatch discussed on Hacker News.

OpenHatchy but not OpenHatch things around the web

The Ada Initiative on HOWTO design a code of conduct for your community.

Jennifer Dixey:

openhatch.org/ looks a little bit like Drupal Ladders for the whole world of OSS. Contributing is easier than ever! via @thecodepath

drupalladder.org:

The Goal of the Drupal Ladder is to have 1% of the Drupal Community contributing to core.

A week of articles on women in open source at opensource.com.

A career panel of sorts, in an article: These Women Are Building The Software That Quietly Runs The World.

Women Outnumber Men For The First Time In Berkeley’s Intro To Computer Science Course; will they have the opportunity to contribute to open source? Related: Can early computer science education boost number of women in tech?

The Scistarter project finder is a little bit like the OpenHatch volunteer opportunity finder, but for science projects.

Also check out links submitted to /r/openhatch, and add your finds!

Get involved

You can help write this newsletter! The March newsletter in progress (preview). Join our publicity list or hop on #openhatch with suggestions and questions.

Read previous newsletters.

Like +1, follow @openhatch at identi.ca or Twitter.

Introducing setup sprints

by Shauna February 27th, 2014

Oppia banner

On Tuesday night we had our first official setup sprint - an IRC get together where OpenHatch volunteers test an open source project’s installation and contribution process and documentation.  Our inaugural project was Oppia, a tool which helps non-technical users create interactive educational activities online.  Three volunteers (Carol Willing, Anurag, and myself) spent two and a half hours working with Oppia maintainer Sean Lip testing and improving documentation.  The quick, casual feedback process meant we made a bunch of changes, including restructuring the documentation to be easier to navigate, adding explanations (and/or links to tutorials/guides) where documentation was too terse, and changing the output of the testing suite to be more understandable.  We also managed to create the project’s 100th issue.

Although there’s always more work to do, we’re pleased to say that Oppia is ready for students to contribute to at our Open Source Comes to Campus events, including the next one on March 9th at UMass-Amherst.

If you’re interested in welcoming new contributors to your project by having it featured at our events, check out our OpenHatch-Affiliated Projects page.  It explains in detail the steps needed to get your project ready.  It also explains why we run setup sprints: “A sprint will help you quickly find and fix problems with dependencies, documentation, and more.”  Or, as Sean remarked during the sprint: “It’s very helpful to have a tight feedback loop with these things.”

If you’d like to contribute to open source projects by participating in these sprints, let us know and we’ll make sure you get a heads up before they happen.  The next one should be soon!

Goals for Open Source Comes to Campus in 2014

by Shauna February 7th, 2014
Goooals.  Photo CC-BY-SA by Thomas Leth-Olsen.

Goooals. Photo CC-BY-SA by Thomas Leth-Olsen.

At OpenHatch we have big dreams. One of them? Keeping better track of our dreams.

When we sat down a few months ago to make a plan for 2014, we regretted not creating clear and public goals at the start of 2013. By committing to specific goals, and promising to measure and report the results, we’re pushing ourselves to make progress.  In the spirit of progress, here are our goals for 2014.

Increase the number of Open Source Comes to Campus events, and make them easier for others to run.

Why: Last year we had many more invitations to run events than we, with our small team, could possibly accept. We’re only human – and we don’t want our humanity to keep students from being introduced to open source! While we will continue planning and attending workshops ourselves, we’re focused on making it so anyone, anywhere can run an Open Source Comes to Campus workshop.

How: In phase one, we documented our planning process and put all of our materials – curriculum, publicity, etc – online. Phase two, currently underway, involves recruiting schools to run events and using their feedback to improve our process.

Measured by:

  • Number of events: We hope to double the number of Open Source Comes to Campus events, from 12 in 2013 to 24 in 2014.
  • Feedback from events: For each event, we will elicit feedback in the form of surveys from students and mentors, and have debriefings with organizers. We hope to see a positive trend in the surveys. A positive trend would be an improvement of the average rating by 1 point or more (on a scale of 1-4).
  • Hands-off events: We plan to run at least one event with minimal-to-no involvement on the part of OpenHatch organizers. We hope our surveys show that these events are just as successful as those we have a more active role in.
  • Repeated events: It’s as good a sign as you can get when organizers want to run more events. We’re hoping to run at least six repeat events this year, and for at least half our event organizers in 2014 to express interest in a repeat event.

Improve the Open Source Comes to Campus curriculum

Why: We’ve worked hard on our curriculum, and have seen the payoff from that in a few key areas. Over the course of eight months and a lot of trial and error, our introduction to version control went from a confusing, too-long lecture to a well-liked, hands-on activity. We want all of our curriculum to be as well-received as Practicing Git – and we’d like to offer more curriculum options for organizers, so they can tailor events to the needs and interest of their participants.

How: Through feedback, we’ve identified the ‘Contributions Workshop’ as the element of our events that needs the most work. We’ve also identified the ‘History and Ethics of Free Software’ section as needing significant improvement. We will continue to brainstorm ways to improve the activities and test those changes by eliciting feedback from attendees and mentors. We’ll also talk to event organizers and community members about what new curriculum elements to add and how to add them.

Measured by:

  • Existing weak areas: For the ‘Contributions Workshop’ and ‘History and Ethics of Free Software’, we hope to go through at least one new iteration of the activity, and to see a positive trend in survey evaluations of these activities.
  • New sections: We hope to add at least two new sections to the curriculum. Current ideas for sections include more openly discussing the mental blocks that keep people from contributing to software, an expanded IRC activity, and an introduction to Linux (either through installations, or a virtual machine).

Partner with open source projects to help students form relationships with communities.

Why: While it’s great to see students submit pull requests at our events and get their changes merged, the truth is that most open source contributions – especially to new projects – don’t take place in an hour or two, even for open source veterans. We’re refocusing our efforts on helping students connect with open source projects that will welcome them into their communities.

How: We’re going to recruit OpenHatch-affiliated projects to participate in Open Source Comes to Campus. We’ll work with these projects to improve their guides and introductory materials, and to help them identify good tasks for students. After events, we’ll help projects follow up with students. We’ll be a resource to help students continue to contribute.

Measured by:

  • 10 OpenHatch-affiliated projects: We hope to have at least ten such projects actively participating in our events by the end of the year.
  • 2 new contributors per project: For each affiliated project, we hope to help them find at least two ongoing contributors from among our students. An ongoing contributor is a student who has made at least one new contribution to the project, separate from what they worked on at the Open Source Comes to Campus event.

Keep students involved in the community after events are over.

Why: We’ve been so focused on improving our events that we’ve neglected the important work of following up with students and seeing how involved they’ve become with open source. While there’s a lot of value in simply knowing more about open source and how to use it, we do hope that some of our students continue to contribute to the community. We want to see if our students are staying involved and, through outreach, help them do so.

How: Most students will work one-on-one or in small groups with at least one mentor during the event. We will ask mentors to take brief notes on their students – their level of enthusiasm, their interests, and the types of problems they encountered. We will also gauge student interest through our exit surveys. We plan to follow up with every student who submits an exit survey as well as every student we receive feedback about from a mentor. Additionally, we plan to do some community-building around OSCTC alumni and organizers.

Measured by:

  • Identifying students: We will attempt to collect contact information and notes on interests and goals for at least half of students at each event.
  • Following up with students: We, or a local organizer, will attempt to follow up with 100% of students we’ve collected contact information for. We hope that 20% or more of those students will go on to participate in the community (or will already be doing so).
  • Community events: We plan to host community events for students, including: a monthly online meetup for OSCTC alumni on IRC; a monthly online meetup for OSCTC and other open source organizers on IRC; and 5 in person meetups for alumni in Boston and San Francisco.
  • Using the mailing list: Our alumni mailing list is currently very quiet. We plan to start sending a monthly email to attendees letting them know about opportunities available to them and events in their area.

How you can help

If you want to help us reach our goals, there are a lot of things you can do.

To help us increase the number of Open Source Comes to Campus events you can invite us to your school!

To help us improve the Open Source Comes to Campus curriculum you can test out our current curriculum and give us feedback. This is especially great if you’re new to one of the topics, such as git, or navigating bug trackers. You can also help us develop new activities.

To help us partner with open source projects you can talk to us about what it would take to make your project an OpenHatch-affiliated project.

To help us keep students involved in the community you can send us information about opportunities such as Google Summer of Code or good tutorials/resources that we can send their way.

Watch this space

I’ll be revisiting this post over the course of the year to check our progress towards our goals.  And in December, I’ll make another post letting you know how we did.  See you then!