Blog RSS Feed Subscribe

Jordi Boggiano

Jordi Boggiano Passionate web developer, specialized in web performance and php. Partner at Nelmio, information junkie and speaker.

Categories

Encouraging contributions with the Easy Pick label

One of the barriers to convert users into contributors in an open-source projects is that many people have no idea where to start. They are usually scared to take on large tasks because they are not comfortable enough with the code-base. Yet I think there are ways you can help them as a project maintainer.

One good way that I found to fix this is to tag specific issues that are a good starting point for new contributors. However I think the practice would be even more effective if more projects did the same way, so that people know to look for it.

The way I do it is using a custom Easy Pick label to indicate issues on GitHub that are just that. Easy to pick up tasks, either because they are small in scope, or just don't involve much in-depth knowledge of the project.

The result of this is a much clearer view of issues. On the Composer project for example if you go in the issues tab and then filter by "Easy Pick", you end up with 14 issues listed instead of 170. A much more manageable amount to look at and pick from, and you are empowered by the knowledge that those should all be reasonably easy to work out.

I have also created this label in the Symfony2 issues a while back. As you see both use the same wording and the same yellow that's one of the default colors on GitHub.

I would love to see this spread because I have already seen it bring in a few new contributors. So if you feel like encouraging people to join in on your project give it a try. And if you feel like giving back this week-end, browse the issues of the projects you use and enjoy. See if you find anything you can help them with.

November 16, 2012 // PHP

Post a comment:


Formatting: you may use [code php] [/code] (or other languages) for code blocks, links are automatically linked. <strong>, <em> and <blockquote> html tags are allowed without nesting, the rest will be escaped.

Subscribe to this RSS Feed Comments

2012-11-16 14:44:38

christian

That's a good idea. Thank you.

2012-11-16 14:50:35

Edorian

I was always a big fan of you doing this. Thanks for the post and for spreading the word. I'll adapt it

2012-11-16 15:15:17

Daniel

Great idea! For both sides, because I for example would love to contribute to a project like Symfony, but am a bit frightened by the "big names" there... So this helps a lot!

2012-11-16 17:11:27

Michelangelo van Dam

I'm in support of this idea as it's always challenging to dive into a new project and fix issues, even if you're an experienced developer.

By using this label, project owners can differentiate the issues in such a way it's easy for everyone to get started.

I like it a lot and will implement this, not just for open-source projects but also for internal projects (for new members on the team).

Thanks for sharing!

Michelangelo

2012-11-17 13:31:32

Richard Tuin

Great idea! I hope that more projects will pick this up, and make the movement even bigger.

2012-11-18 09:50:36

Heikki Naski

This is a great practice. Many projects lose a lot of contributors by never allowing them to easily join the project. The junior contributors might not have enough skills or ability to understand which tasks affect which other things and experienced contributors rarely have a lot of time.

2012-11-25 21:28:31

Willian Veiga

I totally agree. It is helpful. Mozilla uses mentored bugs and seems to be a good idea too.