Skip to content

Commit 8f600fe

Browse files
Add details on how to contribute
1 parent 2fc6259 commit 8f600fe

File tree

2 files changed

+75
-1
lines changed

2 files changed

+75
-1
lines changed

CONTRIBUTING.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# How to Contribute
2+
3+
Firstly, thanks for wanting to contribute back to this project. Below are
4+
guidelines that should hopefully minimise the amount of backwards and forwards
5+
in the review process.
6+
7+
## Getting Started
8+
9+
* Fork the repository on GitHub - well... duh :P
10+
* Create a virtualenv: `virtualenv venv`
11+
* Activate the virtualenv: `. venv/bin/activate`
12+
* Install the package in develop mode: `python setup.py develop`
13+
* Install requirements: `pip install -r requirements.txt`
14+
* Run the tests to check that everything was successful: `py.test tests`
15+
16+
## Making Changes
17+
18+
* Create a topic branch from where you want to base your work.
19+
* This is usually the master branch.
20+
* Only target release branches if you are certain your fix must be on that
21+
branch.
22+
* To quickly create a topic branch based on master; `git checkout -b
23+
/my_contribution master`. Please avoid working directly on the
24+
`master` branch.
25+
* Make commits of logical units.
26+
* Check for unnecessary whitespace with `git diff --check` before committing.
27+
* Make sure you have added the necessary tests for your changes.
28+
* Run _all_ the tests to assure nothing else was accidentally broken.
29+
30+
## Submitting Changes
31+
32+
* Push your changes to a topic branch in your fork of the repository.
33+
* Submit a pull request to the main repository
34+
* After feedback has been given we expect responses within two weeks. After two
35+
weeks will may close the pull request if it isn't showing any activity.

docs/index.rst

Lines changed: 40 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,13 @@
55
.. highlightlang:: python
66

77

8-
8+
============================================
99
Welcome to BrowserMob Proxy's documentation!
1010
============================================
1111

1212
Python client for the BrowserMob Proxy 2.0 REST API.
1313

14+
--------------
1415
How to install
1516
--------------
1617

@@ -30,6 +31,7 @@ Then install it by running::
3031

3132
$ python setup.py install
3233

34+
----------------------------------
3335
How to use with selenium-webdriver
3436
----------------------------------
3537

@@ -53,6 +55,43 @@ Manually::
5355
server.stop()
5456
driver.quit()
5557

58+
-----------------
59+
How to Contribute
60+
-----------------
61+
62+
Getting Started
63+
---------------
64+
65+
* Fork the repository on GitHub - well... duh :P
66+
* Create a virtualenv: `virtualenv venv`
67+
* Activate the virtualenv: `. venv/bin/activate`
68+
* Install the package in develop mode: `python setup.py develop`
69+
* Install requirements: `pip install -r requirements.txt`
70+
* Run the tests to check that everything was successful: `py.test tests
71+
72+
Making Changes
73+
--------------
74+
75+
* Create a topic branch from where you want to base your work.
76+
* This is usually the master branch.
77+
* Only target release branches if you are certain your fix must be on that
78+
branch.
79+
* To quickly create a topic branch based on master; `git checkout -b
80+
/my_contribution master`. Please avoid working directly on the
81+
`master` branch.
82+
* Make commits of logical units.
83+
* Check for unnecessary whitespace with `git diff --check` before committing.
84+
* Make sure you have added the necessary tests for your changes.
85+
* Run _all_ the tests to assure nothing else was accidentally broken.
86+
87+
Submitting Changes
88+
------------------
89+
90+
* Push your changes to a topic branch in your fork of the repository.
91+
* Submit a pull request to the main repository
92+
* After feedback has been given we expect responses within two weeks. After two
93+
weeks will may close the pull request if it isn't showing any activity
94+
5695
Contents:
5796

5897
.. toctree::

0 commit comments

Comments
 (0)