usnistgov/macos_security
1
0
Fork 0
mirror of https://github.com/usnistgov/macos_security.git synced 2026-02-03 14:03:24 +00:00
Code Issues 21 Actions Packages Projects Releases Wiki Activity

Migration from MSCP 1 to MSCP 2.0 #52

New Issue
Open
opened 2026-01-19 18:29:03 +00:00 by michael · 0 comments
michael commented 2026-01-19 18:29:03 +00:00
Owner
Copy Link

Originally created by @jasonmch on GitHub.

Problem to solve

Will there be a migration for customized projects and values from MSCP 1 to MSCP 2.0. While changes and customizations will be documented an automated method to prevent missed controls and configs could save troubleshooting time during transition.

Intended users

Anyone using the project and migrating to 2.0 when released

Further details

Automation prevents issues, it looks like the project is architected in a way that this feels possible

Proposal

On first being pointed at a repository user can choose project to update

Documentation

Testing

Should be little risk as changes are documented and written to disk in the v1 project

What does success look like, and how can we measure that?

Success is a user migrates to 2.0 without spending any time transitioning and evaluating old content

Links / references

Originally created by @jasonmch on GitHub. ### Problem to solve Will there be a migration for customized projects and values from MSCP 1 to MSCP 2.0. While changes and customizations will be documented an automated method to prevent missed controls and configs could save troubleshooting time during transition. ### Intended users Anyone using the project and migrating to 2.0 when released ### Further details Automation prevents issues, it looks like the project is architected in a way that this feels possible ### Proposal On first being pointed at a repository user can choose project to update ### Documentation ### Testing Should be little risk as changes are documented and written to disk in the v1 project ### What does success look like, and how can we measure that? Success is a user migrates to 2.0 without spending any time transitioning and evaluating old content ### Links / references <!-- Any relevant links or references -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: usnistgov/macos_security#52
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?