Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: Call for a new repository sale-promotion
    +1
    Sergio Corato


    Il giorno mer 6 nov 2019 alle ore 16:37 Alex Comba <alex.comba@agilebg.com> ha scritto:


    On Wed, Nov 6, 2019 at 3:07 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

    In order to group some modules related to sale promotion rules (and decreasing sale-workflow repo), we would like to create a new repository called sale-promotion.

    +1 

    --

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

    by Sergio Corato - 04:45 - 6 Nov 2019
  • Re: Call for a new repository sale-promotion


    On Wed, Nov 6, 2019 at 3:07 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

    In order to group some modules related to sale promotion rules (and decreasing sale-workflow repo), we would like to create a new repository called sale-promotion.

    +1 

    --
    by Alex Comba. - 04:36 - 6 Nov 2019
  • Re: Call for a new repository sale-promotion
    +1

    --
    Yves Goldberg - איב גולדברג
    odoo| Official Partner - OCA delegate
    Open Source ERP, CRM & CMS

    T +972 (3) 720 8818
    M +972 (55) 966 1405
    T +32 (2) 588 2500


    LinkedIn  Skype  Github  Quora 
    --


    ----- Original message -----
    From: "Roussel, Denis" <denis.roussel@acsone.eu>
    To: Contributors <contributors@odoo-community.org>
    Subject: Call for a new repository sale-promotion
    Date: Wednesday, November 06, 2019 16:07

    Hi,


    In order to group some modules related to sale promotion rules (and decreasing sale-workflow repo), we would like to create a new repository called sale-promotion.

    You can find the discussion about it:


    Actual modules :


    Many thanks for your feedback !

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

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

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

    by Yves Goldberg - 04:10 - 6 Nov 2019
  • Re: Call for a new repository sale-promotion
    👍 Good idea!

    On Wed, Nov 6, 2019 at 3:07 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
    Hi,


    In order to group some modules related to sale promotion rules (and decreasing sale-workflow repo), we would like to create a new repository called sale-promotion.

    You can find the discussion about it:


    Actual modules :


    Many thanks for your feedback !

    --
    __________________________________________
    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

    by Laurent Mignon - 03:21 - 6 Nov 2019
  • Call for a new repository sale-promotion
    Hi,


    In order to group some modules related to sale promotion rules (and decreasing sale-workflow repo), we would like to create a new repository called sale-promotion.

    You can find the discussion about it:


    Actual modules :


    Many thanks for your feedback !

    --
    __________________________________________
    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 - 03:06 - 6 Nov 2019
  • Re: Problem to filter a tree inside a form [management system]
    Hi,
    Just a fast answer, i didn't look to codes and i didnt ger your idea.

    Vut make in mind you can relate a Many2one() to a On2many() ( db logique only one foreign key will be stored in the many2one table )

    Dont focus too much in the "domain" first until you sortout how the DB logique you would like to change to.

    If you would like to change the data to many two one you can use m2m in both tables and reverse column1 and column2 in table1 and table2. Once you get the data well prganised in db then think about the domains.
    Ps :m2m creates a new table with 2 foreign keys. M2o is only a logical widget for Odoo and m2o is a foreign key.

    Wish it will help you, and sorry if by my missunderstanding i shared with you some basic things.

    Good luck,

    On Fri, Nov 1, 2019, 23:46 Stefano Consolaro <stefano.consolaro@mymage.it> wrote:

    Hi,

    I'm trying to change the behavior of a form (Nonconformity in Management System) replacing a m2o with a m2m field, as a review of the issue #263 (https://github.com/OCA/management-system/issues/263).

    The field is the relation with immediate Actions immediate_action_id used in the Description tab.

     

    Original:

    immediate_action_id = fields.Many2one(

            'mgmtsystem.action',

            'Immediate action',

            domain="[('nonconformity_ids', '=', id)]",

        )

     

    I did this:

    immediate_action_ids = fields.Many2many(

            'mgmtsystem.action',

            'mgmtsystem_nonconformity_action_rel',

            'nonconformity_id',

            'action_id',

            'Immediate Actions',

            domain="[('nonconformity_ids', '=', id)]",

        )

     

    Then in the view I replaced this:

    <field name="immediate_action_id" domain="[('type_action','=','immediate')]"

                               attrs="{'readonly':[('state','not in',['draft', 'analysis'])]}"/>

    with this:

    <field name="immediate_action_ids" domain="[('type_action', '=', 'immediate')]"

                              attrs="{'readonly':[('state','not in',['draft', 'analysis'])]}"/>

     

    Replacing the field in the form view permit to view all the Actions associated with the Nonconformity, but I want to display only immediate Actions.

    I googled a lot but nothing I tryied allow me to show only Actions with type_action attribute set to 'immediate'.

     

    Did I something wrong?

    Some suggestion?

     

    Thanks in advance.

     

    Stefano

     

    PS: I hope this is the right list to post similar question.



    Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus .


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

    by Youness Maafi - 01:26 - 2 Nov 2019
  • Problem to filter a tree inside a form [management system]

    Hi,

    I'm trying to change the behavior of a form (Nonconformity in Management System) replacing a m2o with a m2m field, as a review of the issue #263 (https://github.com/OCA/management-system/issues/263).

    The field is the relation with immediate Actions immediate_action_id used in the Description tab.

     

    Original:

    immediate_action_id = fields.Many2one(

            'mgmtsystem.action',

            'Immediate action',

            domain="[('nonconformity_ids', '=', id)]",

        )

     

    I did this:

    immediate_action_ids = fields.Many2many(

            'mgmtsystem.action',

            'mgmtsystem_nonconformity_action_rel',

            'nonconformity_id',

            'action_id',

            'Immediate Actions',

            domain="[('nonconformity_ids', '=', id)]",

        )

     

    Then in the view I replaced this:

    <field name="immediate_action_id" domain="[('type_action','=','immediate')]"

                               attrs="{'readonly':[('state','not in',['draft', 'analysis'])]}"/>

    with this:

    <field name="immediate_action_ids" domain="[('type_action', '=', 'immediate')]"

                              attrs="{'readonly':[('state','not in',['draft', 'analysis'])]}"/>

     

    Replacing the field in the form view permit to view all the Actions associated with the Nonconformity, but I want to display only immediate Actions.

    I googled a lot but nothing I tryied allow me to show only Actions with type_action attribute set to 'immediate'.

     

    Did I something wrong?

    Some suggestion?

     

    Thanks in advance.

     

    Stefano

     

    PS: I hope this is the right list to post similar question.



    Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus .


    by Stefano Consolaro - 11:45 - 1 Nov 2019
  • Re: Place to share knowledge/tools on deployment
    True, Russell has put together some compelling user stories. I plan to process them somehow to that end.

    El jue., 31 oct. 2019, 7:47 a.m., Jordi Riera <jordi.riera@numigi.com> escribió:
    Great,
    And we can create traffic to the ODEPs through the awesome-list.
    We need to find the good catch phrases to inspire people to contribute on doc.

    Thank you David,
    Jordi

    Le jeu. 31 oct. 2019 à 00:27, David Arnold <dar@xoe.solutions> a écrit :
    Ok. I like, lots of communities do those awesome-x listing ;-)

    A good mix catering to different levels of abstraction should gain enough traction over time, you're right, we need to create practical value, too.

    But I think, especially for the more involved people to let loose of their deer siloes, the foundation's need to be talked true with time and effort (hence ODEPs).

    Only through excellent community governance will we have a chance to eventually agree.

    This week, I intent to create that awesome-deployment-odoo-repo.

    BR,

    David A.

    El mié., 30 oct. 2019, 3:12 p.m., Jordi Riera <jordi.riera@numigi.com> escribió:
    Hello everyone,

    sorry for my silence in the previous days. Busy days as we all know.
    I think we should start small to grow slowly but surely.
    I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.
    In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.
    I see that you have already a good list with:
    * doodba
    * odoo cloud platform
    ...

    What do you think?
    OdooOps seems a good place to start. Could you create a new repo for the listing?

    Cheers,
    Jordi


    Le mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :
    Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!

    From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.

    Namely, to my knowledge, those are:
    - Tecnativa (doodba)
    - Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)
    - Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)
    - Akretion (docky and other tooling)
    - XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)

    Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?

    El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:
    Great stuff David!

    Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?

    I will have a read and make some comments in a bit :)

    Russ

    On Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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

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



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

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

    by dar - 03:35 - 31 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    Great,
    And we can create traffic to the ODEPs through the awesome-list.
    We need to find the good catch phrases to inspire people to contribute on doc.

    Thank you David,
    Jordi

    Le jeu. 31 oct. 2019 à 00:27, David Arnold <dar@xoe.solutions> a écrit :
    Ok. I like, lots of communities do those awesome-x listing ;-)

    A good mix catering to different levels of abstraction should gain enough traction over time, you're right, we need to create practical value, too.

    But I think, especially for the more involved people to let loose of their deer siloes, the foundation's need to be talked true with time and effort (hence ODEPs).

    Only through excellent community governance will we have a chance to eventually agree.

    This week, I intent to create that awesome-deployment-odoo-repo.

    BR,

    David A.

    El mié., 30 oct. 2019, 3:12 p.m., Jordi Riera <jordi.riera@numigi.com> escribió:
    Hello everyone,

    sorry for my silence in the previous days. Busy days as we all know.
    I think we should start small to grow slowly but surely.
    I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.
    In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.
    I see that you have already a good list with:
    * doodba
    * odoo cloud platform
    ...

    What do you think?
    OdooOps seems a good place to start. Could you create a new repo for the listing?

    Cheers,
    Jordi


    Le mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :
    Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!

    From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.

    Namely, to my knowledge, those are:
    - Tecnativa (doodba)
    - Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)
    - Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)
    - Akretion (docky and other tooling)
    - XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)

    Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?

    El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:
    Great stuff David!

    Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?

    I will have a read and make some comments in a bit :)

    Russ

    On Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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

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



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    by Jordi Riera - 01:46 - 31 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    Ok. I like, lots of communities do those awesome-x listing ;-)

    A good mix catering to different levels of abstraction should gain enough traction over time, you're right, we need to create practical value, too.

    But I think, especially for the more involved people to let loose of their deer siloes, the foundation's need to be talked true with time and effort (hence ODEPs).

    Only through excellent community governance will we have a chance to eventually agree.

    This week, I intent to create that awesome-deployment-odoo-repo.

    BR,

    David A.

    El mié., 30 oct. 2019, 3:12 p.m., Jordi Riera <jordi.riera@numigi.com> escribió:
    Hello everyone,

    sorry for my silence in the previous days. Busy days as we all know.
    I think we should start small to grow slowly but surely.
    I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.
    In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.
    I see that you have already a good list with:
    * doodba
    * odoo cloud platform
    ...

    What do you think?
    OdooOps seems a good place to start. Could you create a new repo for the listing?

    Cheers,
    Jordi


    Le mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :
    Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!

    From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.

    Namely, to my knowledge, those are:
    - Tecnativa (doodba)
    - Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)
    - Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)
    - Akretion (docky and other tooling)
    - XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)

    Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?

    El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:
    Great stuff David!

    Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?

    I will have a read and make some comments in a bit :)

    Russ

    On Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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

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



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

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

    by dar - 05:26 - 31 Oct 2019
  • New OCA Delegates and Board Member and Financial Auditors Campaign RE-OPENED
    Dear OCA Contributors,

    I wanted to share with you the new Delegates from the extra election we have just run:
    • Wolfgang Taferner
    • Bruno Joliveau
    • Virginie Dewulf
    • Lois Rilo Antelo
    • Gonzalo Ruzafa
    • Jordi Riera
    • Luis Felipe Mileo
    Thank you to all the Members that applied. It was great to see so much motivation, we had 18 applications in total. It would be awesome to see this enthusiasm kept up for next year when the process starts again to keep an active and engaged community.

    As a Contributor If you aren't already a Member and would like to become one you can purchase your membership online here.

    To let you know we have also reopened the Board Member and Financial Auditor Campaigns.

    Only Delegates can apply to become Board Members (this includes our new Delegates) but you do not need to be a Member or Delegate to apply to become a Financial Auditor. The application survey is here. This campaign will close on Friday 8th November.

    Any questions, please let me know.

    Warm regards,
    Rebecca
    -- 
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 12:21 - 31 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    Hello everyone,

    sorry for my silence in the previous days. Busy days as we all know.
    I think we should start small to grow slowly but surely.
    I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.
    In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.
    I see that you have already a good list with:
    * doodba
    * odoo cloud platform
    ...

    What do you think?
    OdooOps seems a good place to start. Could you create a new repo for the listing?

    Cheers,
    Jordi


    Le mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :
    Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!

    From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.

    Namely, to my knowledge, those are:
    - Tecnativa (doodba)
    - Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)
    - Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)
    - Akretion (docky and other tooling)
    - XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)

    Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?

    El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:
    Great stuff David!

    Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?

    I will have a read and make some comments in a bit :)

    Russ

    On Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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

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



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    by Jordi Riera - 09:10 - 30 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!

    From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.

    Namely, to my knowledge, those are:
    - Tecnativa (doodba)
    - Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)
    - Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)
    - Akretion (docky and other tooling)
    - XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)

    Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?

    El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:
    Great stuff David!

    Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?

    I will have a read and make some comments in a bit :)

    Russ

    On Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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 dar - 05:26 - 30 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    Great stuff David!

    Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?

    I will have a read and make some comments in a bit :)

    Russ

    On Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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 Russell Briggs - 07:26 - 30 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)

    El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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 dar - 09:56 - 29 Oct 2019
  • Re: Place to share knowledge/tools on deployment
    Hi all,

    I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.

    I stepped over some steps and wrote down everything I had in mind.

    For legitimacy building, please comment on the PR and indicate your level of approval:

    Approve: Section 1, Section 2, etc.
    Disaprove: Section 4

    Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.

    According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.


    Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.

    BR,

    David A.

    El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:
    I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

    However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

    So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

    People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

    Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

    My 2 cents.

    El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    The interest will grow if the few involve here make it work...

    El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
    What is the next step for this to move on?
    - Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
    - Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

    It would be nice to know who is interested by this topic.

    tnx
    --
    Yves Goldberg
    --


    ----- Original message -----
    From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
    Subject: Re: Place to share knowledge/tools on deployment
    Date: Tuesday, October 22, 2019 19:52

    Hi Jordi,

    I think we could start with:
    • one repository to store a base/minimal docker image + documented extensions.
    • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
    My 2 cents.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    P.O. BOX 940, HIGLEY, AZ 85236






    On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


    --

    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada













    _______________________________________________

    _______________________________________________


    _______________________________________________
    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 dar - 09:51 - 29 Oct 2019
  • Re: Frepple, supply chain planning & scheduling
    Thanks @Houssine I've seen, interesting

    @Daniel
    I've to investigate some ways and probably will ask you further informations

    Thanks a lot for this really good information

    Bonne journée


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


    Le mar. 29 oct. 2019 à 10:11, Houssine BAKKALI <houssine.bakkali@gmail.com> a écrit :
    Hi David,

    Maybe you're already aware of the existing connector between Odoo and Freeple. Anyway I put it there just in case. https://frepple.com/integrations/odoo-connector/

    Houssine

    Le lun. 28 oct. 2019 à 20:41, Daniel Reis <dgreis@sapo.pt> a écrit :
    Hello David,

    OSI has a customer using Frepple, and is aware of other Odoo customers also using Frepple.

    I could put you in contact with the people familiar with these. Would setting up a call be appropriate?

    Daniel

    No dia 28/10/2019, às 19:21, David Beal <david.beal@akretion.com> escreveu:

    
    Hi dear odoo integrators,

    Just a little message to know if somebody have any experiment with frepple
    connected with Odoo ?

    Did you implement it for customers ?

    What was the feedback of them ?

    Thanks

    Bonne journée


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

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

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

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

    by David BEAL - 05:55 - 29 Oct 2019
  • Re: Frepple, supply chain planning & scheduling
    Hi David,

    Maybe you're already aware of the existing connector between Odoo and Freeple. Anyway I put it there just in case. https://frepple.com/integrations/odoo-connector/

    Houssine

    Le lun. 28 oct. 2019 à 20:41, Daniel Reis <dgreis@sapo.pt> a écrit :
    Hello David,

    OSI has a customer using Frepple, and is aware of other Odoo customers also using Frepple.

    I could put you in contact with the people familiar with these. Would setting up a call be appropriate?

    Daniel

    No dia 28/10/2019, às 19:21, David Beal <david.beal@akretion.com> escreveu:

    
    Hi dear odoo integrators,

    Just a little message to know if somebody have any experiment with frepple
    connected with Odoo ?

    Did you implement it for customers ?

    What was the feedback of them ?

    Thanks

    Bonne journée


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

    _______________________________________________
    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 Houssine BAKKALI - 10:10 - 29 Oct 2019
  • Re: Frepple, supply chain planning & scheduling
    Hello David,

    OSI has a customer using Frepple, and is aware of other Odoo customers also using Frepple.

    I could put you in contact with the people familiar with these. Would setting up a call be appropriate?

    Daniel

    No dia 28/10/2019, às 19:21, David Beal <david.beal@akretion.com> escreveu:

    
    Hi dear odoo integrators,

    Just a little message to know if somebody have any experiment with frepple
    connected with Odoo ?

    Did you implement it for customers ?

    What was the feedback of them ?

    Thanks

    Bonne journée


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

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

    by Daniel Reis - 08:41 - 28 Oct 2019
  • Frepple, supply chain planning & scheduling
    Hi dear odoo integrators,

    Just a little message to know if somebody have any experiment with frepple
    connected with Odoo ?

    Did you implement it for customers ?

    What was the feedback of them ?

    Thanks

    Bonne journée


    David BEAL - akretion.com
    Chef de projet
    Odoo Développement / Intégration
    by David BEAL - 08:21 - 28 Oct 2019