kicad-doc-devs team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

@Kinichiro, great work!  Thank you for taking the lead on getting the
translations up to date.  To make life easier for future stable release
translations, I propose a five week period as follows:

Week 1: Last call for documentation and UI string changes.
Week 2: Freeze documentation and UI strings to allow two weeks for
        translations to catch up.
Week 5: Translation freeze and tag to begin packaging.

This gives everyone a week to get any final doc and UI strings into the
their respective repos, three weeks to complete the translations, and a
week for the package devs.  I will coordinate with the doc, library, and
developer mailing lists so we are all on the same page.  I'm open to
changing the time required to complete these tasks if need be.

Cheers,

Wayne

On 12/15/2016 2:32 PM, Nick Østergaard wrote:
> Hi, I will try to add some comments inline.
> 
> 2016-12-15 17:42 GMT+01:00 kinichiro inoguchi <kinichiro.inoguchi@xxxxxxxxx>:
>> Hi,
>>
>> I think 4.0.5 translation works are done.
>> Thanks for your cooperation.
>>
>> This time 4.0.5 traslation of docs, it was kind of a experiment for
>> translation project, for me.
>>
> 
> Kinichiro, thank you very much for your effort in general and
> especially for taking ownership/responsibility for it.
> 
>> - reveal the announcement by this ML and GitHub issue topic
>> - set the due date
>> - call for translators, and ask them to declare their target language
>>
> 
> Yes, we could also create an issue on github to track it to make it a
> bit more visible. Currently the due date is "a couple of weeks", sort
> of depending on the need. We could make it a policy to have at least
> three weeks after the intention of a KiCad release has been announced.
> 
>> After this 4.0.5 translation period, I have some impressions.
>>
>> - barrier before the translation
>>
>>   This is my reflection point.
>>   There are several barrier before starting translation work.
>>   selecting branch, updating .po file and git operations.
>>   I should remove these barriers before starting translation announcement.
>>   I think GUI i18n translation also has same kind of barrier.
>>
> 
> I don't consider the actions needed for the GUI i18n any different
> from the doc i18n. The only difference is that the GUI translations
> contains less information and is easier to handle. The docs sometimes
> have huge changes done in comparison to the GUI translations.
> 
>> - situations of translators and translations are different each other
>>
>>   Some translators are still working on, but some translators are gone.
>>   Some translations are maintained well, some translations are not.
>>   Keeping the well-translated-state and motivation are important.
>>
> 
> Yes, motivation is important, but we also should take what we can get.
> I don't say you imply this; but we shall not make a policy where we
> only publish a translation if it is 100% complete for all apps. This
> could mean that someone hard work might not get released. By having
> almost 100% complete translations might help motivate
> drive-by-translators or newcomers looking for something to contribute
> with.
> 
>> - travis-ci helps verifying pull-request on GitHub
>>
>>   This was a good point.
>>   Almost translators do not have the build environment, and they could not
>>   tell if their work break the build or not.
>>   Now, pull-request on 4.0 branch is checked by Travis-ci automated build.
>>
>> - more period required, 5 days are too short
>>
>>   Every work requires more days and period than it has.
>>   If it was 20 days, I would say "20 days are too short" :-)
>>   If we were told the due date before, translators could adjust their schedules.
>>
> 
> Well, the five days here came about because it was found that some of
> the python script examples were not matching the kicad release. I am
> not sure it was necessary to call for an update from all translators.
> It might have been easier to just update it manually in the po files,
> but I did not check this before hand.
> 
> The announcement about 4.0.5 was made a month ago in the 7th of
> November [1], and I forwarded that to the kicad-doc-devs list a small
> week after on the 12th [2]. Counting the 7th of November as the
> announcement that is almost six weeks before. Also remember, none of
> us are paid or signed a contract, so none of us can guarantee
> anything, but can try to do a best effort and help each other reach a
> common goal, that is improve KiCad, respect each other, and be proud
> of it. :)
> 
>> Best regards,
>>
>> Kinichiro
>>
> 
> Thanks to all involved parties, and I hope you will still consider
> contributing in the future and remember to also use KiCad now and then
> :)
> 
> Nick Østergaard
> 
> [1] https://lists.launchpad.net/kicad-developers/msg26757.html
> [2] https://lists.launchpad.net/kicad-doc-devs/msg00042.html
>