Skip to content

A tailor-made contribution guide #802

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

Closed
poyea opened this issue May 12, 2019 · 2 comments · Fixed by #864
Closed

A tailor-made contribution guide #802

poyea opened this issue May 12, 2019 · 2 comments · Fixed by #864
Assignees

Comments

@poyea
Copy link
Member

poyea commented May 12, 2019

I think we should write a Contribution Guide from which:

  1. New comers know how they can contribute
  2. Everyone know what do the community, especially users and readers expect
  3. Most importantly, everyone learns about the standard of code contribution, like do we need testing in submission? Is it a strict requirement? Do we need comment description? Are one-liners acceptable? How to deal with "one-liner" alternatives?

I found #432 and #433 relating to this, but the commit concerned is not quite tailor-made to us and thus reading it will not help a newcomer to know points 2 and 3.

@AnupKumarPanwar
Copy link
Member

@poyea I agree with you. I think we should cover the contribution standards in the README.md file. Check the README file of Algorithms-Explaination for reference.

@poyea poyea self-assigned this May 27, 2019
@minddetox
Copy link

This would be helpful. i’m so eager to learn and not sure where to begin. thank you

poyea added a commit that referenced this issue Jun 1, 2019
* Create a tailor-made contribution guide

Closes #802
yanglbme pushed a commit that referenced this issue Jun 2, 2019
* Create CONTRIBUTING.md

* Create a tailor-made contribution guide

Closes #802

* Update README.md

* Rename License to LICENSE.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants