I seem to have a 24h lag in posting these notes. I'll try to catch up tonight.
Along the "there are so many ways (not just code) to get involved" vein, Dave started describing a few very specific contributor types to get everyone thinking.
- QA people who can turn "it broke!" into "it broke at this minute on this day." (regression windows)
- QA people who can turn "gmail makes my browser crash" into "these 3 lines of code make my browser crash." (Note that the same person may not be good at this and regression windows at the same time - even within what we consider a subset of OSS contributions are yet more subsets!)
Here are some more.
- Writing and pushing press releases to newspapers when a new release of the project comes out. (In general, if you understand marketing and PR, OSS projects need you.)
- Keeping up with and summarizing the floods of information about a project - for instance, Gary generates a map like this every so often of keywords floating across the Sugar universe, and reading the Fedora Weekly News is easier than keeping up with all the mailing lists and IRC channels.
- An anthropology student came to the last FUDcon. She was from outside the Fedora community, and talking with her about her observations on how people worked together was one of the most mindblowing conversations I had all week. Holding a mirror up to communities is very, very helpful.
- License questions? Legal debates? IANAL, but maybe you are!
- Can you run events and meetings? Jump into a project and help the folks there keep themselves on track. The success of the first hackathon I ran can be attributed directly to Omar Pradhan, a former US Air Force Captain with amazing project management skills, showing up and kicking ass in getting everyone on track all weekend (actually, making a track to get on; I'd put out this feebly muddled schedule. Why do I drive events and meetings so hard? Because I watched Omar at my first one.
- Do you copeyedit? Can spel, spot sentence fragments - incorrect grammar? Make things make sense? We need you.
What other surprising contributions have you seen to OSS that you'd like more of? (I challenge anyone to find me a person with the slightest interest in contributing to OSS who can't contribute. Small children, employees of proprietary software corporations with a strict "you can't work on this code" clause, luddites... anyone.)
One of my favorite quotes from the past week:
Every newbie is someone's guru.
They're already interested in and good at something. Find that. As Chris said, "It's not that you need to change who you are to contribute - it's that you need to find out who you are and then how you can contribute who you are." Professors create safe spaces for their students to discover these sorts of things. The rest of us who care about new contributors joining our projects ought to do the same.