On Thu, Aug 14, 2014 at 8:00 PM, Amir Ladsgroup ladsgroup@gmail.com wrote:
Hello, Yesterday after some talks in IRC we thought It would be good if we kill off the i18n submodule and bring the files into core, compat will have the i18n folder but won't receive any updates. One of major advantage of this action is making installation of pywikibot so much easier.
Regarding installation with an i18n submodule, the i18n layer could automatically manage the sub-module, updating it periodically.
I think the main benefit is that code changes will include the message definitions with the qqq descriptions, but for that we only need the en and qqq mandatory i18n files, not every language under the sun.
The main disadvantage that I see is that the repository commit log will be filled with i18n updates, and each of those updates will be doing a travis build. Is there a way to tell travis to skip a type of changeset?
Can we update the i18n files in the repo periodically? e.g. weekly. And provide a maintenance script for people to refresh the i18n files if they want the very latest?
Or have i18n updates land immediately in a dedicated branch that is merged periodically.
How will this work with the 'bots' script repository also being discussed at the moment? Will it have its own i18n files? When i18n data is a message bundle per script, as it is in the i18n submodule, there are no ill effects of putting the i18n files for custom scripts into the same repo as the i18n files for the core product.