First of all I think the big misunderstanding here is that every time someone makes a change in translatewiki.net, a patchset will be made. The i18n files are being updated once every week [1] so It's nothing comparing to 53 commits that developers do every week [2] and the files are separated so it won't make history of related files longer.
About the being hard on installation of pywikibot, It's the feedback from workshops and as an example see this bug [3] I was planning to work on this but I think a better solution would be integrating this submodule.
[1] https://gerrit.wikimedia.org/r/#/q/project:pywikibot/i18n,n,z [2] https://github.com/wikimedia/pywikibot-core/graphs/commit-activity [3] https://bugzilla.wikimedia.org/show_bug.cgi?id=66897
Best
On 8/15/14, Antoine Musso hashar+wmf@free.fr wrote:
Le 14/08/2014 15:00, Amir Ladsgroup a écrit :
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.
Another thing that is happening for i18n is that we are migrating to json [1].
I personally prefer having the i18n messages in an other repository and keep the code repository pristine. Ie just en/qqq, the part that actually matter to developers.
What is the issue with git submodule? The install procedure in README.rst seems straightforward.
At worse a tarball could be automatically generated and published somewhere whenever a change is merged in pywikibot/core. This way people can just unzip the result.
So in short: what is hard in installing pywikibot?
Note: if you ever want to merge the i18n repo to core, do a merge commit to keep the history. Probably need specific rights to bypass Gerrit, poke me me if needed.
-- Antoine "hashar" Musso
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l