How to be a successful contributor

Mike McGrath & co. drafted a nice doc titled “How to be a successful contributor” it should help set expectations of and for new contributors. I’ve pasted the first version I have seen but you should go to to see newer versions…

How to be a successful contributor
From FedoraProject


* 1 Audience for this document
* 2 Things to know before you join
o 2.1 Time commitment
o 2.2 Get permission from work
* 3 Joining
o 3.1 Observation
o 3.2 Pick what you want to work on
* 4 Don’t jump into the deep end
o 4.1 First contact
o 4.2 Find a mentor or sponsor
* 5 Contributing
o 5.1 Look for work
o 5.2 Quitting

Audience for this document

This document is targeted at people interested in contributing to the Fedora Project. In the Fedora Project, students, professionals and hobbyists all come together to produce software, marketing materials, art, documentation, etc. We all started as new volunteers at some point. The items below are designed to help you through the process of joining a team. It helps you know what we expect of you and what you can expect of us.
Things to know before you join

Everyone who joins a free software project does so with the best intentions of staying. However, few stay to become regular contributors, and fewer still become leaders within the project. The biggest difference between those that stay and those that leave is commitment and time.
Time commitment

Some volunteers may spend 15-30 hours per week contributing, doing that while holding down a proper day job is a difficult time management skill. As a volunteer, you should ask yourself whether you can devote 2-4 hours per week, even though it’s less than an hour per day. 4 hours a week for most people is an entire afternoon one day. That’s a significant chunk of time.
Get permission from work

There is a mutually beneficial relationship between working for a living and volunteering. Many contributors will find their skill sets at work increase dramatically just by having access to and learning from another environment. This benefits employer and worker. It is completely worthwhile to sit down with an employer or manager and ask for permission to contribute during work hours, even if it’s only a couple of hours on a Friday afternoon. Explain the benefits to you and your employer.

If they say no, then you’ll have to volunteer in your own time.

The single biggest mistake most new contributors make is showing up “just wanting to contribute.” It’s important to take the time to observe the team (refer to the section below) and see how their work aligns with your own skills and personality. Know that getting work to do on day one is very rare, and those who are highly skilled in a specific technology will still have to take the time to get to know an environment before access is granted.

For example, if you’re a database expert it is very unlikely you’ll be given access to databases (where personal info, passwords, etc) are stored within your first several weeks of volunteering. If you’re looking to become an ambassador, it is unlikely you’ll get marketing materials shipped to you in your first week. This may seem unfortunate, but it’s necessary to keep the project members working well together. The same can be said about any major changes, like a complete redesign of a system or a new look and feel for a website. Don’t get discouraged. Show up as often as you can, and get to know the team.

It is important to get to know the organization and teams you are looking to work with before you try to join them. Learn what they do and how they do it, and try to get to know the people involved. It is extremely unlikely you will be able to actually contribute from day one. In organizations with hundreds or thousands of people working together, understanding how things work is critical.

Don’t be shy about asking questions and getting to know people. Plan to spend several days or even weeks attending meetings, emailing on mailing lists and hanging out on IRC before you get to do any actual work. Offer suggestions on topics being discussed, and share any experiences (good or bad) you’ve had that is relevant to the discussion.

Part of observing and making constructive suggestions may require withholding judgement. When making suggestions, don’t assume you come with all of the answers or that the Fedora Project is doing it all wrong. There is a good chance we can improve the way we are doing things, however most of our current practices were developed over long periods of time after lengthy discussion. Your criticism may be better received once you have established yourself in the community and are perceived as understanding our culture.
Pick what you want to work on

It’s your job to decide what you want to work on. Pick something that’s important to you and something you have passion for. You’ll see this advice repeated several times in this document: Don’t just show up looking to have work assigned to you. Get to know the teams and procedures they have in place. Ask questions and really get to know what you’re going to be working on _before_ trying to work on it.
Don’t jump into the deep end

When picking something to work on, don’t be the sole person to take on a huge task as your first contribution. Picking a task that’s too large signifcantly raises the chances of failure. Also don’t pick several things on several teams to work on. Start small, picking at most one or two things, and grow from there. The key is slow, steady, and sustainable growth. Don’t join with the immediate goal of becoming the next leader of the project. Start small.
First contact

After you’ve decided what you’re looking to do and what team you are looking to do it with, it’s time to send an introduction to the list. When sending an introduction (usually by mail list), include the following information:

* Name
* Time Zone / Country
* Basic skills and experiences
* Why you’re joining
* What you’re looking to do (be specific)
* How much time you can contribute (usually hours per week)

If any of the above questions are not clearly answered, don’t send the email yet. You’re not ready. Remember, be specific about what type of work you’re looking to do. Saying “Whatever needs to get done” isn’t helping anyone. Saying “I’d like to help document system A,” “I’d like to translate software for my native language,” or “I noticed this webapp is particularly slow sometimes and I’d like to help fix that” is perfect.
Find a mentor or sponsor

This step is both incredibly difficult and important. Finding a proper sponsor will increase your chances of being a successful contrubitor significantly. Sometimes it’s absolutely required. A sponsor will help with training, introductions and teaching new contributors how a team works.

