Skip to content

Latest commit

 

History

History
177 lines (130 loc) · 7.67 KB

CONTRIBUTING.md

File metadata and controls

177 lines (130 loc) · 7.67 KB
Raw

Contributing guidelines

Pull Request Checklist

Before sending your pull requests, make sure you followed this list.

How to become a contributor and submit your own code

Developer Certificate of Origin (DCO)

We'd love to accept your patches! Before we can take them, please make sure all commit messages to contain the Signed-off-by line with an email address that matches the commit author.

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. DCO Details

Contributing code

If you have improvements to DeepRec, send us your pull requests! For those just getting started, Github has a how to.

DeepRec team members will be assigned to review your pull requests. Once the pull requests are approved and pass continuous integration checks, a DeepRec team member will apply ready to pull label to your change. This means we are working on getting your pull request submitted to our internal repository. After the change has been submitted internally, your pull request will be merged automatically on GitHub.

If you want to contribute, start working through the DeepRec codebase, navigate to the Github "issues" tab and start looking through interesting issues. If you are not sure of where to start, then start by trying one of the smaller/easier issues here i.e. issues with the "good first issue" label and then take a look at the issues with the "contributions welcome" label. These are issues that we believe are particularly well suited for outside contributions, often because we probably won't get to them right now. If you decide to start on an issue, leave a comment so that other people know that you're working on it. If you want to help out, but not alone, use the issue comment thread to coordinate.

Contribution guidelines and standards

Before sending your pull request for review, make sure your changes are consistent with the guidelines and follow the DeepRec coding style.

General guidelines and philosophy for contribution

  • Include unit tests when you contribute new features, as they help to a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost.
  • Bug fixes also generally require unit tests, because the presence of bugs usually indicates insufficient test coverage.
  • Keep API compatibility in mind when you change code in core DeepRec, e.g., code in core and python. DeepRec has reached version 1 and hence cannot make non-backward-compatible API changes without a major release. Reviewers of your pull request will comment on any API compatibility issues.
  • When you contribute a new feature to DeepRec, the maintenance burden is (by default) transferred to the DeepRec team. This means that the benefit of the contribution must be compared against the cost of maintaining the feature.
  • Full new features (e.g., a new op implementing a cutting-edge algorithm) typically will live in tensorflow/addons to get some airtime before a decision is made regarding whether they are to be migrated to the core.

License

Include a license at the top of new files.

Bazel BUILD files also need to include a license section, e.g., BUILD example.

C++ coding style

Changes to DeepRec C++ code should conform to Google C++ Style Guide.

Use clang-tidy to check your C/C++ changes. To install clang-tidy on ubuntu:18.04, do:

apt-get install -y clang-tidy

You can check a C/C++ file by doing:

clang-format <my_cc_file> --style=google > /tmp/my_cc_file.cc
diff <my_cc_file> /tmp/my_cc_file.cc

Python coding style

Changes to DeepRec Python code should conform to Google Python Style Guide

Use pylint to check your Python changes. To install pylint and retrieve DeepRec's custom style definition:

pip install pylint
wget -O /tmp/pylintrc https://raw.githubusercontent.com/alibaba/DeepRec/main/tensorflow/tools/ci_build/pylintrc

To check a file with pylint:

pylint --rcfile=/tmp/pylintrc myfile.py

Coding style for other languages

Git Commit Guidelines

Use meaningful commit message that described what you did. Format should be: [Component]

Component: after using the Component mark, there needs to be a space with the following subject.

Subject: a brief description of the purpose of commit, must be in English, no more than 50 characters. The first letter needs to be capitalized and the ending is .

Description: Description is a further detailed description of the commit, such as bugfix, which is the scene caused by the bug. If it is performance optimization, it is performance data. Use the description as a supplement to the subject.

Example:

[Runtime] Add blacklist and whitelist to JitCugraph. (#578)

1. Refine the auto-clustering policy by adding blacklist and whitelist environment setup.
2. Add documents of using JitCugraph.

Running unit tests

Using Docker and DeepRec's CI scripts.

# Install Docker first, then this will build and run cpu tests
cibuild/cpu-ut/cpu-core-ut.sh

Also you can directly use bazel to run the tests, like:

./configure
bazel test //tensorflow/python/...

See DeepRec Builds for details.