Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify contributing instructions #361

scrabill opened this issue Oct 19, 2019 · 2 comments


Copy link

@scrabill scrabill commented Oct 19, 2019

Related to #360, I could use help coming up with clear contribution language. Perhaps, something I can use year after year.

What I would like it to include

  • How to close this repo, including which branch to focus on (the master branch)
  • How to make quality contributions that are in line with the spirit of Hacktoberfest and this project
  • Best practices for naming branches, refactoring, etc.
  • How to avoid duplicate PRs, 'taking' someone else's idea, saving first-timers-only contributions for first-timers, etc

I am open to input on this and one person does not have to tackle all of what I've included above. Chime in and let's come up with something.

Chime in on this


This comment has been minimized.

Copy link

@praveen-manick praveen-manick commented Oct 19, 2019

I would like to take this up


This comment has been minimized.

Copy link

@alt-glitch alt-glitch commented Oct 19, 2019

I am interested in working on this. Excited for my first real contribution to open source!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.