0x00000000 :l4(Tm  ~ndJbѿ lazj"TS?# Contributing to OpenEXR Thank you for your interest in contributing to OpenEXR. This document explains our contribution process and procedures: * [Getting Information](#Getting-Information) * [Legal Requirements](#Legal-Requirements) * [Development Workflow](#Development-Workflow) * [Coding Style](#Coding-Style) * [Versioning Policy](#Versioning-Policy) * [Creating a Release](#Creating-a-Release) For a description of the roles and responsibilities of the various members of the OpenEXR community, see [GOVERNANCE](GOVERNANCE.md), and for further details, see the project's [Technical Charter](ASWF/charter/OpenEXR-Technical-Charter.md). Briefly, Contributors are anyone who submits content to the project, Committers review and approve such submissions, and the Technical Steering Committee provides general project oversight. ## Getting Information There are two primary ways to connect with the OpenEXR project: * The [openexr-dev](https://lists.aswf.io/g/openexr-dev) mail list: This is a development focused mail list with a deep history of technical conversations and decisions that have shaped the project. * [GitHub Issues](https://github.com/AcademySoftwareFoundation/openexr/issues): GitHub Issues are used both to track bugs and to discuss feature requests. ### How to Ask for Help If you have trouble installing, building, or using the library, but there's not yet reason to suspect you've encountered a genuine bug, start by posting a question to the [openexr-dev](http://lists.aswf.io/openexr-dev) mailing list. This is the place for question such has "How do I...". ### How to Report a Bug OpenEXR use GitHub's issue tracking system for bugs and enhancements: https://github.com/AcademySoftwareFoundation/openexr/issues If you are submitting a bug report, please be sure to note which version of OpenEXR you are using, on what platform (OS/version, which compiler you used, and any special build flags or other unusual environmental issues). Please give a specific account of * what you tried * what happened * what you expected to happen instead with enough detail that others can reproduce the problem. ### How to Request a Change Open a GitHub issue: https://github.com/AcademySoftwareFoundation/openexr/issues. Describe the situation and the objective in as much detail as possible. Feature requests will almost certainly spawn a discussion among the project community. ### How to Report a Security Vulnerability If you think you've found a potential vulnerability in OpenEXR, please refer to [SECURITY.md] to responsibly disclose it. ### How to Contribute a Bug Fix or Change To contribute code to the project, first read over the [GOVERNANCE](GOVERNANCE.md) page to understand the roles involved. You'll need: * A good knowledge of git. * A fork of the GitHub repo. * An understanding of the project's development workflow. * Legal authorization, that is, you need to have signed a Contributor License Agreement. See below for details. ## Legal Requirements OpenEXR is a project of the Academy Software Foundation and follows the open source software best practice policies of the Linux Foundation. ### License OpenEXR is licensed under the [BSD-3-Clause](LICENSE.md) license. Contributions to the library should abide by that standard license. ### Contributor License Agreements Developers who wish to contribute code to be considered for inclusion in the OpenEXR distribution must first complete a **Contributor License Agreement**. OpenEXR uses [EasyCLA](https://lfx.linuxfoundation.org/tools/easycla) for managing CLAs, which automatically checks to ensure CLAs are signed by a contributor before a commit can be merged. * If you are an individual writing the code on your own time and you're SURE you are the sole owner of any intellectual property you contribute, you can [sign the CLA as an individual contributor](https://docs.linuxfoundation.org/lfx/easycla/contributors/individual-contributor). * If you are writing the code