Skip to content

Latest commit

 

History

History
38 lines (28 loc) · 1.68 KB

CONTRIBUTING.md

File metadata and controls

38 lines (28 loc) · 1.68 KB

Contributing to DeepSampler

👍🎉 First off, thanks for taking the time to contribute! 🎉👍

The following is a set of guidelines for contributing to DeepSampler on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

How to contribute to DeepSamplers main repository

PullRequests are welcome!

We follow the standard procedure for contributing on GitHub. Described from the perspective of contributers, we usually follow these steps:

  1. Create a fork of DeepSamplers main repository
  2. Pull the fork into your local IDE
  3. Make your changes
  4. Ensure that the Definition of Done is fullfilled
  5. Create a PullRequest for the main repository
  6. Follow the review process guided by GitHub
  7. Done!

An in-depth tutorial on how to use pullrequests and forks can be found here: GitHub Standard Fork & Pull Request Workflow

How to author plugins

We like to keep plugins in separated repositories. We want to keep the main repository as small and simple as possible and we want to ensure a clear separation between the general framework and specific plugins.

Using separated repositories also gives the authors the opportunity to keep the ownership and to be seen as contributors to the open source communitity, which we believe to be a quite honorably thing.

Definition Of Done

  1. Tests are green
  2. Technical test coverage is >80%. We even try to get above 90%.
  3. Sonarcloud qualitygate is passed
  4. Public methods are documented. Basic design-principles are explained in javadoc.
  5. Peerreview is completed

Styleguide

Development Environment