[16:59:58] Krinkle: how did #wikimedia-general-or-unknown end up called #wmf-general-or-unknown? basically everything in the project description is non-WMF-specific [19:19:28] > For all configuration issues and other issues specific to the sites and instrastructure of Wikimedia Foundation (as opposed to relating the [Wikimedia] software that we develop), including issues specific to the content and configuration of Wikipedia, Wiktionary, Commons, and other Wikimedia projects. [19:20:35] https://phabricator.wikimedia.org/project/view/151/ [19:24:53] I think the point is to distinguish between bugs/issues that affect a WMF site as opposed to bugs experienced elsewhere with software published via/at/by Wikimedia (e.g. a library that has no tag, or any Gerrit-hosted extension, etc.) [19:27:12] What in the description appears non-wmf specific? [19:46:13] it has aliases like #common-js and #local-wiki-issues. It indicates NavPopups and ProveIt are subprojects. [19:46:28] Those don't have anything to do with the WMF. [19:49:01] If you look at actual usage, it's almost entirely related to Wikimedia websites (often volunteer-maintained aspects of the Wikimedia websites) and not to anything the WMF does specifically. [19:52:48] more pragmatically, I think the name discourages people for adding the tag to tasks it should be added to, either because it sounds like official WMF business, or because they don't think to search for "WMF" in the project dropdown in the first place. [22:31:16] I understand what you mean, but to me WMF doesn't mean that in this context. "almost entirely related to Wikimedia sites" = WMF wikis, as opposed to Wikimedia software on itself. [22:32:01] it's aliased either way so wikimedia-general will pull that up [22:32:17] or did that get lost somehow? [22:33:01] yeah, it's there. searching "wikimedia-gene" suggests "wmf-general-or-unknown" [22:34:18] I guess one could rename it "wmf-wiks-other" or "wikimedia-sites-general" or some such. [22:35:39] TimStarling: I'm looking at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TimedMediaHandler/+/1006088 and noticing our fork of pear/File_Ogg actually has you and bvibber as leads at http://pear.php.net/package/File_Ogg. I wonder if that actually needs to be a fork? [22:38:03] It looks like we've made some commits to https://github.com/pear/File_Ogg. I wonder if you/we indeed have commit access there since it moved from sourceforge to github? [22:39:35] https://pear.php.net/bugs/bug.php?id=21129 by Reedy is the only open issue. I wonder how controversial it would be if we moved it to Gerrit and and published it only to packagist. Last release in 2010. So I people aren't waiting for a release.