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].
Any comment about these actions is very welcome. Best
I forgot to mention the patch:
[1]: https://gerrit.wikimedia.org/r/151114
On 8/14/14, 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.
Another thing that is happening for i18n is that we are migrating to json [1].
Any comment about these actions is very welcome. Best -- Amir
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.
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.
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
2014-08-15 1:04 GMT+03:00 Antoine Musso hashar+wmf@free.fr:
So in short: what is hard in installing pywikibot?
Last time I checked, i18n installation wasn't done automatically (no idea if by design or by fault). This means that you actually have to read the instructions, which as we all know, engineers do only as a last resort.
Second, when trying to install manually, all kind of errors would pop up (don't ask me for specifics at this time please).
IMHO, anything more than 2 commands needed to install pywikibot (download/sync + install) would count as "hard".
Strainu
Il 14/08/2014 15:00, Amir Ladsgroup ha scritto:
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].
Any comment about these actions is very welcome. Best
Per Hashar and Xqt, I oppose the merge.