Skip to content

Latest commit

 

History

History
103 lines (75 loc) · 5.89 KB

CONTRIBUTING.md

File metadata and controls

103 lines (75 loc) · 5.89 KB
Raw

👐 Contributing to Obsei

First off, thank you for even considering contributing to this package, every contribution big or small is greatly appreciated. Community contributions are what keep projects like this fueled and constantly improving, so a big thanks to you!

Below are some sections detailing the guidelines we'd like you to follow to make your contribution as seamless as possible.

📜 Code of Conduct

The Code of Conduct applies within all community spaces. If you are not familiar with our Code of Conduct policy, take a minute to read the policy before starting with your first contribution.

🗣️ Query or Discussion

We would like to use Github discussions as the central hub for all community discussions, questions, and everything else in between. While Github discussions is a new service (as of 2021) we believe that it really helps keep this repo as one single source to find all relevant information. Our hope is that discussion page functions as a record of all the conversations that help contribute to the project's development.

If you are new to Github discussions it is a very similar experience to Stack Overflow with an added element of general discussion and discourse rather than solely being question and answer based.

🪲 Issues, Bugs, and Feature Requests

We are very open to community contributions and appreciate anything that improves Obsei. This includes fixings typos, adding missing documentation, fixing bugs or adding new features. To avoid unnecessary work on either side, please stick to the following process:

  1. If you feel like your issue is not specific and more of a general question about a design decision, or algorithm implementation maybe start a discussion instead, this helps keep the issues less cluttered and encourages more open-ended conversation.
  2. Check if there is already an related issue.
  3. If there is not, open a new one to start a discussion. Some features might be a nice idea, but don't fit in the scope of Obsei and we hate to close finished PRs.
  4. If we came to the conclusion to move forward with your issue, we will be happy to accept a pull request. Make sure you create a pull request in an early draft version and ask for feedback.
  5. Verify that all tests in the CI pass (and add new ones if you implement anything new)

See below for some guidelines.

✉️ Submission Guidelines

Submitting an Issue

Before you submit your issue search the archive, maybe your question was already answered.

If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues. Providing the following information will increase the chances of your issue being dealt with quickly:

  • Describe the bug - A clear and concise description of what the bug is.
  • To Reproduce- Steps to reproduce the behavior.
  • Expected behavior - A clear and concise description of what you expected to happen.
  • Environment
    • Obsei version
    • Python version
    • OS
  • Suggest a Fix - if you can't fix the bug yourself, perhaps you can point to what might be causing the problem (line of code or commit)

When you submit a PR you will be presented with a PR template, please fill this in as best you can.

Submitting a Pull Request

Before you submit your pull request consider the following guidelines:

  • Search GitHub for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
  • Fork the main repo if not already done
  • Rebase fork with upstream master
  • Create new branch and add the changes in that branch
  • Add supporting test cases
  • Follow our Coding Rules.
  • Avoid checking in files that shouldn't be tracked (e.g dist, build, .tmp, .idea). We recommend using a global gitignore for this.
  • Before you commit please run the test suite and make sure all tests are passing.
  • Format your code appropriately:
    • This package uses black as its formatter. In order to format your code with black run black . from the root of the package.
  • Run pre-commit run --all-files if you're adding new hooks to pre-commit config file. By default, pre-commit will run on modified files when commiting changes.
  • Commit your changes using a descriptive commit message.
  • In GitHub, send a pull request to obsei:master.
  • If we suggest changes then:
    • Make the required updates.
    • Rebase your branch and force push to your GitHub repository (this will update your Pull Request):

That's it! Thank you for your contribution!

✅ Coding Rules

We generally follow the Google Python style guide.

📝 Contributor License Agreement

That we do not have any potential problems later it is sadly necessary to sign a Contributor License Agreement. That can be done literally with the push of a button.

This guide was inspired by the transformers-interpret, Haystack and n8n