Skip to content

Latest commit

 

History

History
48 lines (31 loc) · 3.67 KB

CONTRIBUTING.md

File metadata and controls

48 lines (31 loc) · 3.67 KB
Raw

Contributing to DAV JS SDK

Thank you for taking the time to lend a hand with the DAV JS SDK project ❤️

Note that we have a separate repo for documentation, any suggestions for improvements or problems with documentation should go there.

There are several ways you can help the project out:

How Can I Contribute?

Contributing Code

A lot of our code comes from pull requests sent by the developer community. Here is how you can contribute too:

  • Open the DAV JS SDK GitHub page and click the ★ Star and then ⑂ Fork buttons.
  • Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
  • Now, make your changes.
  • Commit your local changes by using $ git commit -m "nice detailed message here..."
  • Once you've made sure all your changes work correctly and have been committed, push your local changes back to github with $ git push -u origin master
  • Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
  • Makes sure your pull request describes exactly what you changed and if it relates to an open issue, reference that issue (just include the issue number in the title like this: #49)

Important:

  • Please stick to the project's existing coding style. Coding styles don't need to have a consensus, they just need to be consistent 😄
  • Push your changes to a topic branch in your fork of the repository. Your branch should be based on the master branch
  • When submitting a pull request, please elaborate as much as possible about the change, your motivation for the change, etc.

Reporting Bugs

Bugs are tracked as GitHub issues. If you found a bug with dav-js, the quickest way to get help would be to look through existing open and closed GitHub issues. If the issue is already being discussed and hasn't been resolved yet, you can join the discussion and provide details about the problem you are having. If this is a new bug, please open a new issue.

When you are creating a bug report, please include as much detail as possible.

  • Fill in the predefined template provided.
  • Use a clear and descriptive title for the issue to identify the problem.
  • Describe the exact steps which reproduce the problem. Share the relevant code to reproduce the issue if possible.
  • Try to isolate the issue as much as possible, reducing unrelated code until you get to the minimal amount of code in which the bug still reproduces. This is the most important step to help the community solve the issue.

Feature Requests and Ideas

We track discussions of new features, proposed changes, and other ideas as GitHub issues. If you would like to discuss one of those, please first look through existing open and closed GitHub issues and see if there is already a discussion on this topic which you can join. If there isn't, please open a new issue.

When discussing new ideas or proposing changes, please take the time to be as descriptive as possible about the topic at hand