This document covers Uptane’s governance and committer process. It also lists the individuals who serve on its Industry Advisory Group, and as the steering committee for Uptane within JDF/Linux Foundation.
Uptane as a non-profit entity
In July of 2018, Uptane was officially adopted into IEEE’s Industry Standards and Technology Organization (ISTO) as the non-profit Uptane Alliance. The goal of the Alliance was to standardize the Uptane open-source software in order to ensure that manufacturers and suppliers follow best practices for updates within the automotive industry.
After releasing V. 1.0.0. of the Standard, Uptane formally affiliated with the Linux Foundation as a Joint Development Foundation project. As Joint Development Foundation Projects, LLC, Uptane Series, the project is overseen by a Steering Committee, and is governed by a set of bylaws. The Steering Committee members are:
- Justin Cappos of NYU Tandon School of Engineering
- Ira McDonald of High North Inc.
- Andre Weimerskirch of Lear Corporation and University of Michigan Transportation Research Institute
Uptane Standard and related documents
The Uptane Standard must be approved by a majority of the aforementioned Steering Committee. The Board of Directors may also be changed by action of a majority of committtee members.
Industry Advisory Group
The following industry representatives serve in an advisory capacity for Uptane.
- Cameron Mott of Southwest Research Institute
- Gloria D’anna of General Telecom Systems
- Jon Oster of Toradex
- Philip Lapczynski of Renesas
- Russ Bielawski of Secure Embedded Systems
- Tom Forest of General Motors
- Trishank Karthik Kuppusamy of Datadog and New York University
Maintainership and Consensus Builder (reference implementation)
The reference implementation for the project is maintained by the people indicated in MAINTAINERS. A maintainer is expected to (1) submit and review GitHub pull requests and (2) open issues or submit vulnerability reports. A maintainer has the authority to approve or reject pull requests submitted by contributors. The project’s Consensus Builder (CB) is Justin Cappos (JustinCappos on github).
Changes in maintainership (reference implementation)
A contributor to the project must express interest in becoming a maintainer. The CB has the authority to add or remove maintainers for the reference implementation.
Changes in governance (reference implementation)
The CB supervises changes in governance for the reference implementation.