Meeting minutes: February 2026
Attendees: Matt Caswell, Tomas Mraz, Shubham Kumar, Jon Ericson, Randall Becker, Dr. Yi Ouyang
Notes
Newsletter (Jon)
Annual report webinar (Jon)
-
Distros meeting and priorities (Jon)
We can add more external tests, but the question is what specifically to test. (Tomas)
The release candidate approach allows external organizations to test against configurations that they are specifically interested in. (Randall)
Point releases should have at least an alpha and a beta release to test against. Patch releases are a different story. (Matt)
Test against a nightly release or the latest code from git when a patch release is announced. (currently 1 week out) (Tomas)
2 weeks before a release, we send a pre-notification to a restricted set of people who we trust with the patches. (Matt)
Potentially do a snapshot build on a monthly basis. (Tomas)
Might be more conservative in backporting bug fixes. (Tomas)
-
FOSDEM (Matt and Jon)
-
NCSU Practicum (Matt)
We visited North Carolina State University in November. They would like us to help with their student practicum for a small group of students. We will mentor them through the process. Needs to be fairly standalone and maybe not a new feature that would need a lot of knowledge of the library. Please let us know if you have any ideas. (Matt)
-
AI Policy
Corporation legal advice: no AI contributions. (Randall)
We already have a lot of AI code because we didn’t have a policy. (Tomas)
CLA Trivial AI contributions should be fine. Code tools that use AI, but are ultimately controlled by a human. Also we had CVEs from AISLE, which is an AI company and we now are using it to review PRs. (Matt)
Devil’s advocate: suppose the AI sends the same patch to both WolfSSL and OpenSSL. What happens? (Randall)
For a person who has the rights to the code, this would be fine. (Matt)
Action items
Add Randall to the pre-release list. (Tomas?)
Talk with our lawyers about AI contributions and coordinate with the Corporation.