- Passed security review or already Wikimedia deployed
- Voting CI structure tests
- Runs MediaWiki-CodeSniffer
- Runs phan
- Supports MySQL, SQLite, and Postgres (if there are schema changes)
- GPL v2 or later compatible license
- Extension's default configuration provides optimal experience
- Tested with web installer
|Open||None||T279842 Expand the set of bundled extensions and skins in MediaWiki 1.37|
|Open||None||T191739 Bundle Thanks extension with MediaWiki|
|Open||None||T191746 Bundle LoginNotify extension with MediaWiki|
|Stalled||None||T191738 Bundle Echo extension with MediaWiki|
|Resolved||demon||T186456 PHP Fatal error: Call to undefined method PEAR::encodeHeader() when Echo is enabled|
|Stalled||None||T244898 Notifications ('Echo') should work with postgres|
|Stalled||None||T244899 CentralAuth should work with postgres|
|Open||None||T259376 Migrate CentralAuth to Abstract Schema|
|Open||None||T259375 Migrate Echo to Abstract Schema|
|Resolved||Legoktm||T31134 installer breaks when extensions depend on each other|
- Mentioned In
- T279842: Expand the set of bundled extensions and skins in MediaWiki 1.37
T246381: Expand the set of bundled extensions and skins in MediaWiki 1.36
T232854: Expand the set of bundled extensions and skins in MediaWiki 1.35
T191746: Bundle LoginNotify extension with MediaWiki
T209220: Expand the set of bundled extensions and skins in MediaWiki 1.34
T191739: Bundle Thanks extension with MediaWiki
It almost certainly doesn't work then, since for example the syntax for defining auto-incrementing ID fields is different, PG doesn't have "unsigned", and other incompatibilities.
It might work if someone were to write the schema for it and wire it into EchoHooks::onLoadExtensionSchemaUpdates(). MediaWiki's DQL and DML abstractions are pretty good if used right, it's just the DDL that's almost completely not abstracted.
Based on the determination above, and that clearly we are not going to get DB schemata written, tested, and merged in the next 11 days when there are no volunteers who care about PG support around, I'm moving this and related tasks to 1.35 and marking as Stalled.
Why is that a dependency? CentralAuth is not bundled; if Echo works in Postgres as part of the bundle but doesn't work when random extension X is also added to the bundle, that should not be a blocker IMO.
If you want to write a set of config in CI that knows to pull the CentralAuth dependency from Notifications but only when running the postgresql DB back-end, and convince RelEng to allow that complexity into their stack, be my guest.