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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-8Lines changed: 5 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,22 +28,19 @@ Any JdeRobot project follows the same workflow when contributing.
28
28
29
29
***Find a problem or possible improvement for the project:** First of all, check that the feature/bug is not listed in the current open issues.
30
30
31
-
***Create an issue:** Create an issue in the project with the problem/improvement you will
32
-
address. In this issue, explain carefully what you will be changing and how this changes will impact the project. Provide any complementary information to explain it (code samples, screenshots ...)
31
+
***Create an issue:** Create an issue in the project with the problem/improvement you will address. In this issue, explain carefully what you will be changing and how this changes will impact the project. Provide any complementary information to explain it (code samples, screenshots ...)
33
32
34
33
The two following points are different depending on the permissions you have to the repo.
35
34
***[If you have write permission] Work in a separate branch always:** Create a new branch with a describable name (you can use the issue number as branch name "issue_xxx"). Create your commits in that branch making the apropiate changes. Please, use describable names as commit messages, so everyone can understand easily the changes you made.
36
35
37
36
***[If you only have read permission] Fork the project:** Fork the project. Work on that copy of the repo, making the desirable changes. Please, use describable names as commit messages, so everyone can understand easily the changes you made.
38
37
39
-
***Open a pull request:** A pull request is compulsory any time a new change wants to be added to the core or the project. After solving the issue, create a pull request with your branch. In this pull request include all the commits made,
40
-
write a good description of the changes made and refer to the issue solved to make things easier to the maintainers. Include any additional resource that would be interesting (references, screenshots...). Link the PR with the issue
38
+
***Review and format your code:** Before submitting your PR, make sure that all the changes are properly formatted. All functions must have their docstring in [Sphinx format](https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html). In that way, the corresponding documentation will be generated automatically. Regarding code formatting, we use [Black](https://github.com/psf/black).
39
+
40
+
***Open a pull request:** A pull request is compulsory any time a new change wants to be added to the core or the project. After solving the issue, create a pull request with your branch. In this pull request include all the commits made, write a good description of the changes made and refer to the issue solved to make things easier to the maintainers. Include any additional resource that would be interesting (references, screenshots...). Link the PR with the issue.
41
41
42
42
***Testing and merging pull requests**
43
-
Your pull request will be automatically tested by Travis CI. If any jobs have failed, you should fix them.
44
-
To rerun the automatic builds just push changes to your branch on GitHub. No need to close that pull request and open a new one!
45
-
Once all the builders are "green", one of DetectionMetrics's developers will review your code. Reviewer could ask you to modify your pull request.
46
-
Please provide timely response for reviewers (within weeks, not months), otherwise you submission could be postponed or even rejected.
43
+
One of DetectionMetrics's developers will review your code. Reviewer could ask you to modify your pull request. Please provide timely response for reviewers (within weeks, not months), otherwise you submission could be postponed or even rejected.
47
44
48
45
***[If you have write permission] Don't accept your own pull requests:** Wait for a project maintainer to accept the changes you made. They will probably comment the pull request with some feedback and will consider if it can be merge to the master branch.
@@ -97,7 +97,10 @@ If you are using LiDAR, Open3D currently requires `torch==2.2*`.
97
97
As of now, *DetectionMetrics* can either be used as a Python library or as a command-line application.
98
98
99
99
### Library
100
-
You can check the `examples` directory for inspiration. If you are using *poetry*, you can run the scripts provided either by activating the created environment using `poetry shell` or directly running `poetry run python examples/<some_python_script.py>`.
You can check the `examples` directory for further inspiration. If you are using *poetry*, you can run the scripts provided either by activating the created environment using `poetry shell` or directly running `poetry run python examples/<some_python_script.py>`.
101
104
102
105
### Command-line interface
103
106
DetectionMetrics currently provides a CLI with two commands, `dm_evaluate` and `dm_batch`. Thanks to the configuration in the `pyproject.toml` file, we can simply run `poetry install` from the root directory and use them without explicitly invoking the Python files. More details are provided in [DetectionMetrics website](https://jderobot.github.io/DetectionMetrics/v2/usage/#command-line-interface).
0 commit comments