Last modified: 2013-04-08 15:00:46 UTC
Everything that's on svn.wikimedia.org needs a new home. Putting it on gerrit.wikimedia.org doesn't make sense. I propose a new subdomain (docs.mediawiki.org) to hold this. Not sure where the best home is for it though.
+1 to move it to mediawiki.org subdomain (I proposed it already several years ago ;-)), but suggesting doc. only (aka no plural).
I should follow up by saying that we're looking to move this to a jenkins job instead of being done as a daily cron. I don't think (and Antoine agrees) that we should dual-purpose gallium to serve this information--so it needs a real home somewhere.
(In reply to comment #1) > +1 to move it to mediawiki.org subdomain svn.mediawiki.org has been a CNAME alias for svn.wikimedia.org for some time, so this bug applies to http://svn.mediawiki.org/doc/ as well. although most of the web links are to svn.wikimedia.org. "You are in a maze of {media|wiki(m|p)edia} hosts..." :)
Who actually creates that documentation, who has access etc...?
(In reply to comment #4) > Who actually creates that documentation, who has access etc...? It's auto-generated based on code documentation. It's just a matter of finding a host and a cronjob to update it daily or whatever.
(In reply to comment #2) > I should follow up by saying that we're looking to move this to a jenkins job > instead of being done as a daily cron. I don't think (and Antoine agrees) that > we should dual-purpose gallium to serve this information--so it needs a real > home somewhere. Wouldn't it be easier to trigger this from Gerrit than from Jenkins? After all, we don't want the documentation be based on some random commit, but on merges. Also, given the rate of change in documentation, I think a daily run may not be perfect, but enough.
I have request a DNS entry under mediawiki.org with https://rt.wikimedia.org/Ticket/Display.html?id=4002
(In reply to comment #7) > I have request a DNS entry under mediawiki.org with RT #4002 For everybody's info: That's fixed now.
Moving from Git/Gerrit to "Testing Infrastructure". Will be solved whenever I complete the doc generation jobs in Jenkins.
integration/jenkins: Add tool mwcore-docgen.sh Change-Id: I5dd693c81b28dc8d5231482a914fedf2518a1bb2 integration/jenkins-job-builder-config: Add job mediawiki-core-docgen Change-Id: I67cf7405c562522b95ce216be25c3ad93215e980 integration/zuul-config: Trigger job mediawiki-core-docgen on postmerge Change-Id: I3c8d5e395e35e003689dd15b7c5b1ffec258957e Change-Id: I84579ad01a10fd9377795862bfb262b635925ca6 operations/puppet: Ensure package doxygen Change-Id: Ie7fffca8b685cee49bf39e46a12486bbe1bd977c This also fixes bug 26712.
Followup tasks filed under bug 46302, anybody willing to take a look?