openmcp-project / openmcp-project/backlog
Epic: SIG Extensibility MCP to ControlPlane renaming
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The MCP to ControlPlane renaming needs to be applied consistently across all repositories maintained by SIG Extensibility (see projects). This includes updating all occurrences of the old name to the new name in source code and documentation.
Potential breaking changes must be evaluated/reviewed on a per repository basis.
Acceptance Criteria
- All repositories have been updated with the new naming.
- The codebase builds and tests successfully after the changes.
- No references to the old name remain unless intentionally preserved for backward compatibility.
- Documentation and configuration are consistent with the new naming.
- Cross-repository integrations are verified to work correctly following the rename.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SIG Extensibility subprojects listed in the linked community projects page and inventory references to MCP in each repository's source, documentation, and configuration. Review each repository's build and test commands, assess backward-compatibility risks, and verify cross-repository integrations. Done means every repository is consistently renamed, builds and tests pass, and only intentional compatibility references remain.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100