Contributors

Re: Proposing Alexey Pelykh for currency PSC
Should this be revisited?
by Alexey Pelykh <alexey.pelykh@gmail.com> - 10:55 - 16 Sep 2019
1 replies 1 replies
Re: Proposing Alexey Pelykh for currency PSC

It should be correct now.

Regards.

by Pedro M. Baeza - 12:36 - 17 Sep 2019
OCA Board Member and Financial Auditor Campaign - APPLICATION DATE EXTENDED - 22ND SEPTEMBER

Dear OCA Contributors,

I hope the week is starting well for you all.

We currently only have a small number of applicants for the OCA Board Member campaign.

Due to this, the close date of the campaign has been extended - the final date to have submitted an application is 5pm (CEST) Sunday 22nd September, 2019.

Please see below to apply:

To apply for 2019 OCA Board Member, please fill in this form:
https://odoo-community.org/survey/start/2019-oca-board-members-candidates-30
You need to be a valid (paid) OCA Delegate to apply to be a Board Member.

To apply for 2019 OCA Financial Auditor, please fill in this form:
https://odoo-community.org/survey/start/2019-oca-financial-auditors-candidates-31
You do not need to be a member to apply to be an Auditor.

For more information on their responsibilities, please read the Bylaws:
https://odoo-community.org/page/Bylaws

The campaign will now be closed on Sunday 22nd September, 2019, with voting running from Monday 23rd - Sunday 29th, September 2019.

If you have any questions, please do not hesitate to reply on this list.

Warm regards
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association

by Rebecca Gellatly - 10:46 - 16 Sep 2019
OCA 2019 Financial Auditor Campaign - Still Open

Hello Contributors,

I just wanted to remind our Contributors that the Financial Auditor Campaign is still open. You do not need to be an OCA Member to apply.

You can apply via this link: https://odoo-community.org/survey/start/2019-oca-financial-auditors-candidates-31

If you have any questions please don't hesitate to get in touch on this list.

Warm regards,
Rebecca

--
Rebecca Gellatly
General Secretary
Odoo Community Association

by Rebecca Gellatly - 02:10 - 13 Sep 2019
Request for review: web_widget_dropdown_dynamic

Dear community,

I’d like to present https://github.com/OCA/web/pull/1371 that adds web_widget_dropdown_dynamic, a widget that supports resolving options from backend of:

* `fields.Char`
* `fields.Integer`
* `fields.Selection`

It’s useful when on-the-fly generation of m2m fields with dynamic options is an overkill, yet default static selection field is not applicable.

Kind regards,
Alexey

by Alexey Pelykh <alexey.pelykh@gmail.com> - 11:11 - 12 Sep 2019

Proposal of new Quality modules

Hi all,

