Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • New library to migrate Odoo module code "odoo-migrate" 
    Wow! Thanks Sylvain, this is definitely a very nice helper tool. I for
one would love to see this in OCA/maintainers-tools if people are ok
with this.

It's already installed and tested locally :-D

🙏

Alexandre

On 10/10/2019 18:12, Sylvain LE GAL wrote:

> Dear OCA Contributors,

> 

> I am working on a migration from 8.0 to 12.0.

> For that purpose, I had to migrate a lot a modules. (about 50 OCA

> modules, and >100 custom modules)

> A lot of changes are very recurrent, and automatable. (removing python2

> header, renaming __openerp__.py into __manifest__.py, changing import).

> 

> I began to make some scripts, and finally began to create a new python3

> library, to make that work. The name is "odoo-migrate" and the

> description is available here https://pypi.org/project/odoo-migrate/.

> and can be installed with the command /

> /

> /pip3 install odoo-migrate/

> 

> Once installed, you can run the following command (other options are

> available)/

> /

> /odoo-migrate -m my_module_name -i 8.0 -t 12.0/

> 

> It is based on the OCA recommendations available on this wiki

> .

> In addition to performing recurring operations,

> - the library also execute the weird format-patch

> 

> commandwhich I never remember(if asked).

> - it displays some warning if some patterns are found. (for example, if

> "ir.values" is found in a module 11+)

> - it calls black for recent version

> - it realize commits

> 

> 1) If you're interested by such tool, you can review or test this project.

> 

> 2) If you want to contribute, feel free, especially if you love regular

> expressions.*It is still WIP*, and there is a lot of work**to do, like

> making change in xml file. (replacing openerp + data by odoo tag). Also

> adding test and plug with travis could be great.

> 

> 3) if some OCA members are OK, I can transfer this project under OCA

> umbrella.

> 

> thank you for your feedback.

> 

> kind regards.

> 

> 

> *Sylvain LE GAL - Twitter *

> *GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)*

> Site Web  | FramaSphere

> |

> Facebook 
> 3 Grande rue des Feuillants, 69001 Lyon
> Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
> *Member of the OCA (Odoo Community Association)
> *
> Web Site  | Twitter
> 

> 

> _______________________________________________

> 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 - 06:30 - 10 Oct 2019
  • New library to migrate Odoo module code "odoo-migrate"
    Dear OCA Contributors,

    I am working on a migration from 8.0 to 12.0.
    For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
    A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

    I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
    pip3 install odoo-migrate

    Once installed, you can run the following command (other options are available)
    odoo-migrate -m my_module_name -i 8.0 -t 12.0

    It is based on the OCA recommendations available on this wiki.
    In addition to performing recurring operations,
    - the library also execute the weird format-patch command which I never remember (if asked).
    - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
    - it calls black for recent version
    - it realize commits

    1) If you're interested by such tool, you can review or test this project.

    2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

    3) if some OCA members are OK, I can transfer this project under OCA umbrella.

    thank you for your feedback.

    kind regards.


    Sylvain LE GAL - Twitter
    GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
    Site Web | FramaSphere | Facebook
    3 Grande rue des Feuillants, 69001 Lyon
    Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
    Member of the OCA (Odoo Community Association)
    by Sylvain LE GAL - 06:10 - 10 Oct 2019
  • Re: Consultancy Services - Expressions of Interest - Upgrade of the Odoo CORE Vertical Uruguayan State - Odoo v8 to Odoo Community v12
    Dear OCA Contributors,

    This link has been passed on to share with you for your expressions of interest: https://www.devbusiness.com/ProjectViewer.aspx?ProjectType=1&ProjectID=209644

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

    On Tue, Oct 8, 2019 at 7:26 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Hello Contributors.

    The Ministry of Economy and Finance do Uruguay has decided to extend the deadline for submissions of "Expressions of interest" (EoI) until October 17th, 2019 due to the fact that only 3 EoI have been received thus far.
    In case of any discrepancy, the valid version is the one written in Spanish.

    Warm regards as always,
    Rebecca

    On Sat, Sep 28, 2019 at 9:39 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Dear OCA Contributors,

    Please find attached the English version of this opportunity.


    Wishing you all the best.

    Rebecca

    On Tue, Sep 24, 2019 at 9:51 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Dear Contributors,

    The Government of the Eastern Republic of Uruguay has sent an invitation from The Budgetary and Financial Management Program (PGPF) for expressions of interest for the diagnosis of the effort required for the Upgrade of the Odoo Core Vertical Uruguayan Estate from the version Odoo v8 to the version Odoo Community v12.

    Please find attached the PDF and link to the invitation.

    A short list will be formed by the Ministry of Economy and Finance in Uruguay (MEF) according to the “Policies for the Selection of Consultants Financed by the Inter-American Development Bank GN-2350-9 of March 2011”. This project will be partially financed by the Inter-American Development Bank (IADB) Loan Nº 4705 / OC-UR.

    An English translation for the text will be shared before the end of the week.

    Expressions of interest need to be submitted by October 7th, 2019 at 12:00.

    Warm regards,
    Rebecca

     --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 11:41 - 9 Oct 2019
  • Little bounty proposals : Payment plugin and feed export 
    Hello

