up-for-grabs label

[RichardLitt]

We should make it easier to identify low hanging fruit. Currently, we have the 'difficulty:easy' label, and 'help-wanted'. I think we should highlight these somewhere. At the least, we should link to this search across our repos for these labels.

We should also think about merging these into one label, or highlighting one of the to add to up-for-grabs.net. I think that would be awesome. Don't you?

[jbenet]

+1 for adding to up-for-grabs. that's what "Help Wanted" means.

On Sunday, January 17, 2016, Richard Littauer notifications@github.com
wrote:

We should make it easier to identify low hanging fruit. Currently, we have
the 'difficulty:easy' label, and 'help-wanted'. I think we should highlight
these somewhere. At the least, we should link to this search
https://github.com/search?utf8=%E2%9C%93&q=label%3A%22difficulty%3A+easy%22+user%3AIPFS&type=Issues&ref=searchresults
across our repos for these labels.

We should also think about merging these into one label, or highlighting
one of the to add to up-for-grabs.net http://up-for-grabs.net/#/. I
think that would be awesome. Don't you?

—
Reply to this email directly or view it on GitHub
#94.

[dignifiedquire]

I'm -1 for merging, as eg in the webui there are tasks that I would like help with but they are more difficult on some level. So it's great I can assign help wanted and a level.
I like the idea of having a place where this search is linked to though.

[RichardLitt]

If you assign help wanted, you should assign a difficulty too, to make it easier. That should alleviate the concerns you raise, @dignifiedquire, right?

[dignifiedquire]

@RichardLitt yes sounds good to me

[RichardLitt]

Ok: I am going to add "needs review", "difficulty:*", and "help wanted" to every IPFS repo. i'll make sure they all have the same color.

Repos to add to:

ipfs/ipfs
ipfs/js-ipfs
ipfs/website
ipfs/go-ipfs
ipfs/js-ipfs-api
ipfs/ipfs-hubot
ipfs/webui
ipfs/starlog
ipfs/examples
ipfs/logo
ipfs/astralboot
ipfs/specs
ipfs/container-demos
ipfs/infrastructure
ipfs/community
ipfs/pm
ipfs/papers
ipfs/faq
ipfs/fs-repo-migrations
ipfs/npm-go-ipfs
ipfs/py-ipfs
ipfs/notes
ipfs/blockchain-data
ipfs/http-api-spec
ipfs/js-ipfsd-ctl
ipfs/ipfs-geoip
ipfs/blog
ipfs/archive-format
ipfs/go-ipfs-api
ipfs/station

How does this sound to everyone?

[dignifiedquire]

Thanks but please make sure if they exist they are kept so I don't have to relabel everything

[RichardLitt]

Good call.

[RichardLitt]

Tested: my script works fine. I am using https://www.npmjs.com/package/github-labels, and I will create a config file in this repo with the labels we'll standardize across repos.

[dignifiedquire]

schweet 😸

[jbenet]

👍
On Wed, Jan 20, 2016 at 11:07 Friedel Ziegelmayer notifications@github.com
wrote:

schweet [image: 😸]

—
Reply to this email directly or view it on GitHub
#94 (comment).

[RichardLitt]

Done.

[RichardLitt]

This has been reopened because I need to re-add them to some issues, or find a way of doing that automatically.

[RichardLitt]

Opened bug issue here: popomore/github-labels#17

[RichardLitt]

Add to:

• ipfs/glossary
• ipfs/go-libp2p-*

[daviddias]

Wasn't familiar with http://up-for-grabs.net/#/tags/JavaScript, pretty cool!

[RichardLitt]

Just checked; there are 301 issues in IPFS on up-for-grabs. Directed someone to it today. \o/