Repository migration to the caipe-io organization

[sriaradhyula]

We are moving the CAIPE repositories from the cnoe-io organization to the dedicated caipe-io organization.

Why we are moving

CAIPE intends to re-apply for the CNCF Sandbox following Sandbox application #475. Establishing a dedicated GitHub organization is an important step toward presenting CAIPE as an independent cloud native project with a clear identity, scope, ownership, and governance separate from CNOE.

The move will also provide a clear home for CAIPE repositories and release artifacts while supporting more neutral, transparent project governance and broader community participation. This is one part of our preparation for a future Sandbox application; it does not imply or guarantee CNCF acceptance.

Planned changes

• Move the main repository: cnoe-io/ai-platform-engineering → caipe-io/ai-platform-engineering.
• Move the documentation site: cnoe-io.github.io/ai-platform-engineering/ → caipe.io.
• Consolidate agent utilities before the move: Refactor and merge cnoe-io/cnoe-agent-utils into cnoe-io/ai-platform-engineering.
• Move the chat CLI: cnoe-io/agent-chat-cli → caipe-io/agent-chat-cli.
• Rename the Cloud Native Slack channel: #cnoe-sig-agentic-ai → #caipe-community.
• Change repository visibility: Make cnoe-io/multi-agent-jarvis private.
• Change repository visibility: Make cnoe-io/agent-backstage private.

Tracking progress

The complete migration and CNCF Sandbox re-application readiness checklist is tracked in Issue #2360. Use the issue to track task status and related pull requests; use this discussion for community questions and migration updates.

We will use this discussion to share migration timing, progress, and any actions contributors need to take.

[rayl15]

Thanks for outlining the plan and explaining the reasoning behind it , the dedicated organisation makes sense. I used claude and manual review to look into some points.

I reviewed main for any references to the old organisation and considered them for inclusion in the checklist in #2360. Three items stand out as needing a decision rather than a simple find-and-replace:

1. Docs deep links have drifted with the caipe.io root move.

#2361 changed url: https://caipe.io and baseUrl: '/', removing the /ai-platform-engineering/ path segment. Consequently, old links won’t map perfectly even if cnoe-io.github.io redirects at the host level. This host still appears in 22 files, including the first-run entry points:

• README.md:5 still points to .../ai-platform-engineering/getting-started/quick-start.
• docker-compose.yaml:5 and docker-compose.dev.yaml:6 contain the quick-start link that first-time users encounter.
• setup-caipe.sh:8655 includes the documented --ingest-url=https://cnoe-io.github.io/ai-platform-engineering/ example for ingesting CAIPE documentation.

Additionally, and potentially overlooked, the RAG webloader encodes the redirect in the original direction. The comments in scrapy_worker.py:562 indicate caipe.io -> cnoe-io.github.io, and test_spiders.py:412 asserts this exact scenario. Given that caipe.io is now the origin, it’s worth revisiting this issue.

2. The organisation ghcr.io/cnoe-io appears in 192 files (126 under docs/, 37 under charts/).

The part that extends beyond the repository: chart READMEs publish oci://ghcr.io/cnoe-io/charts/... and values.yaml files in the wild pin ghcr.io/cnoe-io/... images. Does the registry namespace also move and if so will the old paths continue to receive pushes during a deprecation window? This difference impacts whether existing installs break on their next upgrade or a future one.

3. Consolidating the cnoe-agent-utils package has a version skew that needs to be reconciled first.

The merge lands on five pyprojects with differing versions:

• ai_platform_engineering/dynamic_agents/pyproject.toml:12 → 0.4.1
• The root pyproject.toml, utils/pyproject.toml:12, rag/server/pyproject.toml:22, and rag/agent_ontology/pyproject.toml:18 → 0.4.0

Additionally, dynamic_agents/pyproject.toml pins boto3==1.43.16 with a comment indicating it should be bumped “in lockstep with cnoe-agent-utils when it moves”. This means vendoring changes the boto3 resolution story rather than just an import path.