I'm looking for someone to code ! I think it is simple but too long or too 
difficult for me. My budget is very small : around 1000€
There is two projects, all free (GPL) :

1. Port the Lyra / Payzen Odoo payment acquirer to #13. It is an international 
payment solution, their plugin is already available with Odoo 10 to 12 and 
need to be adapted to version #13. https://github.com/lyra/plugin-odoo
See https://payzen.eu/ and https://lyra.com/ for information on their solution

2. We need a very basical solution to connect to multi-channel feed 
distribution services (typicaly to sell  across many marketplaces). Our target 
is Iziflux (France only), but it should be possibly customized to other feeds. 
We need to export products and stocks and to import sales with customers data 
periodicaly.
A CSV export-import based on odoo-connector will do the job in most cases.


-- 
Librement,
Xavier Brochard / zeroheure
« La liberté est à l'homme ce que les ailes sont à l'oiseau » 
(Jean-Pierre Rosnay)
    by xavier - 05:26 - 9 Oct 2019
  • Re: How to use @api.onchange in models.AbstractModel, when the interiting class field name are different.
    Hello Simone,

    Thank you for answer. I did try that with,

    @api.onchange(lambda self: self._get_onchange_analytic_tag_spec)
    also
    @api.onchange(lambda self: (self._analytic_tag_field_name, ))

    But it do not triggered.

    Just FYI. from the existing Odoo source code, I only see some @api.depends that call other function.

    Kitti


    On Mon, Oct 7, 2019 at 2:42 PM Simone Orsi <simahawk@gmail.com> wrote:
    Hi Kitti,

    AFAIS your solution with the lambda probably does not work because you are returning the field name instead of a tuple/list of fields.

    If you want to do it that way I suggest you use a specific method in the base model, eg:

    class AccountInvoiceLine(models.Model):
        _name = 'account.invoice.line'
        _inherit = ['analytic.dimension.line', 'account.invoice.line']
        _analytic_tag_field_name = 'analytic_tag_ids'

     def _get_onchange_analytic_tag_spec(self):
        return (self._analytic_tag_field_name, )

    @api.onchange(self._get_onchange_analytic_tag_spec)
        def _onchange_analytic_tag_ids(self):
        [...]

    Hope this helps. Bests,
    S.


    On Fri, Sep 27, 2019 at 1:31 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    Dear all,

    I have one technical challenge while doing this PR -> https://github.com/OCA/account-analytic/pull/251

    In the origin module, there was abstract class,

    class AnalyticDimensionLine(models.AbstractModel):
        _name = 'analytic.dimension.line'

    Which are inherited by other model, i.e., account.move.line, account.invoice.line, etc.

    class AccountInvoiceLine(models.Model):
        _name = 'account.invoice.line'
        _inherit = ['analytic.dimension.line', 'account.invoice.line']
        _analytic_tag_field_name = 'analytic_tag_ids'

    Now, I wanted to add api.onchange method on a field which can be varied by each inheriting model via _analytic_tag_field_name

    Question is, I would want to do the onchange on the base abstract class, analytic.dimension.line like this, but it doesn't work.

    class AnalyticDimensionLine(models.AbstractModel):
        _inherit = 'analytic.dimension.line'

        @api.onchange(lambda self: self._analytic_tag_field_name)      ---------------------> THIS NOT WORK
        def _onchange_analytic_tag_ids(self):

    And so, I end up having to add @api.onchange in inheriting models. Which I think not very good.

    class AccountInvoiceLine(models.Model):
        _inherit = 'account.invoice.line'

        @api.onchange('analytic_tag_ids')  ----------------------> NOT GOOD
        def _onchange_analytic_tag_ids(self):


    Any thought are appreciated,
    Than you,



    _______________________________________________
    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 Kitti Upariphutthiphong - 10:45 - 9 Oct 2019
  • Re: Linting for 13.0 branches (using black and pre-commit)
    +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, Oct 8, 2019 at 12:52 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
    +1

    Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :
    +1 from "Numigiens"

    Have a good day from Canada!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
    Dear contributors,

    Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

    This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

    In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

    At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

    TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
    • run Black before committing your code on the 13.0 branches
    • sort imports (stdlib, odoo, odoo.addons, local imports)
    • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
    If you are interested in practical details and the rationale, read on.

    pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
    • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
    • you then run "pre-commit install" after cloning a repository
    • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
    • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
    • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
    • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
    The proposed configuration includes the following linters:
    • black, with default options (to facilitate usage)
    • auto fix trailing whitespace
    • auto fix newline at end of files
    • detect debug statements
    • flake8 with same options as before (except line length which is now the 88 black default)
    • pyupgrade, to encourage python 3 idioms
    • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
    • pylint with all checks (optional + mandatory), not failing
    • isort to automatically sort imports (except in __init__.py where import order might be significant)
    • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
    You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
    • checkout these branches
    • run 'pre-commit install'
    • start committing lint failures to see the effect.
    If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

    In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

    When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

    Looking forward to reading your feedback.

    Best regards,

    -sbi


    _______________________________________________
    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 Maxime Chambreuil - 09:56 - 8 Oct 2019
  • Re: CodeTriage "app"
    My main issue is kind of similar to pedro.

    Oca repos are arbitrary collections of topic modules. Some repos are closely associated with particular authors, partners and maintainers, e.g donation, queue some are all sorts.

    We would be better I think using a specific issue template format that a bot can determine who best to triage to. Could even be as simple as just reading an ini style format in a repo root.

    I saw a good pr/ issue template on the pylint repo the other day.

    On Tue, 8 Oct 2019, 10:47 PM Alexandre Fayolle, <alexandre.fayolle@camptocamp.com> wrote:
    Is there a way to 'tag' blueprint issues or 'work needed' issues to get
