Switch to Monorepo

[obulat]

ETA	Start Date	Project Lead	Actual Ship Date
2023-02-19	2022-11-24	@dhruvkb	TBD

Description

This project combines three repositories into one:

• frontend
• API
• openverse

Edit: The project has been expanded to also include the migration of the Openverse Catalog.

Documents

• Project Proposal and Implementation Plan
• Milestone

Tasks

• Update documentation system to cover all projects #443
• Update references to old processes
• Speed up the CI+CD workflow
• Restore ECS prod deploys (Unify rollback & deployment, simplify deployment workflow #767)
• Update references in the infrastructure repo: https://github.com/WordPress/openverse-infrastructure/pull/383
• Update POT path in GlotPress
• Transfer open issues #447
• Add migration notices to separate repo READMEs
  • Monorepo archive notice openverse-frontend#2196
  • Monorepo archive notice openverse-api#1147
• Archive separate repos
• CODEOWNERS issues (details: Add "Skip to main content" to content pages #450 (comment)) PR review requests are not following the CODEOWNERS assignements #850
• Publish a post to our Make blog
• Update "Week in Openverse" script to support monorepo #760
• Issues with Sentry projects pointing to old repos (cc @krysal)

Prior Art

• Discussion about switching to monorepo Discuss switching to a monorepo #192

Note: the start date is the date when the RFC was opened

[zackkrida]

Update POT path in GlotPress

I've reached out to the #meta team in Make WP Slack about this change.

Edit: Done!

[dhruvkb]

GitHub shows me this positive message about the CODEOWNERS file being valid. So it's not a syntax error that caused the PR to not be assigned reviewers automatically.

[AetherUnbound]

I believe #767 should restore our ability to do staging & prod deploys manually!

[zackkrida]

I've updated the project description to include the scope change of adding the catalog. I also updated the Estimated End to April 15th, approximately two weeks after we intend to finish the Provider DAG Stability (#385) project.

[dhruvkb]

Update 2023-04-11

Done

• The PR for making the catalog mergeable with the monorepo is up Restructure codebase to be more monorepo-friendly openverse-catalog#1094

Next

• Merge the catalog into this repo and integrate its workflows into the existing ones
• Update references to the catalog repo in WordPress/openverse-infrastructure.

Blockers

#1094 is blocked on a code-freeze and merge/closure of all open PRs in the catalog.

[dhruvkb]

Update 2023-04-15

Done

The catalog has been merged into the monorepo, making it a true monorepo. The main branch has been renamed to main_old and kept for posterity for a limited time. The new main branch can be acquired locally via

• git fetch and git reset --hard origin/main
• git reset --hard 033ab77 and git pull

Next

• Migrate issues from the catalog to here.
• Archive the catalog with a migration notice (similar to WordPress/openverse-api@1f7877a).
• Move catalog docs into the truly-comprehensive docs site.
  • Update any broken references to the catalog or its components in the docs.

[dhruvkb]

Update 2023-04-21

Done

• The issues were migrated by @obulat
• The catalog was given a transfer notice and archived by @zackkrida

I think we can mark this project as completed as the migration and expansion of the catalog docs is an ongoing long-term process.