I would like to have your opinion on the inclusion in a OCA repository of two modules relative to Quality Management System that we (PNLug - Odoo Group https://odoo.pnlug.it/) developed starting from a project for a customer.

First module proposed as "Management System - Extend"

It is an extension for management-system repository (https://github.com/OCA/management-system).

It adds:

- to Nonconformity: some fields often used in industrial company (e.g. department, workcenter, product), some aditional information like type and quantity managed;

- to Actions: a templating option and efficacy evaluation;

- to Partner: quality dedicated contact and Control Plan (see next module)

Second module proposed as "Quality Control - Plan"

It is an extension for manufacture/quality repository (https://github.com/OCA/manufacture).

It adds control Plan management to automatically calculate how many goods have to be checked for a defined incoming quantity, and the option to associate a Plan to Product, Product Category and Partner.

On an Inspection on incoming goods the quantity to be checked is automatically proposed; in case of scraps there is the possibility to associate (create) a new Nonconformity.

You can find the modules here: https://gitlab.com/PNLUG/Odoo/management-system-improvements/tree/11.0

Thanks in advance for your comments.

Stefano Consolaro

by Stefano Consolaro - 09:31 - 11 Sep 2019

2 replies 2 replies

Re: Proposal of new Quality modules

Hi Maxime,

unfortunately I will not be on OCA Days but I will create the issue soon.

Thanks

Stefano

Da: "Maxime Chambreuil" mchambreuil@opensourceintegrators.com

A: "Contributors" contributors@odoo-community.org

Cc:

Data: Fri, 20 Sep 2019 13:27:42 -0000

Oggetto: Re: Proposal of new Quality modules

Hello Stefano,

Can I ask to create an issue on the Github repo please?

If you'll be at the OCA Days in Belgium in 2 weeks, we can discuss about it there.

Cheers,

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT

O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Sep 11, 2019 at 2:32 AM <stefano.consolaro@mymage.it> wrote:

Hi all,
I would like to have your opinion on the inclusion in a OCA repository of two modules relative to Quality Management System that we (PNLug - Odoo Group https://odoo.pnlug.it/) developed starting from a project for a customer.

First module proposed as "Management System - Extend"
It is an extension for management-system repository (https://github.com/OCA/management-system).
It adds:
- to Nonconformity: some fields often used in industrial company (e.g. department, workcenter, product), some aditional information like type and quantity managed;
- to Actions: a templating option and efficacy evaluation;
- to Partner: quality dedicated contact and Control Plan (see next module)

Second module proposed as "Quality Control - Plan"
It is an extension for manufacture/quality repository (https://github.com/OCA/manufacture).
It adds control Plan management to automatically calculate how many goods have to be checked for a defined incoming quantity, and the option to associate a Plan to Product, Product Category and Partner.
On an Inspection on incoming goods the quantity to be checked is automatically proposed; in case of scraps there is the possibility to associate (create) a new Nonconformity.

You can find the modules here: https://gitlab.com/PNLUG/Odoo/management-system-improvements/tree/11.0

Thanks in advance for your comments.

Stefano Consolaro

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Stefano Consolaro

www.mymage.it

by Stefano Consolaro - 01:15 - 25 Sep 2019

Re: Proposal of new Quality modules

Hello Stefano,

Can I ask to create an issue on the Github repo please?

If you'll be at the OCA Days in Belgium in 2 weeks, we can discuss about it there.

Cheers,

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Sep 11, 2019 at 2:32 AM <stefano.consolaro@mymage.it> wrote:
Hi all,
I would like to have your opinion on the inclusion in a OCA repository of two modules relative to Quality Management System that we (PNLug - Odoo Group https://odoo.pnlug.it/) developed starting from a project for a customer.

First module proposed as "Management System - Extend"
It is an extension for management-system repository (https://github.com/OCA/management-system).
It adds:
- to Nonconformity: some fields often used in industrial company (e.g. department, workcenter, product), some aditional information like type and quantity managed;
- to Actions: a templating option and efficacy evaluation;
- to Partner: quality dedicated contact and Control Plan (see next module)

Second module proposed as "Quality Control - Plan"
It is an extension for manufacture/quality repository (https://github.com/OCA/manufacture).
It adds control Plan management to automatically calculate how many goods have to be checked for a defined incoming quantity, and the option to associate a Plan to Product, Product Category and Partner.
On an Inspection on incoming goods the quantity to be checked is automatically proposed; in case of scraps there is the possibility to associate (create) a new Nonconformity.

You can find the modules here: https://gitlab.com/PNLUG/Odoo/management-system-improvements/tree/11.0

Thanks in advance for your comments.

Stefano Consolaro

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Maxime Chambreuil - 03:26 - 20 Sep 2019

Odoo iCal synchronization Caldav

Dear colleagues,

I know it's a longstanding topic. But I do not understand that the need is not important.

Before OpenERP knew how to do caldav. Now it's a Google sync tool that is not wonderful at all.

Caldav is robust and can handle end-to-end.

I found a module of Open Tech S.L but I have trouble implementing it.

If anyone has a solution ! I am very interested.

Best regards,

Sébastien COURATIN
sebastien-couratin@semperco.fr

Semper Connect
68 Rue George Coubard
91 800 BOUSSY-SAINT-ANTOINE

01 85 48 06 55
télécharger mon application de prise en main à distance
Administration-informatique-événementiel
www.semper-connect.fr

Demeurez numériquement libre ...

Post-scriptum

Ce message est confidentiel. Sous réserve de tout accord conclu par écrit entre vous et Semper Connect. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n’êtes pas destinataire de ce message, merci d'en avertir immédiatement l’expéditeur.

by Sébastien COURATIN - 07:41 - 7 Sep 2019

1 attachments 1 attachments

logopt.png
1 replies 1 replies
Re: Odoo iCal synchronization Caldav

Theres this approach from Holger!

https://github.com/OCA/server-backend/pull/26

Mit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.com

Am 07.09.2019 um 19:42 schrieb Sébastien COURATIN <sebastien-couratin@semperco.fr>:

Dear colleagues,

I know it's a longstanding topic. But I do not understand that the need is not important.

Before OpenERP knew how to do caldav. Now it's a Google sync tool that is not wonderful at all.

Caldav is robust and can handle end-to-end.

I found a module of Open Tech S.L but I have trouble implementing it.

If anyone has a solution ! I am very interested.

Best regards,

Sébastien COURATIN
sebastien-couratin@semperco.fr

Semper Connect
68 Rue George Coubard
91 800 BOUSSY-SAINT-ANTOINE

01 85 48 06 55
télécharger mon application de prise en main à distance
Administration-informatique-événementiel
www.semper-connect.fr

Demeurez numériquement libre ...

Post-scriptum

Ce message est confidentiel. Sous réserve de tout accord conclu par écrit entre vous et Semper Connect. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n’êtes pas destinataire de ce message, merci d'en avertir immédiatement l’expéditeur.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Georg Notter - 07:55 - 7 Sep 2019
base_user_locale: configure locale settings

Dear community,

I’d like to request feedback and ideas regarding https://github.com/OCA/server-ux/pull/86 which is intended to override some locale settings on per-user basis without affecting locale settings in general.

Kind regards,
Alexey

by Alexey Pelykh <alexey.pelykh@gmail.com> - 01:51 - 5 Sep 2019

Service definition modules

Hello all,

In relation with the WMS modules Camptocamp is currently working on, I'm
working on a set of modules to manage service definition.

The idea is to be able to store a set of service levels agreed on with
the customer, with a number of parameters which are specified, and have
default values, but can be customized for a given customer, or a given
sale order.

Typically the parameters could be:

* management of backorders
* days of delivery
* hour of delivery
* invoicing per order (with order reference) or invoicing per delivey
* packaging details in the invoice
* product grouping preference (e.g. a customer could ask for an order of
10 product1, 10 product2, 10 product3 to be packages in 10 parcels
containing each 1 product1, 1 product2, 1 product3 instead of 3 packages
containing a singe product reference)
* constraints on the delivery truck (max dimension, max weight)...

The basic set of user stories is available in
https://github.com/OCA/stock-logistics-warehouse/issues/694 (this issue
will be moved to a better place once we've answerd the question below)

I'm planning to build this as a base module providing the models
required to define the service definitions, and set this on a customer
and on a sale order (+ propagation to invoices and deliveries), +
different smaller modules related to the different aspects (deliveries,
packaging, invoicing...)

I would like to propose these as alpha modules in the OCA but I'm unsure
what repository to target:

* option 1: new repository oca/sale-service-definition, all the addons
go there
* option 2: in repository oca/sale-workflow, at least for the base
module, but then I'm not comfortable in adding cross repository
dependencies, because some of the other modules would probably live in
the WMS repository, others in sale-workflow, others in some maybe in
stock-logistics-*
* option 3: in repository oca/contract because this is related to sale
contract, but I'd like to avoid polluting a self contained module with
lots of cross dependencies
* elsewhere ?

Dear contributors, what would be the best course of action in your opinion?


-- 
Alexandre Fayolle
Chef de Projet
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 - 10:46 - 4 Sep 2019

16 replies 16 replies

Re: Service definition modules

+1 for OCA/contract

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT

O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

On Thu, Sep 5, 2019 at 4:22 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:

+1 for me then for this option. Let's try to see if any synergies are possible.

On Thu, Sep 5, 2019 at 11:11 AM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:

I had originally given this a look and decided it was not cut for our
needs, but upon reflection, it does look like at least a nice place to
host the modules.

If noone objects I'll make the PRs there (and rename my models...)

Alexandre

On 05/09/2019 09:52, David Beal wrote:



> Hi Alexandre,



> 



> If I  understand the purpose, sale term condition, it's the exact scope of



> 



> https://github.com/OCA/contract/tree/12.0/agreement



> https://github.com/OCA/contract/tree/12.0/agreement_sale



> 



> also existing in v10 with agreement_sale and agreement_account



> 



> The objective here is just to have a minimal object, agnostic and



> versatile object



> agreement means : "commercial term conditions" exactly (with your



> customers and suppliers)



> 



> Maxime based its work about legal_agreement on top of it



> 



> Then I propose than you build your modules on top of these, adding your



> needs on this simple object



> https://github.com/OCA/contract/blob/12.0/agreement/models/agreement.py



> 



> EDI repo (and other dependencies) made by Alexis de Lattre use agreement.



> 



> If you build another base object, then customer who want to use both



> will have redondant data !



> If you want move agrement_sale to another repo, it's not a problem for me.



> 



> my 2 cts



> 



> Thanks



> 



> 



> David BEAL - akretion.com 



> Chef de projet



> Odoo Développement / Intégration



> 



> 



> Le jeu. 5 sept. 2019 à 01:12, Pedro M. Baeza (Tecnativa)



>  a écrit :



> 



>     Please don't use plurals in the module name for following



>     guidelines. Take also into account



>     https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule



>     that already allows to set delivery slots for partners, which is one



>     of the concepts you are defining. If everything is related to



>     delivery, I would put modules in OCA/delivery-carrier.



> 



>     Regards.



> 



>     _______________________________________________



>     Mailing-List: https://odoo-community.org/groups/contributors-15



>     Post to: mailto:contributors@odoo-community.org



>     <mailto:contributors@odoo-community.org>



>     Unsubscribe: https://odoo-community.org/groups?unsubscribe



> 



> _______________________________________________



> Mailing-List: https://odoo-community.org/groups/contributors-15



> Post to: mailto:contributors@odoo-community.org



> Unsubscribe: https://odoo-community.org/groups?unsubscribe



> 





-- 
Alexandre Fayolle
Chef de Projet
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

camptocamp

INNOVATIVE SOLUTIONS

BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume

Department Head

Business Solutions

+41 21 619 10 28

www.camptocamp.com

by Maxime Chambreuil - 03:00 - 5 Sep 2019

Re: Request for new repository sale-terms-conditions

Request Cancelled: oca/contract exists and is a suitable place.

On 05/09/2019 10:21, Alexandre Fayolle wrote:

> Hello Pedro,

> 

> Not everything is related to delivery. We have other aspects related to

> order preparation, order invoicing for instance.

> 

> Regarding the naming proposition, I was first thinking of the repository

> name (and should have used hyphens instead of underscores). However,

> "Term & Condition" does not exist in english. This expression is always

> using the plural form. In my opinion you should think of the final 's'

> as part of the spelling, as in "logistics". In any case, I would really

> like to avoid sale_term_multi_and_condition_multi ;-)

> 

> Can we create a new repository sale-terms-conditions?

> 

> Alexandre

> 

> On 05/09/2019 01:12, Pedro M. Baeza (Tecnativa) wrote:

>> Please don't use plurals in the module name for following guidelines.

>> Take also into account

>> https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule

>> that already allows to set delivery slots for partners, which is one of

>> the concepts you are defining. If everything is related to delivery, I

>> would put modules in OCA/delivery-carrier.

>>

>> Regards.

>>

>> _______________________________________________

>> Mailing-List: https://odoo-community.org/groups/contributors-15

>> Post to: mailto:contributors@odoo-community.org

>> Unsubscribe: https://odoo-community.org/groups?unsubscribe

>>

> 

> 



-- 
Alexandre Fayolle
Chef de Projet
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 - 11:36 - 5 Sep 2019

Re: Service definition modules

+1 for me then for this option. Let's try to see if any synergies are possible.

On Thu, Sep 5, 2019 at 11:11 AM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:

I had originally given this a look and decided it was not cut for our
needs, but upon reflection, it does look like at least a nice place to
host the modules.

If noone objects I'll make the PRs there (and rename my models...)

Alexandre

On 05/09/2019 09:52, David Beal wrote:


> Hi Alexandre,


> 


> If I  understand the purpose, sale term condition, it's the exact scope of


> 


> https://github.com/OCA/contract/tree/12.0/agreement


> https://github.com/OCA/contract/tree/12.0/agreement_sale


> 


> also existing in v10 with agreement_sale and agreement_account


> 


> The objective here is just to have a minimal object, agnostic and


> versatile object


> agreement means : "commercial term conditions" exactly (with your


> customers and suppliers)


> 


> Maxime based its work about legal_agreement on top of it


> 


> Then I propose than you build your modules on top of these, adding your


> needs on this simple object


> https://github.com/OCA/contract/blob/12.0/agreement/models/agreement.py


> 


> EDI repo (and other dependencies) made by Alexis de Lattre use agreement.


> 


> If you build another base object, then customer who want to use both


> will have redondant data !


> If you want move agrement_sale to another repo, it's not a problem for me.


> 


> my 2 cts


> 


> Thanks


> 


> 


> David BEAL - akretion.com 


> Chef de projet


> Odoo Développement / Intégration


> 


> 


> Le jeu. 5 sept. 2019 à 01:12, Pedro M. Baeza (Tecnativa)


>  a écrit :


> 


>     Please don't use plurals in the module name for following


>     guidelines. Take also into account


>     https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule


>     that already allows to set delivery slots for partners, which is one


>     of the concepts you are defining. If everything is related to


>     delivery, I would put modules in OCA/delivery-carrier.


> 


>     Regards.


> 


>     _______________________________________________


>     Mailing-List: https://odoo-community.org/groups/contributors-15


>     Post to: mailto:contributors@odoo-community.org


>     <mailto:contributors@odoo-community.org>


>     Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 




-- 
Alexandre Fayolle
Chef de Projet
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

camptocamp

INNOVATIVE SOLUTIONS

BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume

Department Head

Business Solutions

+41 21 619 10 28

www.camptocamp.com

by Joël Grand Guillaume - 11:20 - 5 Sep 2019

Re: Service definition modules

I had originally given this a look and decided it was not cut for our
needs, but upon reflection, it does look like at least a nice place to
host the modules.

If noone objects I'll make the PRs there (and rename my models...)

Alexandre

On 05/09/2019 09:52, David Beal wrote:

> Hi Alexandre,

> 

> If I  understand the purpose, sale term condition, it's the exact scope of

> 

> https://github.com/OCA/contract/tree/12.0/agreement

> https://github.com/OCA/contract/tree/12.0/agreement_sale

> 

> also existing in v10 with agreement_sale and agreement_account

> 

> The objective here is just to have a minimal object, agnostic and

> versatile object

> agreement means : "commercial term conditions" exactly (with your

> customers and suppliers)

> 

> Maxime based its work about legal_agreement on top of it

> 

> Then I propose than you build your modules on top of these, adding your

> needs on this simple object

> https://github.com/OCA/contract/blob/12.0/agreement/models/agreement.py

> 

> EDI repo (and other dependencies) made by Alexis de Lattre use agreement.

> 

> If you build another base object, then customer who want to use both

> will have redondant data !

> If you want move agrement_sale to another repo, it's not a problem for me.

> 

> my 2 cts

> 

> Thanks

> 

> 

> David BEAL - akretion.com 

> Chef de projet

> Odoo Développement / Intégration

> 

> 

> Le jeu. 5 sept. 2019 à 01:12, Pedro M. Baeza (Tecnativa)

>  a écrit :

> 

>     Please don't use plurals in the module name for following

>     guidelines. Take also into account

>     https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule

>     that already allows to set delivery slots for partners, which is one

>     of the concepts you are defining. If everything is related to

>     delivery, I would put modules in OCA/delivery-carrier.

> 

>     Regards.

> 

>     _______________________________________________

>     Mailing-List: https://odoo-community.org/groups/contributors-15

>     Post to: mailto:contributors@odoo-community.org

>     <mailto:contributors@odoo-community.org>

>     Unsubscribe: https://odoo-community.org/groups?unsubscribe

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe

> 



-- 
Alexandre Fayolle
Chef de Projet
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 - 11:10 - 5 Sep 2019

Re: Service definition modules

I'm with David. contract is the right repo, if not a new repo called sale_contract. Terms and conditions form part of the contract with the customer, so it is most appropriate name. Indeed they are often called contractual terms.

On Thu, Sep 5, 2019 at 7:52 PM David Beal <david.beal@akretion.com> wrote:
Hi Alexandre,

If I understand the purpose, sale term condition, it's the exact scope of

https://github.com/OCA/contract/tree/12.0/agreement
https://github.com/OCA/contract/tree/12.0/agreement_sale

also existing in v10 with agreement_sale and agreement_account

The objective here is just to have a minimal object, agnostic and versatile object
agreement means : "commercial term conditions" exactly (with your customers and suppliers)

Maxime based its work about legal_agreement on top of it

Then I propose than you build your modules on top of these, adding your needs on this simple object
https://github.com/OCA/contract/blob/12.0/agreement/models/agreement.py

EDI repo (and other dependencies) made by Alexis de Lattre use agreement.

If you build another base object, then customer who want to use both will have redondant data !
If you want move agrement_sale to another repo, it's not a problem for me.

my 2 cts

Thanks

David BEAL - akretion.com
Chef de projet
Odoo Développement / Intégration

Le jeu. 5 sept. 2019 à 01:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Please don't use plurals in the module name for following guidelines. Take also into account https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule that already allows to set delivery slots for partners, which is one of the concepts you are defining. If everything is related to delivery, I would put modules in OCA/delivery-carrier.

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

by Graeme Gellatly - 10:36 - 5 Sep 2019

New WMS repository

Dear contributors,

As you may have noticed, we're working on a WMS for Odoo to be published under the OCA [1].

I want to request here the creation of a new repository "stock-wms" to host this new apps. I suggest to host this new repo under the existing logistic PSC.

Reasons:

* Stock WMS will provide features and changes that will constitute a change compare to standard Odoo
* Providing good quality demo data and doc is easier on a dedicated repo
* Core WMS features only will be hosted there, all generic (re-usable) module will go in other stock-logistic-* repos (as for example for DDMRP example)

Do you agree ?

Regards,

Joël

[1]
Github issue: https://github.com/OCA/stock-logistics-warehouse/issues/621
Requirement doc:https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
www.camptocamp.com

by Joël Grand Guillaume - 09:31 - 4 Sep 2019
6 replies 6 replies
Re: New WMS repository

+1 for me

On Wed, Sep 4, 2019 at 12:01 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Hi Denis,

The WMS repo is meant to host a set of module that constitute the minimum viable product to make Odoo a WMS. The best comparison I have the th eDDMRP work. It uses a lot of modules hosted in other repo, but the DDMRP repo host the core which provide another way to deal with procurement (e.g. no more scheduler).

So far, I can say that this WMS apps will probably host everything related to zones, area and bin provided as alpha modules (https://github.com/OCA/stock-logistics-warehouse/issues/621). Also, it probably include everything related to the way we release operation in a WH. In sandard, Odoo compute the operation and the reservation at SO confirmation or when the scheduler run. In our case this will be something different. We need to split the reservation and the release of operation. In large WH, you want to "drive" your operation and therefor release them in a smart order (and with them the final reservation occurs).

I hope this is clear enough in a few lines. The discussion to put a module in WMS or not can be discussed, but let's state that if it can be used without this mechanism and zone, it land in existing one. If not, well it goes in WMS.

Is this more clear ?

Regards,

Joël

On Wed, Sep 4, 2019 at 11:37 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:
+1 for me.

The point for me is for future modules.

Which criteria to use to decide when putting them in 'wms' or not?

When you say << that will constitute a change compare to standard Odoo >>, in a way, all external modules will change standard behaviour. So, what do you have in mind saying that - can you explain/calrify ?

Best regards,

On Wed, Sep 4, 2019 at 9:32 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Dear contributors,

As you may have noticed, we're working on a WMS for Odoo to be published under the OCA [1].

I want to request here the creation of a new repository "stock-wms" to host this new apps. I suggest to host this new repo under the existing logistic PSC.

Reasons:

* Stock WMS will provide features and changes that will constitute a change compare to standard Odoo
* Providing good quality demo data and doc is easier on a dedicated repo
* Core WMS features only will be hosted there, all generic (re-usable) module will go in other stock-logistic-* repos (as for example for DDMRP example)

Do you agree ?

Regards,

Joël

[1]
Github issue: https://github.com/OCA/stock-logistics-warehouse/issues/621
Requirement doc:https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : +352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : +352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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 Laurent Mignon - 01:45 - 4 Sep 2019

Re: New WMS repository

Perfect !

Ok, let's go for this.

On Wed, Sep 4, 2019 at 12:01 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Hi Denis,

The WMS repo is meant to host a set of module that constitute the minimum viable product to make Odoo a WMS. The best comparison I have the th eDDMRP work. It uses a lot of modules hosted in other repo, but the DDMRP repo host the core which provide another way to deal with procurement (e.g. no more scheduler).

So far, I can say that this WMS apps will probably host everything related to zones, area and bin provided as alpha modules (https://github.com/OCA/stock-logistics-warehouse/issues/621). Also, it probably include everything related to the way we release operation in a WH. In sandard, Odoo compute the operation and the reservation at SO confirmation or when the scheduler run. In our case this will be something different. We need to split the reservation and the release of operation. In large WH, you want to "drive" your operation and therefor release them in a smart order (and with them the final reservation occurs).

I hope this is clear enough in a few lines. The discussion to put a module in WMS or not can be discussed, but let's state that if it can be used without this mechanism and zone, it land in existing one. If not, well it goes in WMS.

Is this more clear ?

Regards,

Joël

On Wed, Sep 4, 2019 at 11:37 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:
+1 for me.

The point for me is for future modules.

Which criteria to use to decide when putting them in 'wms' or not?

When you say << that will constitute a change compare to standard Odoo >>, in a way, all external modules will change standard behaviour. So, what do you have in mind saying that - can you explain/calrify ?

Best regards,

On Wed, Sep 4, 2019 at 9:32 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Dear contributors,

As you may have noticed, we're working on a WMS for Odoo to be published under the OCA [1].

I want to request here the creation of a new repository "stock-wms" to host this new apps. I suggest to host this new repo under the existing logistic PSC.

Reasons:

* Stock WMS will provide features and changes that will constitute a change compare to standard Odoo
* Providing good quality demo data and doc is easier on a dedicated repo
* Core WMS features only will be hosted there, all generic (re-usable) module will go in other stock-logistic-* repos (as for example for DDMRP example)

Do you agree ?

Regards,

Joël

[1]
Github issue: https://github.com/OCA/stock-logistics-warehouse/issues/621
Requirement doc:https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : +352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : +352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : +352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : +352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

by Denis Roussel - 12:11 - 4 Sep 2019

Re: New WMS repository

Hi Denis,

The WMS repo is meant to host a set of module that constitute the minimum viable product to make Odoo a WMS. The best comparison I have the th eDDMRP work. It uses a lot of modules hosted in other repo, but the DDMRP repo host the core which provide another way to deal with procurement (e.g. no more scheduler).

So far, I can say that this WMS apps will probably host everything related to zones, area and bin provided as alpha modules (https://github.com/OCA/stock-logistics-warehouse/issues/621). Also, it probably include everything related to the way we release operation in a WH. In sandard, Odoo compute the operation and the reservation at SO confirmation or when the scheduler run. In our case this will be something different. We need to split the reservation and the release of operation. In large WH, you want to "drive" your operation and therefor release them in a smart order (and with them the final reservation occurs).

I hope this is clear enough in a few lines. The discussion to put a module in WMS or not can be discussed, but let's state that if it can be used without this mechanism and zone, it land in existing one. If not, well it goes in WMS.

Is this more clear ?

Regards,

Joël

On Wed, Sep 4, 2019 at 11:37 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:
+1 for me.

The point for me is for future modules.

Which criteria to use to decide when putting them in 'wms' or not?

When you say << that will constitute a change compare to standard Odoo >>, in a way, all external modules will change standard behaviour. So, what do you have in mind saying that - can you explain/calrify ?

Best regards,

On Wed, Sep 4, 2019 at 9:32 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Dear contributors,

As you may have noticed, we're working on a WMS for Odoo to be published under the OCA [1].

I want to request here the creation of a new repository "stock-wms" to host this new apps. I suggest to host this new repo under the existing logistic PSC.

Reasons:

* Stock WMS will provide features and changes that will constitute a change compare to standard Odoo
* Providing good quality demo data and doc is easier on a dedicated repo
* Core WMS features only will be hosted there, all generic (re-usable) module will go in other stock-logistic-* repos (as for example for DDMRP example)

Do you agree ?

Regards,

Joël

[1]
Github issue: https://github.com/OCA/stock-logistics-warehouse/issues/621
Requirement doc:https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : +352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : +352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
www.camptocamp.com

by Joël Grand Guillaume - 12:01 - 4 Sep 2019

Re: New WMS repository

+1 for me.

The point for me is for future modules.

Which criteria to use to decide when putting them in 'wms' or not?

When you say << that will constitute a change compare to standard Odoo >>, in a way, all external modules will change standard behaviour. So, what do you have in mind saying that - can you explain/calrify ?

Best regards,

On Wed, Sep 4, 2019 at 9:32 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Dear contributors,

As you may have noticed, we're working on a WMS for Odoo to be published under the OCA [1].

I want to request here the creation of a new repository "stock-wms" to host this new apps. I suggest to host this new repo under the existing logistic PSC.

Reasons:

* Stock WMS will provide features and changes that will constitute a change compare to standard Odoo
* Providing good quality demo data and doc is easier on a dedicated repo
* Core WMS features only will be hosted there, all generic (re-usable) module will go in other stock-logistic-* repos (as for example for DDMRP example)

Do you agree ?

Regards,

Joël

[1]
Github issue: https://github.com/OCA/stock-logistics-warehouse/issues/621
Requirement doc:https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : +352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : +352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

by Denis Roussel - 11:35 - 4 Sep 2019

Re: New WMS repository

Dear Alexey,

I'm also ok with just "wms", to be honest, I was hesitating between the two names ;)

On Wed, Sep 4, 2019 at 9:42 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear Joël,

If stock-wms is for core WMS modules, shall it be called just “wms”?

Kind regards,
Alexey

On Sep 4, 2019, at 09:32, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:

Dear contributors,

As you may have noticed, we're working on a WMS for Odoo to be published under the OCA [1].

I want to request here the creation of a new repository "stock-wms" to host this new apps. I suggest to host this new repo under the existing logistic PSC.

Reasons:

* Stock WMS will provide features and changes that will constitute a change compare to standard Odoo
* Providing good quality demo data and doc is easier on a dedicated repo
* Core WMS features only will be hosted there, all generic (re-usable) module will go in other stock-logistic-* repos (as for example for DDMRP example)

Do you agree ?

Regards,

Joël

[1]
Github issue: https://github.com/OCA/stock-logistics-warehouse/issues/621
Requirement doc:https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
www.camptocamp.com

by Joël Grand Guillaume - 11:20 - 4 Sep 2019
Request for l10n-ukraine
Dear all, I’d like to request creation of l10n-ukraine repository and corresponding PSC. Kind regards, Alexey
by Alexey Pelykh <alexey.pelykh@gmail.com> - 03:06 - 3 Sep 2019
4 replies 4 replies
Re: Request for l10n-ukraine

Done, should be good now

On Sep 3, 2019, at 16:37, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

The repo has been created.

You can initialize it from the template files: https://github.com/OCA/maintainer-quality-tools/tree/master/sample_files

I still need to do some configuration (travis, etc). I'll do that later today.

-sbi

On Tue, Sep 3, 2019 at 3:46 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Hi Stéphane,

Unless there are better candidates, I’m in :)

Kind regards,
Alexey

On Sep 3, 2019, at 15:36, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hello Alexey,

i'll take care of this. I assume you will be the PSC representative?

Best regards,

-sbi

On Tue, Sep 3, 2019 at 3:07 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear all, I’d like to request creation of l10n-ukraine repository and corresponding PSC. Kind regards, Alexey

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Alexey Pelykh <alexey.pelykh@gmail.com> - 05:16 - 3 Sep 2019

Re: Request for l10n-ukraine

The repo has been created.

You can initialize it from the template files: https://github.com/OCA/maintainer-quality-tools/tree/master/sample_files

I still need to do some configuration (travis, etc). I'll do that later today.

-sbi

On Tue, Sep 3, 2019 at 3:46 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Hi Stéphane,

Unless there are better candidates, I’m in :)

Kind regards,
Alexey

On Sep 3, 2019, at 15:36, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hello Alexey,

i'll take care of this. I assume you will be the PSC representative?

Best regards,

-sbi

On Tue, Sep 3, 2019 at 3:07 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear all, I’d like to request creation of l10n-ukraine repository and corresponding PSC. Kind regards, Alexey

_______________________________________________
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 Stéphane Bidoul - 04:36 - 3 Sep 2019

Re: Request for l10n-ukraine

Hi Stéphane,

Unless there are better candidates, I’m in :)

Kind regards,
Alexey

On Sep 3, 2019, at 15:36, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hello Alexey,

i'll take care of this. I assume you will be the PSC representative?

Best regards,

-sbi

On Tue, Sep 3, 2019 at 3:07 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear all, I’d like to request creation of l10n-ukraine repository and corresponding PSC. Kind regards, Alexey

_______________________________________________
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 Alexey Pelykh <alexey.pelykh@gmail.com> - 03:45 - 3 Sep 2019

Re: Request for l10n-ukraine

Hello Alexey,

i'll take care of this. I assume you will be the PSC representative?

Best regards,

-sbi

On Tue, Sep 3, 2019 at 3:07 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear all, I’d like to request creation of l10n-ukraine repository and corresponding PSC. Kind regards, Alexey

_______________________________________________
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 - 03:35 - 3 Sep 2019

2019 OCA Financial Auditors Campaign - NOW OPEN

Dear OCA Contributors,

The 2019 Delegates Campaign has now closed with 3 new Delegates being appointed:

Yves Goldberg
Simone Orsi
Sergio Teruel

We welcome the new Delegates onboard.

The campaign to become an OCA Board Member or OCA Financial Auditor is NOW OPEN.

Only valid (paid) Delegates are eligible to apply for the Board Member positions - the link for these applications has been sent to the Delegates mailing list.

To apply for 2019 OCA Financial Auditor, please fill in this form:

https://odoo-community.org/survey/start/2019-oca-financial-auditors-candidates-31
You do NOT need to have a valid membership to apply.

For more information on their responsibilities, please read the Bylaws:

https://odoo-community.org/page/Bylaws

The campaign will be closed on September 15th, 2019 with the election following.

If you have any questions, please do not hesitate to reply on this list.

Warm regards,

Rebecca

Rebecca Gellatly

General Secretary

Odoo Community Association

by Rebecca Gellatly - 01:50 - 3 Sep 2019

7 replies 7 replies

new PSC dedicated to Brand management

Dear contributors,

We currently have some modules in OCA that are dedicated to brand management spread a few different repositories: product_brand, partner_brand, account_brand, sale_brand.

There are currently two broad brand mechanisms/use cases:
- companies that sell under different brands and want to influence their document layouts, manage
credit control by brand, etc
- classifying products by brand (module product_brand)

Following a conversation in the partner-contact repo, we came to the conclusion a new repository and PSC is appropriate, since this is a transversal concept.

Unless there are objections i'll proceed with the creation of the brand PSC and repo.

As PSC members, I propose Maxime Chambreuil and Souheil Bejaoui who have been and/or will be active in this area in the past/coming months at least. If there are other candidates or suggestion about members, please speak up :)

Since most modules are relatively new the current plan is to move them, as well as related issues and PRs to the new brand repo for the 12.0 branch.

Best regards,

-sbi

--
Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

by Stéphane Bidoul - 11:10 - 2 Sep 2019
6 replies 6 replies
Re: new PSC dedicated to Brand management

The brand project and PSC have been created.

Souheil Bejaoui will proceed with moving the existing modules to the new repo (12.0 branch only).

Best regards,

-sbi

On Tue, Sep 3, 2019 at 3:17 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
+1

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Tue, Sep 3, 2019 at 8:01 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
+1

On Mon, Sep 2, 2019 at 3:06 PM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:
+1

On Mon, Sep 2, 2019 at 12:26 PM Simone Orsi <simahawk@gmail.com> wrote:
+1
Looks good, indeed, thanks!

On Mon, Sep 2, 2019 at 11:52 AM Pedro Manuel Baeza Romero <pedro.baeza@gmail.com> wrote:
+1

Thanks for bringing this to the table.

El lun., 2 sept. 2019 11:12, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:
Dear contributors,

We currently have some modules in OCA that are dedicated to brand management spread a few different repositories: product_brand, partner_brand, account_brand, sale_brand.

There are currently two broad brand mechanisms/use cases:
- companies that sell under different brands and want to influence their document layouts, manage
credit control by brand, etc
- classifying products by brand (module product_brand)

Following a conversation in the partner-contact repo, we came to the conclusion a new repository and PSC is appropriate, since this is a transversal concept.

Unless there are objections i'll proceed with the creation of the brand PSC and repo.

As PSC members, I propose Maxime Chambreuil and Souheil Bejaoui who have been and/or will be active in this area in the past/coming months at least. If there are other candidates or suggestion about members, please speak up :)

Since most modules are relatively new the current plan is to move them, as well as related issues and PRs to the new brand repo for the 12.0 branch.

Best regards,

-sbi

--
Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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

_______________________________________________
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 - 04:36 - 3 Sep 2019

Re: new PSC dedicated to Brand management

+1

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Tue, Sep 3, 2019 at 8:01 AM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
+1

On Mon, Sep 2, 2019 at 3:06 PM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:
+1

On Mon, Sep 2, 2019 at 12:26 PM Simone Orsi <simahawk@gmail.com> wrote:
+1
Looks good, indeed, thanks!

On Mon, Sep 2, 2019 at 11:52 AM Pedro Manuel Baeza Romero <pedro.baeza@gmail.com> wrote:
+1

Thanks for bringing this to the table.

El lun., 2 sept. 2019 11:12, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:
Dear contributors,

We currently have some modules in OCA that are dedicated to brand management spread a few different repositories: product_brand, partner_brand, account_brand, sale_brand.

There are currently two broad brand mechanisms/use cases:
- companies that sell under different brands and want to influence their document layouts, manage
credit control by brand, etc
- classifying products by brand (module product_brand)

Following a conversation in the partner-contact repo, we came to the conclusion a new repository and PSC is appropriate, since this is a transversal concept.

Unless there are objections i'll proceed with the creation of the brand PSC and repo.

As PSC members, I propose Maxime Chambreuil and Souheil Bejaoui who have been and/or will be active in this area in the past/coming months at least. If there are other candidates or suggestion about members, please speak up :)

Since most modules are relatively new the current plan is to move them, as well as related issues and PRs to the new brand repo for the 12.0 branch.

Best regards,

-sbi

--
Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
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 Maxime Chambreuil - 03:16 - 3 Sep 2019

Re: new PSC dedicated to Brand management

+1

On Mon, Sep 2, 2019 at 3:06 PM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:
+1

On Mon, Sep 2, 2019 at 12:26 PM Simone Orsi <simahawk@gmail.com> wrote:
+1
Looks good, indeed, thanks!

On Mon, Sep 2, 2019 at 11:52 AM Pedro Manuel Baeza Romero <pedro.baeza@gmail.com> wrote:
+1

Thanks for bringing this to the table.

El lun., 2 sept. 2019 11:12, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:
Dear contributors,

We currently have some modules in OCA that are dedicated to brand management spread a few different repositories: product_brand, partner_brand, account_brand, sale_brand.

There are currently two broad brand mechanisms/use cases:
- companies that sell under different brands and want to influence their document layouts, manage
credit control by brand, etc
- classifying products by brand (module product_brand)

Following a conversation in the partner-contact repo, we came to the conclusion a new repository and PSC is appropriate, since this is a transversal concept.

Unless there are objections i'll proceed with the creation of the brand PSC and repo.

As PSC members, I propose Maxime Chambreuil and Souheil Bejaoui who have been and/or will be active in this area in the past/coming months at least. If there are other candidates or suggestion about members, please speak up :)

Since most modules are relatively new the current plan is to move them, as well as related issues and PRs to the new brand repo for the 12.0 branch.

Best regards,

-sbi

--
Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28
www.camptocamp.com

by Joël Grand Guillaume - 03:00 - 3 Sep 2019

Re: new PSC dedicated to Brand management

+1

On Mon, Sep 2, 2019 at 12:26 PM Simone Orsi <simahawk@gmail.com> wrote:
+1
Looks good, indeed, thanks!

On Mon, Sep 2, 2019 at 11:52 AM Pedro Manuel Baeza Romero <pedro.baeza@gmail.com> wrote:
+1

Thanks for bringing this to the table.

El lun., 2 sept. 2019 11:12, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:
Dear contributors,

We currently have some modules in OCA that are dedicated to brand management spread a few different repositories: product_brand, partner_brand, account_brand, sale_brand.

There are currently two broad brand mechanisms/use cases:
- companies that sell under different brands and want to influence their document layouts, manage
credit control by brand, etc
- classifying products by brand (module product_brand)

Following a conversation in the partner-contact repo, we came to the conclusion a new repository and PSC is appropriate, since this is a transversal concept.

Unless there are objections i'll proceed with the creation of the brand PSC and repo.

As PSC members, I propose Maxime Chambreuil and Souheil Bejaoui who have been and/or will be active in this area in the past/coming months at least. If there are other candidates or suggestion about members, please speak up :)

Since most modules are relatively new the current plan is to move them, as well as related issues and PRs to the new brand repo for the 12.0 branch.

Best regards,

-sbi

--
Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

_______________________________________________
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 Laurent Mignon - 03:05 - 2 Sep 2019

Re: new PSC dedicated to Brand management

+1
Looks good, indeed, thanks!

On Mon, Sep 2, 2019 at 11:52 AM Pedro Manuel Baeza Romero <pedro.baeza@gmail.com> wrote:
+1

Thanks for bringing this to the table.

El lun., 2 sept. 2019 11:12, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:
Dear contributors,

We currently have some modules in OCA that are dedicated to brand management spread a few different repositories: product_brand, partner_brand, account_brand, sale_brand.

There are currently two broad brand mechanisms/use cases:
- companies that sell under different brands and want to influence their document layouts, manage
credit control by brand, etc
- classifying products by brand (module product_brand)

Following a conversation in the partner-contact repo, we came to the conclusion a new repository and PSC is appropriate, since this is a transversal concept.

Unless there are objections i'll proceed with the creation of the brand PSC and repo.

As PSC members, I propose Maxime Chambreuil and Souheil Bejaoui who have been and/or will be active in this area in the past/coming months at least. If there are other candidates or suggestion about members, please speak up :)

Since most modules are relatively new the current plan is to move them, as well as related issues and PRs to the new brand repo for the 12.0 branch.

Best regards,

-sbi

--
Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

_______________________________________________
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 Simone Orsi - 12:25 - 2 Sep 2019
Call for reviewers: account_bank_statement_import_online

Dear all,

There’s a base module that would allow building online importers of statements from bank accounts. Base does not contain any implementation, as there’s no good enough candidate, but I plan to finish integration of TransferWise support, Holvi, LHV Bank (Estonia) and probably will consider PayPal. Yet base remains important milestone to be merged.

https://github.com/OCA/bank-statement-import/pull/212

Kind regards,
Alexey

by Alexey Pelykh <alexey.pelykh@gmail.com> - 09:55 - 1 Sep 2019
Issue with allowed_user_ids ?
Dear community,

Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570
It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:
Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"

I’ve tried:
<field name="allowed_user_ids" invisible="1"/>
adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?

Alexey
by Alexey Pelykh <alexey.pelykh@gmail.com> - 04:10 - 30 Aug 2019
2 replies 2 replies
Re: Issue with allowed_user_ids ?

With the help from community, it was found. It’s from project_hr module, it alters declaration on user_id field. And Pedro Baeza needs to take a look at that part of project_hr module as it’s his. I think that part should be changed a bit to introduce constraint on user_id field and alter domain in XML, not in code.

On Aug 31, 2019, at 14:57, Lorenzo Battistini <elbaddy@gmail.com> wrote:

Do you know where allowed_user_ids is defined and used?

On Fri, 30 Aug 2019 at 16:11, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,

Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570
It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:
Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"

I’ve tried:
<field name="allowed_user_ids" invisible="1"/>
adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?

Alexey

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--
Lorenzo Battistini
https://github.com/eLBati
Take control of your business

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Alexey Pelykh <alexey.pelykh@gmail.com> - 03:16 - 31 Aug 2019

Re: Issue with allowed_user_ids ?

Do you know where allowed_user_ids is defined and used?

On Fri, 30 Aug 2019 at 16:11, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,

Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570
It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:
Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"

I’ve tried:
<field name="allowed_user_ids" invisible="1"/>
adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?

Alexey

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--
Lorenzo Battistini
https://github.com/eLBati
Take control of your business

by Lorenzo Battistini. - 02:56 - 31 Aug 2019
Payment gateway

Dear all ,
Hope you are well
I was wondering if someone use any payment gateway integration before with odoo in website or with sandbox direct !
Can anyone help with this?
Thank you.

by Esla Amer - 10:55 - 28 Aug 2019