CodeTriage to work on this?

Is there a way to get CodeTriage to look for "needs review" pull requests?

Alexandre

On 08/10/2019 11:22, Pedro M. Baeza (Tecnativa) wrote:


> Thanks for the initiative, Damien,


> 


> I have subscribed to Odoo one to see how it works.


> 


> The initial cons I see are:


> 


> 1. We have a lot of repos, not one, and constantly growing.


> 2. A lot of issues belongs to blueprints or migration tracking, so they


> don't apply directly to this process.


> 


> 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

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

    by Graeme Gellatly - 08:36 - 8 Oct 2019
  • Re: Linting for 13.0 branches (using black and pre-commit)
    +1

    Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :
    +1 from "Numigiens"

    Have a good day from Canada!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
    Dear contributors,

    Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

    This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

    In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

    At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

    TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
    • run Black before committing your code on the 13.0 branches
    • sort imports (stdlib, odoo, odoo.addons, local imports)
    • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
    If you are interested in practical details and the rationale, read on.

    pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
    • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
    • you then run "pre-commit install" after cloning a repository
    • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
    • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
    • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
    • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
    The proposed configuration includes the following linters:
    • black, with default options (to facilitate usage)
    • auto fix trailing whitespace
    • auto fix newline at end of files
    • detect debug statements
    • flake8 with same options as before (except line length which is now the 88 black default)
    • pyupgrade, to encourage python 3 idioms
    • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
    • pylint with all checks (optional + mandatory), not failing
    • isort to automatically sort imports (except in __init__.py where import order might be significant)
    • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
    You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
    • checkout these branches
    • run 'pre-commit install'
    • start committing lint failures to see the effect.
    If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

    In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

    When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

    Looking forward to reading your feedback.

    Best regards,

    -sbi


    _______________________________________________
    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 Joël Grand Guillaume - 07:46 - 8 Oct 2019
  • Re: Kenyan Localization Repo
    Hi. Kiplangat, please write to contribute@odoo-community.org, as this is handle through tasks in our instance through that mail.

    Regards.
    by Pedro M. Baeza - 05:00 - 8 Oct 2019
  • Re: 2019 OCA Extra Delegates Campaign is NOW OPEN
    Rebecca I have passed the invoices for the 3 membership to our finance team, as soon as they pay, we can postulate as delegates, after that all we have to do is fill the form? 


    It is asking to be logged in order to do it and we do not have users :D

    Let me know

    Thanks!



    El mar., 8 de oct. de 2019 a la(s) 01:27, Rebecca Gellatly (rebecca@o4sb.com) escribió:

    Dear OCA Contributors,


    As you may be aware the decision to run an extra campaign to fill the remaining 7 Delegate positions for this year has been made. 

    The 3 new Delegates from the earlier election were: 
    • Yves Goldberg
    • Simone Orsi
    • Sergio Teruel Albert
    The new campaign is now open and will run from today until the 18th of October, 2019. The current Board Member and Financial Auditor Campaign will be suspended until October 28th, 2019.

    Why?


    There are 10 places each year for new Delegates. This year's previous election only had 3 new Delegates elected leaving 7 positions to be filled.

    The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.


    How?


    To apply as a candidate, you have to:

    The campaign will be closed on October 18th, 2019.


    Then what?


    The vote will be open from October 19th to October 25th, 2019: Current OCA Delegates will vote for 7 new Delegates among the candidates.


    The results of the election will be announced on October 26th, 2019.


    The 10 new Delegates and existing Delegates will then take part in:

    • the 2019 OCA Board Member Campaign from October 28th to November 8th, 2019.

    • the 2019 OCA Financial Auditor Campaign from October 28th to November 8th, 2019.

    • the 2019 General Assembly from November 11th to November 22nd, 2019.


    Should you have any questions, please get in touch.


    Warm regards,

    Rebecca--
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

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

    by Gonzalo Ruzafa. - 02:21 - 8 Oct 2019
  • CodeTriage "app" 
    Is there a way to 'tag' blueprint issues or 'work needed' issues to get
