Archives
Contributors
contributors@odoo-community.org
-
Activate runboat in donation's repo
Dear Contributors,
As runboat it quite new, could I ask how to activate it in a repo that still have runbot?
In this case:
https://github.com/OCA/donation/tree/14.0/donation
Thank you
Regards,
Rafael
by Rafael Blasco (Moduon) - 05:00 - 16 Feb 2022 -
PSC in project & service
Dear Contributors,
Jairo sent an email yesterday, but it looks like the OCA Odoo didn’t send it.
:+1 for me
Thank you!
Rafael
PSC in project & service
by "Jairo Llopis" jairo@moduon.team - 14/02/2022 08:30:33
Hi dear community.
I would like to ask permissions to be PSC in the project & service group.
https://odoo-community.org/psc-teams/project-service-28
My profile: https://github.com/Yajo
Thanks!
by Rafael Blasco (Moduon) - 01:06 - 15 Feb 2022 -
Lots of our modules do not handle multi-company correctly with Odoo >= 13
Dear colleagues, It seems we have a widely spread bug on our code base, related to Odoo >= 13.0 and multi-company. Starting on Odoo 13.0 the company switch widget in the UI no longer changes the user's company_id field. It changes the company via the force_company context key, and you get the value of the current company by checking `self.env.company`, and not any longer through `self.env.user.company_id` This is documented in https://www.odoo.com/documentation/13.0/developer/howtos/company.html However, in many places in our code base, I see things such as https://github.com/OCA/account-invoicing/blob/13.0/stock_picking_invoicing/wizards/stock_invoice_onshipping.py#L209 This calls for a massive bug fix campaign (and probably for an official statement from the community to ask customers to upgrade their modules if they are in multi-company). I am not sure what the best course of action is. Things I think we should do: * gather information about affected modules and versions (so that people can quickly check if their instances are affected by this) * prepare fixes and get them applied * publish the fix versions * be super careful about this in the reviews of module migration pull requests (I admit I have been careless on this, and I really feel bad about it) Feedback welcome, -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 01:46 - 9 Feb 2022-
Re: Lots of our modules do not handle multi-company correctly with Odoo >= 13
On Wed, Feb 9, 2022 at 2:41 PM Holger Brunn <mail@hunki-enterprises.nl> wrote:could we write the AST version of grep -RE 'user(_id|).company_id[^s]' --include=*.py ?
I recently came across https://semgrep.dev/ which might be handy in such situations.-sbi
by Stéphane Bidoul - 02:51 - 9 Feb 2022 -
Re: Lots of our modules do not handle multi-company correctly with Odoo >= 13
On 09/02/2022 14:37, Holger Brunn wrote: > Thank you for raising this. > >> * gather information about affected modules and versions (so that people >> can quickly check if their instances are affected by this) > > could we write the AST version of > grep -RE 'user(_id|).company_id[^s]' --include=*.py > ? > (which already finds a lot of problematic cases, but also a lot of false > positives we could exclude when knowing the code, like in default lambdas) > > When we have that we could even flag such lines in PRs to have reviewers/ > contributors pay extra attention. > I don't think we want to exclude default lambdas. In my opinion we want env.company_id in these (and this is what Odoo is using). Tests are a bit more of an issue. We should have a pylint check for this, I think, which would require an explicit deactivation to be able to use user.company_id anywhere. -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 02:51 - 9 Feb 2022 -
Re: Lots of our modules do not handle multi-company correctly with Odoo >= 13
Hi Alex.Indeed as `self.env.user.company_id` is used to represent the default company of the user and not the current one.I think effort can be split through PSC's and I'll be pleased to be part of that effort.We can at least create an issue for that in every repo (I don't know if it has been done automatically or not...)Le mer. 9 févr. 2022 à 13:47, Alexandre Fayolle <alexandre.fayolle@camptocamp.com> a écrit :Dear colleagues, It seems we have a widely spread bug on our code base, related to Odoo >= 13.0 and multi-company. Starting on Odoo 13.0 the company switch widget in the UI no longer changes the user's company_id field. It changes the company via the force_company context key, and you get the value of the current company by checking `self.env.company`, and not any longer through `self.env.user.company_id` This is documented in https://www.odoo.com/documentation/13.0/developer/howtos/company.html However, in many places in our code base, I see things such as https://github.com/OCA/account-invoicing/blob/13.0/stock_picking_invoicing/wizards/stock_invoice_onshipping.py#L209 This calls for a massive bug fix campaign (and probably for an official statement from the community to ask customers to upgrade their modules if they are in multi-company). I am not sure what the best course of action is. Things I think we should do: * gather information about affected modules and versions (so that people can quickly check if their instances are affected by this) * prepare fixes and get them applied * publish the fix versions * be super careful about this in the reviews of module migration pull requests (I admit I have been careless on this, and I really feel bad about it) Feedback welcome, -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel. - 02:25 - 9 Feb 2022
-
Plugin/module multiplexer/switcher for multi company
Hi! I have a client that has multi company installation. Each company resides in a different country. For each country I have created a module that acts the same as partner_autocomplate but retrieveing data from their local authorities (state registers). Now I would like to create something as a plugin system where the client could use all of these modules for different companies. So I'd need to create some sort of plugins and multiplexer/switcher that would route requests to appropriate plugin. Is there anything like that already existing in Odoo? One approach that I see would be creating that multiplexer/switcher as a main module that would provide company-specific configuration. Each of the plugin modules would be a module of its own extending the main module's list of available plugins implemented as fields.Selection via selection_add. That selection would be used as company-specific configuration to know, which plugin should server the requests. So when requests comes and it is passed through plugins each would be able to tell whether it's the correct one to serve it. Is there a better way to do this? Any suggestions are welcome. Best regards Radovan Skolnik
by Radovan Skolnik - 11:26 - 8 Feb 2022-
Re: Plugin/module multiplexer/switcher for multi company
The only problem with the dynamic dispatching according method name is that the code discoverability is more difficult, as you usually look for occurrences of your full method name in other parts of the code, which doesn't happen here. I recently suggest to use a similar approach using inheritance here:and attended by Denis here:Regards.
by Pedro M. Baeza - 02:40 - 9 Feb 2022 -
Re: Plugin/module multiplexer/switcher for multi company
Yes, dispatcher is sort of what I'm looking for. What you suggest is ingenious! Me coming from languages like Java/Pascal/C/Assembler would never think of approach you suggested :-) I mean dynamically calling method name like that. I wanted to do this by standard inheritance chaining of the same method where only the appropriate one would process the request.Thanks for the eye-opener!Best regardsRadovanSent via BlackBerry Hub+ Inbox for AndroidFrom: gdgellatly@gmail.comSent: February 9, 2022 12:36To: contributors@odoo-community.orgReply-to: contributors@odoo-community.orgSubject: Re: Plugin/module multiplexer/switcher for multi company
Hi,It sounds to me like you are suggesting a standard dispatcher.There is already plenty of this in Odoo. Company specific headers, company specific pricelists, bank specific imports, EDI processing orders,mail.channel specific commands (those are dynamically defined and executed, probably best example for this). Just define a parent module with a standard API dispatcher and a selection field (or Char) where it makes sense.e.g in base module - very pseudo if its python, if it is web based or you just need a URL for standard data maybe it may be different but you get the idea.class Company:field =fields.Selection (base) class Partner:def complete:ensure_one()def complete baseextension moduleadd field to selection say modbdef complete_modb()On Wed, Feb 9, 2022 at 8:51 PM Radovan Skolnik <radovan@skolnik.info> wrote:Hi, the question was meant more towards good design of something that covers the same area functionally (in this case partner autocomplete) but needs to provide more implementations that are chosen based on certain criteria. So in my case I need to have more than one different implementation of the same functionality present in the system and choose the appropriate one - in my case based on current company being active and configuration for that company. That leads me to some kind plugin system and was wondering if there was anything like that existing in Odoo / OCA already. Best regards Radovan On streda 9. februára 2022 6:52:24 CET Bruno Joliveau wrote: > Hi, > I think it's probably different from a context to another. > In our case, the majority of our customers work internationally. Their > search for information is dissociated. The autocomplete is not linked to > the company in which the user is connected but the country on which he > creates the new partner for which he is looking for information. All the > countries we needed to cover for this customer had different connection > modes and incompatible data structures. We have therefore chosen to process > outside Odoo in order to standardize the structure of the results thanks to > different mappings. Odoo connects to the service, the service gets data and > digests the information. Hope it helps ! > > > *Bruno Joliveau* - Président NUMIGI SOLUTIONS INC. > bruno.joliveau@numigi.com [1] (514) 317-7944 > Longueuil, Québec, Canada http://www.numigi.com/ [2] > None [3] None [4] None [5] None [6] > [7] > > Le mar. 8 févr. 2022 à 17:27, Radovan Skolnik < radovan@skolnik.info [8] > a > écrit : Hi! > I have a client that has multi company installation. Each company resides in > a different country. For each country I have created a module that acts the > same as partner_autocomplate but retrieveing data from their local > authorities (state registers). Now I would like to create something as a > plugin system where the client could use all of these modules for different > companies. So I'd need to create some sort of plugins and > multiplexer/switcher that would route requests to appropriate plugin. Is > there anything like that already existing in Odoo? One approach that I see > would be creating that multiplexer/switcher as a main module that would > provide company-specific configuration. Each of the plugin modules would be > a module of its own extending the main module's list of available plugins > implemented as
fields.Selection via selection_add. That selection would be > used as company-specific configuration to know, which plugin should server > the requests. So when requests comes and it is passed through plugins each > would be able to tell whether it's the correct one to serve it. Is there a > better way to do this? Any suggestions are welcome. > Best regards > Radovan Skolnik > > > _______________________________________________ > Mailing-List:https://odoo-community.org/groups/contributors-15 [9] > Post to: mailto: contributors@odoo-community.org [10] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11] > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [12] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [13] > > > > [1] mailto:bruno.joliveau@numigi.com > [2] http://www.numigi.com/ > [3] https://fr.linkedin.com/company/numigi > [4] https://www.youtube.com/channel/UC2z69q_2XnumQEE9E7BmelQ > [5] https://blogue.numigi.com/ > [6] https://twitter.com/numigi_ca?lang=fr > [7] https://bit.ly/5W-Numigi > [8] mailto:radovan@skolnik.info > [9] https://odoo-community.org/groups/contributors-15 > [10] mailto:contributors@odoo-community.org > [11] https://odoo-community.org/groups?unsubscribe > [12] https://odoo-community.org/groups/contributors-15 > [13] 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 Radovan Skolnik - 02:21 - 9 Feb 2022 -
Re: Plugin/module multiplexer/switcher for multi company
Lois, that definitely seems like well-thought-out system for even much more complex cases than mine. For the sake of learning something new I will probably try to use it. Thanx a lot. Best regards Radovan On streda 9. februára 2022 10:37:26 CET Lois Rilo Antelo wrote: > Hi Radovan, > I think that components ( > https://github.com/OCA/connector/tree/14.0/component [1] ) might be the > concept you are looking for. You can have a base module and then different > modules that introduce new components for each country (following your > example). Then on execution, the appropriate component will be used > depending on the working context. You can see different examples on how to > use components in the OCA: different connectors, edi... My 2 cents. > Kind regards, > On Wed, Feb 9, 2022 at 8:51 AM Radovan Skolnik < radovan@skolnik.info [2] > > wrote: Hi, > the question was meant more towards good design of something that covers the > same area functionally (in this case partner autocomplete) but needs to > provide more implementations that are chosen based on certain criteria. So > in my case I need to have more than one different implementation of the > same functionality present in the system and choose the appropriate one - > in my case based on current company being active and configuration for that > company. That leads me to some kind plugin system and was wondering if > there was anything like that existing in Odoo / OCA already. > Best regards > Radovan > > On streda 9. februára 2022 6:52:24 CET Bruno Joliveau wrote: > > Hi, > > I think it's probably different from a context to another. > > In our case, the majority of our customers work internationally. Their > > search for information is dissociated. The autocomplete is not linked to > > the company in which the user is connected but the country on which he > > creates the new partner for which he is looking for information. All the > > countries we needed to cover for this customer had different connection > > modes and incompatible data structures. We have therefore chosen to > > process > > outside Odoo in order to standardize the structure of the results thanks > > to > > different mappings. Odoo connects to the service, the service gets data > > and > > digests the information. Hope it helps ! > > > > > > *Bruno Joliveau* - Président NUMIGI SOLUTIONS INC. > > > > bruno.joliveau@numigi.com [3] [1] (514) 317-7944 > > > > Longueuil, Québec, Canada http://www.numigi.com/ [4] [2] > > None [3] None [4] None [5] None [6] > > [7] > > > > Le mar. 8 févr. 2022 à 17:27, Radovan Skolnik < radovan@skolnik.info [5] > > [8] > a écrit : Hi! > > I have a client that has multi company installation. Each company resides > > in a different country. For each country I have created a module that > > acts the same as partner_autocomplate but retrieveing data from their > > local authorities (state registers). Now I would like to create something > > as a plugin system where the client could use all of these modules for > > different companies. So I'd need to create some sort of plugins and > > multiplexer/switcher that would route requests to appropriate plugin. Is > > there anything like that already existing in Odoo? One approach that I see > > would be creating that multiplexer/switcher as a main module that would > > provide company-specific configuration. Each of the plugin modules would > > be > > a module of its own extending the main module's list of available plugins > > implemented as fields.Selection via selection_add. That selection would be > > used as company-specific configuration to know, which plugin should server > > the requests. So when requests comes and it is passed through plugins each > > would be able to tell whether it's the correct one to serve it. Is there a > > better way to do this? Any suggestions are welcome. > > Best regards > > Radovan Skolnik > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] [9] > > Post to: mailto: contributors@odoo-community.org [7] [10] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8] [11] > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [9] [12] > > Post to: mailto: contributors@odoo-community.org [10] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11] [13] > > > > > > > > [1] mailto: bruno.joliveau@numigi.com [12] > > [2] http://www.numigi.com/ [13] > > [3] https://fr.linkedin.com/company/numigi [14] > > [4] https://www.youtube.com/channel/UC2z69q_2XnumQEE9E7BmelQ [15] > > [5] https://blogue.numigi.com/ [16] > > [6] https://twitter.com/numigi_ca?lang=fr [17] > > [7] https://bit.ly/5W-Numigi [18] > > [8] mailto: radovan@skolnik.info [19] > > [9] https://odoo-community.org/groups/contributors-15 [20] > > [10] mailto: contributors@odoo-community.org [21] > > [11] https://odoo-community.org/groups?unsubscribe [22] > > [12] https://odoo-community.org/groups/contributors-15 [23] > > [13] https://odoo-community.org/groups?unsubscribe [24] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [25] > Post to: mailto: contributors@odoo-community.org [26] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [27] > > -- > *Lois Rilo Antelo* Odoo consultant at ForgeFlow S.L. > lois.rilo@forgeflow.com [28] | https://www.forgeflow.com [29] Twitter: > /LoisRForgeFlow [30] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [31] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [32] > > > > [1] https://github.com/OCA/connector/tree/14.0/component > [2] mailto:radovan@skolnik.info > [3] mailto:bruno.joliveau@numigi.com > [4] http://www.numigi.com/ > [5] mailto:radovan@skolnik.info > [6] https://odoo-community.org/groups/contributors-15 > [7] mailto:contributors@odoo-community.org > [8] https://odoo-community.org/groups?unsubscribe > [9] https://odoo-community.org/groups/contributors-15 > [10] mailto:contributors@odoo-community.org > [11] https://odoo-community.org/groups?unsubscribe > [12] mailto:bruno.joliveau@numigi.com > [13] http://www.numigi.com/ > [14] https://fr.linkedin.com/company/numigi > [15] https://www.youtube.com/channel/UC2z69q_2XnumQEE9E7BmelQ > [16] https://blogue.numigi.com/ > [17] https://twitter.com/numigi_ca?lang=fr > [18] https://bit.ly/5W-Numigi > [19] mailto:radovan@skolnik.info > [20] https://odoo-community.org/groups/contributors-15 > [21] mailto:contributors@odoo-community.org > [22] https://odoo-community.org/groups?unsubscribe > [23] https://odoo-community.org/groups/contributors-15 > [24] https://odoo-community.org/groups?unsubscribe > [25] https://odoo-community.org/groups/contributors-15 > [26] mailto:contributors@odoo-community.org > [27] https://odoo-community.org/groups?unsubscribe > [28] mailto:lois.rilo@eficent.com > [29] https://www.forgeflow.com/ > [30] https://twitter.com/LoisRForgeFlow > [31] https://odoo-community.org/groups/contributors-15 > [32] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 11:51 - 9 Feb 2022
-
-
CLA Bot back from the abyss
Hello everyone, We found out that the CLA Bot was not generating any messages on pull requests. This could well have been the case since Nov 2013, 2020 when github stopped accepting basic password auth that was used by the bot. There were probably some emails that were sent to the account of the bot, but it turns out that this email address used to belong to to the original author of the clabot who changed companies, and so noone was receiving this. So... This is now fixed, and the CLAbot should be bugging you again on pull requests. Happy reviewing :) -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 04:11 - 4 Feb 2022-
Re: CLA Bot back from the abyss
Thanks Alex!Le ven. 4 févr. 2022 à 16:12, Alexandre Fayolle <alexandre.fayolle@camptocamp.com> a écrit :
Hello everyone, We found out that the CLA Bot was not generating any messages on pull requests. This could well have been the case since Nov 2013, 2020 when github stopped accepting basic password auth that was used by the bot. There were probably some emails that were sent to the account of the bot, but it turns out that this email address used to belong to to the original author of the clabot who changed companies, and so noone was receiving this. So... This is now fixed, and the CLAbot should be bugging you again on pull requests. Happy reviewing :) -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel. - 04:28 - 4 Feb 2022 -
Re: CLA Bot back from the abyss
Thank you very much for the research about it.Regards.
by Pedro M. Baeza - 04:18 - 4 Feb 2022
-
-
New module website_menu_icon
Hi!
Quite some time ago I created new module: website_menu_icon that allows for adding icons images to website menus. It was a learning experience for me in Odoo/Python/JS. I have posted a PR to include it into OCA here: https://github.com/OCA/website/pull/745 If this might be interesting to you, please review the module as it is waiting there for a long time. Thank you.
Best regards
Radovan Skolnik
by Radovan Skolnik - 03:21 - 4 Feb 2022 -
Goodbye runbot, welcome runboat
Dear contributors,As you may have noticed, a new tool arrived in the OCA landscape: runboat.It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!Most existing links to runbot.odoo-community.org will then redirect to runboat.In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.I also monitor the OCA Infrastructure discord channel from time to time.Best regards, and happy testing!-sbi--Stéphane BidoulOperations Director
M: +32 498 72 46 54
by Stéphane Bidoul - 06:06 - 27 Jan 2022-
Re: Goodbye runbot, welcome runboat
Hooray! Welcome, runboat!Thanks a lot for the outstanding work!On Thu, Jan 27, 2022 at 6:07 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,As you may have noticed, a new tool arrived in the OCA landscape: runboat.It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!Most existing links to runbot.odoo-community.org will then redirect to runboat.In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.I also monitor the OCA Infrastructure discord channel from time to time.Best regards, and happy testing!-sbi--Stéphane BidoulOperations Director
M: +32 498 72 46 54_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40
by Alex Comba. - 02:21 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Le ven. 28 janv. 2022 à 11:57, Raphaël Reverdy <raphael.reverdy@akretion.com> a écrit :Thanks ! It's a huge improvement.Le ven. 28 janv. 2022 à 09:26, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :It works like a charm! I can start an environment instantly, it is a huge improvement.Thanks a lot Stéphane!On Fri, 28 Jan 2022 at 09:16, Radovan Skolnik <radovan@skolnik.info> wrote:Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
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 - 01:21 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thanks ! It's a huge improvement.Le ven. 28 janv. 2022 à 09:26, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :It works like a charm! I can start an environment instantly, it is a huge improvement.Thanks a lot Stéphane!On Fri, 28 Jan 2022 at 09:16, Radovan Skolnik <radovan@skolnik.info> wrote:Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60
by Raphaël Reverdy - 11:56 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
It works like a charm! I can start an environment instantly, it is a huge improvement.Thanks a lot Stéphane!On Fri, 28 Jan 2022 at 09:16, Radovan Skolnik <radovan@skolnik.info> wrote:Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 09:25 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 09:16 - 28 Jan 2022
-
-
Spanish Payroll
Hi all,
Does enyone have experience in Spanish Payroll app ?
We have a very interesting Odoo project, but we lack the experience required for this module in particular.
We are looking for working with someone to help us implement this particular app.
Regards
Jorge Elena Poblet
Consultor Tecnológico
Gerente | Binhex Systems Solutions S.L.
+34 822 179 267 | +34 622 40 08 08 
j.elena@binhex.es 
https://binhex.es 
Calle Lepanto, 3A, Santa Cruz de Tenerife, Islas Canarias, España 
Aviso legal:
Protección de datos. - Binhex Systems Solutions, S.L. le informa que su dirección de correo electrónico, así como el resto de sus datos personales serán usados para nuestra relación y poder prestarle nuestros servicios. Dichos datos son necesarios para poder relacionarnos con usted, lo que nos permite el uso de su información dentro de la legalidad. Asimismo, podrán tener conocimiento de su información aquellas entidades que necesiten tener acceso a la misma para que podamos prestarle nuestros servicios. Conservaremos sus datos durante nuestra relación y mientras nos obliguen las leyes aplicables. En cualquier momento puede dirigirse a nosotros para saber qué información tenemos sobre usted, rectificarla si fuese incorrecta y eliminarla una vez finalizada nuestra relación. También tiene derecho a solicitar el traspaso de su información a otra entidad (portabilidad). Para solicitar alguno de estos derechos, deberá realizar una solicitud escrita a nuestra dirección, junto con una fotocopia de su DNI:
Binhex Systems Solutions, S.L., con dirección en Calle Lepanto 3, 2A, CP 38005, Santa Cruz de Tenerife (Santa Cruz de Tenerife). En caso de que entienda que sus derechos han sido desatendidos, puede formular una reclamación en la Agencia Española de Protección de Datos (www.agpd.es).
Confidencialidad. - El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigida al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
Exención de responsabilidad. - El envío de la presente comunicación no implica la obligación por parte del remitente de controlar la ausencia de virus, gusanos, troyanos y/o cualquier otro programa informático dañino, correspondiendo al destinatario disponer de las herramientas de hardware y software necesarias para garantizar tanto la seguridad de su sistema de información como la detección y eliminación de programas informáticos dañinos. Binhex Systems Solutions, S.L. no se responsabiliza de los daños y perjuicios que tales programas informáticos puedan causar al destinatario.
by Jorge Elena Poblet - 04:51 - 27 Jan 2022-
Re: Spanish Payroll
Hola Harald,
Gracias por tu respuesta, estaba pensando en contactar la asociación a ver si habían más empresas para ejecutar algo así.Por lo complicado que se ve el tema, habría que analizar que alternativa o planteamiento podemos hacer con este cliente particular.
Un saludo !El 28/01/2022 8:01 Harald Panten Lopez <harald.panten@sygel.es> escribió:
Hi Jorge,
What an ambitious project! We've been talking about Spanish payrolls for years but this project didn't continue over.
You can contact https://www.aeodoo.org and ask them about that. Maybe they can help you coordinating a working group, or helping you to find other companies interested in order to carry on the work.
Regards.
El jue, 27 ene 2022 a las 16:52, Jorge Elena Poblet (<j.elena@binhex.es>) escribió:
Hi all,
Does enyone have experience in Spanish Payroll app ?
We have a very interesting Odoo project, but we lack the experience required for this module in particular.
We are looking for working with someone to help us implement this particular app.
Regards
Jorge Elena Poblet
Consultor Tecnológico
Gerente | Binhex Systems Solutions S.L.
+34 822 179 267 | +34 622 40 08 08 j.elena@binhex.es https://binhex.es Calle Lepanto, 3A, Santa Cruz de Tenerife, Islas Canarias, España
Aviso legal:
Protección de datos. - Binhex Systems Solutions, S.L. le informa que su dirección de correo electrónico, así como el resto de sus datos personales serán usados para nuestra relación y poder prestarle nuestros servicios. Dichos datos son necesarios para poder relacionarnos con usted, lo que nos permite el uso de su información dentro de la legalidad. Asimismo, podrán tener conocimiento de su información aquellas entidades que necesiten tener acceso a la misma para que podamos prestarle nuestros servicios. Conservaremos sus datos durante nuestra relación y mientras nos obliguen las leyes aplicables. En cualquier momento puede dirigirse a nosotros para saber qué información tenemos sobre usted, rectificarla si fuese incorrecta y eliminarla una vez finalizada nuestra relación. También tiene derecho a solicitar el traspaso de su información a otra entidad (portabilidad). Para solicitar alguno de estos derechos, deberá realizar una solicitud escrita a nuestra dirección, junto con una fotocopia de su DNI:
Binhex Systems Solutions, S.L., con dirección en Calle Lepanto 3, 2A, CP 38005, Santa Cruz de Tenerife (Santa Cruz de Tenerife). En caso de que entienda que sus derechos han sido desatendidos, puede formular una reclamación en la Agencia Española de Protección de Datos (www.agpd.es).
Confidencialidad. - El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigida al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
Exención de responsabilidad. - El envío de la presente comunicación no implica la obligación por parte del remitente de controlar la ausencia de virus, gusanos, troyanos y/o cualquier otro programa informático dañino, correspondiendo al destinatario disponer de las herramientas de hardware y software necesarias para garantizar tanto la seguridad de su sistema de información como la detección y eliminación de programas informáticos dañinos. Binhex Systems Solutions, S.L. no se responsabiliza de los daños y perjuicios que tales programas informáticos puedan causar al destinatario._______________________________________________
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
by Jorge Elena Poblet - 09:21 - 28 Jan 2022 -
Re: Spanish Payroll
Hi Jorge,What an ambitious project! We've been talking about Spanish payrolls for years but this project didn't continue over.You can contact https://www.aeodoo.org and ask them about that. Maybe they can help you coordinating a working group, or helping you to find other companies interested in order to carry on the work.Regards.El jue, 27 ene 2022 a las 16:52, Jorge Elena Poblet (<j.elena@binhex.es>) escribió:Hi all,
Does enyone have experience in Spanish Payroll app ?
We have a very interesting Odoo project, but we lack the experience required for this module in particular.
We are looking for working with someone to help us implement this particular app.
Regards
Jorge Elena Poblet
Consultor Tecnológico
Gerente | Binhex Systems Solutions S.L.
+34 822 179 267 | +34 622 40 08 08 j.elena@binhex.es https://binhex.es Calle Lepanto, 3A, Santa Cruz de Tenerife, Islas Canarias, España
Aviso legal:
Protección de datos. - Binhex Systems Solutions, S.L. le informa que su dirección de correo electrónico, así como el resto de sus datos personales serán usados para nuestra relación y poder prestarle nuestros servicios. Dichos datos son necesarios para poder relacionarnos con usted, lo que nos permite el uso de su información dentro de la legalidad. Asimismo, podrán tener conocimiento de su información aquellas entidades que necesiten tener acceso a la misma para que podamos prestarle nuestros servicios. Conservaremos sus datos durante nuestra relación y mientras nos obliguen las leyes aplicables. En cualquier momento puede dirigirse a nosotros para saber qué información tenemos sobre usted, rectificarla si fuese incorrecta y eliminarla una vez finalizada nuestra relación. También tiene derecho a solicitar el traspaso de su información a otra entidad (portabilidad). Para solicitar alguno de estos derechos, deberá realizar una solicitud escrita a nuestra dirección, junto con una fotocopia de su DNI:
Binhex Systems Solutions, S.L., con dirección en Calle Lepanto 3, 2A, CP 38005, Santa Cruz de Tenerife (Santa Cruz de Tenerife). En caso de que entienda que sus derechos han sido desatendidos, puede formular una reclamación en la Agencia Española de Protección de Datos (www.agpd.es).
Confidencialidad. - El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigida al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
Exención de responsabilidad. - El envío de la presente comunicación no implica la obligación por parte del remitente de controlar la ausencia de virus, gusanos, troyanos y/o cualquier otro programa informático dañino, correspondiendo al destinatario disponer de las herramientas de hardware y software necesarias para garantizar tanto la seguridad de su sistema de información como la detección y eliminación de programas informáticos dañinos. Binhex Systems Solutions, S.L. no se responsabiliza de los daños y perjuicios que tales programas informáticos puedan causar al destinatario._______________________________________________
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:00 - 28 Jan 2022
-
-
Manufacturing advice needed - materials of measured units being consumed partially
Hello, sorry for asking stupid questions here but I hope someone can provide some wisdom here that I am missing. Let's imagine this scenario: I produce Ethernet cables of various lengths - i.e. 25m, 50m, 75m, 100m, ... Each such final cable requires 2 connectors and that particular amount of "raw" cable. I can only buy raw cable in rolls of 1000m. So when I buy a new roll and produce one final 50m cable, 950m of raw cable remains. When I produce another of 100m length, 850m of raw cable remains. When my remaining raw cable on certain roll is 50m I cannot produce 100m final cable and need to order another raw cable roll. So the idea is tracking remaining quantity of somethings (products? lots? ...) that is bought at certain size and is being gradually consumed. There can of course be more of these (i.e. I have bought 3 rolls at the same time). Is there a way on how to model this? Manufacturing is not really my domain and looking through code of various modules I didn't find anything that would resemble such thing. Thank you very much. Best regards Radovan Skolnik
by Radovan Skolnik - 09:36 - 26 Jan 2022-
Re: Manufacturing advice needed - materials of measured units being
consumed partially
Hi,Yes. It is a well known problem. The 2D PaperCutting Problem, a lot less complex than the 3D one, aka Travelling Salesperson.As for where it goes. I don't know. As I say, I solved differently. Using Unbuild style you start from the raw material so it was never an issue. But to start you can just use a rule of thumb.On Thu, Jan 27, 2022 at 9:37 PM Radovan Skolnik <radovan@skolnik.info> wrote:Graeme, this is what I was looking for and sort of confirms my suspicion that without special handling Odoo would sum contents of all lots of same kind into one (which perfectly makes sense when dealing with units, weights, volumes and such that can be added/joined). Question though if I may: where should that pseudo-code fit in? Is that supposed to be extension somewhere in MRP BoM process where appropriate materials are being looked for when manufacturing the final product? Dumb question maybe but haven't had much experience with MRP yet. Your algorithm actually reminds me very much of a thing I was doing just not a year ago as a favour to a friend who builds pergolas using alluminium joists of certain fixed size. From the design you receive required cutting sizes and you need to optimize how to cut the source material with the least waste. But that was written in Excel and Visual Basic :-) However it is basically the same as what you have outlined. Best regards Radovan P.S.: BTW, have you had a chance to have a look at my comment regarding variant_seller_ids for product.[template|product]? Is till consider that thing broken and not following the desired design... On štvrtok 27. januára 2022 9:17:06 CET Graeme Gellatly wrote:
by Graeme Gellatly - 10:05 - 27 Jan 2022 -
Re: Manufacturing advice needed - materials of measured units being consumed partially
Graeme, this is what I was looking for and sort of confirms my suspicion that without special handling Odoo would sum contents of all lots of same kind into one (which perfectly makes sense when dealing with units, weights, volumes and such that can be added/joined). Question though if I may: where should that pseudo-code fit in? Is that supposed to be extension somewhere in MRP BoM process where appropriate materials are being looked for when manufacturing the final product? Dumb question maybe but haven't had much experience with MRP yet. Your algorithm actually reminds me very much of a thing I was doing just not a year ago as a favour to a friend who builds pergolas using alluminium joists of certain fixed size. From the design you receive required cutting sizes and you need to optimize how to cut the source material with the least waste. But that was written in Excel and Visual Basic :-) However it is basically the same as what you have outlined. Best regards Radovan P.S.: BTW, have you had a chance to have a look at my comment regarding variant_seller_ids for product.[template|product]? Is till consider that thing broken and not following the desired design... On štvrtok 27. januára 2022 9:17:06 CET Graeme Gellatly wrote: > Hi, > I've solved a similar problem. A bit more complicated, slitting coil into > multiple widths, weights and lengths. No way to join. That was custom based > around MRP Unbuild but a lot of the concepts still apply. Unbuild is still > potentially an option. But in basic terms 1. Use Lot tracking. 2. Use > orderpoints or similar. Now for the automatic reorder you might want some > custom code for reordering. In pseudocode. a. counters = [[lot qty], [lot > qty]] for finished_good in finished_goods.sorted(length desc): find lot > raw material that can handle if found decrement counter. if not found: > buy some, break b. if all lots < <some_length>: order > c. Rule of thumb orderpoint. I hold 3 rolls. so 3 x max length of finished > as total rolls means I need to order some more. Or whatever suites. It will > be easiest that way. On Thu, Jan 27, 2022 at 7:11 PM Radovan Skolnik < > radovan@skolnik.info [1] > wrote: Hello, > thank you for all the answers.I guess I have to test this thoroughly. My > worry is generally this: let's say I have 2 lots/rolls each with 50m raw > cable remaining. I need to produce 100m final cable. I think the system > would consider I have enough of raw cable for this. Because that would work > for certain scenarios. Imagine you need 100kg of something to prdouce > something else. If you have 2 lots each with 50kg you're good to go - you > just combine 50kg from each. Similarily if it was pieces. All these can be > joined / added. I am talking about scenario where partial residual amounts > cannot be added together to create a larger piece / amount. Hope I am > making myself clear. Best regards > Radovan > > On štvrtok 27. januára 2022 0:17:23 CET James Dominy wrote: > > Hello Radovan, > > I would track your rolls of cable using Lots, this way when the order > > calls > > for 25, 50, or 100 m of cable if the lot does not have the qty needed to > > produce the ethernet cable it will use the lot that has enough for the > > finished product. On Wed, Jan 26, 2022 at 3:57 PM Radovan Skolnik < > > > > radovan@skolnik.info [2] [1] > wrote: Daniel, > > > > thank you for answer. Yes it does make sense. But will it cover scenario > > where I have let's say 2 rolls with 50m remaining on each and I want to > > produce 100m final cable? Because in such case a completely new roll > > should > > be ordered as I cannot join those 2 50m pieces together... So it comes to > > a > > requirement here that you just do not track the total number of meters > > remaining but you need to track each roll individually. Similar example > > would be a woodmaker who needs certain sizes of wood for various products > > (chair, table, ...) and he procures wood in 3m planks. What is your > > opinion? Best regards > > Radovan > > > > On streda 26. januára 2022 21:51:47 CET Daniel Reis wrote: > > > I believe you need to use different Units of Measure (UoM). > > > In this case, the "Cable" Product is purchased in "Rolls" and used > > > in "Meters". > > > The "Roll" UoM should be configured to convert to Meters at a rate > > > of 1:1000. > > > This way you track your cable stock in meters available, and you > > > order to your supplier in rolls. > > > Dos this make sense? > > > Thanks > > > Daniel > > > > > > On 26/01/22 20:37, Radovan Skolnik > > > wrote: > > > > > > Hello, > > > sorry for asking stupid questions here but I hope someone can provide > > > some > > > wisdom here that I am missing. Let's imagine this scenario: I produce > > > Ethernet cables of various lengths - i.e. 25m, 50m, 75m, 100m, ... Each > > > such final cable requires 2 connectors and that particular amount of > > > "raw" > > > cable. I can only buy raw cable in rolls of 1000m. So when I buy a new > > > roll > > > and produce one final 50m cable, 950m of raw cable remains. When I > > > produce > > > another of 100m length, 850m of raw cable remains. When my remaining raw > > > cable on certain roll is 50m I cannot produce 100m final cable and need > > > to > > > order another raw cable roll. So the idea is tracking remaining quantity > > > of > > > somethings (products? lots? ...) that is bought at certain size and is > > > being gradually consumed. There can of course be more of these (i.e. I > > > have > > > bought 3 rolls at the same time). Is there a way on how to model this? > > > Manufacturing is not really my domain and looking through code of > > > various > > > modules I didn't find anything that would resemble such thing. Thank you > > > very much. Best regards > > > Radovan Skolnik > > > > > > > > > _______________________________________________ > > > Mailing-List: https://odoo-community.org/groups/contributors-15 [3] [2] > > > [1] Post to: mailto: contributors@odoo-community.org [4] [3] [2] > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] [4] [3] > > > > > > > > > > > > -- > > > DANIEL > > > REIS* > > > MANAGING DIRECTOR > > > M:* > > > +351 919 991 307 > > > E:* > > > dreis@OpenSourceIntegrators.com [4] > > > A:* > > > Avenida da República 3000, Estoril Office B, #34 > > > > > > > > > None [5] None [6] None [7] > > > > > > > > > _______________________________________________ > > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] [5] > > > [8] Post to: mailto: contributors@odoo-community.org [7] [6] > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8] [7] [9] > > > > > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 [9] [8] > > > [2] mailto: contributors@odoo-community.org [10] [9] > > > [3] https://odoo-community.org/groups?unsubscribe [11] [10] > > > [4] mailto: dreis@OpenSourceIntegrators.com [11] > > > [5] https://www.magentointegrators.com/ [12] [12] > > > [6] https://www.hadoopintegrators.com/ [13] [13] > > > [7] https://www.usaodoo.com/ [14] [14] > > > [8] https://odoo-community.org/groups/contributors-15 [15] [15] > > > [9] https://odoo-community.org/groups?unsubscribe [16] [16] > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [17] [17] > > Post to: mailto: contributors@odoo-community.org [18] [18] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [19] [19] > > > > -- > > * James Dominy * > > CEO > > * Lunel, Inc * > > Saratoga Springs, UT > > 719-888-9582 > > > > jamesdominy@lunelerp.com [20] [20] > > > > * www.lunel.co [21] [21] > > * > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [22] [22] > > Post to: mailto: contributors@odoo-community.org [23] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [24] [23] > > > > > > > > [1] mailto: radovan@skolnik.info [25] > > [2] https://odoo-community.org/groups/contributors-15 [26] > > [3] mailto: contributors@odoo-community.org [27] > > [4] https://odoo-community.org/groups?unsubscribe [28] > > [5] https://odoo-community.org/groups/contributors-15 [29] > > [6] mailto: contributors@odoo-community.org [30] > > [7] https://odoo-community.org/groups?unsubscribe [31] > > [8] https://odoo-community.org/groups/contributors-15 [32] > > [9] mailto: contributors@odoo-community.org [33] > > [10] https://odoo-community.org/groups?unsubscribe [34] > > [11] mailto: dreis@OpenSourceIntegrators.com [35] > > [12] https://www.magentointegrators.com/ [36] > > [13] https://www.hadoopintegrators.com/ [37] > > [14] https://www.usaodoo.com/ [38] > > [15] https://odoo-community.org/groups/contributors-15 [39] > > [16] https://odoo-community.org/groups?unsubscribe [40] > > [17] https://odoo-community.org/groups/contributors-15 [41] > > [18] mailto: contributors@odoo-community.org [42] > > [19] https://odoo-community.org/groups?unsubscribe [43] > > [20] mailto: james@lunelerp.com [44] > > [21] http://www.lunel.co [45] > > [22] https://odoo-community.org/groups/contributors-15 [46] > > [23] https://odoo-community.org/groups?unsubscribe [47] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [48] > Post to: mailto: contributors@odoo-community.org [49] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [50] > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [51] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [52] > > > > [1] mailto:radovan@skolnik.info > [2] mailto:radovan@skolnik.info > [3] https://odoo-community.org/groups/contributors-15 > [4] mailto:contributors@odoo-community.org > [5] https://odoo-community.org/groups?unsubscribe > [6] https://odoo-community.org/groups/contributors-15 > [7] mailto:contributors@odoo-community.org > [8] https://odoo-community.org/groups?unsubscribe > [9] https://odoo-community.org/groups/contributors-15 > [10] mailto:contributors@odoo-community.org > [11] https://odoo-community.org/groups?unsubscribe > [12] https://www.magentointegrators.com/ > [13] https://www.hadoopintegrators.com/ > [14] https://www.usaodoo.com/ > [15] https://odoo-community.org/groups/contributors-15 > [16] https://odoo-community.org/groups?unsubscribe > [17] https://odoo-community.org/groups/contributors-15 > [18] mailto:contributors@odoo-community.org > [19] https://odoo-community.org/groups?unsubscribe > [20] mailto:jamesdominy@lunelerp.com > [21] http://www.lunel.co > [22] https://odoo-community.org/groups/contributors-15 > [23] mailto:contributors@odoo-community.org > [24] https://odoo-community.org/groups?unsubscribe > [25] mailto:radovan@skolnik.info > [26] https://odoo-community.org/groups/contributors-15 > [27] mailto:contributors@odoo-community.org > [28] https://odoo-community.org/groups?unsubscribe > [29] https://odoo-community.org/groups/contributors-15 > [30] mailto:contributors@odoo-community.org > [31] https://odoo-community.org/groups?unsubscribe > [32] https://odoo-community.org/groups/contributors-15 > [33] mailto:contributors@odoo-community.org > [34] https://odoo-community.org/groups?unsubscribe > [35] mailto:dreis@OpenSourceIntegrators.com > [36] https://www.magentointegrators.com/ > [37] https://www.hadoopintegrators.com/ > [38] https://www.usaodoo.com/ > [39] https://odoo-community.org/groups/contributors-15 > [40] https://odoo-community.org/groups?unsubscribe > [41] https://odoo-community.org/groups/contributors-15 > [42] mailto:contributors@odoo-community.org > [43] https://odoo-community.org/groups?unsubscribe > [44] mailto:james@lunelerp.com > [45] http://www.lunel.co > [46] https://odoo-community.org/groups/contributors-15 > [47] https://odoo-community.org/groups?unsubscribe > [48] https://odoo-community.org/groups/contributors-15 > [49] mailto:contributors@odoo-community.org > [50] https://odoo-community.org/groups?unsubscribe > [51] https://odoo-community.org/groups/contributors-15 > [52] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 09:35 - 27 Jan 2022 -
Re: Manufacturing advice needed - materials of measured units being
consumed partially
Hi,I've solved a similar problem. A bit more complicated, slitting coil into multiple widths, weights and lengths. No way to join. That was custom based around MRP Unbuild but a lot of the concepts still apply. Unbuild is still potentially an option.But in basic terms1. Use Lot tracking.2. Use orderpoints or similar. Now for the automatic reorder you might want some custom code for reordering. In pseudocode.a.counters = [[lot qty], [lot qty]]for finished_good in finished_goods.sorted(length desc):find lot raw material that can handleif found decrement counter.if not found: buy some, breakb.if all lots < <some_length>: orderc. Rule of thumb orderpoint.I hold 3 rolls. so 3 x max length of finished as total rolls means I need to order some more. Or whatever suites. It will be easiest that way.On Thu, Jan 27, 2022 at 7:11 PM Radovan Skolnik <radovan@skolnik.info> wrote:
Hello, thank you for all the answers.I guess I have to test this thoroughly. My worry is generally this: let's say I have 2 lots/rolls each with 50m raw cable remaining. I need to produce 100m final cable. I think the system would consider I have enough of raw cable for this. Because that would work for certain scenarios. Imagine you need 100kg of something to prdouce something else. If you have 2 lots each with 50kg you're good to go - you just combine 50kg from each. Similarily if it was pieces. All these can be joined / added. I am talking about scenario where partial residual amounts cannot be added together to create a larger piece / amount. Hope I am making myself clear. Best regards Radovan On štvrtok 27. januára 2022 0:17:23 CET James Dominy wrote: > Hello Radovan, > I would track your rolls of cable using Lots, this way when the order calls > for 25, 50, or 100 m of cable if the lot does not have the qty needed to > produce the ethernet cable it will use the lot that has enough for the > finished product. On Wed, Jan 26, 2022 at 3:57 PM Radovan Skolnik < > radovan@skolnik.info [1] > wrote: Daniel, > thank you for answer. Yes it does make sense. But will it cover scenario > where I have let's say 2 rolls with 50m remaining on each and I want to > produce 100m final cable? Because in such case a completely new roll should > be ordered as I cannot join those 2 50m pieces together... So it comes to a > requirement here that you just do not track the total number of meters > remaining but you need to track each roll individually. Similar example > would be a woodmaker who needs certain sizes of wood for various products > (chair, table, ...) and he procures wood in 3m planks. What is your > opinion? Best regards > Radovan > > On streda 26. januára 2022 21:51:47 CET Daniel Reis wrote: > > I believe you need to use different Units of Measure (UoM). > > In this case, the "Cable" Product is purchased in "Rolls" and used > > in "Meters". > > The "Roll" UoM should be configured to convert to Meters at a rate > > of 1:1000. > > This way you track your cable stock in meters available, and you > > order to your supplier in rolls. > > Dos this make sense? > > Thanks > > Daniel > > > > On 26/01/22 20:37, Radovan Skolnik > > wrote: > > > > Hello, > > sorry for asking stupid questions here but I hope someone can provide some > > wisdom here that I am missing. Let's imagine this scenario: I produce > > Ethernet cables of various lengths - i.e. 25m, 50m, 75m, 100m, ... Each > > such final cable requires 2 connectors and that particular amount of "raw" > > cable. I can only buy raw cable in rolls of 1000m. So when I buy a new > > roll > > and produce one final 50m cable, 950m of raw cable remains. When I produce > > another of 100m length, 850m of raw cable remains. When my remaining raw > > cable on certain roll is 50m I cannot produce 100m final cable and need to > > order another raw cable roll. So the idea is tracking remaining quantity > > of > > somethings (products? lots? ...) that is bought at certain size and is > > being gradually consumed. There can of course be more of these (i.e. I > > have > > bought 3 rolls at the same time). Is there a way on how to model this? > > Manufacturing is not really my domain and looking through code of various > > modules I didn't find anything that would resemble such thing. Thank you > > very much. Best regards > > Radovan Skolnik > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [2] [1] > > Post to: mailto: contributors@odoo-community.org [3] [2] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4] [3] > > > > > > > > -- > > DANIEL > > REIS* > > MANAGING DIRECTOR > > M:* > > +351 919 991 307 > > E:* > > dreis@OpenSourceIntegrators.com [4] > > A:* > > Avenida da República 3000, Estoril Office B, #34 > > > > > > None [5] None [6] None [7] > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [5] [8] > > Post to: mailto: contributors@odoo-community.org [6] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] [9] > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 [8] > > [2] mailto: contributors@odoo-community.org [9] > > [3] https://odoo-community.org/groups?unsubscribe [10] > > [4] mailto: dreis@OpenSourceIntegrators.com [11] > > [5] https://www.magentointegrators.com/ [12] > > [6] https://www.hadoopintegrators.com/ [13] > > [7] https://www.usaodoo.com/ [14] > > [8] https://odoo-community.org/groups/contributors-15 [15] > > [9] https://odoo-community.org/groups?unsubscribe [16] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [17] > Post to: mailto: contributors@odoo-community.org [18] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [19] > > -- > * James Dominy * > CEO > * Lunel, Inc * > Saratoga Springs, UT > 719-888-9582 > jamesdominy@lunelerp.com [20] > * www.lunel.co [21] > * > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [22] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [23] > > > > [1] mailto:radovan@skolnik.info > [2] https://odoo-community.org/groups/contributors-15 > [3] mailto:contributors@odoo-community.org > [4] https://odoo-community.org/groups?unsubscribe > [5] https://odoo-community.org/groups/contributors-15 > [6] mailto:contributors@odoo-community.org > [7] https://odoo-community.org/groups?unsubscribe > [8] https://odoo-community.org/groups/contributors-15 > [9] mailto:contributors@odoo-community.org > [10] https://odoo-community.org/groups?unsubscribe > [11] mailto:dreis@OpenSourceIntegrators.com > [12] https://www.magentointegrators.com/ > [13] https://www.hadoopintegrators.com/ > [14] https://www.usaodoo.com/ > [15] https://odoo-community.org/groups/contributors-15 > [16] https://odoo-community.org/groups?unsubscribe > [17] https://odoo-community.org/groups/contributors-15 > [18] mailto:contributors@odoo-community.org > [19] https://odoo-community.org/groups?unsubscribe > [20] mailto:james@lunelerp.com > [21] http://www.lunel.co > [22] https://odoo-community.org/groups/contributors-15 > [23] 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 Graeme Gellatly - 09:15 - 27 Jan 2022 -
Re: Manufacturing advice needed - materials of measured units being consumed partially
Hello, thank you for all the answers.I guess I have to test this thoroughly. My worry is generally this: let's say I have 2 lots/rolls each with 50m raw cable remaining. I need to produce 100m final cable. I think the system would consider I have enough of raw cable for this. Because that would work for certain scenarios. Imagine you need 100kg of something to prdouce something else. If you have 2 lots each with 50kg you're good to go - you just combine 50kg from each. Similarily if it was pieces. All these can be joined / added. I am talking about scenario where partial residual amounts cannot be added together to create a larger piece / amount. Hope I am making myself clear. Best regards Radovan On štvrtok 27. januára 2022 0:17:23 CET James Dominy wrote: > Hello Radovan, > I would track your rolls of cable using Lots, this way when the order calls > for 25, 50, or 100 m of cable if the lot does not have the qty needed to > produce the ethernet cable it will use the lot that has enough for the > finished product. On Wed, Jan 26, 2022 at 3:57 PM Radovan Skolnik < > radovan@skolnik.info [1] > wrote: Daniel, > thank you for answer. Yes it does make sense. But will it cover scenario > where I have let's say 2 rolls with 50m remaining on each and I want to > produce 100m final cable? Because in such case a completely new roll should > be ordered as I cannot join those 2 50m pieces together... So it comes to a > requirement here that you just do not track the total number of meters > remaining but you need to track each roll individually. Similar example > would be a woodmaker who needs certain sizes of wood for various products > (chair, table, ...) and he procures wood in 3m planks. What is your > opinion? Best regards > Radovan > > On streda 26. januára 2022 21:51:47 CET Daniel Reis wrote: > > I believe you need to use different Units of Measure (UoM). > > In this case, the "Cable" Product is purchased in "Rolls" and used > > in "Meters". > > The "Roll" UoM should be configured to convert to Meters at a rate > > of 1:1000. > > This way you track your cable stock in meters available, and you > > order to your supplier in rolls. > > Dos this make sense? > > Thanks > > Daniel > > > > On 26/01/22 20:37, Radovan Skolnik > > wrote: > > > > Hello, > > sorry for asking stupid questions here but I hope someone can provide some > > wisdom here that I am missing. Let's imagine this scenario: I produce > > Ethernet cables of various lengths - i.e. 25m, 50m, 75m, 100m, ... Each > > such final cable requires 2 connectors and that particular amount of "raw" > > cable. I can only buy raw cable in rolls of 1000m. So when I buy a new > > roll > > and produce one final 50m cable, 950m of raw cable remains. When I produce > > another of 100m length, 850m of raw cable remains. When my remaining raw > > cable on certain roll is 50m I cannot produce 100m final cable and need to > > order another raw cable roll. So the idea is tracking remaining quantity > > of > > somethings (products? lots? ...) that is bought at certain size and is > > being gradually consumed. There can of course be more of these (i.e. I > > have > > bought 3 rolls at the same time). Is there a way on how to model this? > > Manufacturing is not really my domain and looking through code of various > > modules I didn't find anything that would resemble such thing. Thank you > > very much. Best regards > > Radovan Skolnik > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [2] [1] > > Post to: mailto: contributors@odoo-community.org [3] [2] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4] [3] > > > > > > > > -- > > DANIEL > > REIS* > > MANAGING DIRECTOR > > M:* > > +351 919 991 307 > > E:* > > dreis@OpenSourceIntegrators.com [4] > > A:* > > Avenida da República 3000, Estoril Office B, #34 > > > > > > None [5] None [6] None [7] > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [5] [8] > > Post to: mailto: contributors@odoo-community.org [6] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] [9] > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 [8] > > [2] mailto: contributors@odoo-community.org [9] > > [3] https://odoo-community.org/groups?unsubscribe [10] > > [4] mailto: dreis@OpenSourceIntegrators.com [11] > > [5] https://www.magentointegrators.com/ [12] > > [6] https://www.hadoopintegrators.com/ [13] > > [7] https://www.usaodoo.com/ [14] > > [8] https://odoo-community.org/groups/contributors-15 [15] > > [9] https://odoo-community.org/groups?unsubscribe [16] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [17] > Post to: mailto: contributors@odoo-community.org [18] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [19] > > -- > * James Dominy * > CEO > * Lunel, Inc * > Saratoga Springs, UT > 719-888-9582 > jamesdominy@lunelerp.com [20] > * www.lunel.co [21] > * > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [22] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [23] > > > > [1] mailto:radovan@skolnik.info > [2] https://odoo-community.org/groups/contributors-15 > [3] mailto:contributors@odoo-community.org > [4] https://odoo-community.org/groups?unsubscribe > [5] https://odoo-community.org/groups/contributors-15 > [6] mailto:contributors@odoo-community.org > [7] https://odoo-community.org/groups?unsubscribe > [8] https://odoo-community.org/groups/contributors-15 > [9] mailto:contributors@odoo-community.org > [10] https://odoo-community.org/groups?unsubscribe > [11] mailto:dreis@OpenSourceIntegrators.com > [12] https://www.magentointegrators.com/ > [13] https://www.hadoopintegrators.com/ > [14] https://www.usaodoo.com/ > [15] https://odoo-community.org/groups/contributors-15 > [16] https://odoo-community.org/groups?unsubscribe > [17] https://odoo-community.org/groups/contributors-15 > [18] mailto:contributors@odoo-community.org > [19] https://odoo-community.org/groups?unsubscribe > [20] mailto:james@lunelerp.com > [21] http://www.lunel.co > [22] https://odoo-community.org/groups/contributors-15 > [23] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 07:11 - 27 Jan 2022
-
-
How to prevent odoo to send the entire traceback
Hi,Not sure if this is the right place to ask:Whenever there is an error, Odoo will send back a traceback (whether it is an API call, or from the browser).This could be a security issue, as a lot of data can be sent back. Is it possible to reduce the size of the traceback? - so as to prevent an attacker from retrieving any information on the server ?Regards,Dominique
by dominique.k - 05:25 - 21 Jan 2022-
Re: How to prevent odoo to send the entire traceback
Hi Dominique,You can try with a server wide module that overrides serialize_exception:old_http_serialize_exception = http.serialize_exception
def http_serialize_exception(e):
tmp = old_http_serialize_exception(e)
tmp['debug'] = 'Please check the logs for the traceback.'
return tmp
if 'redacted_module' in config.get('server_wide_modules'):
_logger.debug('Overriding default serialize_exception')
http.serialize_exception = http_serialize_exceptionRegards,NilsOn Fri, Jan 21, 2022 at 11:27 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:Hi,Not sure if this is the right place to ask:Whenever there is an error, Odoo will send back a traceback (whether it is an API call, or from the browser).This could be a security issue, as a lot of data can be sent back. Is it possible to reduce the size of the traceback? - so as to prevent an attacker from retrieving any information on the server ?Regards,Dominique_______________________________________________
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 Hamerlinck - 10:06 - 21 Jan 2022
-
Weblate contact
Hi,I tried to contact weblate support in https://translation.odoo-community.org/contact but after I sent the email, it said "Could not send message to administrator.".From what I understand of the platform, maybe there is some configuration missing in OCA's weblate installation? Can someone have a look?I have looked in https://odoo-community.org/groups but haven't found any mailing list dedicated to platform or translations issues, let me know if I should write somewhere else.Thanks,Simone Rubino
by Simone Rubino - 10:36 - 20 Jan 2022-
Re: Weblate contact
Hi Simone,I'm not sure why the weblate contact form doesn't work.In the meantime send your question to transbot@odoo-community.org. That is where we (well, I) manage the registration requests and if there weblate-related support questions, i'll see them there too when I look at new users requests.Best,-sbiOn Thu, Jan 20, 2022 at 10:36 AM Simone Rubino <simone.rubino@agilebg.com> wrote:Hi,I tried to contact weblate support in https://translation.odoo-community.org/contact but after I sent the email, it said "Could not send message to administrator.".From what I understand of the platform, maybe there is some configuration missing in OCA's weblate installation? Can someone have a look?I have looked in https://odoo-community.org/groups but haven't found any mailing list dedicated to platform or translations issues, let me know if I should write somewhere else.Thanks,Simone Rubino
_______________________________________________
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 - 01:46 - 22 Jan 2022
-
-
Proposing new PSC's
Dear Odoo Community contributors,I would like to propose new PSC members from ForgeFlow and Creu Blanca.The names I'm proposing are all very active contributors. You can check their contributions in the table below.PSC Team Propose Github handles Banking Aaron Henriquez, Enric Tobella, Jordi Ballester aaronhforgeflow, etobella, jordibforgeflow HR Alba Riera albariera Reporting engine Hector Villarreal, Enric Tobella hviorforgeflow,etobella Search Hector Villarreal, Enric Tobella hviorforgeflow,etobella Social Enric Tobella etobella Web Enric Tobella etobella Regards,--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
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 Jordi Ballester Alomar - 10:30 - 20 Jan 2022-
Re: Proposing new PSC's
Thanks!!El jue., 20 ene. 2022 16:32, Simone Orsi <simahawk@gmail.com> escribió:Hola,wow, that was a big list! :DAll done. You'll get invitations on the next sync as usual.Cheers,S.On Thu, Jan 20, 2022 at 10:32 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:Dear Odoo Community contributors,I would like to propose new PSC members from ForgeFlow and Creu Blanca.The names I'm proposing are all very active contributors. You can check their contributions in the table below.
PSC Team Propose Github handles Banking Aaron Henriquez, Enric Tobella, Jordi Ballester aaronhforgeflow, etobella, jordibforgeflow HR Alba Riera albariera Reporting engine Hector Villarreal, Enric Tobella hviorforgeflow,etobella Search Hector Villarreal, Enric Tobella hviorforgeflow,etobella Social Enric Tobella etobella Web Enric Tobella etobella Regards,--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
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._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jordi Ballester Alomar - 06:56 - 20 Jan 2022 -
Re: Proposing new PSC's
Hola,wow, that was a big list! :DAll done. You'll get invitations on the next sync as usual.Cheers,S.On Thu, Jan 20, 2022 at 10:32 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:Dear Odoo Community contributors,I would like to propose new PSC members from ForgeFlow and Creu Blanca.The names I'm proposing are all very active contributors. You can check their contributions in the table below.PSC Team Propose Github handles Banking Aaron Henriquez, Enric Tobella, Jordi Ballester aaronhforgeflow, etobella, jordibforgeflow HR Alba Riera albariera Reporting engine Hector Villarreal, Enric Tobella hviorforgeflow,etobella Search Hector Villarreal, Enric Tobella hviorforgeflow,etobella Social Enric Tobella etobella Web Enric Tobella etobella Regards,--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
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._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi. - 04:30 - 20 Jan 2022 -
Re: Proposing new PSC's
+1El jue, 20 ene 2022 a las 15:47, Saran Limpajitkutaporn (<saranl@ecosoft.co.th>) escribió:+1On Thu, Jan 20, 2022 at 7:42 PM Harald Panten Lopez <harald.panten@sygel.es> wrote:+1 to all of them! 👍El jue, 20 ene 2022 a las 13:06, Joël Grand-Guillaume (<joel.grandguillaume@camptocamp.com>) escribió:+1On Thu, Jan 20, 2022 at 11:17 AM Alex Comba <alex.comba@agilebg.com> wrote:+1On Thu, Jan 20, 2022 at 10:32 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:Dear Odoo Community contributors,I would like to propose new PSC members from ForgeFlow and Creu Blanca.The names I'm proposing are all very active contributors. You can check their contributions in the table below.PSC Team Propose Github handles Banking Aaron Henriquez, Enric Tobella, Jordi Ballester aaronhforgeflow, etobella, jordibforgeflow HR Alba Riera albariera Reporting engine Hector Villarreal, Enric Tobella hviorforgeflow,etobella Search Hector Villarreal, Enric Tobella hviorforgeflow,etobella Social Enric Tobella etobella Web Enric Tobella etobella Regards,--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
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._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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
--Valentín Vinagre Urteaga
CTO
Sygel Technology S.L
+34 662 68 78 95 valentin.vinagre@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Valentín Vinagre - 04:05 - 20 Jan 2022 -
Re: Proposing new PSC's
+1On Thu, Jan 20, 2022 at 7:42 PM Harald Panten Lopez <harald.panten@sygel.es> wrote:+1 to all of them! 👍El jue, 20 ene 2022 a las 13:06, Joël Grand-Guillaume (<joel.grandguillaume@camptocamp.com>) escribió:+1On Thu, Jan 20, 2022 at 11:17 AM Alex Comba <alex.comba@agilebg.com> wrote:+1On Thu, Jan 20, 2022 at 10:32 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:Dear Odoo Community contributors,I would like to propose new PSC members from ForgeFlow and Creu Blanca.The names I'm proposing are all very active contributors. You can check their contributions in the table below.PSC Team Propose Github handles Banking Aaron Henriquez, Enric Tobella, Jordi Ballester aaronhforgeflow, etobella, jordibforgeflow HR Alba Riera albariera Reporting engine Hector Villarreal, Enric Tobella hviorforgeflow,etobella Search Hector Villarreal, Enric Tobella hviorforgeflow,etobella Social Enric Tobella etobella Web Enric Tobella etobella Regards,--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
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._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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
by saranl - 03:41 - 20 Jan 2022 -
Re: Proposing new PSC's
+1 to all of them! 👍El jue, 20 ene 2022 a las 13:06, Joël Grand-Guillaume (<joel.grandguillaume@camptocamp.com>) escribió:+1On Thu, Jan 20, 2022 at 11:17 AM Alex Comba <alex.comba@agilebg.com> wrote:+1On Thu, Jan 20, 2022 at 10:32 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:Dear Odoo Community contributors,I would like to propose new PSC members from ForgeFlow and Creu Blanca.The names I'm proposing are all very active contributors. You can check their contributions in the table below.
PSC Team Propose Github handles Banking Aaron Henriquez, Enric Tobella, Jordi Ballester aaronhforgeflow, etobella, jordibforgeflow HR Alba Riera albariera Reporting engine Hector Villarreal, Enric Tobella hviorforgeflow,etobella Search Hector Villarreal, Enric Tobella hviorforgeflow,etobella Social Enric Tobella etobella Web Enric Tobella etobella Regards,--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
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._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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 - 01:41 - 20 Jan 2022
-
-
Vendor Pricelist records for Product Variants - what am I missing?
Hello,
as New Year came it fell upon me to update lots of pricelists. As we use Product Variants (product.product) quite a bit I am invalidating (i.e. setting date_end) on existing Supplier Pricelist (product.supplierinfo) records and creating new ones. Using base_import_match to match the correct product variant by internal reference (default_code) and trying to import related product.supplierinfo record. Originally I wanted to create small helper that would invalidate all existing records (no end date, same variant, same template, same supplier, same company) when creating new one. Just to save time updating existing records and creating new ones. However it never works (more on that below).
Now there are 2 fields defined for product.template and none for product.product that would serve what I am wanting to do. Here's what's defined for product.template (in 13.0, 14.0 and 15.0 as well):
seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors', depends_context=('company',), help="Define vendor pricelists.")
variant_seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id')In Purchase there is this for product.template view:
<field name="seller_ids" context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id), 'product_template_invisible_variant': True}" nolabel="1" attrs="{'invisible': [('product_variant_count','>',1)]}"/>
<field name="variant_seller_ids" context="{'default_product_tmpl_id': context.get('product_tmpl_id', active_id)}" nolabel="1" attrs="{'invisible': [('product_variant_count','<=',1)]}"/>
Just for clarity, here's part from product.supplierinfo:
product_id = fields.Many2one('product.product', 'Product Variant', check_company=True, help="If not set, the vendor price will apply to all variants of this product.")
product_tmpl_id = fields.Many2one('product.template', 'Product Template', check_company=True, index=True, ondelete='cascade')
Am I missing something here or are these the same besides the context and some witchcraft in views? While trying to import the product.product records when creating product.supplierinfo records there's always product_tmpl_id but never product_id. Shouldn't the definition of variant_s be like this and defined in product.product model:
variant_seller_ids = fields.One2many('product.supplierinfo', 'product_id')
What is the purpose of current design? Would anyone be willing to shed some light here? Hope such post fits in the mailing list.
Thank you very much.Best regards
Radovan Skolnik
by Radovan Skolnik - 08:31 - 20 Jan 2022-
Re: Vendor Pricelist records for Product Variants - what am I missing?
Graeme,
I perfectly undertsand the design of product.supplierinfo and have no problem dealing with date_end (I created a small module that upon creation of new record end the existing ones with the same combination of attributes)
What puzzles me is the design from the side of product.template and/or product.product side. You see there are basically 2 identical one2many attributes (so actually no database tables / columns are created) on product.template that reference product.supplierinfo: seller_ids and variant_seller_ids:
seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors', help="Define vendor pricelists.")
variant_seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id')
As the name would suggest the latter should somehow provide info on sellers of variants. But it does not in any way. The variant_seller_ids is never used in code. It is only referenced in one view where it is displayed instead of seller_ids in purchase/views/product_views.xml when there are more than 1 variants of that product:
<field name="seller_ids" context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id), 'product_template_invisible_variant': True}" nolabel="1" attrs="{'invisible': [('product_variant_count','>',1)]}"/>
<field name="variant_seller_ids" context="{'default_product_tmpl_id': context.get('product_tmpl_id', active_id)}" nolabel="1" attrs="{'invisible': [('product_variant_count','<=',1)]}"/>
But it still shows the same thing as seller_ids would! According to a comment on PR that introduced this back in June 2017 in version 11.0 from sswapnesh (who I believe is best Odoo contributor for years 2019, 2020 and 202) this does not make sense as well. Just see it there - tho comment is from August 2020. I believe the variant_seller_ids should have been defined in product.product and the name of its inverse filed should have been product_id. Or something similar.
I stumbled upon this situation when attempting to import-update product variant and also create new corresponding record for product.supplierinfo. It seems that's impossible. Why? Because there is no one2many relation between product.product and product.supplierinfo. I do not believe this was intended.
Am I making sense? Do those 2 attributes together make sense in context of product.supplierinfo? Not to me.
Best regards
Radovan
On štvrtok 20. januára 2022 20:56:57 CET Graeme Gellatly wrote:
> In general when you do lots of seller pricelist you enable Vendor Pricelists
> and import from there. The end date problem is still a problem. You can
> kind of get around it with sequences, start dates on new records and then
> find dups after. It would be good to have a specific module to do
> everything. But supplierinfo is straightforward. Those are the fields you
> care about. Not product template relational references. Do it via vendor
> pricelists and much easier. product_id = fields . Many2one (
> 'product.product' , 'Product Variant' , check_company = True , help = "If
> not set, the vendor price will apply to all variants of this product." )
> product_tmpl_id = fields . Many2one ( 'product.template' , 'Product
> Template' , check_company = True , index = True , ondelete =
> 'cascade' ) On Thu, Jan 20, 2022 at 10:27 PM Radovan Skolnik <
> radovan@skolnik.info [1] > wrote: What's more the field variant_seller_ids
> is never used anywhere besides that view. It was introduced into 11.0 by
> this PR: https://github.com/odoo/odoo/pull/17789 [2]
>
> R.S.
>
> On štvrtok 20. januára 2022 8:32:15 CET Radovan Skolnik wrote:
> > Hello,
> >
> > as New Year came it fell upon me to update lots of pricelists. As we use
> > Product Variants (product.product) quite a bit I am invalidating (i.e.
> > setting date_end) on existing Supplier Pricelist (product.supplierinfo)
> > records and creating new ones. Using base_import_match to match the
> > correct
> > product variant by internal reference (default_code) and trying to import
> > related product.supplierinfo record. Originally I wanted to create small
> > helper that would invalidate all existing records (no end date, same
> > variant, same template, same supplier, same company) when creating new
> > one.
> > Just to save time updating existing records and creating new ones. However
> > it never works (more on that below).
> >
> > Now there are 2 fields defined for product.template and none for
> > product.product that would serve what I am wanting to do. Here's what's
> > defined for product.template (in 13.0, 14.0 and 15.0 as well): seller_ids
> > =
> > fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors',
> > depends_context=('company',), help="Define vendor pricelists.")
> > variant_seller_ids = fields.One2many('product.supplierinfo',
> > 'product_tmpl_id')
> >
> > In Purchase there is this for product.template view:
> > <field name="seller_ids"
> > context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_i
> > d
> > ), 'product_template_invisible_variant': True}" nolabel="1"
> > attrs="{'invisible': [('product_variant_count','>',1)]}"/> <field
> > name="variant_seller_ids" context="{'default_product_tmpl_id':
> > context.get('product_tmpl_id', active_id)}" nolabel="1"
> > attrs="{'invisible': [('product_variant_count','<=',1)]}"/>
> >
> > Just for clarity, here's part from product.supplierinfo:
> > product_id = fields.Many2one('product.product', 'Product Variant',
> > check_company=True, help="If not set, the vendor price will apply to all
> > variants of this product.") product_tmpl_id =
> > fields.Many2one('product.template', 'Product Template',
> > check_company=True,
> > index=True, ondelete='cascade')
> >
> > Am I missing something here or are these the same besides the context and
> > some witchcraft in views? While trying to import the product.product
> > records when creating product.supplierinfo records there's always
> > product_tmpl_id but never product_id. Shouldn't the definition of
> > variant_s
> > be like this and defined in product.product model: variant_seller_ids =
> > fields.One2many('product.supplierinfo', ' *product_id* ')
> >
> > What is the purpose of current design? Would anyone be willing to shed
> > some
> > light here? Hope such post fits in the mailing list.
> >
> > Thank you very much.Best regards
> >
> > Radovan Skolnik
> >
> > _______________________________________________
> > Mailing-List: https://odoo-community.org/groups/contributors-15 [3] [1]
> > Post to: mailto: contributors@odoo-community.org [4]
> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] [2]
> >
> >
> >
> > [1] https://odoo-community.org/groups/contributors-15 [6]
> > [2] https://odoo-community.org/groups?unsubscribe [7]
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [8]
> Post to: mailto: contributors@odoo-community.org [9]
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [10]
>
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [11]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [12]
>
>
>
> [1] mailto:radovan@skolnik.info
> [2] https://github.com/odoo/odoo/pull/17789
> [3] https://odoo-community.org/groups/contributors-15
> [4] mailto:contributors@odoo-community.org
> [5] https://odoo-community.org/groups?unsubscribe
> [6] https://odoo-community.org/groups/contributors-15
> [7] https://odoo-community.org/groups?unsubscribe
> [8] https://odoo-community.org/groups/contributors-15
> [9] mailto:contributors@odoo-community.org
> [10] https://odoo-community.org/groups?unsubscribe
> [11] https://odoo-community.org/groups/contributors-15
> [12] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 09:36 - 20 Jan 2022 -
Re: Vendor Pricelist records for Product Variants - what am I missing?
In general when you do lots of seller pricelist you enable Vendor Pricelists and import from there. The end date problem is still a problem. You can kind of get around it with sequences, start dates on new records and then find dups after. It would be good to have a specific module to do everything.But supplierinfo is straightforward. Those are the fields you care about. Not product template relational references. Do it via vendor pricelists and much easier.
product_id = fields.Many2one( 'product.product', 'Product Variant', check_company=True, help="If not set, the vendor price will apply to all variants of this product.") product_tmpl_id = fields.Many2one( 'product.template', 'Product Template', check_company=True, index=True, ondelete='cascade') On Thu, Jan 20, 2022 at 10:27 PM Radovan Skolnik <radovan@skolnik.info> wrote:What's more the field variant_seller_ids is never used anywhere besides that view.
It was introduced into 11.0 by this PR: https://github.com/odoo/odoo/pull/17789
R.S.
On štvrtok 20. januára 2022 8:32:15 CET Radovan Skolnik wrote:
> Hello,
>
> as New Year came it fell upon me to update lots of pricelists. As we use
> Product Variants (product.product) quite a bit I am invalidating (i.e.
> setting date_end) on existing Supplier Pricelist (product.supplierinfo)
> records and creating new ones. Using base_import_match to match the correct
> product variant by internal reference (default_code) and trying to import
> related product.supplierinfo record. Originally I wanted to create small
> helper that would invalidate all existing records (no end date, same
> variant, same template, same supplier, same company) when creating new one.
> Just to save time updating existing records and creating new ones. However
> it never works (more on that below).
>
> Now there are 2 fields defined for product.template and none for
> product.product that would serve what I am wanting to do. Here's what's
> defined for product.template (in 13.0, 14.0 and 15.0 as well): seller_ids =
> fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors',
> depends_context=('company',), help="Define vendor pricelists.")
> variant_seller_ids = fields.One2many('product.supplierinfo',
> 'product_tmpl_id')
>
> In Purchase there is this for product.template view:
> <field name="seller_ids"
> context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id
> ), 'product_template_invisible_variant': True}" nolabel="1"
> attrs="{'invisible': [('product_variant_count','>',1)]}"/> <field
> name="variant_seller_ids" context="{'default_product_tmpl_id':
> context.get('product_tmpl_id', active_id)}" nolabel="1"
> attrs="{'invisible': [('product_variant_count','<=',1)]}"/>
>
> Just for clarity, here's part from product.supplierinfo:
> product_id = fields.Many2one('product.product', 'Product Variant',
> check_company=True, help="If not set, the vendor price will apply to all
> variants of this product.") product_tmpl_id =
> fields.Many2one('product.template', 'Product Template', check_company=True,
> index=True, ondelete='cascade')
>
> Am I missing something here or are these the same besides the context and
> some witchcraft in views? While trying to import the product.product
> records when creating product.supplierinfo records there's always
> product_tmpl_id but never product_id. Shouldn't the definition of variant_s
> be like this and defined in product.product model: variant_seller_ids =
> fields.One2many('product.supplierinfo', ' *product_id* ')
>
> What is the purpose of current design? Would anyone be willing to shed some
> light here? Hope such post fits in the mailing list.
>
> Thank you very much.Best regards
>
> Radovan Skolnik
>
> _______________________________________________
> 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]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] 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 Graeme Gellatly - 08:55 - 20 Jan 2022 -
Re: Vendor Pricelist records for Product Variants - what am I missing?
What's more the field variant_seller_ids is never used anywhere besides that view.
It was introduced into 11.0 by this PR: https://github.com/odoo/odoo/pull/17789
R.S.
On štvrtok 20. januára 2022 8:32:15 CET Radovan Skolnik wrote:
> Hello,
>
> as New Year came it fell upon me to update lots of pricelists. As we use
> Product Variants (product.product) quite a bit I am invalidating (i.e.
> setting date_end) on existing Supplier Pricelist (product.supplierinfo)
> records and creating new ones. Using base_import_match to match the correct
> product variant by internal reference (default_code) and trying to import
> related product.supplierinfo record. Originally I wanted to create small
> helper that would invalidate all existing records (no end date, same
> variant, same template, same supplier, same company) when creating new one.
> Just to save time updating existing records and creating new ones. However
> it never works (more on that below).
>
> Now there are 2 fields defined for product.template and none for
> product.product that would serve what I am wanting to do. Here's what's
> defined for product.template (in 13.0, 14.0 and 15.0 as well): seller_ids =
> fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors',
> depends_context=('company',), help="Define vendor pricelists.")
> variant_seller_ids = fields.One2many('product.supplierinfo',
> 'product_tmpl_id')
>
> In Purchase there is this for product.template view:
> <field name="seller_ids"
> context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id
> ), 'product_template_invisible_variant': True}" nolabel="1"
> attrs="{'invisible': [('product_variant_count','>',1)]}"/> <field
> name="variant_seller_ids" context="{'default_product_tmpl_id':
> context.get('product_tmpl_id', active_id)}" nolabel="1"
> attrs="{'invisible': [('product_variant_count','<=',1)]}"/>
>
> Just for clarity, here's part from product.supplierinfo:
> product_id = fields.Many2one('product.product', 'Product Variant',
> check_company=True, help="If not set, the vendor price will apply to all
> variants of this product.") product_tmpl_id =
> fields.Many2one('product.template', 'Product Template', check_company=True,
> index=True, ondelete='cascade')
>
> Am I missing something here or are these the same besides the context and
> some witchcraft in views? While trying to import the product.product
> records when creating product.supplierinfo records there's always
> product_tmpl_id but never product_id. Shouldn't the definition of variant_s
> be like this and defined in product.product model: variant_seller_ids =
> fields.One2many('product.supplierinfo', ' *product_id* ')
>
> What is the purpose of current design? Would anyone be willing to shed some
> light here? Hope such post fits in the mailing list.
>
> Thank you very much.Best regards
>
> Radovan Skolnik
>
> _______________________________________________
> 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]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 10:26 - 20 Jan 2022
-
-
Cash flow statement report
Dear Contributors,I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?This is report in enterprise versionBest Regards,Tharathip C.
by tharathipc - 03:51 - 20 Jan 2022-
Re: Cash flow statement report
Great! I will try. Thank you kindly :)ในวันที่ พฤ. 20 ม.ค. 2022 เวลา 15:22 Roussel, Denis <denis.roussel@acsone.eu> เขียนว่า:Hi,If you follow the links, you find this: https://github.com/OCA/account-financial-reporting/tree/14.0/mis_builder_cash_flowOn Thu, Jan 20, 2022 at 9:12 AM Virginie Dewulf <virginie@coopiteasy.be> wrote:Hello,I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154Maybe someone else here knows where it is!Good luck,PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie0477/64.17.20-----Original Message-----From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Cash flow statement reportDate: Thu, 20 Jan 2022 02:52:45 -0000Dear Contributors,I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?This is report in enterprise versionBest Regards,Tharathip C._______________________________________________
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 tharathipc - 04:31 - 24 Jan 2022 -
Re: Cash flow statement report
Dear Virginie,In my experience, the best way to find modules is the OCA App Store, mainly for functional consultants who don't have GitHub profile.So the module isAnd in the screenshot you can see how I found it easylyMy bestRafael Blasco@ModuonEl jue., 20 ene. 2022 9:12, Virginie Dewulf <virginie@coopiteasy.be> escribió:Hello,I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154Maybe someone else here knows where it is!Good luck,PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie0477/64.17.20-----Original Message-----From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Cash flow statement reportDate: Thu, 20 Jan 2022 02:52:45 -0000Dear Contributors,I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?This is report in enterprise versionBest Regards,Tharathip C._______________________________________________
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 Rafael Blasco (Moduon) - 09:25 - 20 Jan 2022 -
Re: Cash flow statement report
Hi,If you follow the links, you find this: https://github.com/OCA/account-financial-reporting/tree/14.0/mis_builder_cash_flowOn Thu, Jan 20, 2022 at 9:12 AM Virginie Dewulf <virginie@coopiteasy.be> wrote:Hello,I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154Maybe someone else here knows where it is!Good luck,PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie0477/64.17.20-----Original Message-----From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Cash flow statement reportDate: Thu, 20 Jan 2022 02:52:45 -0000Dear Contributors,I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?This is report in enterprise versionBest Regards,Tharathip C._______________________________________________
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 Denis Roussel. - 09:21 - 20 Jan 2022 -
Re: Cash flow statement report
The OCA apps library is your friend :)
by Pedro M. Baeza - 09:21 - 20 Jan 2022 -
Re: Cash flow statement report
Hello,I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154Maybe someone else here knows where it is!Good luck,PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!--
Virginie0477/64.17.20-----Original Message-----From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Cash flow statement reportDate: Thu, 20 Jan 2022 02:52:45 -0000Dear Contributors,I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?This is report in enterprise versionBest Regards,Tharathip C._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Virginie Dewulf. - 09:10 - 20 Jan 2022
-
-
New repositories : cooperative and participative supermarket
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :- cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
- beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to- remove all references to Obeesdoo and Easy My Coop (debranding) ;
- split modules by features ;
- cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :- cooperative with all modules in beta-stage while we debrand them.
- shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
- vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40
by Robin Keunen - 11:26 - 14 Jan 2022-
Re: New repositories : cooperative and participative supermarket
Hi Robin,I have created the 3 repositories and the Cooperative PSC.I set you as PSC representative and added Remy and Houssine as members.@Enrico, I could not find a user with your name nor Daniel Palomar in the OCA database. Could you register so I can add you as PSC members ?@Robin, I'll let you initialize the branches you need with `copier copy git+https://github.com/oca/oca-addons-repo-template`. Please answer GitHub to the CI question so it uses GitHub actions.Let me know if I forgot anything or if you need help setting it up.Best regards,-sbi
by Stéphane Bidoul - 07:48 - 27 Feb 2022 -
Re: New repositories : cooperative and participative supermarket
I would be glad to join.I agree with Robin. Not sure that the PSC association is suitable as from what I see it covers mainly the membership aspect. While a cooperative verticalization will mainly cover the specifics for a commercial cooperative company as the share management for example.Anyway there is also a membership aspect for cooperative but it is far different from the way it is conceived for association.Le jeu. 10 févr. 2022 à 10:46, Enrico Stano <enrico.stano@coopdevs.org> a écrit :
+1 on Rémy and/or Houssine of course.
If needed, from Coopdevs we would be glad to participate (Daniel Palomar or myself). Thanks.
Not sure about the "Association" PSC, it also seems unrelated IMHO. But maybe PSC members from "Association" have a different opinion. Could we ask?
Bye,
Enrico
coopdevs.org
On 2/9/22 19:17, robin@coopiteasy.be wrote:
Rémy Taymans (remy@coopiteasy.be) should be in the PSC as well. Is there candidates at Coopdevs ? If Houssine Bakkali is still around and interested, he would be a good candidate as well.
Expanding “Association” could work if we need to have people outside of Coop IT Easy in the PSC. Otherwise, it seems unrelated.
All the best,
On 9 Feb 2022, 18:42 +0100, Daniel Reis <dreis@opensourceintegrators.com>, wrote:
Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91
/Daniel
On 09/02/22 17:32, Stéphane Bidoul wrote:
Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?
I don't immediately see an existing PSC to cover this scope.So shall we create one new PSC (named Ccooperative?) for the 3 repos ?Who would be the PSC representative (Robin?). Who would be the first members ?-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,
+1 and a big thank you!
Bye,
Enrico Stano
On 1/27/22 18:57, Roussel, Denis wrote:
Hi Robin,
+1 for the three repos.
On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:
Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
--
Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Enrico Stano coopdevs.org_______________________________________________
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 662 68 78 95 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
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
-- Enrico Stano coopdevs.org_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Houssine BAKKALI - 11:01 - 10 Feb 2022 -
Re: New repositories : cooperative and participative supermarket
+1 on Rémy and/or Houssine of course.
If needed, from Coopdevs we would be glad to participate (Daniel Palomar or myself). Thanks.
Not sure about the "Association" PSC, it also seems unrelated IMHO. But maybe PSC members from "Association" have a different opinion. Could we ask?
Bye,
Enrico
coopdevs.org
On 2/9/22 19:17, robin@coopiteasy.be wrote:
Rémy Taymans (remy@coopiteasy.be) should be in the PSC as well. Is there candidates at Coopdevs ? If Houssine Bakkali is still around and interested, he would be a good candidate as well.
Expanding “Association” could work if we need to have people outside of Coop IT Easy in the PSC. Otherwise, it seems unrelated.
All the best,
On 9 Feb 2022, 18:42 +0100, Daniel Reis <dreis@opensourceintegrators.com>, wrote:
Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91
/Daniel
On 09/02/22 17:32, Stéphane Bidoul wrote:
Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?
I don't immediately see an existing PSC to cover this scope.So shall we create one new PSC (named Ccooperative?) for the 3 repos ?Who would be the PSC representative (Robin?). Who would be the first members ?-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,
+1 and a big thank you!
Bye,
Enrico Stano
On 1/27/22 18:57, Roussel, Denis wrote:
Hi Robin,
+1 for the three repos.
On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:
Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
--
Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Enrico Stano coopdevs.org_______________________________________________
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 662 68 78 95 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
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
-- Enrico Stano coopdevs.org
by Enrico Stano - 10:45 - 10 Feb 2022 -
Re: New repositories : cooperative and participative supermarket
Rémy Taymans (remy@coopiteasy.be) should be in the PSC as well. Is there candidates at Coopdevs ? If Houssine Bakkali is still around and interested, he would be a good candidate as well.
Expanding “Association” could work if we need to have people outside of Coop IT Easy in the PSC. Otherwise, it seems unrelated.
All the best,
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40On 9 Feb 2022, 18:42 +0100, Daniel Reis <dreis@opensourceintegrators.com>, wrote:
Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91
/Daniel
On 09/02/22 17:32, Stéphane Bidoul wrote:Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?I don't immediately see an existing PSC to cover this scope.So shall we create one new PSC (named Ccooperative?) for the 3 repos ?Who would be the PSC representative (Robin?). Who would be the first members ?-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:Hi,
+1 and a big thank you!
Bye,
Enrico Stano
On 1/27/22 18:57, Roussel, Denis wrote:Hi Robin,+1 for the three repos.
On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
--
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe-- Enrico Stano coopdevs.org_______________________________________________
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 662 68 78 95 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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Robin Keunen - 07:16 - 9 Feb 2022 -
Re: New repositories : cooperative and participative supermarket
Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91
/Daniel
On 09/02/22 17:32, Stéphane Bidoul wrote:
Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?
I don't immediately see an existing PSC to cover this scope.So shall we create one new PSC (named Ccooperative?) for the 3 repos ?Who would be the PSC representative (Robin?). Who would be the first members ?-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,
+1 and a big thank you!
Bye,
Enrico Stano
On 1/27/22 18:57, Roussel, Denis wrote:
Hi Robin,
+1 for the three repos.
On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:
Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
--
Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Enrico Stano coopdevs.org_______________________________________________
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 662 68 78 95 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 06:41 - 9 Feb 2022
-
New repo proposal: repair
Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 02:10 - 12 Jan 2022-
Re: New repo proposal: repair
Thank you Lois!On Wed, 19 Jan 2022 at 10:31, Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:On Wed, Jan 19, 2022 at 10:02 AM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:Thank you Community! Thank you Simone!I tried to initialize the repo but I am not part of the @OCA/manufacturing-maintainers group so I will ask someone else to do that.Regards,AaronOn Wed, 19 Jan 2022 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 10:45 - 19 Jan 2022 -
Re: New repo proposal: repair
On Wed, Jan 19, 2022 at 10:02 AM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:Thank you Community! Thank you Simone!I tried to initialize the repo but I am not part of the @OCA/manufacturing-maintainers group so I will ask someone else to do that.Regards,AaronOn Wed, 19 Jan 2022 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L.
by Lois Rilo Antelo - 10:30 - 19 Jan 2022 -
Re: New repo proposal: repair
Thank you Community! Thank you Simone!I tried to initialize the repo but I am not part of the @OCA/manufacturing-maintainers group so I will ask someone else to do that.Regards,AaronOn Wed, 19 Jan 2022 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 10:01 - 19 Jan 2022 -
Re: New repo proposal: repair
On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi. - 09:01 - 19 Jan 2022 -
Re: New repo proposal: repair
+1De: "Antonio M. Vigliotti (gmail)" <antoniomaria.vigliotti@gmail.com>
Para: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Enviadas: Terça-feira, 18 de janeiro de 2022 13:11:45
Assunto: Re: New repo proposal: repairFull agree
+1
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 12/01/22 14:12, Aarón Henríquez Quintana ha scritto:
Hi Community,
The reasons that support this new repo are:
* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo
Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.
For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.
WDYT?
Thank you for considering this proposal.
Have a nice day.--
Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
_______________________________________________
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 Luis F Miléo - 05:31 - 18 Jan 2022
-
