Oct/Nov LBC Meeting minutes

Thanks to everyone who attended. Here are the AI generated notes. I am also attaching a recording in case anyone would like to play it back. Jeff's Notes and Anton's Notes both below.

thx,

-jj

Anton's Notes:

### OpenSSL Engine Removal Discussion

The main topic of the meeting centered on the planned removal of the legacy Engine API in OpenSSL version 4.0. This API has been deprecated since version 3.0, and the engineering team now aims to clean it up as the 4.0 release allows breaking changes. The goal is to fully transition to the provider-based architecture, modernizing the cryptographic integration in OpenSSL.

The engineering team has reached a consensus to exclude engine support by default in builds for version 4.0 and onwards, with support available for those who still need to transition. To ensure backward compatibility, stub functions will be provided to prevent compilation breakage for applications that use engines indirectly or unnecessarily. 

Transition support will be available, particularly through extended and premium customer support. Guides and whitepapers have already been drafted internally (e.g., by Cisco) for engine-to-provider migration.

Efforts have been made to ensure that older OpenSSL releases (e.g., 1.1.0, 1.1.1, and 3.x) remain unaffected, so users aren’t forced to transition immediately. Discussions emphasized the importance of proactive community support and open feedback channels before formalizing these decisions.

### Clang-Based Code Reformatting Initiative

A second major topic discussed was the reformatting of the OpenSSL library codebase using Clang, specifically the WebKit format style. This aims to simplify contributions and developer workflows by aligning the entire codebase with a consistent, automated style. This change also addresses pain points in code review and patching caused by inconsistent formats.

The reformatting proposal is already well-developed, and testing has been successfully carried out to ensure no functional changes are introduced. All maintained versions, possibly excluding OpenSSL 1.1.1 (pending final decision), will be reformatted. Scripts and documentation will be provided to help maintainers and contributors adapt existing patches.

Community input is still being sought before finalizing the process. Once approved, the reformatting will be released and thoroughly documented to minimize disruption.

### Community Communication and Roadmap Planning

The OpenSSL team discussed improvements in community engagement and predictability. A push is being made to publish clearer development roadmaps, with community and stakeholder input guiding prioritization. These changes are designed to reduce confusion surrounding new features and breaking changes.

Efforts will include blog posts, LinkedIn updates, and social outreach to better inform users and gather feedback. Items like engine removal and clang reformatting will be officially announced and open to comments prior to the merge.

### Governance Updates

Proposals are underway to adjust the terms of service for members of the Business and Technical Advisory Committees. The suggested model establishes two-year terms with staggered appointments, so that half the members stand for election each cycle.

The vote around this change is still ongoing.

### Upcoming Events

An OpenSSL-themed event is scheduled for November 18 during the “All Things Open” conference week. Cisco will host the event featuring a panel discussion on OpenSSL’s future, including post-quantum cryptography. The event will also provide opportunities for in-person engagement with open-source communities and developers.

The evening meetup affiliated with the conference routinely hosts several hundred attendees and is expected to feature swag and networking opportunities. Members of the OpenSSL team, including Anton and Matt, will participate in the discussion.

Jeff's Notes: