Why Open Access to ISO Standards Is Vital for LLVM’s Future

Thesis

LLVM’s ability to compile, analyze, and evolve code for languages such as C, C++, and Fortran rests on unrestricted access to the working and committee drafts of the ISO standards that define those languages. A pending ISO policy shift threatens to seal those drafts behind a paywall, and the LLVM community is preparing a coordinated testimonial to demonstrate the concrete harms such a move would cause.

The Core Argument

1. Historical context of openness – In the early 1990s, the JTC1 committee within ISO experimented with making its technical documents publicly available. Although the experiment was never formally codified, the practice persisted for three decades, allowing developers worldwide to read the drafts that later became the official standards.
2. ISO’s new tightening effort – Recent internal audits revealed that ISO believed many of those documents were still private. Consequently, ISO is now attempting to retroactively close access to all working drafts, committee drafts, and N‑numbered proposals (including issue lists and defect reports). The final published standards will remain closed, as they have always been.
3. LLVM’s dependence on draft access – LLVM developers use the drafts to:
   • Track feature implementation status on a per‑document basis.
   • Verify the correctness of their interpretation when the wording of a standard is ambiguous.
   • Communicate progress and regressions to downstream projects that fork LLVM. Without the drafts, developers would have to rely on reverse‑engineered behavior or on costly, delayed official publications, both of which erode confidence in the compiler’s conformance.
4. Community scale and diversity – LLVM’s contributor base spans continents, ages, and employment situations. Many contributors are volunteers or work for organizations that cannot afford the subscription fees that ISO imposes on its standards. Closing the drafts would effectively exclude a large segment of the community from the information they need to contribute meaningfully.
5. Economic and practical impact – Companies that ship products built on LLVM (including major hardware vendors, IDE vendors, and cloud providers) would face increased compliance costs. They would need to purchase the drafts individually or rely on third‑party summaries, which introduces legal risk and slows down release cycles.

The Planned Response

The LLVM Foundation has agreed to issue an official statement on behalf of the community. The process, compressed into a two‑week window, is:

1. Draft preparation – A Google Docs draft of the testimonial has been posted for community comment.
2. Community feedback – Contributors can suggest edits until May 27.
3. Project Council review – An out‑of‑band meeting on May 28 will incorporate feedback and finalize the wording.
4. Foundation ratification – The LLVM Foundation will meet on June 2 to adopt the statement.
5. Submission to ISO – The final testimonial will be sent on June 3, just before the June 4 deadline.

Because the timeline is tight, the community is urged to focus on concrete, impact‑oriented language rather than abstract arguments about “tradition of access.” The testimonial should explain how loss of draft access would directly harm LLVM’s ability to implement and verify ISO standards.

Implications for the Wider Ecosystem

• Preserving an open development model – If ISO reverses the 30‑year de‑facto openness, LLVM may need to restructure its development workflow, potentially creating private mirrors of the drafts that only certain contributors can see. This would fragment the community and undermine the meritocratic ethos that has driven LLVM’s success.
• Precedent for other open‑source projects – Many projects (e.g., GCC, Rust, and various hardware description language tools) also rely on early access to standards drafts. A successful LLVM testimonial could encourage ISO to maintain open access for a broader set of communities.
• Legal and compliance considerations – Companies that cannot obtain the drafts may be forced to adopt a “clean‑room” implementation approach, increasing the risk of non‑conformance and exposing them to potential litigation from standards bodies.

Counter‑Perspectives

ISO argues that the drafts are intellectual property of the standards committees and that unrestricted distribution undermines the commercial model that funds the development of the standards themselves. While this viewpoint has merit—standards development is costly—ISO’s own experiment demonstrated that open drafts can coexist with a sustainable funding model, especially when the final standard remains a revenue source. Moreover, the open‑source ecosystem provides indirect value to standards bodies by surfacing defects and driving adoption, which can be quantified as a form of contribution.

Call to Action

• Review the draft testimonial – Visit the linked Google Docs and leave comments before May 27.
• Advocate within your organization – If you work for a company that depends on LLVM, encourage leadership to endorse the testimonial.
• Offer assistance – Contributors who need help submitting a testimonial on behalf of their employer can contact Aaron Ballman directly.

By presenting a unified, evidence‑based argument, the LLVM community can help ensure that the drafts of ISO standards remain freely accessible, preserving the collaborative environment that has made LLVM the cornerstone of modern compilation technology.