[MIGRATION] Kubeflow Organization Transfer - Planning & Checklist

[vara-bonthu]

🚀 Migration to Kubeflow Organization - Planning Checklist

This issue tracks the migration of mcp-apache-spark-history-server from DeepDiagnostix-AI
organization to the Kubeflow organization following official approval.

📋 Background

• Status: ✅ Approved by Kubeflow maintainers
• Proposal: Community PR #873
• Approval Date: September 8, 2025
• Target Repository: kubeflow/mcp-apache-spark-history-server

---

🔄 Pre-Migration Preparation

Repository Compliance

• Create OWNERS file with appropriate approvers/reviewers
• Update CONTRIBUTING.md with Kubeflow guidelines
• Ensure CODE_OF_CONDUCT.md compliance
• Add DCO (Developer Certificate of Origin) sign-off documentation
• Verify Apache 2.0 license formatting ✅
• Update copyright notices for Kubeflow ownership

Code Quality Standards

• Run full test suite and ensure passing ✅
• Run security scan (bandit) and address issues ✅
• Verify linting standards (ruff) compliance ✅
• Confirm type checking (mypy) passes ✅
• Update pre-commit hooks for Kubeflow standards

CI/CD & Repository Settings

• Prepare GitHub Actions workflows for Kubeflow org
• Create prow_config.yaml for Kubeflow CI system
• Plan branch protection rules per Kubeflow standards
• Configure team permissions (ci-bots, core-approvers)

---

🔄 Migration Process

Data Preservation

• Verify full commit history preservation plan
• Confirm issue/PR history migration approach
• Document release/tag migration strategy
• Plan for any Git LFS objects (if applicable)

Repository Transfer

• Coordinate with Kubeflow maintainers for repository creation
• Execute repository transfer with GitHub admin
• Verify URL redirects from old to new location
• Test repository access post-transfer

External References Update

• Update PyPI package metadata with new repository URL
• Update Docker Hub references
• Update Helm chart repository references
• Update CI badge URLs in documentation
• Update example configurations and manifests

---

✅ Post-Migration Validation

Functionality Testing

• Test local development environment setup
• Verify CI/CD pipeline functionality
• Test package installation from new location
• Validate Docker builds from new repository
• Test Kubernetes deployment with updated manifests

Integration Verification

• Test MCP Inspector integration
• Verify AI agent integrations (Claude Desktop, Amazon Q CLI)
• Test AWS integrations (Glue, EMR)
• Validate multi-server configurations

Community Access

• Verify contributor access for existing team members
• Test issue reporting process
• Confirm PR submission workflow
• Validate release process

---

📢 Communication Plan

Pre-Migration

• Notify existing contributors about new processes
• Inform integration partners of upcoming URL changes
• Post community announcements on relevant channels

Post-Migration

• Announce migration completion
• Publish updated installation/contribution guides
• Update redirect notices on old repository
• Create ecosystem integration announcement

---

📝 Timeline & Coordination

Migration Lead: @vara-bonthu @nabuskey
Status: Planning Phase
Next Milestone: Complete pre-migration checklist items

Important Links:

• Original Proposal PR #873
• Kubeflow Repository
  Guidelines
• Kubeflow Contributing Guide

---

Progress Updates: Please comment on this issue with progress updates and any blockers
encountered.