Skip to content

Latest commit

 

History

History
46 lines (35 loc) · 1.96 KB

File metadata and controls

46 lines (35 loc) · 1.96 KB

Contributing to ELI v2.0

Thanks for your interest! One thing to know up front: ELI is source-available, not open-source (see LICENSE), and that shapes how contributions work.

How you can help

  • Report bugs or suggest improvements via issues.
  • Submit fixes or features via pull request.
  • You may use and modify ELI for your own purposes under the license, but you may not redistribute it. Contributing improvements back here — rather than publishing your own copy — is the supported path.

Contributor terms (please read before opening a PR)

Because the project is source-available and the author retains the right to maintain and commercialise it, contributions require a simple inbound grant.

By submitting a contribution (a pull request, patch, or code suggestion you author), you agree that:

  1. The contribution is your own original work and you have the right to submit it.
  2. You grant Jason Fitzgibbon Bridgeman (the copyright holder) a perpetual, worldwide, irrevocable, royalty-free license to use, modify, sublicense, and relicense your contribution — including for commercial purposes — as part of ELI v2.0, under the project's current license and any future license the holder may choose (including commercial / dual licensing).
  3. You retain your own copyright in your contribution; you are simply granting the license above so I can keep the whole project under one license and keep steering it.
  4. Contributions are provided "as is", without warranty.

If you can't agree to these terms, please open an issue to discuss rather than sending code.

Practical notes

  • Keep pull requests focused and small where possible.
  • Run the test suite before submitting: pytest -q tests/.
  • No personal data, secrets, or machine-specific paths (e.g. /home/<you>) in commits.
  • Be respectful and constructive.

Questions? jaybridgeman0095@gmail.com