Dear localization teams,
yesterday (august 11th), during Flock at Budapest, all items written in the migration plan were discussed and agreed. Future translation platform will be Weblate.
I opened this ticket to the Fedora Council to get the budget to make our translation platform hosted by the Weblate company itself: https://pagure.io/Fedora-Council/tickets/issue/268
If all goes fine, we'll have a testing period with a few projects and a GO/NO GO in December.
Our community need to have more than one person being able to _administrate_ Weblate (mostly adding projects/components and configuring processes). Please express your interest if you feel like you can help on this subject, we'll do the first configuration, document it and test it together so we can learn together.
--- additional information
Access information about this migration: https://fedoraproject.org/wiki/L10N_Move_to_Weblate
My personal goal during my talk was to make sure we shared the "context" and "current processes" titles of these pages, including strengths and weaknesses, so that what I wrote represent the community as a whole, and not my own point of view.
The full session was recorded and I tried my best to repeat the questions.
Please note some feedback done during the session are not yet added to the wiki, but doesn't really impact the request done to Council.
The "User stories" would require quite a lot of work to be complete and be really useful, but take it as an overview of key features we expect. I may go further in describing it over time to help explain how Weblate will work.
There is a huge amount of work ahead of us, most of them should be easy to do, please come to the next meetings and don't be afraid to offer your help.
Have a nice day,
On 11/8/19 2:25 ਬਾ.ਦੁ., Jean-Baptiste wrote:
Dear localization teams,
Hi Jean-Baptiste,
Our community need to have more than one person being able to _administrate_ Weblate (mostly adding projects/components and configuring processes).
I would like to contribute to migration and will help to administration tasks as required.
Thanks Alam
On 8/13/19 5:00 AM, A S Alam wrote:
On 11/8/19 2:25 ਬਾ.ਦੁ., Jean-Baptiste wrote:
Dear localization teams,
Hi Jean-Baptiste,
Our community need to have more than one person being able to _administrate_ Weblate (mostly adding projects/components and configuring processes).
I would like to contribute to migration and will help to administration tasks as required.
Thanks Alam
Hi Jean-Baptiste,
Would also be willing to help out with this.
Regards,
Benson
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Le 13/08/2019 à 15:07, Benson Muite a écrit :
On 8/13/19 5:00 AM, A S Alam wrote:
I would like to contribute to migration and will help to administration tasks as required.
Thanks Alam
Hi Jean-Baptiste,
Would also be willing to help out with this.
Regards,
Benson
Thank you Alam, Benson and Sundeep for offering your help! This is much appreciated :)
Sundeep, would you like to contribute as a developer? Like trying to patches Weblate itself? For example, one think we'll probably need is to make the contributor agreement platform-wide instead of per-component, would you like to give it a look? https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreemen...
Alam, Benson (and eventually Sundeep?), I assume you want to help administrating Weblate, have you ever tried to install Weblate either using Docker or YunoHost?
Anyway, whatever you have your own Weblate or not, you can connect to http://training.holcroft.fr using your FAS account, and I'll promote you administrator, so we can work together.
On 8/15/19 9:06 AM, Jean-Baptiste wrote:
Le 13/08/2019 à 15:07, Benson Muite a écrit :
On 8/13/19 5:00 AM, A S Alam wrote:
I would like to contribute to migration and will help to administration tasks as required.
Thanks Alam
Hi Jean-Baptiste,
Would also be willing to help out with this.
Regards,
Benson
Thank you Alam, Benson and Sundeep for offering your help! This is much appreciated :)
Sundeep, would you like to contribute as a developer? Like trying to patches Weblate itself? For example, one think we'll probably need is to make the contributor agreement platform-wide instead of per-component, would you like to give it a look? https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreemen...
Alam, Benson (and eventually Sundeep?), I assume you want to help administrating Weblate, have you ever tried to install Weblate either using Docker or YunoHost?
Anyway, whatever you have your own Weblate or not, you can connect to http://training.holcroft.fr using your FAS account, and I'll promote you administrator, so we can work together.
Thanks. The setup for Fedora/CentOS seems ok:
https://docs.weblate.org/en/latest/admin/install/venv-redhat.html
How do we want to configure translation memory? (https://docs.weblate.org/en/latest/admin/memory.html)
Is it worth trying to integrate with machine translation? (https://docs.weblate.org/en/latest/admin/machine.html)
Is a multimachine approach worthwhile? If so should we use Kubernetes?
Yunohost is nice but seems quite Debian specific. Have you looked at Ansible, Puppet, Chef or Salt?
I recommend to use Communishift for hosting our own Weblate. See https://fedoraproject.org/wiki/Infrastructue/Communishift
It's an Openshift instance for community hosted by Fedora Infrastructure team.
Best regards, zlopez
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, August 15, 2019 9:58 AM, Benson Muite benson_muite@emailplus.org wrote:
On 8/15/19 9:06 AM, Jean-Baptiste wrote:
Le 13/08/2019 à 15:07, Benson Muite a écrit :
On 8/13/19 5:00 AM, A S Alam wrote:
I would like to contribute to migration and will help to administration tasks as required. Thanks Alam Hi Jean-Baptiste,
Would also be willing to help out with this. Regards, Benson Thank you Alam, Benson and Sundeep for offering your help! This is much appreciated :)
Sundeep, would you like to contribute as a developer? Like trying to patches Weblate itself? For example, one think we'll probably need is to make the contributor agreement platform-wide instead of per-component, would you like to give it a look? https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreemen... Alam, Benson (and eventually Sundeep?), I assume you want to help administrating Weblate, have you ever tried to install Weblate either using Docker or YunoHost? Anyway, whatever you have your own Weblate or not, you can connect to http://training.holcroft.fr using your FAS account, and I'll promote you administrator, so we can work together.
Thanks. The setup for Fedora/CentOS seems ok:
https://docs.weblate.org/en/latest/admin/install/venv-redhat.html
How do we want to configure translation memory? (https://docs.weblate.org/en/latest/admin/memory.html)
Is it worth trying to integrate with machine translation? (https://docs.weblate.org/en/latest/admin/machine.html)
Is a multimachine approach worthwhile? If so should we use Kubernetes?
Yunohost is nice but seems quite Debian specific. Have you looked at Ansible, Puppet, Chef or Salt?
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Well, using community shift is an option if some people are OK with assuming the maintenance of the tool (without the infrastructure team support) for the coming years.
This is a responsibility I personally won't assume.
I opened a request to the council to make it hosted by the Weblate company, so we have a sustainable hosting with upstream support. We should only focus on the tool management (adding a project, a component, managing groups...) a no sysadmin tasks.
-------- Courriel d’origine -------- De : Michal Konecny michal.konecny@packetseekers.eu Envoyé : 15 août 2019 11:39:35 GMT+03:00 À : Fedora Translation Project List trans@lists.fedoraproject.org Objet : Re: Translation platform migration: status update
I recommend to use Communishift for hosting our own Weblate. See https://fedoraproject.org/wiki/Infrastructue/Communishift
It's an Openshift instance for community hosted by Fedora Infrastructure team.
Best regards, zlopez
Communitshift would give a bit more flexibility, for example in adding machine translation - Pontoon is well suited to the Mozilla workflow because they can actively modify it. Am not a member of infrastructure group, but am happy to help.
On 8/15/19 1:06 PM, Jean-Baptiste wrote:
Well, using community shift is an option if some people are OK with assuming the maintenance of the tool (without the infrastructure team support) for the coming years.
This is a responsibility I personally won't assume.
I opened a request to the council to make it hosted by the Weblate company, so we have a sustainable hosting with upstream support. We should only focus on the tool management (adding a project, a component, managing groups...) a no sysadmin tasks.
-------- Courriel d’origine -------- De : Michal Konecny michal.konecny@packetseekers.eu Envoyé : 15 août 2019 11:39:35 GMT+03:00 À : Fedora Translation Project List trans@lists.fedoraproject.org Objet : Re: Translation platform migration: status update
I recommend to use Communishift for hosting our own Weblate. See https://fedoraproject.org/wiki/Infrastructue/Communishift
It's an Openshift instance for community hosted by Fedora Infrastructure team.
Best regards, zlopez _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
On Thu, Aug 15, 2019 at 11:37 AM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
Le 13/08/2019 à 15:07, Benson Muite a écrit :
On 8/13/19 5:00 AM, A S Alam wrote:
I would like to contribute to migration and will help to administration tasks as required.
Thanks Alam
Hi Jean-Baptiste,
Would also be willing to help out with this.
Regards,
Benson
Thank you Alam, Benson and Sundeep for offering your help! This is much appreciated :)
Sundeep, would you like to contribute as a developer? Like trying to patches Weblate itself? For example, one think we'll probably need is to make the contributor agreement platform-wide instead of per-component, would you like to give it a look?
https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreemen...
Sure - thank you - let me take a look! Shall we use https://teams.fedoraproject.org/ to create tasks and track progress?
Alam, Benson (and eventually Sundeep?), I assume you want to help administrating Weblate, have you ever tried to install Weblate either using Docker or YunoHost?
We had deployed Weblate (in RH network) to test and try. (and to learn and compare with Zanata) Had comprehensive study as well.
Anyway, whatever you have your own Weblate or not, you can connect to http://training.holcroft.fr using your FAS account, and I'll promote you administrator, so we can work together. -- Jean-Baptiste Holcroft _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Ok, teams.fedoraproject.org uses FAS login. Have setup a project and sent invitations. Feedback welcome.
Is it worth adding something on the wiki for this, or do we just want to use this for the migration?
On 8/15/19 1:25 PM, Sundeep Anand wrote:
On Thu, Aug 15, 2019 at 11:37 AM Jean-Baptiste <jean-baptiste@holcroft.fr mailto:jean-baptiste@holcroft.fr> wrote:
Sundeep, would you like to contribute as a developer? Like trying to patches Weblate itself? For example, one think we'll probably need is to make the contributor agreement platform-wide instead of per-component, would you like to give it a look? https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreementSure - thank you - let me take a look! Shall we use https://teams.fedoraproject.org/%C2%A0to create tasks and track progress
Alam, Benson (and eventually Sundeep?), I assume you want to help administrating Weblate, have you ever tried to install Weblate either using Docker or YunoHost?We had deployed Weblate (in RH network) to test and try. (and to learn and compare with Zanata) Had comprehensive study as well.
Anyway, whatever you have your own Weblate or not, you can connect to http://training.holcroft.fr using your FAS account, and I'll promote you administrator, so we can work together. -- Jean-Baptiste Holcroft _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org <mailto:trans@lists.fedoraproject.org> To unsubscribe send an email to trans-leave@lists.fedoraproject.org <mailto:trans-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
At the moment admins for the teams.fedoraproject.org migration task tracking are Benson, Sundeep and Jean-Baptiste
Anyone with a FAS account should be able to login - can add a few more details on wiki if it is helpful. Flock and Silverblue projects seem to be the most active:
https://teams.fedoraproject.org/project/silverblue
https://teams.fedoraproject.org/project/bex-flock-2019
Expect can follow something similar. Need to make tasks out of items listed on the wiki:
https://fedoraproject.org/wiki/L10N_Move_to_Weblate
Would there be community objections to use of the translations as machine translation training material? If not, this might allow for some collaboration with machine translation companies in a similar way to the use of reCaptcha for crowdsourcing image labels.
On 8/15/19 3:03 PM, Benson Muite wrote:
Ok, teams.fedoraproject.org uses FAS login. Have setup a project and sent invitations. Feedback welcome.
Is it worth adding something on the wiki for this, or do we just want to use this for the migration?
On 8/15/19 1:25 PM, Sundeep Anand wrote:
On Thu, Aug 15, 2019 at 11:37 AM Jean-Baptiste <jean-baptiste@holcroft.fr mailto:jean-baptiste@holcroft.fr> wrote:
Sundeep, would you like to contribute as a developer? Like trying to patches Weblate itself? For example, one think we'll probably need is to make the contributor agreement platform-wide instead of per-component, would you like to give it a look? https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreementSure - thank you - let me take a look! Shall we use https://teams.fedoraproject.org/%C2%A0to create tasks and track progress
Alam, Benson (and eventually Sundeep?), I assume you want to help administrating Weblate, have you ever tried to install Weblate either using Docker or YunoHost?We had deployed Weblate (in RH network) to test and try. (and to learn and compare with Zanata) Had comprehensive study as well.
Anyway, whatever you have your own Weblate or not, you can connect to http://training.holcroft.fr using your FAS account, and I'll promote you administrator, so we can work together. -- Jean-Baptiste Holcroft _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org <mailto:trans@lists.fedoraproject.org> To unsubscribe send an email to trans-leave@lists.fedoraproject.org <mailto:trans-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
trans mailing list --trans@lists.fedoraproject.org To unsubscribe send an email totrans-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
No objection from the Hebrew team.
On Thu, Aug 15, 2019, 22:51 Yuri Chornoivan yurchor@ukr.net wrote:
четвер, 15 серпня 2019 р. 22:38:27 EEST Benson Muite написано:
Would there be community objections to use of the translations as machine translation training material?
No objections from Ukrainian team.
Best regards, Yuri _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
It looks like I'm not an admin, and that non project member can't do anything.
Can you please make it work as Pagure or the wiki? Any logged user should be able to add items and comments. If we can't do that, I would prefer to use Pagure and the roadmap feature or the labelling feature.
Thanks for your help!
-------- Courriel d’origine -------- De : Benson Muite benson_muite@emailplus.org Envoyé : 15 août 2019 22:38:27 GMT+03:00 À : trans@lists.fedoraproject.org Objet : Re: Translation platform migration: status update
At the moment admins for the teams.fedoraproject.org migration task tracking are Benson, Sundeep and Jean-Baptiste
Anyone with a FAS account should be able to login - can add a few more details on wiki if it is helpful.
On Sun, Aug 18, 2019 at 2:36 PM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
Can you please make it work as Pagure or the wiki? Any logged user should be able to add items and comments. If we can't do that, I would prefer to use Pagure and the roadmap feature or the labelling feature.
The trick with that is to enable those permissions for unauthenticated users. It sounds scarier than it is because our FAS authentication plugin prevents actual non-authenticated users from making changes, as best as I have been able to tell.
I added some of the Weblate capabilities in here: https://fedoraproject.org/wiki/L10N_Move_to_Weblate/Objective:_hosting_proje...
Can you please add the Fedora side? I'm not really sure what are the requirements but I know Weblate meets most localization demands. Yaron Shahrabani
<DevOps - Hebrew translator>
On Mon, Aug 19, 2019 at 3:47 PM Ben Cotton bcotton@redhat.com wrote:
On Sun, Aug 18, 2019 at 2:36 PM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
Can you please make it work as Pagure or the wiki? Any logged user
should be able to add items and comments. If we can't do that, I would prefer to use Pagure and the roadmap feature or the labelling feature.
The trick with that is to enable those permissions for unauthenticated users. It sounds scarier than it is because our FAS authentication plugin prevents actual non-authenticated users from making changes, as best as I have been able to tell.
-- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Le 2019-08-20 09:38, Yaron Shahrabani a écrit :
Can you please add the Fedora side? I'm not really sure what are the requirements but I know Weblate meets most localization demands.
In the "Current processes" part, you'll see: --- Multiple files format are theoretically supported by Zanata, but only gettext format really matter. `SELECT contentType, count(id) FROM hdocument GROUP BY contentType` shows 12702 application/x-gettext and 137 text/plain. Default file type by project: File 12, Gettext 80, NULL 23, Podir 5, Properties 2, Xliff 1, Xml 1 ---
This means only gettext really is required for the migration. I assume the categories files/Xliff and XML are tests or side projects. Anyway Weblate handles it if it appears to be more important than expected.
Although it also supports the other types, should we invest energy in making sure the rare formats works or it's a waste of time? Any other thing needed for completion? Yaron Shahrabani
<DevOps - Hebrew translator>
On Tue, Aug 20, 2019 at 2:27 PM Jean-Baptiste Holcroft < jean-baptiste@holcroft.fr> wrote:
Le 2019-08-20 09:38, Yaron Shahrabani a écrit :
Can you please add the Fedora side? I'm not really sure what are the requirements but I know Weblate meets most localization demands.
In the "Current processes" part, you'll see:
Multiple files format are theoretically supported by Zanata, but only gettext format really matter. `SELECT contentType, count(id) FROM hdocument GROUP BY contentType` shows 12702 application/x-gettext and 137 text/plain. Default file type by project: File 12, Gettext 80, NULL 23, Podir 5, Properties 2, Xliff 1, Xml 1
This means only gettext really is required for the migration. I assume the categories files/Xliff and XML are tests or side projects. Anyway Weblate handles it if it appears to be more important than expected. _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
As all we do is open source, it's fine to reuse our work for any activity as long as it respect the license.
If such activities interests you, here is an extraction of all our translation I did for the amagama team:
https://jibecfed.fedorapeople.org/partage/2019-07-06-all-fedora-zanata-org-t...
And here is the script to run it yourself: https://github.com/Jibec/fedora-translation-statistics/blob/master/get_zanat...
You just have to change the headers; headers = {"X-Auth-User":"jibecfed", "X-Auth-Token":"change-me"}
Note: it produce one multilingual translation memory file (tmx) per project-iteration. If you had a Python script to transform+merge it in one tmx per language with all projects, it would be great!
Would there be community objections to use of the translations as machine translation training material? If not, this might allow for some collaboration with machine translation companies in a similar way to the use of reCaptcha for crowdsourcing image labels.
niedz., 18 sie 2019 o 20:48 Jean-Baptiste jean-baptiste@holcroft.fr napisał(a):
As all we do is open source, it's fine to reuse our work for any activity as long as it respect the license.
If such activities interests you, here is an extraction of all our translation I did for the amagama team:
https://jibecfed.fedorapeople.org/partage/2019-07-06-all-fedora-zanata-org-t...
And here is the script to run it yourself: https://github.com/Jibec/fedora-translation-statistics/blob/master/get_zanat...
You just have to change the headers; headers = {"X-Auth-User":"jibecfed", "X-Auth-Token":"change-me"}
Note: it produce one multilingual translation memory file (tmx) per project-iteration. If you had a Python script to transform+merge it in one tmx per language with all projects, it would be great!
Would there be community objections to use of the translations as machine translation training material? If not, this might allow for some collaboration with machine translation companies in a similar way to the use of reCaptcha for crowdsourcing image labels.
I’m pretty sure translators have copyright over their work and you can’t reuse translations without attribution (additionally to any license concerns.) I’m not a lawyer, of course.
Best regards,
Le 18/08/2019 à 21:56, Piotr Drąg a écrit :
I’m pretty sure translators have copyright over their work and you can’t reuse translations without attribution (additionally to any license concerns.) I’m not a lawyer, of course.
Best regards,
I believe you this is true, but I'm unsure how we can respect it with the TMX extracted (which doesn't contain any list of contributors).
Anyway, what would be the requirement? Only listing the contributor name or what we have in GNOME (name, email, years)?
Could you someday write about it on the Fedora community blog to refresh memories?
There probably is some clarification needed with copyleft and non copyleft licenses some of us (I include myself in this) use daily without paying a lot of attention.
I'm often annoyed by projects not including translators in the list of contributors, this may be a good argument on why we should be listed ;)
Thanks a lot for your help
On 8/18/19 9:56 PM, Piotr Drąg wrote:
niedz., 18 sie 2019 o 20:48 Jean-Baptiste jean-baptiste@holcroft.fr napisał(a):
As all we do is open source, it's fine to reuse our work for any activity as long as it respect the license.
If such activities interests you, here is an extraction of all our translation I did for the amagama team:
https://jibecfed.fedorapeople.org/partage/2019-07-06-all-fedora-zanata-org-t...
And here is the script to run it yourself: https://github.com/Jibec/fedora-translation-statistics/blob/master/get_zanat...
You just have to change the headers; headers = {"X-Auth-User":"jibecfed", "X-Auth-Token":"change-me"}
Note: it produce one multilingual translation memory file (tmx) per project-iteration. If you had a Python script to transform+merge it in one tmx per language with all projects, it would be great!
It seems possible to configure Weblate to do this for all projects in a single Weblate instance. Ideally would want to do this across a larger number of translation projects for open source software.
Would there be community objections to use of the translations as machine translation training material? If not, this might allow for some collaboration with machine translation companies in a similar way to the use of reCaptcha for crowdsourcing image labels.
I’m pretty sure translators have copyright over their work and you can’t reuse translations without attribution (additionally to any license concerns.) I’m not a lawyer, of course.
Best regards,
Ok. License terms for use of translation memory may need some thought - if it is an exact string match of a previous translation, does attribution go to the person that first entered the translation or to the person that approved the translation? If it is not an exact match, and one has a derived work, what more should be done? At present Pontoon assigns credit to the person that authorizes the translation, even if it came from translation memory suggestions or a machine learned suggestion. Pontoon's terms and conditions do not seem to be very specific in this area - https://pontoon.mozilla.org/terms/
On 19/8/2019 2:56 AM, Piotr Drąg wrote:
niedz., 18 sie 2019 o 20:48 Jean-Baptiste jean-baptiste@holcroft.fr
Would there be community objections to use of the translations as machine translation training material? If not, this might allow for some collaboration with machine translation companies in a similar way to the use of reCaptcha for crowdsourcing image labels.
I’m pretty sure translators have copyright over their work and you can’t reuse translations without attribution (additionally to any license concerns.) I’m not a lawyer, of course.
Best regards,
I think we all agreed CLA[1] and FPCA[2] when we decided to make contributions. So we can use the FPCA as the basic. It's safe when the use of the translations follows the agreement.
[1] https://fedoraproject.org/wiki/Legal:Licenses/CLA [2] https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement
On Mon, Aug 12, 2019 at 2:56 AM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
Dear localization teams,
yesterday (august 11th), during Flock at Budapest, all items written in the migration plan were discussed and agreed. Future translation platform will be Weblate.
I opened this ticket to the Fedora Council to get the budget to make our translation platform hosted by the Weblate company itself: https://pagure.io/Fedora-Council/tickets/issue/268
If all goes fine, we'll have a testing period with a few projects and a GO/NO GO in December.
Our community need to have more than one person being able to _administrate_ Weblate (mostly adding projects/components and configuring processes). Please express your interest if you feel like you can help on this subject, we'll do the first configuration, document it and test it together so we can learn together.
--- additional information
Access information about this migration: https://fedoraproject.org/wiki/L10N_Move_to_Weblate
My personal goal during my talk was to make sure we shared the "context" and "current processes" titles of these pages, including strengths and weaknesses, so that what I wrote represent the community as a whole, and not my own point of view.
The full session was recorded and I tried my best to repeat the questions.
Please note some feedback done during the session are not yet added to the wiki, but doesn't really impact the request done to Council.
The "User stories" would require quite a lot of work to be complete and be really useful, but take it as an overview of key features we expect. I may go further in describing it over time to help explain how Weblate will work.
There is a huge amount of work ahead of us, most of them should be easy to do, please come to the next meetings and don't be afraid to offer your help.
Happy to help with whatever (and in any manner) I can.
thanks, sundeep
Have a nice day,
Jean-Baptiste Holcroft _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
-
A S Alam -
Ben Cotton -
Benson Muite -
Jean-Baptiste -
Jean-Baptiste Holcroft
-
Michal Konecny -
Piotr Drąg -
Sundeep Anand -
Tiansworld -
Yaron Shahrabani -
Yuri Chornoivan