Skip to content

License & Contributing

License

OmniBox and its documentation are released under the MIT License. OmniBox is free of charge, but donations are welcome to help offset development costs.

MIT License

Copyright (c) 2022-2024 Jon Harper

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Contributing to OmniBox

Note: This section is in progress.

Users may contribute directly or indirectly to OmniBox. Accepted contributions are accredited in the documentation.

Direct Contribution

Direct contributions to OmniBox are completed through git:

  1. Fork the OmniBox unstable branch.
  2. Add your files in the correct subfolder (e.g. an MCU tray belongs under /Trays/MCU/[Product Name]).
  3. Submit a pull request to merge your files.

Indirect Contribution

If you would prefer to contribute your changes under a different license or otherwise upload them elsewhere, consider Printables.com. Users who do not contribute directly have (so far) chosen to upload to Printables.

  1. Upload your file to Printables or another site.
  2. Open an Issue on GitHub with a link to your file(s).
  3. If the link does not include installation instructions, include them in the issue.