Skip to content

Release of The Memory Safety Continuum #827

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Mar 31, 2025
Merged

Release of The Memory Safety Continuum #827

merged 2 commits into from
Mar 31, 2025

Conversation

balteravishay
Copy link
Contributor

This PR adds the Memory Safety Continuum document to the best.openssf.org website.

@david-a-wheeler
Copy link
Contributor

@balteravishay - for now this seems like the right call.

In the longer term, do you want this document to look prettier, like the Concise Guide for Developing More Secure Software
? If you do, we need to implement some nice way to generate the web pages. We typically use the Simplest Possible Process (SPP), which uses GitHub Pages, unless you have a need for something fancier.

@balteravishay balteravishay force-pushed the avbalter/memory-continuum-release branch from 21444b5 to fc13810 Compare March 31, 2025 18:07
@balteravishay balteravishay merged commit f8bd072 into ossf:main Mar 31, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@thomasnyman thomasnyman thomasnyman approved these changes

@david-a-wheeler david-a-wheeler david-a-wheeler approved these changes

@gkunz gkunz gkunz approved these changes

Assignees
No one assigned
Labels
Product: Memory Safety Continuum
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@balteravishay @david-a-wheeler @thomasnyman @gkunz