Archives
Contributors
-
Re: Manufacturing advice needed - materials of measured units being consumed partially
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 [1] > Post to: mailto:contributors@odoo-community.org [2] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [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 [8] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9] > > > > [1] https://odoo-community.org/groups/contributors-15 > [2] mailto:contributors@odoo-community.org > [3] https://odoo-community.org/groups?unsubscribe > [4] mailto:dreis@OpenSourceIntegrators.com > [5] https://www.magentointegrators.com/ > [6] https://www.hadoopintegrators.com/ > [7] https://www.usaodoo.com/ > [8] https://odoo-community.org/groups/contributors-15 > [9] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 10:55 - 26 Jan 2022 -
Re: Manufacturing advice needed - materials of measured units being
consumed partially
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
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 - 09:45 - 26 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: 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: 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 -
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 -
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: 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 -
Re: Proposing new PSC's
+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
by Joël Grand Guillaume - 01:06 - 20 Jan 2022 -
Re: Proposing new PSC's
+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
by Alex Comba. - 11:16 - 20 Jan 2022 -
Re: Proposing new PSC's
+1 yes!On Thu, Jan 20, 2022 at 3:06 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:OK for me. I know all of them and indeed are very active contributors.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inRegards,----------------------------------------------------------------------------------------------------------------------------Jay Vora Managing Director 
Direct: +91-9879354457 Office: +91-9033472982 Skype: jaynvora Twitter : jaynvora -------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
by Jay Vora - 11:01 - 20 Jan 2022