CodeTriage to work on this?

Is there a way to get CodeTriage to look for "needs review" pull requests?

Alexandre

On 08/10/2019 11:22, Pedro M. Baeza (Tecnativa) wrote:

> Thanks for the initiative, Damien,

> 

> I have subscribed to Odoo one to see how it works.

> 

> The initial cons I see are:

> 

> 1. We have a lot of repos, not one, and constantly growing.

> 2. A lot of issues belongs to blueprints or migration tracking, so they

> don't apply directly to this process.

> 

> 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:45 - 8 Oct 2019
  • Re: CodeTriage "app"
    Thanks for the initiative, Damien,

    I have subscribed to Odoo one to see how it works.

    The initial cons I see are:

    1. We have a lot of repos, not one, and constantly growing.
    2. A lot of issues belongs to blueprints or migration tracking, so they don't apply directly to this process.

    Regards.
    by Pedro M. Baeza - 11:21 - 8 Oct 2019
  • Re: Propose Héctor Villarreal as PSC of purchases
    +1

    On Mon, Sep 30, 2019 at 6:26 PM Lois Rilo Antelo <lois.rilo@eficent.com> wrote:
    Hi all,

    Here is his Github account. He has actively participated with a lot of contributions at purchase-workflow repository in the newest versions: https://github.com/OCA/purchase-workflow/pulls/hveficent and has migrated to latest version purchase_request among others.

    Regards,

    --
    Lois Rilo Antelo
    Eficent Business and IT Consulting Services, S.L.
    (+34) 679052448 | lois.rilo@eficent.com | http://www.eficent.com
    Twitter: lreficent_erp

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



    --
    by Alex Comba. - 11:11 - 8 Oct 2019
  • Re: Consultancy Services - Expressions of Interest - Upgrade of the Odoo CORE Vertical Uruguayan State - Odoo v8 to Odoo Community v12
    Hello,

    Although not planning to approach on this project. But we has interest to create government vertical in OCA, especially on procurement and budgeting. I am sure there will be some common modules to work together. So, please keep us posted, if you got the project.

    Currently we already started some work in OCA/account-budgeting, but not that close to finish yet.

    I am not sure it is a good time to create new project i.e., OCA/government

    Thank you,

    On Tue, Oct 8, 2019 at 1:32 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Hello Contributors.

    The Ministry of Economy and Finance do Uruguay has decided to extend the deadline for submissions of "Expressions of interest" (EoI) until October 17th, 2019 due to the fact that only 3 EoI have been received thus far.
    In case of any discrepancy, the valid version is the one written in Spanish.

    Warm regards as always,
    Rebecca

    On Sat, Sep 28, 2019 at 9:39 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Dear OCA Contributors,

    Please find attached the English version of this opportunity.


    Wishing you all the best.

    Rebecca

    On Tue, Sep 24, 2019 at 9:51 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Dear Contributors,

    The Government of the Eastern Republic of Uruguay has sent an invitation from The Budgetary and Financial Management Program (PGPF) for expressions of interest for the diagnosis of the effort required for the Upgrade of the Odoo Core Vertical Uruguayan Estate from the version Odoo v8 to the version Odoo Community v12.

    Please find attached the PDF and link to the invitation.

    A short list will be formed by the Ministry of Economy and Finance in Uruguay (MEF) according to the “Policies for the Selection of Consultants Financed by the Inter-American Development Bank GN-2350-9 of March 2011”. This project will be partially financed by the Inter-American Development Bank (IADB) Loan Nº 4705 / OC-UR.

    An English translation for the text will be shared before the end of the week.

    Expressions of interest need to be submitted by October 7th, 2019 at 12:00.

    Warm regards,
    Rebecca

     --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

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

    by Kitti Upariphutthiphong - 10:51 - 8 Oct 2019
  • CodeTriage "app"
    Hello,

    Maybe some of you already know CodeTriage. 
    For those who don't know it yet, it's a platform that allow you to receive (by mail) some bugs (github issues) of public project to help them handle those issues. 
    Here is a page explaining what's this app for: https://www.codetriage.com/what

    I noticed Odoo is there: https://www.codetriage.com/odoo/odoo

    Seems the public GitHub repo has to register to appear in the list of projects to help.

    Question: Do you think it's worth it for OCA repo to register to this app? 

    IMHO, if some OCA repo were registered there, I would subscribe.
    What about you?

    Have a nice day

    Cheers,

    -- 
    Damien Crier
    Camptocamp France SAS
    18 rue du Lac Saint André
    Savoie Technolac - Bâtiment Le Dauphin
    F-73370 Le Bourget du Lac
    
