Proposal: "Good first contrib" tag on github issues


#1

Ohai Chefs,

I saw an interesting idea on the Ratpack[0] Github issue tracker. They have
a Tag for “Good First Contribution” for newbies to find an issue and
contribute a patch back. It can be daunting looking through 100’s of issues
trying to find one that is simple to start and not a rabbit hole. Also the
tag could also mean the person reporting it or who tagged it could help
guide the person through the issue.

Also this is helpful when running a Chef Hackathon or Hacker Garden[1] to
help new people contribute back in a short amount of time.

I participated in the Hacker Garden at GR8Conf, was a lot of fun to
contribute a feature back in ~3 hours to Ratpack.

Thanks,
-Eric Helgeson

[0]

[1] http://hackergarten.net/

  • Different than a hackathon, not competing to win but tending the garden
    of our software community (bugs/docs/features/etc).

#2

I think this is a great idea. Perhaps we should raise that at the dev meeting?

An example of a bug that I think is a “good first contribution” one:

  • Julian

On Mon, Jul 14, 2014 at 8:40 AM, Eric Helgeson erichelgeson@gmail.com wrote:

Ohai Chefs,

I saw an interesting idea on the Ratpack[0] Github issue tracker. They have
a Tag for “Good First Contribution” for newbies to find an issue and
contribute a patch back. It can be daunting looking through 100’s of issues
trying to find one that is simple to start and not a rabbit hole. Also the
tag could also mean the person reporting it or who tagged it could help
guide the person through the issue.

Also this is helpful when running a Chef Hackathon or Hacker Garden[1] to
help new people contribute back in a short amount of time.

I participated in the Hacker Garden at GR8Conf, was a lot of fun to
contribute a feature back in ~3 hours to Ratpack.

Thanks,
-Eric Helgeson

[0]
https://github.com/ratpack/ratpack/issues?labels=good-first-contrib&page=1&state=open

[1] http://hackergarten.net/

  • Different than a hackathon, not competing to win but tending the garden
    of our software community (bugs/docs/features/etc).


[ Julian C. Dunn jdunn@aquezada.com * Sorry, I’m ]
[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]
[ gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]


#3

I love this idea as well. Didn’t berkshelf have a ‘Jump In’ or ‘Hop in’ or
something label that targeted smaller things that might be easy to poke at?
I remember some repo that had that (maybe still does?).

On Thu, Jul 17, 2014 at 12:20 PM, Julian C. Dunn jdunn@aquezada.com wrote:

I think this is a great idea. Perhaps we should raise that at the dev
meeting?

An example of a bug that I think is a “good first contribution” one:
https://github.com/opscode/chef/issues/1634

  • Julian

On Mon, Jul 14, 2014 at 8:40 AM, Eric Helgeson erichelgeson@gmail.com
wrote:

Ohai Chefs,

I saw an interesting idea on the Ratpack[0] Github issue tracker. They
have
a Tag for “Good First Contribution” for newbies to find an issue and
contribute a patch back. It can be daunting looking through 100’s of
issues
trying to find one that is simple to start and not a rabbit hole. Also
the
tag could also mean the person reporting it or who tagged it could help
guide the person through the issue.

Also this is helpful when running a Chef Hackathon or Hacker Garden[1] to
help new people contribute back in a short amount of time.

I participated in the Hacker Garden at GR8Conf, was a lot of fun to
contribute a feature back in ~3 hours to Ratpack.

Thanks,
-Eric Helgeson

[0]

https://github.com/ratpack/ratpack/issues?labels=good-first-contrib&page=1&state=open

[1] http://hackergarten.net/

  • Different than a hackathon, not competing to win but tending the
    garden
    of our software community (bugs/docs/features/etc).


[ Julian C. Dunn jdunn@aquezada.com * Sorry, I’m ]
[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]
[ gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]

Scott Hain — Software Development Engineer

360.360.7433 – shain@getchef.com – *my: *Linkedin http://www.linkedin.com/
Twitter http://www.twitter.com/elejia

CHEF

GETCHEF.COM http://www.getchef.com/

TM

getchef.com http://www.getchef.com/ Blog
http://www.opscode.com/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef