Our Motivation, Objective, and Scope are outlined in the README of our repo
Our original deliverable was revised language for Stream 4 of the OpenSSF's Mobilization plan. Our revised language for Stream 4 is here.
We also established common definitions of memory safety terms to refer to in our work.
Our in progress deliverables include:
- Best Practices - Memory-Safe By Default Languages
- Best Practices - Non-Memory-Safe By Default Languages
- The Memory Safety Continuum
- Nell Shamrell-Harrington (Microsoft, Rust Foundation)
- Avishay Balter (Microsoft)
The SIG have a minimum of 3 members with 2 different organizational affiliations.
- Jay White, Microsoft
- Gabriel Dos Reis, Microsoft, GabrielDosReis
- Charles Palmer, IBM Research, Dartmouth
- David Edelsohn, IBM
- Andrew Fryer, Andrew-Fryer
- Justin Cappos, NYU, JustinCappos
- Andrew Lilley Brinker, Mitre, alilleybrinker
- Joshua J. Drake, jduck
- Chris de Almeida, IBM, ctcpip
- Jordan Harband, TC39, ljharb
SIGs may report to an existing OpenSSF Working Group or directly to the TAC as their governing body. The SIG commits to providing the governing body quarterly updates on progress.
The SIG should provide a list of existing resources with links to the repository, and if available, website, a roadmap, demos and walkthroughs, and any other material to showcase the existing breadth, maturity, and direction of the SIG.
Reference | URL |
---|---|
Repo | https://github.com/ossf/Memory-Safety |
Meeting Agenda | https://docs.google.com/document/d/1RnIzqeKyrOJvs6vQ8xGH6TjZDoEFaGUs1NkAx--v_3Y/edit |
OSSF Calendar Entry | Not sure how to link this, but there is one! |
Website | |
Security.md | |
Roadmap | |
code-of-conduct.md | https://openssf.org/community/code-of-conduct/ |
Demos | |
Other |