Archives
Contributors
-
Translation in Odoo and OCA
Dear OCA friends,I'm about to start an initiative to improve the French translation of Odoo v14 (official and OCA modules), which is currently very poor compared to other languages before the release of v15. My experience on this topic is very limited, so I have several questions and I'm interested in some advice from translation communities of other languages.Experience/Advice==============I'm interested by the experience of other Odoo translation communities that achieve high coverage and high quality (but not where only 1 company makes all the translation work) :- How are you organised ?- How do you ensure that translations are "coherent" among official and OCA modules ? For example, making sure that "Currency" is always translated by "Devise" and not by "Monnaie". Or how to translate "Quantity on hand" vs "Available quantity" (in the current French translation of Odoo, these 2 terms have the same translation which is a big problem !!!).- Are translations mostly done by developers or by non-developers ?- How do you motivate translators ?- What are the best practice for translation communities on Odoo/OCA ?OCA modules============I only found this page, which gives very little information https://odoo-community.org/page/translateHere are my questions :- what is the delay between translation in Weblate and commit on Github (it seems very fast ; commits seem to be done on a daily basis...)- Does a moderation/review take place before commit on Github for untranslated terms ? (seems that the answer is "no") and when we change/improve a translation ?- are there different access rights for translation of a particular language ? If yes, who is the "master" for French language ?Official modules=============For the official modules, there is a wiki page which gives a lot of information :I read that there are 3 levels of access rights :1) translator2) reviewer3) coordinatorIn my Transifex profile, it says :lang French of the team "Odoo Translators"So I guess I'm at the first level. Do some of you see "Odoo Reviewers'" or "Odoo Coordinator" on your profile page ? How can I know who is the Coordinator for the French language ?On the wiki page, it says that Reviewers "Can approve translation suggestions from Translators". But, when I translate some odoo strings in Transifex, it seems that my changes are commited without review. Or is it only when I change an existing translation ? All these access rights are not clear to me.I remember that, a few years ago, there was a page on a wiki or Etherpad, where there was some guidelines/instructions for the French translation : this page said for example that "Currency" should always be translated by "Devise" (and not "Monnaie"), etc... But I don't find this page any more...Thanks in advance for your answers !--Alexis de Lattre
Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
Mail : alexis.delattre@akretion.com
by Alexis de Lattre - 12:26 - 22 Jul 2021 -
Re: Changes in Odoo v14
Hi Graeme, thanks for your thoughts. Concerning the enterprise migration logs are you aware of any public space where people share insights from these logs or is the only way to obtain those really going through this lenghty and unreliable offical process ourselfes ;-) Best Frederik Am Mittwoch, den 21.07.2021, 07:32 +0000 schrieb Graeme Gellatly: > Hi, > > Generally Odoo release notes are most authoritative and complete. > Also for technical specifics OCA Migration Guides and the issues and > notes in Openupgrade repo are good guides. > > Finally the instructions to fix all the mess caused by Odoo > enterprise migration gives a few hints, as do the enterprise > migration logs. > > For code/ideas taken from OCA, twitter on release day :) > > On Wed, Jul 21, 2021 at 7:12 PM Frederik Kramer < > frederik.kramer@initos.com> wrote: > > Dear all > > > > is anybody of you aware of a near complete collection of changes > > (functionality, code / api) between Odoo major versions (ideally > > regularly maintained). Specifically v13 to v14? I know there are a > > couple of websites out there that do bits and pieces of it but what > > i > > am searching for, is some sort of collective review of the > > community > > (e.g. in a OCA wiki page). any answer on the matter is appreciated > > > > Cheers Frederik > > > > > > > > -- > > Dr.-Ing. Frederik Kramer > > Geschäftsführer > > > > initOS GmbH > > An der Eisenbahn 1 > > 21224 Rosengarten > > > > Phone: +49 4105 56156-12 > > Fax: +49 4105 56156-10 > > Mobil: +49 179 3901819 > > > > Email: frederik.kramer@initos.com > > Web: www.initos.com > > > > Geschäftsführung: > > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > > > Sitz der Gesellschaft: Rosengarten – Klecken > > Amtsgericht Tostedt, HRB 205226 > > Steuer-Nr: 15/200/53247 > > USt-IdNr.: DE815580155 > > > > _______________________________________________ > > 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 -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 10:30 - 21 Jul 2021 -
Re: Changes in Odoo v14
Hi,Generally Odoo release notes are most authoritative and complete. Also for technical specifics OCA Migration Guides and the issues and notes in Openupgrade repo are good guides.Finally the instructions to fix all the mess caused by Odoo enterprise migration gives a few hints, as do the enterprise migration logs.For code/ideas taken from OCA, twitter on release day :)On Wed, Jul 21, 2021 at 7:12 PM Frederik Kramer <frederik.kramer@initos.com> wrote:Dear all is anybody of you aware of a near complete collection of changes (functionality, code / api) between Odoo major versions (ideally regularly maintained). Specifically v13 to v14? I know there are a couple of websites out there that do bits and pieces of it but what i am searching for, is some sort of collective review of the community (e.g. in a OCA wiki page). any answer on the matter is appreciated Cheers Frederik -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 09:31 - 21 Jul 2021 -
Changes in Odoo v14
Dear all is anybody of you aware of a near complete collection of changes (functionality, code / api) between Odoo major versions (ideally regularly maintained). Specifically v13 to v14? I know there are a couple of websites out there that do bits and pieces of it but what i am searching for, is some sort of collective review of the community (e.g. in a OCA wiki page). any answer on the matter is appreciated Cheers Frederik -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 09:11 - 21 Jul 2021 -
Re: Produce multiple products from one component
Hi Rémi,It seems native "Unbuild Orders" is the perfect tool for your request.Le lun. 19 juil. 2021 à 15:52, Yoshi Tashiro <tashiro@quartile.co> a écrit :As far as I understand, there is no logic to distribute the production cost to the by-product using Odoo's standard function.A recent inquiry I got from a potential client was about implanting parts and cutting out multiple circuit boards out of a large board. Would be happy to know if there is a good solution.--Yoshi TashiroOn Mon, Jul 19, 2021 at 4:06 PM Tom <tom@sunflowerweb.nl> wrote:Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require multiple compoments as an input, can also be just one
Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>:
Dear Community,
For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)
First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.
Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.
Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.
The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?
Do you know of any company / person / module implementing this need ?
Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.
Thanks for your help !
Best Regards,
Rémi
SCOP Le Filament_______________________________________________
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 David BEAL - 08:11 - 19 Jul 2021 -
Re: Produce multiple products from one component
As far as I understand, there is no logic to distribute the production cost to the by-product using Odoo's standard function.A recent inquiry I got from a potential client was about implanting parts and cutting out multiple circuit boards out of a large board. Would be happy to know if there is a good solution.--Yoshi TashiroOn Mon, Jul 19, 2021 at 4:06 PM Tom <tom@sunflowerweb.nl> wrote:Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require multiple compoments as an input, can also be just one
Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>:
Dear Community,
For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)
First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.
Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.
Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.
The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?
Do you know of any company / person / module implementing this need ?
Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.
Thanks for your help !
Best Regards,
Rémi
SCOP Le Filament_______________________________________________
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 Yoshi Tashiro. - 03:51 - 19 Jul 2021 -
Re: Produce multiple products from one component
Поздрав,
Росен Владимиров
+359886100204На пн, 19.07.2021 г. в 9:07 ч. Rémi CAZENAVE - Le Filament <remi@le-filament.com> написа:Dear Community,
For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)
First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.
Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.
Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.
The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?
Do you know of any company / person / module implementing this need ?
Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.
Thanks for your help !
Best Regards,
Rémi
SCOP Le Filament_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rosen Vladimirov - 09:46 - 19 Jul 2021 -
Re: Produce multiple products from one component
Haven't worked with any of these but the discussion caught my attention so I went to check the modules. mrp_byproduct existed up until 12.0, in 13.0 it was merge with/into mrp module. Just my $0.02 Best regards Radovan Skolnik On pondelok 19. júla 2021 9:06:50 CEST Tom wrote: > Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require > multiple compoments as an input, can also be just one > > > Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>: > > Dear Community, For the second time, we are requested by customers to make > Odoo produce multiple products from a single component (when mrp is > basically doing the other way around : 1 product and some side products > from multiple components) First time was by wood industry, from a single > trunk they produce at once various planks of different sizes. At that time > we answered that we were not in a position to handle this need. Second time > is for food industry, from a single fish, they will make at once various > fillets or blocks of different sizes. This time we should put in place a > solution for that. Later on we should look at how to plan/automate from SO > the quantities and sizes to be produced. The fact that the same functional > need coming from 2 different industries is brought to us, makes me think > that we could go for a generic solution that could fit both needs. Also I > suppose that this need may have already been solved by some of you ? Do you > know of any company / person / module implementing this need ? Otherwise I > should raise an RFC as issue on manufacture repo to functionnally describe > the need and collect your inputs/comments/remarks before starting > development. Thanks for your help ! Best Regards, Rémi SCOP Le Filament > > _______________________________________________ Mailing-List: > https://odoo-community.org/groups/contributors-15 [1] Post to: > mailto:contributors@odoo-community.org Unsubscribe: > https://odoo-community.org/groups?unsubscribe [2] > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [3] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4] > > > > [1] https://odoo-community.org/groups/contributors-15 > [2] https://odoo-community.org/groups?unsubscribe > [3] https://odoo-community.org/groups/contributors-15 > [4] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 09:15 - 19 Jul 2021 -
Produce multiple products from one component
Dear Community,
For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)
First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.
Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.
Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.
The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?
Do you know of any company / person / module implementing this need ?
Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.
Thanks for your help !
Best Regards,
Rémi
SCOP Le Filament
by Rémi Cazenave - 08:06 - 19 Jul 2021 -
Re: Prevent 2 modules from testing together in OCA repo.
Yes, this is exactly what I am looking for.Thank you Kevin!On Sat, Jul 17, 2021 at 8:12 PM Kevin Khao <kevinkhao@gmail.com> wrote:Hi Kitti,Here is an example of how I did it.On Sat, Jul 17, 2021 at 7:27 AM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:Hello,When we have 2 module that's will failed when tested together. In OCA repo, are there ways to ensure not to run tests together?I remember it is about setting in travis.yaml? but can't find the sample. (Also in the future if we move to github action, how to?Thank you,_______________________________________________
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 Kitti Upariphutthiphong - 05:55 - 17 Jul 2021 -
Re: Prevent 2 modules from testing together in OCA repo.
Hi Kitti,Here is an example of how I did it.On Sat, Jul 17, 2021 at 7:27 AM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:Hello,When we have 2 module that's will failed when tested together. In OCA repo, are there ways to ensure not to run tests together?I remember it is about setting in travis.yaml? but can't find the sample. (Also in the future if we move to github action, how to?Thank you,_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kevin Khao. - 03:11 - 17 Jul 2021 -
Prevent 2 modules from testing together in OCA repo.
Hello,When we have 2 module that's will failed when tested together. In OCA repo, are there ways to ensure not to run tests together?I remember it is about setting in travis.yaml? but can't find the sample. (Also in the future if we move to github action, how to?Thank you,
by Kitti Upariphutthiphong - 07:26 - 17 Jul 2021 -
Re: Migration Folders during migration in OCA Modules
Yes, a pre-requisite is to have the previous version up to date before starting the migration, and if you run a migration across several versions in between, you have to manually launch the intermediate version scripts. It's what you have if you go through the enterprise path. I doubt Odoo performs all the migrations in one step, but it would be a version per version migration, but you only see the final result of the black box.It's not possible to keep all the migration scripts across versions due to several reasons:- "Logistic" one: keeping in sync such migration scripts across versions is a pain. If you perform a fix on v12 migration scripts, would you sincerely do the same patch on v13 and v14?- And the main one: there are data transformations that aren't idempotent (for example, the renaming of a column), which means that running them several times will lead to errors. This combined with the pre/post/end mechanism, makes a non deterministic scenario where you will need to add a lot of control logic - or it will be directly impossible- to be handled across several versions. Example:- On v12, you have 12.0.1.0.0 and 12.0.2.0.0 with scripts.- On v13, you have 13.0.1.0.0 with scripts.Migrating from v11 to v13, if all the scripts are in v13 (12.0.1.0.0, 12.0.2.0.0, 13.0.1.0.0 and 13.0.2.0.0), and you are not accessing v12 migration cycle, you will get this execution pipeline:- Run 12.0.1.0.0 pre-migration- Run 12.0.2.0.0 pre-migration- Run 13.0.1.0.0 pre-migration- Run 12.0.1.0.0 post-migration- Run 12.0.2.0.0 post-migration- Run 13.0.1.0.0 post-migrationRunning with OpenUpgrade on each version, the execution pipeline is:- Run 12.0.1.0.0 pre-migration- Run 12.0.2.0.0 pre-migration- Run 12.0.1.0.0 post-migration- Run 12.0.2.0.0 post-migration<new migration cycle>- Run 13.0.1.0.0 pre-migration- Run 13.0.1.0.0 post-migrationThe only way is to manually re-create the same sequence. And this, expecting that there's no other dependent modules that perform operations on the expected pipeline.More things to take into account: OCA module migration scripts are settled on expected renamed columns by OpenUpgrade, so we don't know how enterprise migration scripts are letting data, and thus, you will probably need to adapt existing migration scripts. Example: on the migration from 12 to 13, account.invoice model is merged with account.move. On OpenUpgrade, we created the columns `old_invoice_id` and `old_invoice_line_id` to link the previous record, and a lot of migration scripts rely on these columns for transferring information from old invoices to new moves.Conclusion: I have resigned to use enterprise migration services, even on enterprise instances, and always do it through OpenUpgrade.Regards.
by Pedro M. Baeza - 02:30 - 15 Jul 2021 -
Re: OCA module contributors and migrations
+1 JairoEl jue, 15 jul 2021 a las 11:07, Jairo Llopis (<jairo.llopis@tecnativa.com>) escribió:El jue, 15 de jul de 2021 a las 07:32:02 AM, Harald Panten Lopez <harald.panten@sygel.es> escribió:I think the responsibility to control these "fake contributors" shouldn't be for the modules authors but for PSC.Don't you think so?If a spammer properly migrates a module, let him spam!If he just fixes one typo in the readme, block that from being added to contributors.I think spam contributions are a valid point, but still anything like that should be recorded in the contribution guidelines too. How to identify a spammy contribution is a subject in itself that is interesting not only for OCA, so if somebody has a study on that, it would help here._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 12:06 - 15 Jul 2021 -
Re: Propose Alba Riera as PSC for Donation
Le mer. 14 juil. 2021 à 11:27, Lois Rilo Antelo <lois.rilo@forgeflow.com> a écrit :+1 It seems some more hands will help to manage the repositoryYes, good idea, we need more active PSC on the donation project ! Let's welcome Alba as PSC.--Alexis de Lattre
by Alexis de Lattre - 11:35 - 15 Jul 2021 -
Re: OCA module contributors and migrations
Hi Raphaël,I think the responsibility to control these "fake contributors" shouldn't be for the modules authors but for PSC.Don't you think so?El mié, 14 jul 2021 a las 19:42, Raphaël Valyi (<rvalyi@akretion.com>) escribió:Hello,I think it should be up to modules authors to decide if a contribution is worth getting mentioned or not as in any open source project. Don't like it? Then fork, but make sure you can do better or go back to your place. Indeed we already see some kind of "contribution squatting". I won't give names here but I have seen people forcing new pointless features into famous modules just to drive attention to their own company. This is very real already... Usually people doing this are not serious people, their trivial work won't be missed.And it didn't stop there, in some project you got noobs artificially inflating their image with non relevant contribs and starting to get their noob employee destroy serious modules... In Brazil so many companies failed their project because this kind of un responsable behaviors from noobs trying to auto promote them as expert at any cost to make a dent in the saas business...If you state rules like any tiny contrib is with a mention, soon enough you'll have contribution trolling exploding, just like during the Hacktober fest when gazillions of people were making pointless PRs to any project just to win a free T-shirt. Now think about getting it's company named along with Tecnativa or CamToCamp...This is sad, but this is the wild world we live in. Instead when module authors decide, then real efforts can be rewarded and notoriety squating may be avoided.Also bare in mind that one can always see the number of commits and lines changed in any git(hub) repo, so it's not like it's invisible either...On Wed, Jul 14, 2021, 6:26 AM Harald Panten Lopez <harald.panten@sygel.es> wrote:I think any migration should be considered as a contribution. As some of you said before, that may encourage more users to contribute.Any migration (even if it's a standard migration) needs an investment of time. On the other hand, when a user starts a migration he/she is "open" to receive suggestions, changes... Any migration is liable to become a headache.I agree that correcting a small typo (for example) wouldn't be enough for being considered as a contributor.Regards.El mié, 14 jul 2021 a las 9:17, Jairo Llopis (<jairo.llopis@tecnativa.com>) escribió:El mar, 13 de jul de 2021 a las 15:37:13 PM, David Beal <david.beal@akretion.com> escribió:A point of view could be that contributors should be someone who can answer any questions about the module in the future.Then it should have the expertise on the topic to do it.That sounds more like a maintainer.El mar, 13 de jul de 2021 a las 15:37:12 PM, Tom Blauwendraat <tom@sunflowerweb.nl> escribió:
- The "authors" list in manifest is something you want to keep small and just for important companies which contributed to the development, since it's also ugly when it's very long
- The contributors list in README can be as long as you want because it's not directly in anyone's view IMO - and I think any "thank you" that we can give people that invest their time in OCA, should be given
Just if people themselves feel their contribution is not worth a lot they can just not add it
100% agree.As a side note, remember that there are plenty of ways to contribute to a module without writing a single line of code.OCA should be generous in this kind of attribution. That will encourage people to contribute more.This should be hardcoded in the guidelines though._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 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
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 09:30 - 15 Jul 2021 -
Migration Folders during migration in OCA Modules
Hi all,Increasingly I am facing an issue with both OpenUpgrade and Enterprise migrations in relation to migrations folders. We have a practice of deleting them whenever a module is migrated.So my question is why?Let me outline a few issues on one side and hope I can be enlightened of the other side.Client is on version 8.0.1 of mis_builder. They migrate using OpenUpgrade and it skips the very important 8.0.2 migration.Another client chose to use Openupgrade only for core modules for intervening versions. This is essentially the same issue as an enterprise migration of 2 versions. You get the database back without 3rd party modules migrated.The latest module version only contains scripts for 1 version. So you spend hours hunting through finding the scripts, forking repos etc to get the scripts you need.But also I ask myself if we couldn't reduce multiversion migration time if a current version ran multiple folders. But then again, Odoo enterprise migration does all modules for a version, then moves to the next version so perhaps not feasible.
by Graeme Gellatly - 01:20 - 15 Jul 2021
