Archives
Contributors
-
Re: Proposing myself as Procurement & Purchase PSC
+1El mar., 27 jun. 2023 12:17, Harald Panten Lopez <notifications@odoo-community.org> escribió:Hi Community,I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).Thanks!--Harald Panten López
CEO
Sygel Technology S.L
+34 613 04 76 66 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 08:55 - 28 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1El mar, 27 jun 2023 a las 17:17, Julien Carette (<notifications@odoo-community.org>) escribió:+1
Le 27 juin 2023 à 12:17, Harald Panten Lopez <notifications@odoo-community.org> a écrit :
Hi Community,
I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).
My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).
Thanks!
--
Harald Panten López
CEOSygel Technology S.L+34 613 04 76 66 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Angel Moya Pardo
Tlf: (+34) 636 441 277
angel.moya@pesol.es
http://pesol.es
http://angelmoya.es
No me imprimas si no es necesario. Protejamos el medio ambiente
AVISO LEGAL: El contenido de este mensaje de correo electrónico, incluidos los ficheros adjuntos, es confidencial y está protegido por el artículo 18.3 de la Constitución Española, que garantiza el secreto de las comunicaciones. Si usted recibe este mensaje por error, por favor póngase en contacto con el remitente para informarle de este hecho, y no difunda su contenido ni haga copias.
Este aviso legal ha sido incorporado automáticamente al mensaje.
by angel.moya - 08:25 - 28 Jun 2023 -
Publish accounting entries + budget on the website
Hello,We have a public organization who wants to publish all their accounting data including the account budgets on the website in real time (not in the portal but on the website - the module would be like website_account and website_account_budget)Do you know something that can help ?Thanks in advanceBest regards--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.com
by Cyril VINH-TUNG - 06:30 - 28 Jun 2023 -
Routes, trucks and gates
Hello,I have a customer using Odoo 16 to manage his logistics operations: they have 2 warehouses with 12 gates, a fleet of 30 trucks of different sizes and a number of routes.
I checked the transport repo but didn't find much there. Am I missing something?Any suggestion that could help?Thank you--
Maxime Chambreuil
Desde mi móvil
by Maxime Chambreuil - 05:21 - 28 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1
Le 27 juin 2023 à 12:17, Harald Panten Lopez <notifications@odoo-community.org> a écrit :
Hi Community,
I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).
My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).
Thanks!
--
Harald Panten López
CEOSygel Technology S.L+34 613 04 76 66 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Julien Carette - 05:16 - 27 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1
--
NICO SOLUTIONS - ENGINEERING & IT
Inhaber (Owner): Nils Coenen
Dr.-Ruckert-Str. 1G
28865 Lilienthal
Deutschland (Germany)Von: Harald Panten Lopez <notifications@odoo-community.org>
Antworten an: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>
Datum: Dienstag, 27. Juni 2023 um 12:17
An: Contributors <contributors@odoo-community.org>
Betreff: Proposing myself as Procurement & Purchase PSCHi Community,
I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).
My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).
Thanks!
--
Harald Panten López
CEO
Sygel Technology S.L
C/ Àlaba 61, 5ª planta, 08005, Barcelona
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 05:01 - 27 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1--Héctor Villarreal OrtegaTechnical Consultanttwitter: /h_vior | Linkedin: /hectorvior
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
by Héctor Villarreal Ortega - 04:56 - 27 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1From: "Valentin Vinagre Urteaga" <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Tue, 27 Jun 2023 14:42:23 -0000
Subject: Re: Proposing myself as Procurement & Purchase PSC
+1El mar, 27 jun 2023 a las 12:17, Harald Panten Lopez (<notifications@odoo-community.org>) escribió:Hi Community,I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).Thanks!--Harald Panten López
CEOSygel Technology S.L+34 613 04 76 66 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe--Valentín Vinagre Urteaga
CTOSygel Technology S.L+34 613 04 66 67 valentin.vinagre@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
by Enric Tobella Alomar - 04:51 - 27 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1El mar, 27 jun 2023 a las 12:17, Harald Panten Lopez (<notifications@odoo-community.org>) escribió:Hi Community,I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).Thanks!--Harald Panten López
CEO
Sygel Technology S.L
+34 613 04 76 66 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David Vidal - 04:46 - 27 Jun 2023 -
Re: Proposing myself as Procurement & Purchase PSC
+1El mar, 27 jun 2023 a las 12:17, Harald Panten Lopez (<notifications@odoo-community.org>) escribió:Hi Community,I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).Thanks!--Harald Panten López
CEO
Sygel Technology S.L
+34 613 04 76 66 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Valentín Vinagre Urteaga
CTO
Sygel Technology S.L
+34 613 04 66 67 valentin.vinagre@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Valentín Vinagre - 04:42 - 27 Jun 2023 -
Proposing myself as Procurement & Purchase PSC
Hi Community,I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).Thanks!--Harald Panten López
CEO
Sygel Technology S.L
+34 613 04 76 66 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 12:16 - 27 Jun 2023 -
Re: [FIX]:Weblate - use po file download/upload - revisions
Perhaps it could help to look at our Sphinx-based documentation which is automatically translated with deepl and managed (e.g. corrected) via Weblate. The integration is scripted and available here: https://github.com/Nitrokey/nitrokey-documentation/ Am 22.06.23 um 18:16 schrieb Stéphane Bidoul: > A DeepL integration in weblate would be great. If the budget is > reasonable we may even imagine that OCA could cover the DeepL cost. > > I suspect however that a prerequisite to make that work is the better > organization of the projects and glossaries that I mentioned before. > > -sbi > > > On Thu, Jun 22, 2023 at 5:52 PM Rémi CAZENAVE - Le Filament > <notifications@odoo-community.org > <mailto:notifications@odoo-community.org>> wrote: > > Hi Stefano, > > We also had discussions for French translations earlier today (not > really to add validation layers / access rights but rather to > improve the number of translated modules) and we are about to test > translating with DeepL using Traduction Memory and Glossaries to see > how good it gets and if it can improve a lot contributing with > French translation. > > (For now we will test it outside Weblate and import translations > manually in Weblate, but it is also possible to directly interface > Weblate with DeepL to get automatic translations or suggestions, > maybe we could go into that direction if it really helps !) > > > Also, I had a few spare minutes so I unlocked all the repositories > you listed below in Weblate. > > It seems that this could be scripted but I would have needed access > to the server which I do not have so I did it manually, one by one. > > As for why they were locked I cannot say, the only thing I see is > that these were locked because of error, but I could not find the > error... > > > Best Regards, > > Rémi > > > --X-BM-SIGNATURE-- > Le 22/06/2023 à 08:31, Stefano Consolaro a écrit : >> Hi Stéphane, >> you are not alone with a lot a things to do and the my reply time >> to your answer prove it ;-) >> >> We (italian members) have talked a bit and will probably install a >> test server after the summer to test configuration options and >> functionalities. >> After that we will share results and some ideas on how to rules >> the translations. >> >> In the meantime I ask you the favour to unlock some modules listed >> below (but there are many more). >> But, why some modules are locked? >> Is there a way to unlock all at once or do you have to do them one >> at a time? >> Thanks >> >> Modules locked >> agreement-16.0-agreement >> bank-payment-16-0-account_payment_mode >> connector-16-0-test_component >> contract-16-0-contract >> crm-16.0-crm_claim >> currency-16.0-currency_rate_update >> data-protection-16-0/data-protection-16-0-privacy >> fleet-16.0-fleet_vehicle_fuel_type_ethanol >> helpdesk-16.0-helpdesk_mgmt >> hr-16.0-hr_employee_firstname >> iot-16.0-iot_oca >> l10n-italy-16.0-l10n_it_rea >> management-system-16.0-mgmtsystem >> manufacture-16.0-mrp_warehouse_calendar >> project-16.0-project_type >> purchase-workflow-16.0-purchase_discount >> report-print-send-15-0-base_report_to_printer >> report-print-send-16-0-base_report_to_printer >> server-backend-16.0-base_user_role >> server-backend-16-0-base_user_role >> server-env-16-0-server_environment >> vertical-association-16-0-membership_extension >> vertical-hotel-15.0-hotel_reservation >> >> >> Da"Stéphane Bidoul" notifications@odoo-community.org >> <mailto:notifications@odoo-community.org> >> A"Contributors" contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Cc >> DataSat, 10 Jun 2023 12:32:03 -0000 >> OggettoRe: [FIX]:Weblate - use po file download/upload - revisions >> >> Hi Stefano, >> >> I also support the idea, obviously ;) >> >> Unfortunately that alone will not help get things moving as I have >> several other priorities with OCA infrastructure and tooling that >> already barely fit in the time I can allocate to it. >> For instance, just preventing weblate to bring down the OCA server >> swallowed several hours already, recently (and there is still more >> to do). >> >> I'm happy to tweak any configuration you propose but I'd need >> precise indications of what to do with links to the weblate >> documentation. >> The process part also needs to be elaborated. The high level >> principle you mentioned sound good but how do we concretely do >> that in practice? For instance, when one asks to get translation >> access how will Rebecca know which role to give them? What is the >> process to accept a new reviewer for a given language? Can we have >> languages with reviewers and other without? Do we need to publish >> who has reviewer rights? What does all that imply in terms of >> weblate configuration? >> >> Regarding glossaries and translation memories there are also >> important questions to be investigated. For instance, we now have >> one project per repo and branch. Is it possible to share >> glossaries across these? If not, should we / can we group them? >> Who should have permissions to manage glossaries, etc. >> >> So there is quite a bit of research to do that, as far as I know, >> as not been done by anyone yet. >> >> As I don't think these can be easily experimented live on the OCA >> instance (I may be wrong about that), I'd recommend anyone who >> would like to dive in that to setup a test weblate on their local >> machine and play with that to come up with a proposal or a plan. >> I'm happy to help with that too. >> >> Best regards, >> >> -Stéphane >> >> On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro >> <notifications@odoo-community.org >> <mailto:notifications@odoo-community.org>> wrote: >> >> Hi Stéphane, >> did you give a look to mine and Sergio replies (i attached >> them below)? >> >> Last month, as italian community, we had the Odoo Italia Days >> in Milan. We talked with other people interested in setting up >> a better way to manage translations, at least for italian >> language. >> >> We met Simone Orsi, OCA member, that support this idea. >> >> In fact we think that what we are looking for could be useful >> for all language teams. >> >> If you, or someone else, can invest some time to configure >> Weblate to activate the requested features, we can test it and >> give a fast feedback. >> >> Obviously, we welcome all people willing to join the project. >> >> Thanks for your time and help. >> >> Stefano >> >> >> Da"Stefano Consolaro" stefano.consolaro@mymage.it >> <mailto:stefano.consolaro@mymage.it> >> Acontributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Cc >> DataMon, 23 Jan 2023 08:40:30 +0100 >> OggettoRe: [FIX]:Weblate - use po file download/upload - revisions >> >> I give my reply for italian language/community: >> >> > Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of >> existing translations (this could be solved by banning >> offenders)? Or is it incorrect/low quality new translations >> (which can be fixed easily after the fact, I suppose)? Or >> something else? >> As far I know we don't have problems of a misuse of the tool. >> What we noticed is that the "need" and the "hurry" to have the >> translations, or a lack in the definition of a glossary for >> common terms, or the contributions of a new entry (like in >> part I am), goes to some incorrect or not so pertinent >> translations. >> >> > What would be the process to appoint/elect reviewers? Currently we accept anyone who asks. >> Hm, here I don't know what to say, can't be done in the "same >> way" that PSC are nominated for repository in GitHub? >> >> > How to make sure translation proposals are not stuck for too >> long waiting for review? >> Yes, this is a weakness. I don't know if it can be done and >> how, but I'd like to have a system in which the reviewed terms >> can be changed only by reviewers and other terms can be >> changed (and then loaded) by anyone (view *). >> > Should/can we enable the review process per language? This >> may be important as not all language communities have the >> resources to have dedicated reviewers. >> Absolutely yes: the lack of resources is a problem and (*) I >> prefer that a thing is done now than perfect never. So the >> activation of the review process should be decided by each >> community. >> >> Thanks for expanding the discussion, I hope others will join. >> >> >> >> Da"Sergio Zanchetta" notifications@odoo-community.org >> <mailto:notifications@odoo-community.org> >> A"Contributors" contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Cc >> DataMon, 23 Jan 2023 10:36:56 -0000 >> OggettoRe: [FIX]:Weblate - use po file download/upload - revisions >> >> Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul >> <notifications@odoo-community.org >> <mailto:notifications@odoo-community.org>> ha scritto: >> >> We discussed a translation review mechanism before, I >> think, but IIRC we concluded we need a process first. >> >> >> Yes, you are right. :-) >> >> Below, as italian community in addition to Stefano answers, >> you can find a proposal. >> >> Here are a few questions that come to mind. There might be >> more. >> >> - Clearly define the problem we are attempting to solve? >> For instance, Is it "vandalism" of existing translations >> (this could be solved by banning offenders)? Or is it >> incorrect/low quality new translations (which can be fixed >> easily after the fact, I suppose)? Or something else? >> >> >> The second one. Incorrect/low level translations, not only >> new, that don't follow current community guidelines and >> glossaries (language specific). >> >> - What would be the process to appoint/elect reviewers? >> Currently we accept anyone who asks. >> >> - How to make sure translation proposals are not stuck for >> too long waiting for review? >> >> >> I would replicate Transifex structure or similar, if possible. >> Here is a proposal: >> - Anyone can be accepted as translator, strings are pushed as >> soon as translated. (or on a periodic basis) >> - There is a reviewer role, reviewed strings are freezed and >> can't be changed by translators. >> - The coordinator role has reviewer power and can appoint >> translators as reviewers. >> >> The coordinator could be nominated by each localization >> repository PSC. (l10n-*) >> He would be in charge of appointing reviewers evaluating the >> quality of their translations over time, based on >> guidelines/glossary compliance. >> >> - Should/can we enable the review process per language? >> This may be important as not all language communities have >> the resources to have dedicated reviewers. >> >> >> Sure, I add that not all communities have translation >> guidelines. [*] >> >> [*] e.g. italian guidelines (and glossaries) >> https://www.odoo-italia.org/documentazione/14.0/traduzioni.html <https://www.odoo-italia.org/documentazione/14.0/traduzioni.html> >> >> >> >> >> >> >> >> Da"Stéphane Bidoul" notifications@odoo-community.org >> <mailto:notifications@odoo-community.org> >> A"Contributors" contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Cc >> DataSun, 22 Jan 2023 10:27:40 -0000 >> OggettoRe: [FIX]:Weblate - use po file download/upload - revisions >> >> We discussed a translation review mechanism before, I think, >> but IIRC we concluded we need a process first. >> >> Here are a few questions that come to mind. There might be more. >> >> - Clearly define the problem we are attempting to solve? For >> instance, Is it "vandalism" of existing translations (this >> could be solved by banning offenders)? Or is it incorrect/low >> quality new translations (which can be fixed easily after the >> fact, I suppose)? Or something else? >> - What would be the process to appoint/elect reviewers? >> Currently we accept anyone who asks. >> - How to make sure translation proposals are not stuck for too >> long waiting for review? >> - Should/can we enable the review process per language? This >> may be important as not all language communities have the >> resources to have dedicated reviewers. >> >> Best regards, >> >> -sbi >> >> >> >> _______________________________________________ >> Mailing-List: >> https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> >> >> >> Stefano Consolaro >> www.mymage.it <http://www.mymage.it> >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > <mailto:contributors@odoo-community.org> > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> >
by Jan Suhr - 09:41 - 27 Jun 2023 -
Re: Proposing myself as Tools PSC
+1 Le vendredi 16 juin 2023 à 21:12 +0000, Sylvain LE GAL (GRAP) a écrit : > > Hi all, > > I like to become member of the "Tools PSC Team". (https://odoo-community.org/psc-teams/tools-30). My contributions in this area: > > > - Funder of interface-github and odoo-module-migrator repositories > > - I have proposed the following modules to the community : auth_admin_passkey, module_analysis, module_change_auto_install, server_action_navigate, pos_environment, user_all_groups and deeply refactored : server_action_mass_edit (formely "mass_editing") > > Thanks for your attention. > > -- > Sylvain LE GAL > - GRAP, service informatique > - 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17 > - Astreinte : 06.81.85.61.43 // informatique@grap.coop > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- Carmen Bianca BAKKER <carmen@coopiteasy.be> Coop IT Easy
by Carmen Bianca Bakker - 01:33 - 23 Jun 2023 -
Re: Question regarding the Community Discuss functionnality
Hi @David,A great thanks for your answer !RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNANDe: "David Vidal" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Mardi 20 Juin 2023 09:06:50
Objet: Re: Question regarding the Community Discuss functionnalityThat's it. It uses the technology available in the browser itself which is widely supported https://caniuse.com/rtcpeerconnectionEl lun, 19 jun 2023 a las 15:42, Florent Thomas (<notifications@odoo-community.org>) escribió:Thanks for your answer David,So from your point of view, everything is embedded in the community version and don't use external services ?RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNANDe: "David Vidal" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Lundi 19 Juin 2023 09:36:54
Objet: Re: Question regarding the Community Discuss functionnalityEl dom, 18 jun 2023 a las 18:48, Florent Thomas (<notifications@odoo-community.org>) escribió:Hi Community,I'm running v16 community version and I'm wondering what is the technology hiding behind the live discuss feature :I didn't succeed to find out if it relies on an external dependency or ant IAP service.Any feedback will be appreciated,RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNAN_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Florent THOMAS - 09:10 - 23 Jun 2023 -
Re: Proposing myself as Tools PSC
Thanks !
It works.
Le 19/06/2023 à 11:21, Enric Tobella Alomar a écrit :
+1I added you on the group. You should receive the notification soonFrom: "Mignon, Laurent" <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Mon, 19 Jun 2023 08:31:57 -0000
Subject: Re: Proposing myself as Tools PSC
+1On Mon, Jun 19, 2023 at 9:47 AM Jairo Llopis <notifications@odoo-community.org> wrote:El vie, 16 de jun de 2023 a las 21:12:01 PM, Sylvain LE GAL (GRAP) <notifications@odoo-community.org> escribió:I like to become member of the "Tools PSC Team"
+1_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Sylvain LE GAL - GRAP, service informatique - 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17 - Astreinte : 06.81.85.61.43 // informatique@grap.coop
by Sylvain LE GAL - 06:21 - 22 Jun 2023 -
Re: [FIX]:Weblate - use po file download/upload - revisions
A DeepL integration in weblate would be great. If the budget is reasonable we may even imagine that OCA could cover the DeepL cost.I suspect however that a prerequisite to make that work is the better organization of the projects and glossaries that I mentioned before.-sbiOn Thu, Jun 22, 2023 at 5:52 PM Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:Hi Stefano,
We also had discussions for French translations earlier today (not really to add validation layers / access rights but rather to improve the number of translated modules) and we are about to test translating with DeepL using Traduction Memory and Glossaries to see how good it gets and if it can improve a lot contributing with French translation.
(For now we will test it outside Weblate and import translations manually in Weblate, but it is also possible to directly interface Weblate with DeepL to get automatic translations or suggestions, maybe we could go into that direction if it really helps !)
Also, I had a few spare minutes so I unlocked all the repositories you listed below in Weblate.
It seems that this could be scripted but I would have needed access to the server which I do not have so I did it manually, one by one.
As for why they were locked I cannot say, the only thing I see is that these were locked because of error, but I could not find the error...
Best Regards,
Rémi
--X-BM-SIGNATURE--Le 22/06/2023 à 08:31, Stefano Consolaro a écrit :
Hi Stéphane,
you are not alone with a lot a things to do and the my reply time to your answer prove it ;-)
We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
After that we will share results and some ideas on how to rules the translations.
In the meantime I ask you the favour to unlock some modules listed below (but there are many more).
But, why some modules are locked?
Is there a way to unlock all at once or do you have to do them one at a time?Thanks
Modules locked
agreement-16.0-agreement
bank-payment-16-0-account_payment_mode
connector-16-0-test_component
contract-16-0-contract
crm-16.0-crm_claim
currency-16.0-currency_rate_update
data-protection-16-0/data-protection-16-0-privacy
fleet-16.0-fleet_vehicle_fuel_type_ethanol
helpdesk-16.0-helpdesk_mgmt
hr-16.0-hr_employee_firstname
iot-16.0-iot_oca
l10n-italy-16.0-l10n_it_rea
management-system-16.0-mgmtsystem
manufacture-16.0-mrp_warehouse_calendar
project-16.0-project_type
purchase-workflow-16.0-purchase_discount
report-print-send-15-0-base_report_to_printer
report-print-send-16-0-base_report_to_printer
server-backend-16.0-base_user_role
server-backend-16-0-base_user_role
server-env-16-0-server_environment
vertical-association-16-0-membership_extension
vertical-hotel-15.0-hotel_reservation
Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sat, 10 Jun 2023 12:32:03 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
Hi Stefano,
I also support the idea, obviously ;)
Unfortunately that alone will not help get things moving as I have several other priorities with OCA infrastructure and tooling that already barely fit in the time I can allocate to it.For instance, just preventing weblate to bring down the OCA server swallowed several hours already, recently (and there is still more to do).
I'm happy to tweak any configuration you propose but I'd need precise indications of what to do with links to the weblate documentation.The process part also needs to be elaborated. The high level principle you mentioned sound good but how do we concretely do that in practice? For instance, when one asks to get translation access how will Rebecca know which role to give them? What is the process to accept a new reviewer for a given language? Can we have languages with reviewers and other without? Do we need to publish who has reviewer rights? What does all that imply in terms of weblate configuration?
Regarding glossaries and translation memories there are also important questions to be investigated. For instance, we now have one project per repo and branch. Is it possible to share glossaries across these? If not, should we / can we group them? Who should have permissions to manage glossaries, etc.
So there is quite a bit of research to do that, as far as I know, as not been done by anyone yet.
As I don't think these can be easily experimented live on the OCA instance (I may be wrong about that), I'd recommend anyone who would like to dive in that to setup a test weblate on their local machine and play with that to come up with a proposal or a plan. I'm happy to help with that too.
Best regards,
-Stéphane
On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
Hi Stéphane,
did you give a look to mine and Sergio replies (i attached them below)?
Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.
We met Simone Orsi, OCA member, that support this idea.
In fact we think that what we are looking for could be useful for all language teams.
If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.
Obviously, we welcome all people willing to join the project.
Thanks for your time and help.
Stefano
Da "Stefano Consolaro" stefano.consolaro@mymage.itCcData Mon, 23 Jan 2023 08:40:30 +0100Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
I give my reply for italian language/community:
> Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect or not so pertinent translations.
> What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.> How to make sure translation proposals are not stuck for too long waiting for review?
Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
> Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.
Thanks for expanding the discussion, I hope others will join.
Da "Sergio Zanchetta" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Mon, 23 Jan 2023 10:36:56 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.
Yes, you are right. :-)
Below, as italian community in addition to Stefano answers, you can find a proposal.
Here are a few questions that come to mind. There might be more.
- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).
- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
- How to make sure translation proposals are not stuck for too long waiting for review?
I would replicate Transifex structure or similar, if possible. Here is a proposal:
- Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)
- There is a reviewer role, reviewed strings are freezed and can't be changed by translators.
- The coordinator role has reviewer power and can appoint translators as reviewers.
The coordinator could be nominated by each localization repository PSC. (l10n-*)
He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.
- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Sure, I add that not all communities have translation guidelines. [*]
[*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.html
Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sun, 22 Jan 2023 10:27:40 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.
Here are a few questions that come to mind. There might be more.
- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.- How to make sure translation proposals are not stuck for too long waiting for review?
- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Best regards,
-sbi
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Stefano Consolaro
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 06:16 - 22 Jun 2023 -
Re: [FIX]:Weblate - use po file download/upload - revisions
Thanks a lot for handling this, Rémy!Regarding the root cause of the locks I'm not sure but it might be due to git merge conflicts.Conflicts happen when there are force push to the main branches in GitHub or when conflicting changes are made to .po files.Both should be infrequent so there might be something else at play here.-StéphaneOn Thu, Jun 22, 2023 at 5:52 PM Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:
Hi Stefano,
We also had discussions for French translations earlier today (not really to add validation layers / access rights but rather to improve the number of translated modules) and we are about to test translating with DeepL using Traduction Memory and Glossaries to see how good it gets and if it can improve a lot contributing with French translation.
(For now we will test it outside Weblate and import translations manually in Weblate, but it is also possible to directly interface Weblate with DeepL to get automatic translations or suggestions, maybe we could go into that direction if it really helps !)
Also, I had a few spare minutes so I unlocked all the repositories you listed below in Weblate.
It seems that this could be scripted but I would have needed access to the server which I do not have so I did it manually, one by one.
As for why they were locked I cannot say, the only thing I see is that these were locked because of error, but I could not find the error...
Best Regards,
Rémi
--X-BM-SIGNATURE--Le 22/06/2023 à 08:31, Stefano Consolaro a écrit :
Hi Stéphane,
you are not alone with a lot a things to do and the my reply time to your answer prove it ;-)
We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
After that we will share results and some ideas on how to rules the translations.
In the meantime I ask you the favour to unlock some modules listed below (but there are many more).
But, why some modules are locked?
Is there a way to unlock all at once or do you have to do them one at a time?Thanks
Modules locked
agreement-16.0-agreement
bank-payment-16-0-account_payment_mode
connector-16-0-test_component
contract-16-0-contract
crm-16.0-crm_claim
currency-16.0-currency_rate_update
data-protection-16-0/data-protection-16-0-privacy
fleet-16.0-fleet_vehicle_fuel_type_ethanol
helpdesk-16.0-helpdesk_mgmt
hr-16.0-hr_employee_firstname
iot-16.0-iot_oca
l10n-italy-16.0-l10n_it_rea
management-system-16.0-mgmtsystem
manufacture-16.0-mrp_warehouse_calendar
project-16.0-project_type
purchase-workflow-16.0-purchase_discount
report-print-send-15-0-base_report_to_printer
report-print-send-16-0-base_report_to_printer
server-backend-16.0-base_user_role
server-backend-16-0-base_user_role
server-env-16-0-server_environment
vertical-association-16-0-membership_extension
vertical-hotel-15.0-hotel_reservation
Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sat, 10 Jun 2023 12:32:03 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
Hi Stefano,
I also support the idea, obviously ;)
Unfortunately that alone will not help get things moving as I have several other priorities with OCA infrastructure and tooling that already barely fit in the time I can allocate to it.For instance, just preventing weblate to bring down the OCA server swallowed several hours already, recently (and there is still more to do).
I'm happy to tweak any configuration you propose but I'd need precise indications of what to do with links to the weblate documentation.The process part also needs to be elaborated. The high level principle you mentioned sound good but how do we concretely do that in practice? For instance, when one asks to get translation access how will Rebecca know which role to give them? What is the process to accept a new reviewer for a given language? Can we have languages with reviewers and other without? Do we need to publish who has reviewer rights? What does all that imply in terms of weblate configuration?
Regarding glossaries and translation memories there are also important questions to be investigated. For instance, we now have one project per repo and branch. Is it possible to share glossaries across these? If not, should we / can we group them? Who should have permissions to manage glossaries, etc.
So there is quite a bit of research to do that, as far as I know, as not been done by anyone yet.
As I don't think these can be easily experimented live on the OCA instance (I may be wrong about that), I'd recommend anyone who would like to dive in that to setup a test weblate on their local machine and play with that to come up with a proposal or a plan. I'm happy to help with that too.
Best regards,
-Stéphane
On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
Hi Stéphane,
did you give a look to mine and Sergio replies (i attached them below)?
Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.
We met Simone Orsi, OCA member, that support this idea.
In fact we think that what we are looking for could be useful for all language teams.
If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.
Obviously, we welcome all people willing to join the project.
Thanks for your time and help.
Stefano
Da "Stefano Consolaro" stefano.consolaro@mymage.itCcData Mon, 23 Jan 2023 08:40:30 +0100Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
I give my reply for italian language/community:
> Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect or not so pertinent translations.
> What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.> How to make sure translation proposals are not stuck for too long waiting for review?
Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
> Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.
Thanks for expanding the discussion, I hope others will join.
Da "Sergio Zanchetta" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Mon, 23 Jan 2023 10:36:56 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.
Yes, you are right. :-)
Below, as italian community in addition to Stefano answers, you can find a proposal.
Here are a few questions that come to mind. There might be more.
- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).
- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
- How to make sure translation proposals are not stuck for too long waiting for review?
I would replicate Transifex structure or similar, if possible. Here is a proposal:
- Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)
- There is a reviewer role, reviewed strings are freezed and can't be changed by translators.
- The coordinator role has reviewer power and can appoint translators as reviewers.
The coordinator could be nominated by each localization repository PSC. (l10n-*)
He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.
- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Sure, I add that not all communities have translation guidelines. [*]
[*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.html
Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sun, 22 Jan 2023 10:27:40 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.
Here are a few questions that come to mind. There might be more.
- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.- How to make sure translation proposals are not stuck for too long waiting for review?
- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Best regards,
-sbi
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Stefano Consolaro
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 06:11 - 22 Jun 2023 -
Re: [FIX]:Weblate - use po file download/upload - revisions
On Thu, Jun 22, 2023 at 8:31 AM Stefano Consolaro <notifications@odoo-community.org> wrote:
We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
After that we will share results and some ideas on how to rules the translations.Cool, thank you very much. Let me know if you need help with the test server setup.-Stéphane
by Stéphane Bidoul - 06:10 - 22 Jun 2023 -
Re: [FIX]:Weblate - use po file download/upload - revisions
Hi Stefano,
We also had discussions for French translations earlier today (not really to add validation layers / access rights but rather to improve the number of translated modules) and we are about to test translating with DeepL using Traduction Memory and Glossaries to see how good it gets and if it can improve a lot contributing with French translation.
(For now we will test it outside Weblate and import translations manually in Weblate, but it is also possible to directly interface Weblate with DeepL to get automatic translations or suggestions, maybe we could go into that direction if it really helps !)
Also, I had a few spare minutes so I unlocked all the repositories you listed below in Weblate.
It seems that this could be scripted but I would have needed access to the server which I do not have so I did it manually, one by one.
As for why they were locked I cannot say, the only thing I see is that these were locked because of error, but I could not find the error...
Best Regards,
Rémi
--X-BM-SIGNATURE--Le 22/06/2023 à 08:31, Stefano Consolaro a écrit :
Hi Stéphane,
you are not alone with a lot a things to do and the my reply time to your answer prove it ;-)
We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
After that we will share results and some ideas on how to rules the translations.
In the meantime I ask you the favour to unlock some modules listed below (but there are many more).
But, why some modules are locked?
Is there a way to unlock all at once or do you have to do them one at a time?Thanks
Modules locked
agreement-16.0-agreement
bank-payment-16-0-account_payment_mode
connector-16-0-test_component
contract-16-0-contract
crm-16.0-crm_claim
currency-16.0-currency_rate_update
data-protection-16-0/data-protection-16-0-privacy
fleet-16.0-fleet_vehicle_fuel_type_ethanol
helpdesk-16.0-helpdesk_mgmt
hr-16.0-hr_employee_firstname
iot-16.0-iot_oca
l10n-italy-16.0-l10n_it_rea
management-system-16.0-mgmtsystem
manufacture-16.0-mrp_warehouse_calendar
project-16.0-project_type
purchase-workflow-16.0-purchase_discount
report-print-send-15-0-base_report_to_printer
report-print-send-16-0-base_report_to_printer
server-backend-16.0-base_user_role
server-backend-16-0-base_user_role
server-env-16-0-server_environment
vertical-association-16-0-membership_extension
vertical-hotel-15.0-hotel_reservation
Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sat, 10 Jun 2023 12:32:03 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
Hi Stefano,
I also support the idea, obviously ;)
Unfortunately that alone will not help get things moving as I have several other priorities with OCA infrastructure and tooling that already barely fit in the time I can allocate to it.For instance, just preventing weblate to bring down the OCA server swallowed several hours already, recently (and there is still more to do).
I'm happy to tweak any configuration you propose but I'd need precise indications of what to do with links to the weblate documentation.The process part also needs to be elaborated. The high level principle you mentioned sound good but how do we concretely do that in practice? For instance, when one asks to get translation access how will Rebecca know which role to give them? What is the process to accept a new reviewer for a given language? Can we have languages with reviewers and other without? Do we need to publish who has reviewer rights? What does all that imply in terms of weblate configuration?
Regarding glossaries and translation memories there are also important questions to be investigated. For instance, we now have one project per repo and branch. Is it possible to share glossaries across these? If not, should we / can we group them? Who should have permissions to manage glossaries, etc.
So there is quite a bit of research to do that, as far as I know, as not been done by anyone yet.
As I don't think these can be easily experimented live on the OCA instance (I may be wrong about that), I'd recommend anyone who would like to dive in that to setup a test weblate on their local machine and play with that to come up with a proposal or a plan. I'm happy to help with that too.
Best regards,
-Stéphane
On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
Hi Stéphane,
did you give a look to mine and Sergio replies (i attached them below)?
Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.
We met Simone Orsi, OCA member, that support this idea.
In fact we think that what we are looking for could be useful for all language teams.
If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.
Obviously, we welcome all people willing to join the project.
Thanks for your time and help.
Stefano
Da "Stefano Consolaro" stefano.consolaro@mymage.itCcData Mon, 23 Jan 2023 08:40:30 +0100Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
I give my reply for italian language/community:
> Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect or not so pertinent translations.
> What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.> How to make sure translation proposals are not stuck for too long waiting for review?
Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
> Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.
Thanks for expanding the discussion, I hope others will join.
Da "Sergio Zanchetta" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Mon, 23 Jan 2023 10:36:56 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.
Yes, you are right. :-)
Below, as italian community in addition to Stefano answers, you can find a proposal.
Here are a few questions that come to mind. There might be more.
- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).
- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
- How to make sure translation proposals are not stuck for too long waiting for review?
I would replicate Transifex structure or similar, if possible. Here is a proposal:
- Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)
- There is a reviewer role, reviewed strings are freezed and can't be changed by translators.
- The coordinator role has reviewer power and can appoint translators as reviewers.
The coordinator could be nominated by each localization repository PSC. (l10n-*)
He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.
- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Sure, I add that not all communities have translation guidelines. [*]
[*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.html
Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sun, 22 Jan 2023 10:27:40 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.
Here are a few questions that come to mind. There might be more.
- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.- How to make sure translation proposals are not stuck for too long waiting for review?
- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Best regards,
-sbi
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Stefano Consolaro
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rémi Cazenave - 05:50 - 22 Jun 2023
