Skip to content

Latest commit

 

History

History
144 lines (100 loc) · 3.7 KB

CONTRIBUTING.md

File metadata and controls

144 lines (100 loc) · 3.7 KB
Raw

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

!!! note It is required to fill out the Eclipse Contributor Agreement form to contribute in Eclipse Foundation projects. For more information and complete the acknowledgment of Eclipse Contributor Agreement, please see Eclipse Contributor Agreement.

Environment setup

Nothing easier!

Fork and clone the repository, then:

cd volttron-bacnet-proxy
make setup

!!! note If it fails for some reason, you'll need to install Poetry manually.

You can install it with:

```bash
python3 -m pip install --user pipx
pipx install poetry
```

Now you can try running `make setup` again,
or simply `poetry install`.

You now have the dependencies installed.

You can run the application with poetry run volttron-bacnet-proxy [ARGS...].

Run make help to see all the available actions!

Tasks

This project uses duty to run tasks. A Makefile is also provided. The Makefile will try to run certain tasks on multiple Python versions. If for some reason you don't want to run the task on multiple Python versions, you can do one of the following:

  1. export PYTHON_VERSIONS= : this will run the task with only the current Python version
  2. run the task directly with poetry run duty TASK, or duty TASK if the environment was already activated through poetry shell

The Makefile detects if the Poetry environment is activated, so make will work the same with the virtualenv activated or not.

Development

As usual:

  1. create a new branch: git checkout -b feature-or-bugfix-name
  2. edit the code and/or the documentation

If you updated the documentation or the project dependencies:

  1. run make docs-regen
  2. run make docs-serve, go to http://localhost:8000 and check that everything looks good

Before committing:

  1. run make format to auto-format the code
  2. run make check to check everything (fix any warning)
  3. run make test to run the tests (fix any issue)
  4. follow our commit message convention

If you are unsure about how to fix or ignore a warning, just let the continuous integration fail, and we will help you during review.

Don't bother updating the changelog, we will take care of this.

Commit message convention

Commits messages must follow the Angular style:

<type>[(scope)]: Subject

[Body]

Scope and body are optional. Type can be:

  • build: About packaging, building wheels, etc.
  • chore: About packaging or repo/files management.
  • ci: About Continuous Integration.
  • docs: About documentation.
  • feat: New feature.
  • fix: Bug fix.
  • perf: About performance.
  • refactor: Changes which are not features nor bug fixes.
  • style: A change in code style/format.
  • tests: About tests.

Subject (and body) must be valid Markdown. If you write a body, please add issues references at the end:

Body.

References: #10, #11.
Fixes #15.

Pull requests guidelines

Link to any related issue in the Pull Request message.

During review, we recommend using fixups:

# SHA is the SHA of the commit you want to fix
git commit --fixup=SHA

Once all the changes are approved, you can squash your commits:

git rebase -i --autosquash master

And force-push:

git push -f

If this seems all too complicated, you can push or force-push each new commit, and we will squash them ourselves if needed, before merging.