[WIP] Contributing guidelines

You reckon I should add that comment to the contributing document?

On Fri, Sep 19, 2014 at 3:24 PM, Nick Korasidis <notifications@github.com>
wrote:

> In CONTRIBUTING.md:
>
> > +1. You want to fix an existing issue. Just go to the
> > +[open issues page](https://github.com/OpenBazaar/OpenBazaar/issues?state=open),
> > +pick an issue that you think is worthy, and start fixing it. Like before, don't
> > +forget to mention in a comment that you're working on it (or assign it to
> > +yourself) and make sure nobody else is doing the same work.
> > +
> > +1. You want to implement a feature we're planning. We don't yet have a
> > +detailed roadmap, but we're working on having one on our wiki.
> > +For now, visit us on #openbazaar on IRC so that we can tell you about our plans.
> > +Then create an issue and mention that you'll
> > +be working on it (or assign it to yourself if you're a collaborator). Make sure an issue
> > +doesn't already exist for the feature you chose! If someone else is working on it, speak with
> > +them.
> > +
> > +1. Look at the code and see if you can refactor something. Look for
> > +[broken windows](http://pragmatictips.com/4).
>
> Once pylint checks are in place, almost all checks disabled in .pylintrc
> are sources of inspiration for refactoring and cleanup. Same applies for
> jshint.conf.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/OpenBazaar/OpenBazaar/pull/617/files#r17781329>.
>