Skip to content
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.

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

Add blog index section and introductory post #44

Merged
merged 13 commits into from
Sep 19, 2023
Merged
Show file tree
Hide file tree
Changes from 9 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/content/about/blog/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: OSCAL Blog
heading: Blog
description: Blog posts from staff and community about OSCAL.
toc:
enabled: true
---
24 changes: 24 additions & 0 deletions src/content/about/blog/oscal-first-deep-cleaning.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
title: OSCAL's Fall Cleaning
---

Welcome to the Open Security Controls Assessment Language (OSCAL) Blog, open to the NIST OSCAL Team and to the community!
aj-stein-nist marked this conversation as resolved.
Show resolved Hide resolved

If you work closely with us, you might have noticed we finished [a large code repository reorganization](https://github.com/usnistgov/OSCAL/blob/f24dd56d5569ade8489924cf6fc2640dc297bfbe/decisions/0005-repository-reorganization.md) alongside [the release of OSCAL v1.1.0](https://github.com/usnistgov/OSCAL/releases/tag/v1.1.0). The OSCAL Project was in a desperate need of some internal restructuring, a fall cleaning of sorts. As an OSCAL user, the differences should not affect affect you, but we will still summarize some key changes for you.
aj-stein-nist marked this conversation as resolved.
Show resolved Hide resolved

One may wonder why we reorganized our code repos only recently. Our answer is simple: we started small (more than six years ago!) and wanted to keep everything in one place to reduce the maintenance overhead. As we expanded our work, we needed to separate code repos to get better organized.

Here is what changed:

- The OSCAL website's source code (known as OSCAL pages) moved to its own repo, [OSCAL-Pages](https://github.com/usnistgov/OSCAL-Pages).
- The OSCAL reference documentation's source code moved to its own repo, [OSCAL-Reference](https://github.com/usnistgov/OSCAL-Reference).
- The Metaschema tooling's source code, which we use to process OSCAL models and generate documentation, moved to its own repo, [metaschema-xslt](https://github.com/usnistgov/metaschema-xslt).
- The generated JSON and XML schemas for the models and converters for JSON-XML and XML-JSON conversion are only [published as part of releases](https://github.com/usnistgov/OSCAL/releases), they are not saved in the [OSCAL repo](https://github.com/usnistgov/OSCAL/) like source code anymore. We've also [simplified the build process](https://github.com/usnistgov/OSCAL/blob/main/build/README.md) making it easier for community members to prototype and propose changes to the OSCAL models.
aj-stein-nist marked this conversation as resolved.
Show resolved Hide resolved

The NIST OSCAL Team officially maintains those new repos above and the same [oscal-content](https://github.com/usnistgov/oscal-content/), [liboscal-java](https://github.com/usnistgov/liboscal-java/), [oscal-cli](https://github.com/usnistgov/oscal-cli/) repos just like before. As priorities shifted, we have paused development on [oscal-cat, the catalog authoring tool](https://github.com/usnistgov/oscal-cat), and [oscal-tools, a library of XSLT transformations for OSCAL developer use cases](https://github.com/usnistgov/oscal-tools). Those projects are archived and remain available for reference and demonstration.
aj-stein-nist marked this conversation as resolved.
Show resolved Hide resolved

OSCAL leverages the [Metaschema Information Modeling Framework](https://github.com/usnistgov/metaschema) just like before, but we changed where and how we use the same Metaschema tooling.
aj-stein-nist marked this conversation as resolved.
Show resolved Hide resolved

For an up-to-date description of all projects and their relationship to one another, please take a moment and review the [OSCAL project structure](https://pages.nist.gov/OSCAL/about/projects/) on our website.

Moving forward, the NIST team will author future blog posts as needed. If you have an OSCAL topic you would like to read about or you want to guest-author a blog, you can email the [NIST OSCAL team](mailto:oscal@nist.gov?subject=NIST%20Blog) your proposal and the team will work with you to approve and post the blog.
Loading