-
Notifications
You must be signed in to change notification settings - Fork 181
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
(EPIC) OSCAL and Metaschema cleanup and declutter #966
Comments
wendellpiez
added a commit
to wendellpiez/OSCAL
that referenced
this issue
Jun 21, 2021
… into other repositories such as usnistgov/oscal-tools. Cf usnistgov#966.
Notes on OSCAL repo cleanup (see WIP branch at https://github.com/wendellpiez/oscal/tree/issue966-defenestration-jun2021):
|
wendellpiez
added a commit
to wendellpiez/OSCAL
that referenced
this issue
Jun 21, 2021
wendellpiez
added a commit
to wendellpiez/OSCAL
that referenced
this issue
Jul 1, 2021
… into other repositories such as usnistgov/oscal-tools. Cf usnistgov#966.
wendellpiez
added a commit
to wendellpiez/OSCAL
that referenced
this issue
Jul 1, 2021
8 tasks
Now done, for now (always more) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story:
As an OSCAL developer and user, I need the OSCAL repository to be orderly, intelligible, documented accurately and comprehensively, and consistent.
Goals:
The OSCAL repository needs to be comfortable and welcoming to visitors. This means not a lot of confusion, loose and unexplained resources, or out of date readmes.
This applies to the Metaschema and other OSCAL-related repositories as well. See usnistgov/metaschema#164.
Dependencies:
None currently.
Acceptance Criteria
{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}
The text was updated successfully, but these errors were encountered: