Change Details

(10:36:32 AM) bawolff: Id really like the extension infobox to be loaded from extension.json (10:36:54 AM) bawolff: Almost all of our code works (10:37:14 AM) James_F: bawolff: I'd really like to kill most of the content of MW.org and load it "live" from git. (10:37:19 AM) ***brion hmm, i may want to realign my priorities for 2017 to support roadmap & docs explicitly (10:37:23 AM) addshore: James_F: +1 to that (10:37:32 AM) bawolff: yep (10:37:48 AM) James_F: bawolff: That way we can version the documentation properly for the version you have, rather than in one document try to explain config for MW 1.12 all the way up to master. (10:37:50 AM) MatmaRex_mobile: James_F: hmm, didn't we have an OPW intern who wrote an extension to allow that? (10:37:57 AM) MatmaRex_mobile: load stuff into MediaWiki from a Git repo

== Problem == There are some widely used information templates on mediawiki.org which display some software information that could be easily extracted from the source code, but those templates are currently created and maintained manually. This is inefficient and ineffective - it's a significant amount of manual work and often not done, or not updated when code changes. Example: [[https://www.mediawiki.org/wiki/Template:Extension|extension]], [[https://www.mediawiki.org/wiki/Template:MediaWikiHook|hook]] and [[https://www.mediawiki.org/wiki/Template:SettingSummary|config variable]] templates. == Who would benefit == * Developers who don't need to spend time on creating or updating hook/config var pages whenever they * Extension maintainers (especially people who routinely change others' extensions) who don't need to track things like required MW version in two different places * Developers and site admins who will gain access to correct and complete documentation * Possibly site admins running older MW versions because this would allow a much more user-friendly presentation of MW compatibility information == Proposed solution == # find a place to store structured mw.org infobox data - there are several possible approaches, see {T155024} for discussion # write a bot to extract the data from git (`extension.json`, `hooks.txt`, `DefaultSettings.php` phpdoc) and upload it # fetch the data in the infoboxes # for hook/configvar pages, make the bot create them automatically with stub content when they don't exist

(10:36:32 AM) bawolff: Id really like the extension infobox to be loaded from extension.json== Problem == (10:36:54 AM) bawolff: Almost all of our code worksThere are some widely used information templates on mediawiki.org which display some software information that could be easily extracted from the source code, but those templates are currently created and maintained manually. This is inefficient and ineffective - it's a significant amount of manual work and often not done, or not updated when code changes. Example: [[https://www.mediawiki.org/wiki/Template:Extension|extension]], [[https://www.mediawiki.org/wiki/Template:MediaWikiHook|hook]] and [[https://www.mediawiki.org/wiki/Template:SettingSummary|config variable]] templates. == Who would benefit == (10:37:14 AM) James_F: bawolff: I'd really like to kill most of the content of MW.org and load it "live" from git.* Developers who don't need to spend time on creating or updating hook/config var pages whenever they * Extension maintainers (especially people who routinely change others' extensions) who don't need to track things like required MW version in two different places (10:37:19 AM) ***brion hmm, i may want to realign my priorities for 2017 to support roadmap &* Developers and site admins who will gain access to correct and complete docs explicitlyumentation (10:37:23 AM) addshore: James_F: +1 to that* Possibly site admins running older MW versions because this would allow a much more user-friendly presentation of MW compatibility information == Proposed solution == (10:37:32 AM) bawolff: yep# find a place to store structured mw.org infobox data - there are several possible approaches, see {T155024} for discussion (10:37:48 AM) James_F: bawolff: That way we can version the documentation properly for the version you have# write a bot to extract the data from git (`extension.json`, `hooks.txt`, rather than in one document try to explain config for MW 1.12 all the way up to master.`DefaultSettings.php` phpdoc) and upload it (10:37:50 AM) MatmaRex_mobile: James_F: hmm, didn't we have an OPW intern who wrote an extension to allow that? (10:37:57 AM) MatmaRex_mobile: load stuff into MediaWiki from a Git repo# fetch the data in the infoboxes # for hook/configvar pages, make the bot create them automatically with stub content when they don't exist