Contributing
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change. Please note we have a code of conduct, please follow it in all your interactions with the project.
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
I Have a Question
If you want to ask a question, we assume that you have read the available documentation.
Before you ask a question, it is best to search for existing issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
Report bugs using Github’s issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue.
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)
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
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch from
master
. - Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- If you’ve added code that should be tested, add tests.
- Update the README.md with details of changes
- Ensure the test suite passes.
- Make sure your code lints (@nicolasmondain/eslint-config)
- Issue that pull request!
Any contributions you make will be under the MIT Software License
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that’s a concern.
License
By contributing, you agree that your contributions will be licensed under its MIT License.
References
This document was adapted from the open-source contribution guidelines for Facebook’s Draft
Notes
-
How to use opencv?
It is possible to use
opencv
to process images. Example with thebilateral.ts
filter: -
How to use WebAssembly?
It is possible to use
C/C++
to process images. Example with thewebassembly.ts
filter: -
Create both WebGl and JavaScript methods
webGL
andJavaScript
code must match.