Skip to content

Latest commit

 

History

History
67 lines (45 loc) · 2.53 KB

CONTRIBUTING.md

File metadata and controls

67 lines (45 loc) · 2.53 KB
Raw

Contributing to Virtual File System

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

We develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

We use Github Flow, so 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.
  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 Software License

In short, when you submit code changes, your submissions are understood to be under the same BSD-3-Clause 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; it's that easy!

Write bug reports with detail, background, and sample code

This is an example of a well-written bug report, and I think it's not a bad model. Here's also a guide from Software Testing Help, which is a bit more in-depth.

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 a Consistent Coding Style

An editorconfig file is provided to help with this.

License

By contributing, you agree that your contributions will be licensed under its BSD-3-Clause License.

References

This document was adapted from the open-source contribution gist by briandk