Archives
Contributors
-
Re: Proposing new PSC's
OK for me. I know all of them and indeed are very active contributors.Regards.
by Pedro M. Baeza - 10:36 - 20 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: 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 -
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 -
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 -
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: 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 -
Re: New repo proposal: repair
Full 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
by Antonio M. Vigliotti - 05:11 - 18 Jan 2022 -
Re: New repo proposal: repair
Em qua., 12 de jan. de 2022 às 15:46, Harald Panten Lopez <harald.panten@sygel.es> escreveu:I agree +1El mié, 12 ene 2022 a las 16:42, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:+1 for me tooEl mié., 12 ene. 2022 15:41, Raphaël Valyi <rvalyi@akretion.com> escribió:Great! +1On Wed, Jan 12, 2022 at 11:27 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:It makes sense.On Wed, Jan 12, 2022 at 3:12 PM Sergio Corato <sergiocorato@gmail.com> wrote:+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :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
_______________________________________________
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
--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
--Raphaël ValyiFounder and consultant_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Marcel Savegnago - 04:36 - 18 Jan 2022 -
Re: PSC Real Estate
Hi Simone,Seems ok in odoo-community.org but no sync with GitHub.I found also the repo has no id(for runbot etc...)Le mar. 11 janv. 2022 à 09:07, Simone Orsi <simahawk@gmail.com> a écrit :Sorry. Should be ok on next sync.On Tue, Jan 11, 2022 at 8:56 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi Simone,Wrong PSC ;-) I can stay in Rental but I don't have any input there :-)ThanksOn Mon, Jan 10, 2022 at 3:51 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Great! Thanks.On Mon, Jan 10, 2022 at 11:42 AM Simone Orsi <simahawk@gmail.com> wrote:Hello,Sorry, I was still on holidays :PYou've been added Denis :)Happy new year everyone!On Wed, Jan 5, 2022 at 4:16 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi all,I think this is not the interest of too much people, but it would be helpful to have write access to it to go forward as some core people approved this.ThanksLe dim. 21 nov. 2021 à 14:52, Roussel, Denis <denis.roussel@acsone.eu> a écrit :@Ignacio Yes, it could be great to push a PR.That can be a base for beginning.ThanksOn Mon, Nov 15, 2021 at 10:12 AM Ignacio Ibeas (Acysos S.L.) <ignacio@acysos.com> wrote:
Hello,
This is correct, but we not commit modules because there aren't compliant with the OCA requirements. The modules are in production but are to extense, i we don't make tests.
We can make a PR with all our work.
Greetings
El 15/11/21 a las 9:52, Stéphane Bidoul escribió:
The PSC Representative and only member is currently Ignacio Ibeas (https://odoo-community.org/psc-teams/real-estate-116).
Best regards,
-sbi
On Mon, Nov 15, 2021 at 9:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
+1
Le ven. 12 nov. 2021 à 15:57, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
@Pedro Manuel Baeza there is one there https://github.com/orgs/OCA/teams/vertical-real-state-maintainers
Le ven. 12 nov. 2021 à 15:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Not sure which is the PSC for that, but a valuable contributor like you is a sure +1
Regards.
_______________________________________________
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
--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Ignacio Ibeas
Acysos S.L. (www.acysos.com)
Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
Github (http://www.github.com/acysos)
Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
C/ Miguel Astrain 18, 1º Oficina A
31006 Pamplona, Navarra.
ignacio@acysos.com
Tel. 948238905
---------------------- // -------------------
La información contenida en este mensaje de correo electrónico es
confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
persona a la que va dirigido, cualquier divulgación, copia o distribución de
la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
tomada o dejada de tomar basada en la información contenida en este mensaje
queda prohibida y puede ser ilegal.
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone is
unauthorised. If you are not the intended recipient, any disclousure,
copying, distribuition or any action taken or omited to be taken in reliance
on it, is prohibited and may be unlawful.
_______________________________________________
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
--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
----_______________________________________________
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 Denis Roussel - 01:20 - 15 Jan 2022 -
Re: New repositories : cooperative and participative supermarket
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
_______________________________________________
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 - 06:31 - 14 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
