1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
Contributing code
=================
How to contribute
-----------------
The preferred way to contribute to resampy is to fork the
[main repository](http://github.com/bmcfee/resampy/) on
GitHub:
1. Fork the [project repository](http://github.com/bmcfee/resampy):
click on the 'Fork' button near the top of the page. This creates
a copy of the code under your account on the GitHub server.
2. Clone this copy to your local disk:
$ git clone git@github.com:YourLogin/resampy.git
$ cd resampy
3. Create a branch to hold your changes:
$ git checkout -b my-feature
and start making changes. Never work in the ``master`` branch!
4. Work on this copy on your computer using Git to do the version
control. When you're done editing, do:
$ git add modified_files
$ git commit
to record your changes in Git, then push them to GitHub with:
$ git push -u origin my-feature
Finally, go to the web page of the your fork of the resampy repo,
and click 'Pull request' to send your changes to the maintainers for
review. This will send an email to the committers.
(If any of the above seems like magic to you, then look up the
[Git documentation](http://git-scm.com/documentation) on the web.)
It is recommended to check that your contribution complies with the
following rules before submitting a pull request:
- All public methods should have informative docstrings with sample
usage presented.
You can also check for common programming errors with the following
tools:
- Code with good unittest coverage (at least 99%), check with:
$ pip install pytest pytest-cov pytest-faulthandler
$ python setup.py build_ext -i
$ py.test --cov-report term-missing --cov resampy
Documentation
-------------
You can edit the documentation using any text editor and then generate
the HTML output by typing ``make html`` from the docs/ directory.
The resulting HTML files will be placed in _build/html/ and are viewable
in a web browser. See the README file in the doc/ directory for more information.
For building the documentation, you will need
[sphinx](http://sphinx.pocoo.org/),
[matplotlib](http://matplotlib.sourceforge.net/), and [scikit-learn](http://scikit-learn.org/).
Note
----
This document was gleefully borrowed from [scikit-learn](http://scikit-learn.org/).
|