Most teams have mailing lists. Email the list, say you’re looking for a sponsor, and explain what you are wanting to do. If you haven’t heard back in a few days, reply saying that you are still looking. Keep doing this. Most sponsors are people that have been in the project for a long time, and are often very busy.

They don’t mean to be rude and don’t want to send the impression they don’t want new contributors. It’s just that at the moment, some people will assume other people will take care of you and so for the moment, no one does. This is a common problem — in real life as well as in online communities — and a difficult one to fix. But sticking to it and continuing to ask for help without being annoying will show that you are serious and ready to contribute. Don’t send this kind of message more than once every couple of days, but be positive, and persistent if needed.

Once you’ve got something to work on, it’s time to actually do work. The first several tasks you will work on will likely be small or maybe mundane. Do them consistently, conscientiously and well. This will raise the level of trust you have from the other team members.

As with other volunteer organizations, there are high turnover rates in the free software universe. Training volunteers is time consuming, especially for more complex tasks, and requires a commitment from currently busy volunteers. Spending days or weeks training someone only for them to vanish can be disheartening for mentors and sponsors. By giving out small tasks that have been hanging around, a sponsor can help you take small but vital steps, and learn whether or not the work you’re going to be doing is really for you.
Look for work

If you have access to a repository, system, or content, consider yourself a partial owner. This doesn’t mean you should immediately re-design everything. Remember that other owners have time and effort invested in the current material as well. It does mean, though, that you should take pride in the work you are doing. If you see something not quite right, do research on it and notify the list. Seek work out, keep yourself busy and help others.

If volunteering isn’t for you, that’s OK. You don’t need to be embarrassed that you can’t contribute further. Contributors will not make you feel bad about it either. Realize that lots of contributors come and go every day. Being busy with your day job or not having enough free time is a perfectly valid reason for not being able to contribute. It’s even possible that you might not feel a good fit with the team or organization. You’re entitled to offer help as a volunteer how you want and when you want.

First and foremost, though, don’t just vanish. When a contributor or potential contributor agrees to do work, can’t follow through for a valid reason, and vanishes, the team may not know the work can be reassigned. In some cases, people in the team may even worry about the contributor’s health or well being.

When you’ve decided it’s time for you to go or take a break, let your sponsor or the list know and let them know what you were working on. Having people think you are working on something when you aren’t slows the team down, and ultimately doesn’t benefit you or the team.

Out of Flamewar arises a Phoenix of Hope

I don’t remember the original post that got this whole thing going but in about 24 hours something awesome happened. The Fedora Project has set a goal turning users into contributors. If you have ANY free time and (just about) ANY skill we can find a place for you. One place where people are needed badly is testing. There are just more packages than there are testers, that’s just the way it is. There are only two ways to slove this 1. stop maintaining so many packages. If you cant find people to test it then its obvious no one uses it. This is the wrong answer. or 2. find more testers, this is the right answer. Spot came up with a great idea

… I posit an alternative suggestion:

* At firstboot, the installing user is asked if they would be willing to
participate in user-driven updates testing. It is explained to them that
in Fedora, updates to packages need to be tested by users, and that if
they opt-in, they will be prompted from PackageKit about updates which
need user testing. They can choose an update which needs testing from a
list. Once an update is selected from the list, PackageKit will apply
the update from updates-testing, then open a new window which contains:

* General update testing advice
* Package specific update testing advice (this can live on the wiki)
* A graphical selector for giving +1 (works great!), 0 (cannot determine
state) or -1 (something didn’t work)
* A text box for inputting comments

The user then submits the results, which go into Bodhi. Once results are
submitted, that update no longer appears in the PackageKit “updates
which need testing” list.

If they report a 0 or -1, they are then prompted to back out the update
by PackageKit (at their choice).

* On the backend, should a user choose to opt-in, they would be prompted
to create a FAS account (or authenticate to an existing FAS account)
(e.g. RHN handling in the past). They would _NOT_ be required to sign
the Fedora CLA in order to participate in user-driven testing, as
reported results from QA testing has already been determined to be
non-copyrightable and thus, not considered a contribution.

Each user who opts-in to perform user-driven testing will have it
flagged in their account. Each successful update testing submission will
be minimally logged (package, target, timedate stamp) and a count
incremented for unique update feedback performed.

In thanks for their testing, users will be informed (at firstboot) that
they will receive Fedora swag, both in random drawings and at certain
threshold points (give good feedback on N updates and get a Fedora
Tester T-shirt).

Users can choose to opt out at any time. …

But that wasn’t the only proposed solution. There are some that think that poping crap up at people on first boot is bad form and that we should strive to give people a running functional desktop before we start bothering them. Meh good point. So here was another solution This
one by Mike McGrath.

Random thought: We could put a pretty ajaxy signup thing on that keeps them logged in via community.

I’m thinking of something similar to how works now. With no
login you get the generic pageg. With a login you might get a more
feature rich “targeting contributors” page. If they’ve gone far enough to
do the ajax sign up, we can try to consider them a potential contributor.

This topic is still hot on the Advisory Board Mailinglist , but what are your thoughts? Would you test packages for swag? Would you test packages if there was no swag? Would you be annoyed if this was presented to you at firstboot? Let me know in the comments or link me if you put your thoughts up somewhere eles.