|
Sort Order:
I understand that this is needed to resolve Is there any progress on this? It really is getting quite tough to maintain the docs; check which ones have been changed and need review/transcluding. There's a special need for this now since we need to rewrite a lot of documentation for NGS... Short answer: no. It's a non-trivial problem and takes up waaaay more time than I have available to spend, I'm afraid. Anyone else is welcome to volunteer a solution. Acceptable solutions will be appropriate to our hosting; repeatable; maintainable; documented; secure; and should ideally come with an almost-zero-downtime upgrade path from where we are now. Perhaps others understand the problems with this; however I'm certainly unable to comment personally Is it the maintenance cost of vast numbers of URL rewrite rules to workaround not using "preferred" url structure? (if I understand Pavan's suggestion correctly) Or the sheer amount of testing required? 1. wiki.musicbrainz.org is part of the live stack, i.e. you can't just dive in and make changes; and we have no test rig. So this slows progress. 2. In order to become maintainable, at some point we need to reinstall the wiki from scratch and migrate all the data across. The bare mediawiki + a couple of rewriterules + API is actually pretty easy. 3. Then, install a truckload of extensions that the community deems to be requirements. All those extensions need to be sourced from somewhere in a maintainable manner, and installed, and tested, and shown to work with each other. For me, this is the time consuming part. 4. Seamlessly switch over from the existing wiki installation to the new one. A workaround for transclusion is in place now, so this isn't as critical as it was before - will leave in Decision Required, i.e. On Hold. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Normal
MediaWiki api not working
Perhaps it'd help if we could define the problem better. I'm not actually entirely sure what Pavan was asking for you to do here; or which part is extremely time consuming. Could you please spell out which parts of the above are unacceptable or too time consuming?
Dave, did you get a chance to look into this at all?
While this may not be as important as other tickets, an api does need to be made accessible soon. The wikidoc transclusion system will be a pita to maintain without one.