Skip to content

Commit 60a494a

Browse files
authored
Merge pull request #90 from sahildua2305/add-contributing-guide
Add Contributing guide
2 parents 0892c00 + 1acd824 commit 60a494a

File tree

1 file changed

+70
-0
lines changed

1 file changed

+70
-0
lines changed

CONTRIBUTING.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
How to contribute
2+
=================
3+
4+
Thanks for your interest in contributing to Kinto!
5+
6+
## Reporting Bugs
7+
8+
Report bugs at https://github.com/Kinto/kinto-http.py/issues/new
9+
10+
If you are reporting a bug, please include:
11+
12+
- Any details about your local setup that might be helpful in troubleshooting.
13+
- Detailed steps to reproduce the bug or even a PR with a failing tests if you can.
14+
15+
16+
## Ready to contribute?
17+
18+
### System Requirements
19+
20+
Depending on the platform and chosen configuration, some libraries or extra services are required.
21+
22+
The following commands will install necessary tools for cryptography and Python packaging like Virtualenv.
23+
24+
#### Linux
25+
On Debian / Ubuntu based systems:
26+
27+
```bash
28+
apt-get install libffi-dev libssl-dev python-dev python-virtualenv
29+
```
30+
31+
#### OS X
32+
Assuming [brew](http://brew.sh/) is installed:
33+
34+
```bash
35+
brew install libffi openssl pkg-config python
36+
37+
pip install virtualenv
38+
```
39+
40+
### Getting Started
41+
42+
- Fork the repo on GitHub and clone locally:
43+
44+
```bash
45+
git clone [email protected]:Kinto/kinto-http.py.git
46+
git remote add {your_name} [email protected]:{your_name}/kinto-http.py.git
47+
```
48+
49+
## Testing
50+
51+
- `make tests-once` to run the test with the current venv.
52+
- `make tests` to run all the tests (with Py2 and Py3, flake8 and functional tests)
53+
54+
You may need to use `make run-kinto` before running the functional tests.
55+
If you want to run the functional tests only, you can use `make functional`.
56+
57+
## Submitting Changes
58+
59+
```bash
60+
git checkout master
61+
git pull origin master
62+
git checkout -b issue_number-bug-title
63+
git commit # Your changes
64+
git push -u {your_name} issue_number-bug-title
65+
```
66+
67+
Then you can create a Pull-Request.
68+
Please create your pull-request as soon as you have one commit even if it is only a failing tests. This will allow us to help and give guidance.
69+
70+
You will be able to update your pull-request by adding commit in your branch.

0 commit comments

Comments
 (0)