Red Hat Bugzilla – Bug 196961
Wiki update to capture SoC changes
Last modified: 2014-01-21 18:24:31 EST
As you are likely aware, we are working with a Summer of Code student to make improvements in the MoinMoin handling of XML output: http://fedoraproject.org/wiki/MoinDocBookProject Mikko is working with upstream Moin Moin, hosting his code changes in their CVS and working closely with their development team on everything. This, after all, is the Fedora Way. Now we are going to be just downstream consumers. We'd like to get the instance of MoinMoin on fp.org ... or on a stage.fp.org ... updated to the latest (CVS HEAD?), so that we can output Docs/Beats into XML for the FC6 tests and release. Naturally, the sooner we can get an instance under our control, the better. The FDP team working on release notes needs to be able to make changes and output to XML at-will in order to meet the very tight deadlines around release notes translation and ISO spins: http://fedoraproject.org/wiki/DocsProject/Schedule Please let us know ASAP what is feasible and what schedule for update you would like to follow. Thanks - Karsten
We're going to use the test instance at docbook.wikiwikiweb.de for the FC6 test2 release notes. To do so, I've decided that we are going to use new syntax and macros that are only in the latest Moin Moin code. The content needs to move forward like this, so we are definitely going to need the underlying platform to move along with it. The age old battle, on Fedora Project ground -- can we afford our own infrastructure to be as leading edge as the packages? I hope so and think we should. *munch, munch* Dog food tastes good!
You can install per-instance configurations of moin in a subdir w/o a lot of trouble - especially if you just want it to run as a cgi. I'd suggest we get the vhost configured on fpserv and then once we're ready for production make sure the new site goes there.
Awesome, great idea. Elliot - can someone on the Infrastructure team be accountable for getting that done? Something like: 1. Identify what is a good $DATE for a live instance and the projected $VERSION of Moin Moin to be used, then work backward from there. 2. Install the HEAD (?) of Moin Moin development into a sub-directory and create a vhost to point at it. Goal -- working usage as a CGI, as soon as possible. 3. Keep the sub-directory updated to coincide with the changes rolling in from the Summer of Code hacking. At least twice a week? 4. Prepare a plan for rolling out the sub-directory instance as the live instance when we reach $DATE. Things to ponder: i. Can we keep a sync on the Wiki files themselves, so that changes made in the one instance propagate to the other (symlinks?)? Or is this not advised, and we should just copy over pages manually when preparing to do a release notes XML output?
I'll be working on this very soon.
When is the SOC code supposed to get applied to our infrastructure for roll out?
Thanks for the reminder; there is a bit more that has to be done before we can use the code. i) I'll write an email today that connects mmcgrath, Thomas Waldmann from Moin, and mvirkill. The SoC code has some small stuff that needs to be done to get it accepted into the main: * Code styling * Documentation ii) We need to push the content on the project that is on the fedoraproject.org Wiki up into moinmoin.wikiwikiweb.de iii) Waldmann is going to have a small list of what we need to do to prepare for the upgrade, aiui mainly around page names (no spaces, etc.). I saw a number of examples of one of the problems, iirc, but Thomas said there are some scripts we can use. Doing all this will get the SoC code into the trunk in time for the next release. We can then start using an RC of that release on fp.org.
With MoinMoin no longer being used this bug should be somehow closed.