Rooba
/
kivy
mirror of https://github.com/kivy/kivy.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md 

Fix the appearance
This commit is contained in:
Howard Chang 2019-11-28 11:36:30 +08:00 committed by GitHub
parent fd7e81ef82
commit 9e8f89e1de
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
.github/CONTRIBUTING.md vendored
View File

@ -1,4 +1,4 @@
##[Contributing](https://kivy.org/docs/contribute.html)
# [Contributing](https://kivy.org/docs/contribute.html)
There are many ways in which you can contribute to Kivy.
Code patches are just one thing amongst others that you can submit to help the
@ -7,7 +7,7 @@ improvements, advertisement & advocating, testing, graphics contributions and
many different things. Just talk to us if you want to help, and we will help you
help us.
##[Feedback](https://kivy.org/docs/contact.html)
## [Feedback](https://kivy.org/docs/contact.html)
This is by far the easiest way to contribute something. If you're using
Kivy for your own project, don't hesitate sharing. It doesn't have to be a
@ -22,14 +22,14 @@ feel encouraged to report any obstacles you encountered such as missing
documentation, misleading directions or similar.
We are perfectionists, so even if it's just a typo, let us know.
#[Reporting an Issue](https://kivy.org/docs/contribute.html#reporting-an-issue)
## [Reporting an Issue](https://kivy.org/docs/contribute.html#reporting-an-issue)
If you have any problems, a crash, a segfault, missing documentation, invalid
spelling, weird examples, please take 2 minutes to report the issue and follow
the guide lines mentioned
[here.](https://kivy.org/docs/contribute.html#reporting-an-issue)
##[Code Contributions](https://kivy.org/docs/contribute.html#code-contributions)
## [Code Contributions](https://kivy.org/docs/contribute.html#code-contributions)
Code contributions (patches, new features) are the most obvious way to help with
the project's development. Since this is quite common, we ask you to follow our
@ -44,7 +44,7 @@ code history (you can opt-out if you don't want that).
* [Git & GitHub](https://kivy.org/docs/contribute.html#git-github)
* [Code Workflow](https://kivy.org/docs/contribute.html#code-workflow)
##[Documentation Contributions](https://kivy.org/docs/contribute.html#documentation-contributions)
## [Documentation Contributions](https://kivy.org/docs/contribute.html#documentation-contributions)
Documentation contributions generally follow the same workflow as code
contributions, just a bit more lax. We don't ask you to go through all the
@ -55,7 +55,7 @@ follow the suggested workflow.
* [Docstrings](https://kivy.org/docs/contribute.html#docstrings)
#Unit tests contributions
## Unit tests contributions
The [Unit tests](https://kivy.org/docs/contribute-unittest.html) page
explains how the Kivy unit tests work and how you can create your own. Please