The OpenColorIO project is governed by its Committers, including a Technical Steering Committee (TSC) which is responsible for high-level guidance of the project.
The OpenColorIO project grows and thrives from assistance from Contributors. Contributors include anyone in the community that contributes code, documentation, or other technical artifacts that have been incorporated into the projects repository.
The OpenColorIO GitHub repository is maintained by OCIO Committers. Committers are Contributors who have earned the ability to modify source code, documentation, or other technical artifacts to the project. Upon becoming Committers, they become members of the OCIO leadership team.
Their privileges include, but are not limited to:
- Commit access to the OpenColorIO repository
- Moderator status on all communication channels
Typical activities of a Committer include:
- Helping users and novice contributors
- Contributing code and documentation changes that improve the project
- Reviewing and commenting on issues and pull requests
- Participation in working groups
- Merging pull requests
The TSC periodically reviews the Committer list to identify inactive Committers. Past Committers are typically given Emeritus status. Emeriti may request that the TSC restore them to active Committer status.
Any existing Committer can nominate an individual making significant and valuable contributions to the OpenColorIO project to become a new Committer.
To nominate a new Committer, open an issue in the OCIO repository, with a summary of the nominee's contributions.
If there are no objections raised by any Committers two weeks after the issue is opened, the nomination will be considered as accepted. Should there be any objections against the nomination, the TSC is responsible for working with the individuals involved and finding a resolution. The nomination must be approved by the TSC, which is assumed when there are no objections from any TSC members.
Prior to the public nomination, the Committer initiating it may seek feedback from other Committers in private channels and work with the nominee to improve the nominee's contribution profile, in order to make the nomination as frictionless as possible.
If individuals making valuable contributions do not believe they have been considered for a nomination, they may log an issue or contact a Committer directly.
A subset of the Committers forms the Technical Steering Committee (TSC), which has final authority over this project. As defined in the project charter, TSC responsibilities include, but are not limited to:
- Coordinating technical direction of the Project, including but not limited to:
- Participating in roadmapping and feature priority each year
- Participating in Working Groups as appropriate
- Actively tracking development & giving feedback promptly
- Participating in maintenance of technical documentation
- Actively discussing issues & reviewing pull requests
- Actively monitoring and assisting contributors on GitHub
- Actively monitoring and assisting folks on the OCIO slack instance
- Project governance and process (including this policy)
- Contribution policy
- GitHub repository hosting
- Conduct guidelines
- Maintaining the list of additional Committers
- Appointing representatives to work with other open source or open standards communities
- Discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects
- Coordinating any marketing, events, or communications regarding the project
Within the TSC are two elected leadership roles to be held by its members and voted on annually. Any TSC member can express interest in serving in a role, or nominate another member to serve. There are no term limits, and one person may hold multiple roles simultaneously. Should a TSC member resign from a leadership role before their term is complete, a successor shall be elected through the standard nomination and voting process to complete the remainder of the term. The leadership roles are:
-
Chair: This position acts as the project manager, organizing meetings and providing oversight to project administration.
-
Chief Architect: This position makes all the final calls on design and technical decisions, and is responsible for avoiding "design by committee" pitfalls.
At the time of election, the TSC will also agree upon which of these two leaders will serve as the OpenColorIO ASWF (Academy Software Foundation) TAC (Technical Advisory Council) representative for the term. This member represents the project at all ASWF TAC meetings.
- Chair: Carol Payne
- Chief Architect: Doug Walker
- Rémi Achard - DNEG
- Mark Boorer - Industrial Light & Magic
- Mei Chu - Sony Pictures Imageworks
- Sean Cooper - ARRI
- Michael Dolan - Epic Games
- Zach Lewis - Method Studios
- Thomas Mansencal - Wētā FX
- Cuneyt Ozdas - Autodesk
- Carol Payne - Independent Consultant
- Mark Titchener - Foundry
- Mark Reid - Animal Logic
- Doug Walker - Autodesk
- Kevin Wheatley - Framestore
- Patrick Hodoul - Autodesk
- Carl Rand - Wētā FX
Any meetings of the TSC are intended to be open to the public, except where there is a reasonable need for privacy. The TSC meets regularly in a voice conference call, at a cadence deemed appropriate by the TSC. The meeting is run by a designated meeting chair approved by the TSC. Meetings may also be streamed online where appropriate; connection details will be posted to the ocio-dev mail list in advance of the scheduled meeting.
Items are added to the TSC agenda which are considered contentious or are modifications of governance, contribution policy, TSC membership, or release process, in addition to topics involving the high-level technical direction of the project.
The intention of the agenda is not to approve or review all patches. That should happen continuously on GitHub and be handled by the larger group of Committers.
Any community member or Contributor can ask that something be reviewed by the
TSC by logging a GitHub issue. Any Committer, TSC member, or the meeting chair
can bring the issue to the TSC's attention by applying the Needs Discussion label.
Prior to each TSC meeting, the meeting chair will share the agenda with members of the TSC. TSC members can also add items to the agenda at the beginning of each meeting. The meeting chair and the TSC cannot veto or remove items.
The TSC may invite additional persons to participate in a non-voting capacity.
The meeting chair is responsible for ensuring that minutes are taken and that notes are submitted after the meeting to the public wiki.
Due to the challenges of scheduling a global meeting with participants in several time zones, the TSC will seek to resolve as many agenda items as possible outside of meetings via discussion on Slack or other methods.
Any proposal for additional members of the TSC may be submitted by Committers and/or TSC members by opening an issue outlining their case. Formal consensus should be reached by the existing TSC members. No objections raised by any TSC members two weeks after the issue is opened does not imply acceptance, if general consensus cannot be reached by this time a formal vote is required.
Should there be any objections against the nomination, the TSC is responsible for working with the individuals involved and finding a resolution.
A voting member of the TSC may nominate a successor in the event that such voting member decides to leave the TSC, and the TSC, including the departing member, shall confirm or reject such nomination by a vote.
In the event that the departing member’s nomination for successor is rejected by vote of the TSC, the departing member shall be entitled to continue nominating successors until one such successor is confirmed by vote of the TSC. If the departing member fails or is unable to nominate a successor, the TSC may nominate one on the departing member’s behalf.