Last modified: 2014-09-12 09:17:32 UTC
There is the LocalisationUpdate extension [1] but only few people use it. It is slow and needs a special configuration with cron. If we could integrate it into core, make it fast enough so that cron would not be needed it would allow a lot of third parties to enjoy the blazingly fast localisation updates (under 36 hours) that Wikimedia projects currently have. To make it fast enough, it is likely that a separate service needs to be implemented. It could be standalone or part of some MediaWiki instance. It should be secure and allow querying only needed data. http://www.mediawiki.org/wiki/Extension:LocalisationUpdate Proposed by the Language team at http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#MediaWiki_LocalisationUpdate_for_all Since MediaWiki core is affected, we need the buy-in from the maintainers before proposing it as a GSOC / OPW project.
Hi, this project is still listed at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#MediaWiki_LocalisationUpdate_for_all Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the "Featured projects" section if it has community support and mentors.
According to GSoC 2014 results: A project was created: https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2 Code was published at https://github.com/konarak/LUv2/tree/epicmess The mentors considered the project PASSED, but it is unclear from the updates in which status it is now: https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates We are also missing the required blog post summarizing all this. Please wrap up properly your project.
Hi Quim, sorry for the delays. The work on the LUv2 service is done. I am yet to start working on writing code for the extension (which can be integrated with core) due to some meatspace work. I'll make sure to publish the final report by the end of this week (SF time).
