[wp-trac] [WordPress Trac] #65314: Make `wp-includes/pomo` the canonical pomo source; retire `svn.glotpress.org/trunk/pomo`

[WordPress Trac]

#65314: Make `wp-includes/pomo` the canonical pomo source; retire
`svn.glotpress.org/trunk/pomo`
----------------------------+-----------------------------
 Reporter:  dd32            |      Owner:  (none)
     Type:  task (blessed)  |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  I18N            |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  docs            |
----------------------------+-----------------------------
 == Background ==

 The pomo library (PO/MO file reading and writing, plus the Translations
 and plural-form helpers) currently exists in two places:

 - wp-includes/pomo/ — shipped with WordPress core.
 - https://glotpress.svn.wordpress.org/trunk/pomo/ — the original home,
 dating from when GlotPress was an SVN project that bundled pomo as its own
 subdirectory.

 When that split was set up, GlotPress was the source of truth: changes
 landed in the GlotPress SVN copy and were synced into core.

 That arrangement no longer reflects reality:

 - GlotPress is now a WordPress plugin developed on GitHub
 (https://github.com/GlotPress/GlotPress).
 - GlotPress requires WordPress, so at runtime it uses the pomo library
 shipped in wp-includes/pomo/.
 - GlotPress no longer pulls from, depends on, or syncs with the SVN copy
 of pomo. The SVN copy is effectively orphaned and only continues to matter
 to the extent that core still mirrors it.

 == Proposal ==

 Officially recognize `wp-includes/pomo/` as the canonical, upstream copy
 of the library. All future changes (bug fixes, deprecations, PHP
 compatibility work, etc.) land in core directly via Trac/SVN and are
 reviewed under the I18N component.

 == Notes on divergence ==

 The GlotPress SVN copy of pomo contains a samples/ directory with example
 .po/.mo fixtures used during the library's original development. WordPress
 core has never shipped that folder and shouldn't start — but those
 fixtures may still be useful as test data. Options:

 - Move the fixtures into core's PHPUnit i18n test fixtures (if not already
 covered).
 - Or, move them into the GlotPress GitHub repo under tests/.
 - Or, leave them where they are and treat the SVN location as a frozen
 fixture archive.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65314>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform