Last modified: 2014-10-12 16:27:22 UTC
Prior to Git and Puppet and other niceties, https://noc.wikimedia.org/conf/ served a more important purpose: providing snapshots and later up-to-date symlinks of Wikimedia configuration files that weren't available elsewhere. Today, as an index, https://noc.wikimedia.org/conf/ continues to be useful, but it's a bit tedious/awkward to update currently and the page content could use love. https://noc.wikimedia.org/conf/ should be moved to a wiki page on https://wikitech.wikimedia.org and a redirect should be put in place so that https://noc.wikimedia.org/conf/ redirects to the wiki page. The wiki page will allow for much easier editing, meaning a more up-to-date page and we can easily link to GitHub or git.wikimedia.org or elsewhere, with syntax highlighting or serving the raw files. I think https://noc.wikimedia.org/conf/ is a helpful cheatsheet/reference guide, but it doesn't need the additional infrastructure (such as highlight.php) to continue providing the service it provides. I think a wiki page will suffice.
The main thing conf/ provides (or any dynamically created overview) is listing all files in a directory. You'd have to manually keep it in sync. This is where the tables turn and a wiki page will always be behind and the noc page always up to date, by design. I don't oppose it moving elsewhere, but as for edit-ability: It was previously not in version control (or in puppet) but for a while now it's in Git in the (more accessible) mediawiki-config repo: https://github.com/wikimedia/operations-mediawiki-config/blob/master/docroot/noc/conf/index.php It only takes code review, which seems like a valuable thing to have in this case (since the reviewers in that repo are pretty much the same people that use the code the very page is documenting).
(In reply to Krinkle from comment #1) > The main thing conf/ provides (or any dynamically created overview) is > listing all files in a directory. You'd have to manually keep it in sync. > > This is where the tables turn and a wiki page will always be behind and the > noc page always up to date, by design. > > I don't oppose it moving elsewhere, but as for edit-ability: It was > previously not in version control (or in puppet) but for a while now it's in > Git in the (more accessible) mediawiki-config repo: > > https://github.com/wikimedia/operations-mediawiki-config/blob/master/docroot/ > noc/conf/index.php > > It only takes code review, which seems like a valuable thing to have in this > case (since the reviewers in that repo are pretty much the same people that > use the code the very page is documenting). Or we switch it to something like the wikipedia (et al) portals - https://www.wikipedia.org/
(In reply to Sam Reed (reedy) from comment #2) > Or we switch it to something like the wikipedia (et al) portals - > https://www.wikipedia.org/ How's that better than a wikipage? That'll be subject to the same limitations (no globbing of the actual repos), except that it allows arbitrary HTML, which doesn't seem very valuable for a list of just external links and some section headers (probably easier as wikitext).