http://www.camptocamp.com
    by Damien Crier - 09:11 - 8 Oct 2019
  • Re: Consultancy Services - Expressions of Interest - Upgrade of the Odoo CORE Vertical Uruguayan State - Odoo v8 to Odoo Community v12
    Hello Contributors.

    The Ministry of Economy and Finance do Uruguay has decided to extend the deadline for submissions of "Expressions of interest" (EoI) until October 17th, 2019 due to the fact that only 3 EoI have been received thus far.
    In case of any discrepancy, the valid version is the one written in Spanish.

    Warm regards as always,
    Rebecca

    On Sat, Sep 28, 2019 at 9:39 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Dear OCA Contributors,

    Please find attached the English version of this opportunity.


    Wishing you all the best.

    Rebecca

    On Tue, Sep 24, 2019 at 9:51 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:
    Dear Contributors,

    The Government of the Eastern Republic of Uruguay has sent an invitation from The Budgetary and Financial Management Program (PGPF) for expressions of interest for the diagnosis of the effort required for the Upgrade of the Odoo Core Vertical Uruguayan Estate from the version Odoo v8 to the version Odoo Community v12.

    Please find attached the PDF and link to the invitation.

    A short list will be formed by the Ministry of Economy and Finance in Uruguay (MEF) according to the “Policies for the Selection of Consultants Financed by the Inter-American Development Bank GN-2350-9 of March 2011”. This project will be partially financed by the Inter-American Development Bank (IADB) Loan Nº 4705 / OC-UR.

    An English translation for the text will be shared before the end of the week.

    Expressions of interest need to be submitted by October 7th, 2019 at 12:00.

    Warm regards,
    Rebecca

     --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 08:31 - 8 Oct 2019

    2 attachments 2 attachments

    Llamado a EdI Migración GRO Odoo v8.0a v12.0 sp.pdf
    Llamado a EdI Migración GRO Odoo v8.0a v12.0_eng.pdf
  • 2019 OCA Extra Delegates Campaign is NOW OPEN

    Dear OCA Contributors,


    As you may be aware the decision to run an extra campaign to fill the remaining 7 Delegate positions for this year has been made. 

    The 3 new Delegates from the earlier election were: 
    • Yves Goldberg
    • Simone Orsi
    • Sergio Teruel Albert
    The new campaign is now open and will run from today until the 18th of October, 2019. The current Board Member and Financial Auditor Campaign will be suspended until October 28th, 2019.

    Why?


    There are 10 places each year for new Delegates. This year's previous election only had 3 new Delegates elected leaving 7 positions to be filled.

    The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.


    How?


    To apply as a candidate, you have to:

    The campaign will be closed on October 18th, 2019.


    Then what?


    The vote will be open from October 19th to October 25th, 2019: Current OCA Delegates will vote for 7 new Delegates among the candidates.


    The results of the election will be announced on October 26th, 2019.


    The 10 new Delegates and existing Delegates will then take part in:

    • the 2019 OCA Board Member Campaign from October 28th to November 8th, 2019.

    • the 2019 OCA Financial Auditor Campaign from October 28th to November 8th, 2019.

    • the 2019 General Assembly from November 11th to November 22nd, 2019.


    Should you have any questions, please get in touch.


    Warm regards,

    Rebecca--
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 01:26 - 8 Oct 2019
  • Re: 2019 OCA Delegates Campaign is NOW OPEN.
    HI Bruno, 

    We had to contact the existing Delegates to get a sort of general consensus to move forward and share with those that weren't at OCA Days.
    We now have it.

    I'll have the NEW CAMPAIGN up and running in a few hours.

    Watch this space.

    Warm regards,
    Rebecca

    On Tue, Oct 8, 2019 at 4:41 AM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Hi Rebecca and Contributors,

    We understood during OCADays in LLN we could apply as delegate until this 6th october.

    Is it the same way described in  the initial email?

    Regards,

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le dim. 4 août 2019 à 22:41, Rebecca Gellatly <rebecca@o4sb.com> a écrit :
    Hello Contributors,

    Apologies, I stated in the first couple of lines that the campaign is open "From now and until 18th of September, 2019", this was meant to read "till the 18th of August" as you'll see confirmed later in the text.

    Basically, if you would like to put in an application to become a Delegate, you need to make sure your membership for 2019 is paid and you have till the 18th of August to fill in the application survey.

    Sorry for any confusion.

    Warm regards,
    Rebecca

    On Mon, Aug 5, 2019 at 2:20 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:

    Dear Odoo enthusiasts, OCA members and contributors,


    The 2019 OCA Delegates Campaign is open. From now and until 18th of September, 2019, you can apply to become an OCA Delegate.


    Why?


    The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.


    How?


    To apply as a candidate, you have to:

    The campaign will be closed on August 18th, 2019.


    Then what?


    The vote will be open from August 19th to September 1st, 2019: Current OCA Delegates will vote for 10 new Delegates among the candidates.


    The results of the election will be announced on those lists on September 2nd, 2019.


    The 10 new Delegates will then take part in:

    • the 2019 OCA Board Member Campaign from September 2nd to September 15th, 2019

    • the 2019 OCA Financial Auditor Campaign from September 2nd to September 15th 2019

    • the 2019 General Assembly from September 15th to 29th, 20189


    Should you have any questions, please get in touch.


    Warm regards,

    Rebecca Gellatly

    General Secretary

    Odoo Community Association




    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    _______________________________________________
    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



    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 10:16 - 7 Oct 2019
  • Re: Linting for 13.0 branches (using black and pre-commit)
    +1 from "Numigiens"

    Have a good day from Canada!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
    Dear contributors,

    Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

    This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

    In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

    At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

    TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
    • run Black before committing your code on the 13.0 branches
    • sort imports (stdlib, odoo, odoo.addons, local imports)
    • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
    If you are interested in practical details and the rationale, read on.

    pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
    • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
    • you then run "pre-commit install" after cloning a repository
    • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
    • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
    • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
    • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
    The proposed configuration includes the following linters:
    • black, with default options (to facilitate usage)
    • auto fix trailing whitespace
    • auto fix newline at end of files
    • detect debug statements
    • flake8 with same options as before (except line length which is now the 88 black default)
    • pyupgrade, to encourage python 3 idioms
    • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
    • pylint with all checks (optional + mandatory), not failing
    • isort to automatically sort imports (except in __init__.py where import order might be significant)
    • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
    You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
    • checkout these branches
    • run 'pre-commit install'
    • start committing lint failures to see the effect.
    If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

    In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

    When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

    Looking forward to reading your feedback.

    Best regards,

    -sbi


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

    by Bruno Joliveau - 06:10 - 7 Oct 2019
  • Re: 2019 OCA Delegates Campaign is NOW OPEN.
    Hi Rebecca and Contributors,

    We understood during OCADays in LLN we could apply as delegate until this 6th october.

    Is it the same way described in  the initial email?

    Regards,

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le dim. 4 août 2019 à 22:41, Rebecca Gellatly <rebecca@o4sb.com> a écrit :
    Hello Contributors,

    Apologies, I stated in the first couple of lines that the campaign is open "From now and until 18th of September, 2019", this was meant to read "till the 18th of August" as you'll see confirmed later in the text.

    Basically, if you would like to put in an application to become a Delegate, you need to make sure your membership for 2019 is paid and you have till the 18th of August to fill in the application survey.

    Sorry for any confusion.

    Warm regards,
    Rebecca

    On Mon, Aug 5, 2019 at 2:20 PM Rebecca Gellatly <rebecca@o4sb.com> wrote:

    Dear Odoo enthusiasts, OCA members and contributors,


    The 2019 OCA Delegates Campaign is open. From now and until 18th of September, 2019, you can apply to become an OCA Delegate.


    Why?


    The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.


    How?


    To apply as a candidate, you have to:

    The campaign will be closed on August 18th, 2019.


    Then what?


    The vote will be open from August 19th to September 1st, 2019: Current OCA Delegates will vote for 10 new Delegates among the candidates.


    The results of the election will be announced on those lists on September 2nd, 2019.


    The 10 new Delegates will then take part in:

    • the 2019 OCA Board Member Campaign from September 2nd to September 15th, 2019

    • the 2019 OCA Financial Auditor Campaign from September 2nd to September 15th 2019

    • the 2019 General Assembly from September 15th to 29th, 20189


    Should you have any questions, please get in touch.


    Warm regards,

    Rebecca Gellatly

    General Secretary

    Odoo Community Association




    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

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

    by Bruno Joliveau - 05:41 - 7 Oct 2019