Merge branch 'develop' into codegen

CONTRIBUTING.md

@@ -42,8 +42,6 @@ All requests for changes and enhancements to OSCAL are initiated through the pro
 * [Defect Report](../../issues/new?template=bug_report.md&labels=bug): Use to report a problem with an existing OSCAL feature or capability.
 * [Question](../../issues/new?labels=question&template=question.md): Use to ask a question about OSCAL.
 
-Issue triage is managed by the core OSCAL project team using a [specialized project board](../../projects/52).
-
 The core OSCAL project team regularly reviews open issues, prioritizes their handling, and updates the issue statuses and comments as needed.
 
 ## Communications mechanisms

decisions/0004-issue-triage.md

@@ -10,7 +10,7 @@ Approved
 
 The NIST OSCAL Team must plan work to add, change, or remove code in project repositories. We document these plans in GitHub issues, and implement the changes as specified in these issues with pull requests. Some of these issues are decided internally by the NIST OSCAL Team, others are requested by external community members. In the past and present, many issues, especially requests from external community members, are created and do not receive timely feedback. Initially or over time, it is not clear when NIST staff have officially received a request, intend to accept the work recommendation or reject it, and an approximate time window for when that work should start.
 
-In response to this, the former technical director and a subset of the team were involved in issue triage informally. Those team members [implemented some automation to process incoming requests](https://github.com/usnistgov/OSCAL/blob/60918cd3fc5508b69b71e8691b071108dab46ec9/.github/workflows/issue-triage.yml) and assist with ongoing triage by adding them to [a specific GitHub project, distinct from the (now legacy) project that tracked each sprint, for managing triage in bi-weekly meetings](https://github.com/usnistgov/OSCAL/projects/52). Subsequently, the team migrated sprint and overall backlog tracking from one version of project boards in GitHub, both the Issue Triage board and other uses in OSCAL-related projects, to [a newer cross-repository project board with other usability enhancements](https://github.com/orgs/usnistgov/projects/25/). The consequence of this change was the issue triage board, and process more generally, became more and more disjointed from the more recent process and tooling for planning work through issue management.
+In response to this, the former technical director and a subset of the team were involved in issue triage informally. Those team members [implemented some automation to process incoming requests](https://github.com/usnistgov/OSCAL/blob/60918cd3fc5508b69b71e8691b071108dab46ec9/.github/workflows/issue-triage.yml) and assist with ongoing triage by adding them to ["Needs Triage" in the NIST OSCAL Work Board](https://github.com/orgs/usnistgov/projects/25). Subsequently, the team migrated sprint and overall backlog tracking from one version of project boards in GitHub, both the Issue Triage board and other uses in OSCAL-related projects, to [This newer cross-repository project board with other usability enhancements](https://github.com/orgs/usnistgov/projects/25/). The consequence of this change was the issue triage board, and process more generally, became more and more disjointed from the more recent process and tooling for planning work through issue management.
 
 The NIST OSCAL Team potentially needs a more transparent (to NIST staff and the community) and resilient issue triage process, with larger team involvement, and supporting tooling to align with cross-repository project board they are to use day to day.
 
@@ -19,7 +19,7 @@ The NIST OSCAL Team potentially needs a more transparent (to NIST staff and the
 The NIST OSCAL Team should perform periodic backlog refinement and integrate issue triage as part of the process to formally accept or reject work for inclusion into the backlog. To act upon this decision, the team would need to complete the following steps of a plan.
 
 1. Document the backlog process (as minimally and clearly as possible).
-1. Adjust the supporting automation to automate issues to go to [the new project board](https://github.com/usnistgov/OSCAL/projects/52) with a triage status.
+1. Adjust the supporting automation to automate issues to go to [the project board](https://github.com/usnistgov/OSCAL/projects/25) with a triage status.
 1. Decommission the old issue triage board.
 1. Schedule and initiate periodic backlog refinement with the team, asynchronously or synchronolously in private meetings (to start).