Skip to end of metadata
Go to start of metadata


Opticks is an open-source remote sensing workbench released by Ball Aerospace & Technologies Corp (BATC) under the GNU LGPL version 2.1.


Opticks and associated web sites are governed by the Opticks Governance Board (the Board) which is comprised of members of the Opticks community. The Board's purpose is to provide direction for Opticks, ensure quality contributions to the project, arbitrate community discussions, and address community concerns. The Board is established by and derives its rules and organization from this document.

The board shall consist of five members and shall have a chairperson elected by members of the board. The chairperson's responsibility is to run board meetings, administer board votes, publish board decisions, and arbitrate board discussions. In cases of a tied board vote, the chairperson shall break the tie. The chairperson may, as he or she sees fit, create and appoint administrative positions and delegate any and all responsibilities except for tie breaking.

Board Meetings

The board shall hold meetings at least once every three months. Board meetings will typically coincide with bi-weekly IRC status meetings but may be held online or offline at other times. The time and location of board meetings shall be announced ahead of time in a public Opticks forum unless the immediacy of a meeting makes this difficult or impossible.


Official board decisions are made via votes. Any board member may call for a vote at any time. Vote decisions shall be published to the Opticks community using established communication methods (typically the Opticks mailing lists). When a vote is requested, the voting period begins. The voting period shall last 24 hours unless otherwise requested by a member of the board. If all board members vote before the end of the voting period or if enough votes are tallied such that additional board votes would not affect the outcome, voting may end early at the discretion of the chairperson. In this case the remaining votes are tallied as abstentions.

All board votes require a simple majority of the board to pass. Members not attending a vote will count as an abstention. A member may vote for a proposal, against a proposal, or abstain. Proposals should be worded such that a vote for a proposal indicates a change in policy or situation.

After a vote is finished, the chairperson shall publish the vote indicating the members present, each member's vote, and the total for, against, and abstaining. The result of the vote should be clearly documented, and if the proposal passes, the change takes place immediately unless otherwise indicated.

It is expected that formal votes will not be required very often and discussions should normally be resolved by an informal tally of community desire. Common proposals include, but are not limited to:

  • Addition or removal of a board member or committer
  • Choosing a chairperson
  • Changing the Opticks Governance Policy
  • Formal resolution of a discussion

Roles and Responsibilities

Everyone is encouraged to participate in the Opticks project. The easiest way to contribute is simply to use Opticks. In addition to using Opticks, tell your friends, family, and colleagues about Opticks, and encourage others to try Opticks. There are a number of forums and email lists associated with Opticks which you can and should join. Take part in discussions, and have a say in the future of Opticks. Mailing lists and other forums can be found on the web site.

In addition, there are a few well-defined roles associated with the Opticks community:


A member is a user of Opticks who has created an account on, joined the mailing lists, or is otherwise actively participating in the Opticks community.


Anyone from the community can contribute to Opticks according to the procedure outlined in this document. Contributions may or may not be code-based. More information on this process can be found in the Welcome To Opticks Development section of this web site. Patch Submission Process:

  1. Create a JIRA account and log in.
  2. Create a new JIRA issue for the patch.
  3. If this refers to an existing issue, the original issue ID should be mentioned in the description so it will be linked.
  4. Attach the patch file to the new issue.
  5. The issue will be triaged and assigned to a committer for inclusion in the trunk.
    • When an issue is submitted to JIRA, only a limited number of people have access to view the issue. The triage process determines that an issue is properly described and not a duplicate of another issue before releasing the issue to the community. We make every effort to move issues out of triage as soon as possible so they become visible to the entire community.
  6. The patch is applied like any other fix/feature.


Committers can commit to the subversion source code repositories and are expected to fix bugs, implement new features, integrate community patches, and review the code of other committers regularly. Committers have a very different role in the Opticks community compared to members and contributors. Committers are responsible for moving Opticks in a direction which is best for the community as a whole. The Board must approve all committers.

Board Member

Governance board members have final decision making authority over the Opticks project. Their role is to dictate the direction of the Opticks project, create and enforce governance rules, approve committers, and ensure that community issues are resolved. The governance board is intended to be a light handed position of control and should only exert control when required to ensure the smooth operation of the Opticks community. Board membership is a two year position and may be vacated voluntarily. If vacated early, a replacement finishes the length of the term.

The current makeup of the governance board is:

  • Chairperson: Trevor Clarke  (term ending April 1, 2015)
  • Dustan Adkins (term ending April 1, 2015)
  • Nathan Jennings (term ending April 1, 2016)
  • Bob Goffena (term ending April 1, 2016)
  • Glen Geisen (term ending April 1, 2016)
  • None