I’m happy to help with any mechanical aspects, particularly the docs-URL sweep.

[sriaradhyula]

@rayl15 - Thank you for bringing up this.

• 1. Docs deep links have drifted with the caipe.io root move.

Apologize for this. I will take a look and try to fix the deep links if possible

2. The organisation ghcr.io/cnoe-io appears in 192 files (126 under docs/, 37 under charts/).

There will be a cut over version after migration. We can officially tag 1.0.0 after migration.

3. Consolidating the cnoe-agent-utils package has a version skew that needs to be reconciled first.

Agreed, I will also tag @subbaksh @suwhang-cisco @kevkantes @ErikMLutz @artdroz for their feedback.

Please let me know which areas or topics you are would be interested in picking up #2360

[rayl15]

Thanks for the quick answers, and for #2374 — that covers point 1 completely. I left my review notes on the PR.

On picking things up from #2360, two I would like to take. Both are small enough that I can actually finish them:

1. Document the sign-off requirement in CONTRIBUTING.md (section 4)

The guide is currently 50 lines and does not mention DCO or sign-off anywhere, but the DCO check gates every PR — I found that out by failing it. The conventional-commits job is in the same position, and the prebuild/ branch convention for image builds is not written down either. So enforcement is already live and only the documentation half of that checklist item is missing. I would add DCO with a git commit -s example, the commit message convention, branch naming, and the local check commands.

2. Align the cnoe-agent-utils pins ahead of the consolidation (section 2)

Prep work rather than the consolidation itself. #2374 touched the root pyproject.toml, but only for the release bump, so the skew is still there: dynamic_agents is on 0.4.1 and the other four are on 0.4.0. I would unify them, refresh uv.lock, and confirm the boto3==1.43.16 pin still matches what the shared package resolves to. If aligning on 0.4.1 turns out to break something, I will report it on the issue rather than force it through.

I am happy to take the contributor-facing migration guide (section 3) later if nobody has claimed it by then, but I would rather land these two first than sign up for more than I can deliver.

Both would be fork PRs with sign-off. Usual disclosure: I use Claude alongside manual review for sweeps like this.

[sriaradhyula]

@rayl15 - #2374

[kevkantes]

Is there a timeline with actual dates for this?

[sriaradhyula]

@kevkantes - The plan is to start the move activity later next week. Let's touch base again in the community meeting on Monday

[sriaradhyula]

📢 CAIPE repository migration

We plan to begin moving CAIPE repositories to the dedicated caipe-io GitHub organization on Monday, August 24, 2026, in preparation for resubmitting CAIPE to the CNCF Sandbox.

🏠 New home
The dedicated organization will give CAIPE an independent home, separate from CNOE, with clearer project ownership, identity, and community governance.
• GitHub organization: https://github.com/caipe-io
• Main repository after migration: https://github.com/caipe-io/ai-platform-engineering
• Governance repository: https://github.com/caipe-io/governance
• Project website and documentation: https://caipe.io

💬 Follow the migration
• Community discussion: #2359
• Migration and resubmission tracker: #2360
• CNCF Sandbox application: cncf/sandbox#475 (will be reopened for Sep 22nd review)

📅 Join the weekly community call
Every Monday, 12:00–13:00 Central / 10:00–11:00 Pacific / 19:00–20:00 Central European.
• Join via Webex: https://go.webex.com/meet/cnoe
• View the calendar: https://calendar.google.com/calendar/u/0/embed?src=064a2adfce866ccb02e61663a09f99147f22f06374e7a8994066bdc81e066986@group.calendar.google.com&ctz=America/Los_Angeles

💬 Join us on CNCF Slack
The #cnoe-sig-agentic-ai channel will be renamed to #caipe-community. Existing channel members will remain in the renamed channel.
• Community channel: #cnoe-sig-agentic-ai
• Need a CNCF Slack invitation? https://communityinviter.com/apps/cloud-native/cncf

#cnoe-sig-agentic-ai