77 - [ Submit Feedback] ( #submit-feedback )
88 - [ Get Started!] ( #get-started )
99 - [ Pull Request Guidelines] ( #pull-request-guidelines )
10- - [ Tips] ( #tips )
11- - [ Deploying] ( #deploying )
12- - [ Docker recipe] ( #docker-recipe )
1310
1411# CONTRIBUTING
1512
16- Contributions are welcome, and they are greatly appreciated!
17- Every little bit helps, and credit will always be given.
13+ Contributions are welcome, and they are greatly appreciated! Every little bit
14+ helps, and credit will always be given.
1815
1916You can contribute in many ways:
2017
@@ -26,35 +23,37 @@ Report bugs at https://github.com/cpp-lln-lab/bidsmreye/issues.
2623
2724If you are reporting a bug, please include:
2825
29- - Your operating system name and version.
30- - Any details about your local setup that might be helpful in troubleshooting.
31- - Detailed steps to reproduce the bug.
26+ - Your operating system name and version.
27+ - Any details about your local setup that might be helpful in troubleshooting.
28+ - Detailed steps to reproduce the bug.
3229
3330### Fix Bugs
3431
35- Look through the GitHub issues for bugs.
36- Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.
32+ Look through the GitHub issues for bugs. Anything tagged with "bug" and "help
33+ wanted" is open to whoever wants to implement it.
3734
3835### Implement Features
3936
40- Look through the GitHub issues for features.
41- Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.
37+ Look through the GitHub issues for features. Anything tagged with "enhancement"
38+ and "help wanted" is open to whoever wants to implement it.
4239
4340### Write Documentation
4441
45- bidsMReye could always use more documentation,
46- whether as part of the official bidsMReye docs, in docstrings,
47- or even on the web in blog posts, articles, and such.
42+ bidsMReye could always use more documentation, whether as part of the official
43+ bidsMReye docs, in docstrings, or even on the web in blog posts, articles, and
44+ such.
4845
4946### Submit Feedback
5047
51- The best way to send feedback is to file an issue at https://github.com/cpp-lln-lab/bidsmreye/issues .
48+ The best way to send feedback is to file an issue at
49+ https://github.com/cpp-lln-lab/bidsmreye/issues .
5250
5351If you are proposing a feature:
5452
55- - Explain in detail how it would work.
56- - Keep the scope as narrow as possible, to make it easier to implement.
57- - Remember that this is a volunteer-driven project, and that contributions are welcome :)
53+ - Explain in detail how it would work.
54+ - Keep the scope as narrow as possible, to make it easier to implement.
55+ - Remember that this is a volunteer-driven project, and that contributions are
56+ welcome :)
5857
5958## Get Started!
6059
@@ -67,12 +66,15 @@ Ready to contribute? Here's how to set up `bidsmreye` for local development.
6766git clone
[email protected] :your_name_here/bidsmreye.git
6867```
6968
70- 3 . Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
69+ 3 . Install your local copy into a virtualenv. Assuming you have
70+ virtualenvwrapper installed, this is how you set up your fork for local
71+ development:
7172
7273``` bash
7374mkvirtualenv bidsmreye
7475cd bidsmreye/
75- python setup.py develop
76+ pip install -e .[dev]
77+ ```
7678```
7779
78801. Create a branch for local development:
@@ -87,9 +89,8 @@ Now you can make your changes locally.
8789 tests, including testing other Python versions with tox:
8890
8991``` bash
90- flake8 bidsmreye tests
91- python setup.py test or pytest
92- tox
92+ make lint
93+ make test
9394```
9495
9596To get flake8 and tox, just pip install them into your virtualenv.
@@ -109,65 +110,9 @@ git push origin name-of-your-bugfix-or-feature
109110Before you submit a pull request, check that it meets these guidelines:
110111
1111121 . The pull request should include tests.
112- 2 . If the pull request adds functionality, the docs should be updated. Put
113- your new functionality into a function with a docstring, and add the
114- feature to the list in README.rst.
113+ 2 . If the pull request adds functionality, the docs should be updated. Put your
114+ new functionality into a function with a docstring, and add the feature to
115+ the list in README.rst.
1151163 . The pull request should work for Python 3.8, and for PyPy. Check
116- https://travis-ci.com/Remi-Gau/bidsmreye/pull_requests
117- and make sure that the tests pass for all supported Python versions.
118-
119- ## Tips
120-
121- To run a subset of tests:
122-
123- ``` bash
124- pytest tests.test_bidsmreye
125- ```
126-
127- ## Deploying
128-
129- A reminder for the maintainers on how to deploy.
130- Make sure all your changes are committed (including an entry in HISTORY.rst).
131-
132- Then run
133-
134- ``` bash
135- bump2version patch # possible: major / minor / patch
136- git push
137- git push --tags
138- ```
139-
140- Travis will then deploy to PyPI if tests pass.
141-
142- ## Docker recipe
143-
144- Made using neurodocker
145-
146- ``` bash
147- docker run --rm repronim/neurodocker:0.7.0 generate docker \
148- --base debian:bullseye-slim \
149- --pkg-manager apt \
150- --install " git wget" \
151- --miniconda \
152- version=" latest" \
153- create_env=" deepmreye" \
154- conda_install=" python=3.7 pip" \
155- pip_install=" git+https://github.com/DeepMReye/DeepMReye.git" \
156- activate=" true" \
157- --run " mkdir -p /inputs/models" \
158- --run " wget https://osf.io/cqf74/download -O /inputs/models/dataset1_guided_fixations.h5" \
159- --output Dockerfile
160- ```
161-
162- Build image
163-
164- ``` bash
165- docker build --tag deepmreye:0.1.0 --file Dockerfile .
166- ```
167-
168- Run it
169-
170- ``` bash
171- docker run -it --rm \
172- deepmreye:0.1.0
173- ```
117+ https://github.com/cpp-lln-lab/bidsMReye/actions and make sure that the
118+ tests pass for all supported Python versions.
0 commit comments