Charter

Why DisplayXR exists, what the project commits to, and how it is run.

Why DisplayXR exists

Spatial displays, with or without glasses, are reaching laptops, monitors, tablets and phones, but each vendor ships its own SDK. An app written for one display has to be rewritten for the next, so few apps get written at all.

DisplayXR fixes this with one open platform for every spatial display, built on OpenXR, the industry standard for XR. Developers write an app once and it runs on any supported display. Display makers plug their hardware in once and get every DisplayXR app.

The project was founded and incubated at Leia, and it is open to every display vendor, developer and device maker.

What the project commits to

  • Open source. The DisplayXR runtime is licensed under BSL-1.0 and the project's original components under Apache-2.0. Contributors keep the copyright to their work.
  • Vendor neutrality. Every display connects through the same documented plug-in interface, and the DisplayXR runtime contains no vendor-specific code. The extensions are designed for all spatial displays, not one family of panels.
  • Open development. Issues, pull requests, design decisions and releases are all public.
  • One shared core. Every product built on DisplayXR, including those of the companies that contribute to it, uses the same public code and released versions.
  • Testing, not certification. The project publishes tests that anyone can run against their own plug-in, and it makes no claim of Khronos conformance before that conformance has been granted.
  • Working with the standard. Extensions proven on several vendors' hardware are proposed for the official OpenXR specification.

How the project is run

Today the project is led by its founder with a small group of maintainers, named in each repository. Anyone can become a maintainer through their contributions.

As other display vendors adopt DisplayXR, the project will move to shared governance: a technical steering committee drawn from the participating organizations, and an independent steward holding the project's name, domain and repositories. How decisions are made day to day is described on the governance page.