You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the spirit of free software, everyone is encouraged to help improve this project.
69
-
70
-
Here are some ways you can contribute:
71
-
72
-
- by reporting bugs
73
-
- by suggesting new features
74
-
- by translating to a new language
75
-
- by writing or editing documentation
76
-
- by writing code (**no pull request is too small**: fix typos in the user interface, add code comments, clean up inconsistent whitespace)
77
-
- by refactoring code or adding new features (please get in touch with us before you do, so we can syncronize the efforts and prevent misunderstandings)
78
-
- by [closing issues](https://github.com/AUSSDA/pyDataverse/issues)
79
-
- by [reviewing pull requests](https://github.com/AUSSDA/pyDataverse/pulls)
80
-
81
-
When you are ready, submit a [pull request](https://github.com/AUSSDA/pyDataverse).
82
-
83
-
### Submitting an Issue
84
-
85
-
We use the [GitHub issue tracker](https://github.com/AUSSDA/pyDataverse/issues) to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. When submitting a bug report, please try to provide a screenshot that demonstrates the problem.
86
-
87
-
## DEVELOPMENT
88
-
89
-
### Install
90
-
91
-
```bash
92
-
virtualenv venv
93
-
source venv/bin/activate
94
-
pip install -r requirements.txt
95
-
```
96
-
97
-
### Documentation
98
-
99
-
**Create Sphinx Docs**
100
-
101
-
Use Sphinx to create class and function documentation out of the doc-strings. You can call it via `tox`. This creates the created docs inside `docs/build`.
102
-
103
-
```
104
-
tox -e docs
105
-
```
106
-
107
-
**Create Coverage Reports**
108
-
109
-
Run tests with coverage to create html and xml reports as an output. Again, call it via `tox`. This creates the created docs inside `docs/coverage_html/`.
Copy file name to clipboardExpand all lines: src/pyDataverse/docs/source/developer.rst
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,3 +79,32 @@ When you only want to run one test, e.g. the py36 test:
79
79
.. code-block:: shell
80
80
81
81
tox -e py36
82
+
83
+
84
+
Documentation
85
+
-----------------------------
86
+
87
+
88
+
**Create Sphinx Docs**
89
+
90
+
Use Sphinx to create class and function documentation out of the doc-strings. You can call it via `tox`. This creates the created docs inside `docs/build`.
91
+
92
+
.. code-block:: shell
93
+
94
+
tox -e docs
95
+
96
+
**Create Coverage Reports**
97
+
98
+
Run tests with coverage to create html and xml reports as an output. Again, call it via `tox`. This creates the created docs inside `docs/coverage_html/`.
Copy file name to clipboardExpand all lines: src/pyDataverse/docs/source/index.rst
+27-1Lines changed: 27 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ pyDataverse ecosystem and community.
75
75
community/releases
76
76
77
77
78
-
Developer Documentation
78
+
Developer Guide
79
79
-----------------------------
80
80
81
81
If you are looking for information on a specific function, class, or method,
@@ -85,3 +85,29 @@ this part of the documentation is for you.
85
85
:maxdepth:2
86
86
87
87
developer
88
+
89
+
90
+
Contributor Guide
91
+
-----------------------------
92
+
93
+
In the spirit of free software, everyone is encouraged to help improve this project.
94
+
95
+
Here are some ways you can contribute:
96
+
97
+
- by reporting bugs
98
+
- by suggesting new features
99
+
- by translating to a new language
100
+
- by writing or editing documentation
101
+
- by writing code (**no pull request is too small**: fix typos in the user interface, add code comments, clean up inconsistent whitespace)
102
+
- by refactoring code or adding new features (please get in touch with us before you do, so we can syncronize the efforts and prevent misunderstandings)
103
+
- by `closing issues <https://github.com/AUSSDA/pyDataverse/issues>`_
104
+
- by `reviewing pull requests <https://github.com/AUSSDA/pyDataverse/pulls>`_
105
+
106
+
When you are ready, submit a `pull request <https://github.com/AUSSDA/pyDataverse>`_.
107
+
108
+
**Submitting an Issue**
109
+
110
+
We use the `GitHub issue tracker <https://github.com/AUSSDA/pyDataverse/issues>`_
111
+
to track bugs and features. Before submitting a bug report or feature request,
112
+
check to make sure it hasn't already been submitted. When submitting a bug report,
113
+
please try to provide a screenshot that demonstrates the problem.
0 commit comments