Contribution to WSKNN#

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it’s:

  • Reporting a bug

  • Discussing the current state of the code

  • Submitting a fix

  • Proposing new features

  • Becoming a maintainer

Where should I start?#

On GitHub! We use GitHub to host the code, to track issues and feature requests, as well as accept pull requests.

—

Developer setup#

Setup for developers differs from the package installation from PyPI.

  1. Fork the wsknn repository.

  2. Clone forked repository.

  3. Connect the main repository with your fork locally:

git remote add upstream https://github.com/nokaut/wsknn.git

  1. Synchronize your repository with the core repository.

git checkout main
git pull upstream main

  1. Create your branch.

git checkout -b name-of-your-branch

  1. Create [virtual environment](https://docs.python.org/3/library/venv.htmlc) or [conda environment](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#creating-an-environment-with-commands).

  2. Activate your environment.

  3. Install requirements listed in the requirements-dev.txt file.

Virtual Environment

>> (your-virtual-environment) pip install -r requirements-dev.txt

Conda

>> (your-conda-environment) conda install -c conda-forge --file requirements-dev.txt

  1. Make changes in a code or write something new.

  2. Write tests if required.

  3. Perform tests with pytest. (Run tests from the tests directory).

>> (your-environment) (your-username:~/path/wsknn/tests) pytest

  1. If all tests pass, push changes into your fork.

git add .
git commit -m "description what you have done"
git push origin name-of-your-branch

  1. Navigate to your repository. You should see a button Compare and open a pull request. Use it to make a pull request! Send it to the dev branch in the main repository. Don’t send pull requests into ``main`` branch of the core repository!

We Use Github Flow#

-> All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

  1. Fork the repo and create your branch from main.

  2. If you’ve added code that should be tested, add tests in the test package. We use Python’s pytest package to perform testing.

  3. If you’ve changed APIs, update the documentation.

  4. Ensure the test suite passes.

  5. Make sure your code lints.

  6. Issue that pull request!

Any contributions you make will be under the BSD 3-Clause “New” or “Revised” License#

In short, when you submit code changes, your submissions are understood to be under the same [BSD 3-Clause “New” or “Revised” License] that covers the project. Feel free to contact the maintainers if that’s a concern.

Report bugs using Github’s issues#

We use GitHub issues to track public bugs. Report a bug by opening a new issue.

Write bug reports with detail, background, and sample code#

Great Bug Reports tend to have:

  • A quick summary and/or background

  • Steps to reproduce

  • Be specific!

  • Give sample code if you can.

  • What you expected would happen

  • What actually happens

  • Notes (possibly including why you think this might be happening, or stuff you tried that didn’t work)

People love thorough bug reports. I’m not even kidding.

Use PEP8 Guidelines#

PEP8 Python Guidelines

License#

By contributing, you agree that your contributions will be licensed under its BSD 3-Clause “New” or “Revised” License.

References#

This document was adapted from the open-source contribution guidelines for Facebook’s Draft

Example of Contribution#

  1. You have an idea to speed-up computation. You plan to use multiprocessing package for it.

  2. Fork repo from main branch and at the same time propose change or issue in the project issues.

  3. Create the new child branch from the forked main branch. Name it as dev-your-idea. In this case dev-multiprocessing is descriptive enough.

  4. Code in your branch.

  5. Create few unit tests in tests directory or re-design actual tests if there is a need. For programming cases write unit tests, for mathematical and logic problems write functional tests. Use data from tests/tdata directory.

  6. Multiprocessing maybe does not require new tests. But always run unittests in the tests directory after any change in the code and check if every test has passed.

  7. Run all tutorials (demo-notebooks) too. Their role is not only informational. They serve as a functional test playground.

  8. If everything is ok make a pull request from your forked repo.