Skip to main content

Sponsorship and governance

Workbench for Zephyr and Devicetree Manager

1. Why​

Workbench for Zephyr is an open source VS Code tool for Zephyr, under the same Apache 2.0 licence as Zephyr. Devicetree Manager is its companion tool for device tree editing; its code is shared with the sponsors today and is planned to become open source. AC6 wrote both tools and maintains them. The goal of this programme is to keep them silicon vendor neutral: no single vendor owns the tools, and every sponsor can add and ship support for its own devices without waiting for us. The shared mission is to make Workbench for Zephyr the reference open source platform for Zephyr and, one day, to bring it into the Zephyr project. Sponsors provide the backing, share the direction, and get a seat where the code is merged.

2. Who takes part​

  • AC6: founder, host and lead maintainer of both projects.
  • Sponsors: silicon vendors who sign the sponsorship agreement.
  • Community: anyone can open issues and send pull requests to Workbench for Zephyr. That stays open, as in Zephyr.

3. What a sponsor gets​

  • Two maintainer seats on each project (Workbench for Zephyr and Devicetree Manager): named engineers from the sponsor, with write access to the repositories, so work goes on when one is away.
  • One vote on the steering committee.
  • Access to Devicetree Manager before it is open source, for as many of the sponsor's developers as it needs.
  • Its name and logo on the project pages and on the marketplace listings.

4. The maintainer seats​

The sponsor maintainers can review and merge changes. No AC6 approval is needed, so a vendor release never waits on us. Changes to the shared core follow the normal rule: at least one maintainer from another organisation approves before merge.

Features in the shared core stay as generic as possible, in the spirit of Zephyr.

5. Steering committee​

Small and technical, in the spirit of the Zephyr TSC. Members: one voting representative per sponsor, plus AC6. It can meet once a month, and on demand when needed, but meetings are not compulsory. It decides the roadmap and the release plan, what goes into the shared core, the development work the sponsorship fees pay for, new sponsors and new seats, and any change to this document. AC6 chairs the meetings and writes the notes.

6. How we decide​

  • We look for consensus first. Most topics end there.
  • If there is no consensus, the chair calls a vote: one vote per member, quorum of half the members, simple majority wins. Votes can be held in the meeting or by email, and the result goes in the notes.
  • If the vote is a tie, the AC6 vote breaks the tie.
  • AC6 keeps the final word on the shared core, the project name, and anything that would break silicon vendor neutrality.

7. What stays with AC6​

The project name and logo, the publication of the extensions on the marketplaces, the Devicetree Manager code until it is open source, and a reference from the tools to AC6 and its related training, directly or through the Zephyr Project Training Partner Program.

8. Fee and term​

  • Sponsorship fee: USD 15,000 per year.
  • Term: one year. AC6 sends the invoice for the next year at least 90 days before the anniversary date; if it is paid, the sponsorship continues for one more year, otherwise it ends on that date.
  • The same fee and rules apply to every sponsor.

9. Toward the Zephyr project​

  • Goal: Workbench for Zephyr joins the Zephyr project, under the Linux Foundation.
  • Devicetree Manager: the steering committee votes on when to publish it as open source.
  • After the move: the Zephyr project governance applies. AC6 stays lead maintainer, sponsors keep their maintainers, and the community contributes as in Zephyr. The reference to AC6 and its related training described in section 7 stays.