Message Threads | The Odoo Community Association

Re: test mail

Got it.

Le ven. 1 juil. 2022 à 15:30, Jairo Llopis <notifications@odoo-community.org> a écrit :

Somebody gets this message?

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

by carlos - 05:36 - 1 Jul 2022

Re: test mail

Copy that :)

On Fri, Jul 1, 2022, 16:30 Jairo Llopis <notifications@odoo-community.org> wrote:

Somebody gets this message?

_______________________________________________
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 - 05:36 - 1 Jul 2022

Re: test mail

Yes!

On Fri, 1 Jul 2022 at 17:30, Jairo Llopis <notifications@odoo-community.org> wrote:

Somebody gets this message?

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

by "Aarón Henríquez Quintana" <aaron.henriquez@forgeflow.com> - 05:36 - 1 Jul 2022

Re: test mail

yep :)

On 1.7.22 17:30, Jairo Llopis wrote:

> Somebody gets this message?

>

> _______________________________________________

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

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

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

>

-- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer

web: https://www.lambda-is.com
tel: +38971753823

by Kiril Vangelovski - 05:36 - 1 Jul 2022

Re: test mail

Got it.

-sbi

On Fri, Jul 1, 2022 at 5:30 PM Jairo Llopis <notifications@odoo-community.org> wrote:

Somebody gets this message?

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

by Stéphane Bidoul - 05:36 - 1 Jul 2022

Re: test mail

yesss :)

El vie., 1 jul. 2022 17:30, Jairo Llopis <notifications@odoo-community.org> escribió:

Somebody gets this message?

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

by dariodafoz - 05:36 - 1 Jul 2022

test mail

Somebody gets this message?

by Jairo Llopis - 05:30 - 1 Jul 2022

Tip: Always call `clean_action` when returning an `ir.actions.act_window`

Hi,

Simple tip after losing my afternoon on this:

If you add a python `action_open_view_xxx` code that returns an `ir.actions.act_window` dict, you should always use the built-in `clean_action` that will convert any `tree` to `list`, otherwise the list view will be missing from the web client.

Note that this fix is always done internally by the webclient.

from odoo.addons.web.controllers.main import clean_action

class ProjectProject(models.Model):
    _inherit = 'project.project'

    def action_open_all_tasks(self, view_domain=False, view_type=False):
        act = clean_action(self.env.ref("project.action_view_task").read()[0])
        return act

--
Yann PAPOUIN, Ingénieur R&D | DEC

by Yann Papouin - 04:55 - 30 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Hi Moises,

I just created the repo: https://github.com/OCA/odoo-pre-commit-hooks/

Best regards,

-sbi

On Mon, Jun 27, 2022 at 10:12 PM Moises Lopez <moylop260@vauxoo.com> wrote:

Currently, we are using pylint-odoo project as pre-commit hooks for other kind of files

Now, we are using pre-commit for new projects.

So we can remove all the checks unrelated with python from pylint-odoo
e.g. eslint (javascript lints), XML checks, PO (translations) checks and so on

Then they could be replaced in the pre-commit configuration file with the id of the related check

e.g. eslint see https://github.com/pre-commit/mirrors-eslint

There are other custom checks in pylint-odoo as unnecessary-utf8-coding-comment
But it is duplicated with the following hook id fix-encoding-pragma from:
- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/fix_encoding_pragma.py

It even has the option to auto-fix it

Similar case for pylint-odoo check incoherent-interpreter-exec-perm:
- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/check_executables_have_shebangs.py

Similar case for pylint-odoo check wrong-tabs-instead-of-spaces
- https://github.com/Lucas-C/pre-commit-hooks/blob/master/pre_commit_hooks/remove_tabs.py

They are duplicated from pylint-odoo and they are better since they have the option to auto-fix if you want.

But there are other kinds of custom checks in pylint-odoo unrelated with python files that could be good to create a new pre-commit-hook custom for Odoo modules

In order to check XMLs, PO, CSS, CSV, and so on in the context of Odoo modules.

Currently, pylint-odoo is overloaded trying to do checks for non-python code since the core is not supporting check non-python files
And pylint-odoo doesn't have the auto-fix option

e.g. for XML files:
- dangerous-filter-wo-user
- duplicate-xml-record-id
- deprecated-openerp-xml-node
- create-user-wo-reset-password
- duplicate-xml-fields
- redundant-modulename-xml
- deprecated-data-xml-node

e.g. for CSV files:
- duplicate-id-csv

e.g. for PO files (Maybe, If we look for if exists hooks related to PO files they could be already developed from another hook project, so use it instead):
- duplicate-po-message-definition
- po-msgstr-variables

So, IMHO in OCA we need to create a new project to push all these custom pre-commit hooks and add documentation of the useful projects replacing pylint-odoo checks.

The name proposal is oca/odoo-pre-commit-hooks similar to main hooks repository:
- https://github.com/pre-commit/pre-commit-hooks/tree/main/pre_commit_hooks

And we can (or not) enable the option to auto fix (we can even push checks without auto fix)

Check the following discussion about creating custom repository to detect and autofix:
- https://github.com/OCA/pylint-odoo/issues/375

Check the following discussion about deprecating duplicated checks if pre-commit supports:
- https://github.com/OCA/pylint-odoo/issues/267

Check the following plan to create a freeze branch in pylint-odoo with the current behavior in pro to create a new version with new focus and clean code, delete old unused checks, deprecate py2 and so on:
- https://github.com/OCA/pylint-odoo/issues/381

If you agree, Could you help us to create the repository in OCA, please?

--
Moisés López Calderón
Mobile: (+521) 477-752-22-30
Twitter: @moylop260
hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner
Twitter: @vauxoo

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

by Stéphane Bidoul - 11:15 - 29 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Hi Moises,

Sounds great to make pylint-odoo simpler!

I take the opportunity to mention the semgrep (https://semgrep.dev) project that I recently discovered and may be a simple solution to implement some checks.

I'll create the new repo soon.

> Question: how does this coordinate with the OCA repo template? Pre commit hooks are currently maintained there, right?

Once the new checkers/fixers are ready in the new repo(s), they will need to be referenced in the .pre-commit-config.yaml template in the addons repo template.

Best regards,

-sbi

On Tue, Jun 28, 2022 at 9:52 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:

Thank you for taking care of this Moises.

Question: how does this coordinate with the OCA repo template? Pre commit hooks are currently maintained there, right?

--dr

No dia 28/06/2022, às 07:46, Mignon, Laurent <laurent.mignon@acsone.eu> escreveu:

Good Idea!

Regards.

On Tue, Jun 28, 2022 at 8:17 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Yes, I agree.

Regards.

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

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

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

by Stéphane Bidoul - 12:41 - 28 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

I have done a big progress in this subject recently, and it's open sourced. Get it here: https://gitlab.com/moduon/devsecops/precommix

It's based on Nix, so you will never get another random failure. It's a definitive solution for problems such as:

Your pre-commit configurations will keep working forever.

Just go ahead and wire precommix with oca-addons-repo-template.

Apart from that, I agree on removing the non-python stuff from pylint-odoo.

by Jairo Llopis - 11:16 - 28 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Great ! +1

On Mon, Jun 27, 2022 at 10:12 PM Moises Lopez <moylop260@vauxoo.com> wrote:

Currently, we are using pylint-odoo project as pre-commit hooks for other kind of files

Now, we are using pre-commit for new projects.

So we can remove all the checks unrelated with python from pylint-odoo
e.g. eslint (javascript lints), XML checks, PO (translations) checks and so on

Then they could be replaced in the pre-commit configuration file with the id of the related check

e.g. eslint see https://github.com/pre-commit/mirrors-eslint

There are other custom checks in pylint-odoo as unnecessary-utf8-coding-comment
But it is duplicated with the following hook id fix-encoding-pragma from:
- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/fix_encoding_pragma.py

It even has the option to auto-fix it

Similar case for pylint-odoo check incoherent-interpreter-exec-perm:
- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/check_executables_have_shebangs.py

Similar case for pylint-odoo check wrong-tabs-instead-of-spaces
- https://github.com/Lucas-C/pre-commit-hooks/blob/master/pre_commit_hooks/remove_tabs.py

They are duplicated from pylint-odoo and they are better since they have the option to auto-fix if you want.

But there are other kinds of custom checks in pylint-odoo unrelated with python files that could be good to create a new pre-commit-hook custom for Odoo modules

In order to check XMLs, PO, CSS, CSV, and so on in the context of Odoo modules.

Currently, pylint-odoo is overloaded trying to do checks for non-python code since the core is not supporting check non-python files
And pylint-odoo doesn't have the auto-fix option

e.g. for XML files:
- dangerous-filter-wo-user
- duplicate-xml-record-id
- deprecated-openerp-xml-node
- create-user-wo-reset-password
- duplicate-xml-fields
- redundant-modulename-xml
- deprecated-data-xml-node

e.g. for CSV files:
- duplicate-id-csv

e.g. for PO files (Maybe, If we look for if exists hooks related to PO files they could be already developed from another hook project, so use it instead):
- duplicate-po-message-definition
- po-msgstr-variables

So, IMHO in OCA we need to create a new project to push all these custom pre-commit hooks and add documentation of the useful projects replacing pylint-odoo checks.

The name proposal is oca/odoo-pre-commit-hooks similar to main hooks repository:
- https://github.com/pre-commit/pre-commit-hooks/tree/main/pre_commit_hooks

And we can (or not) enable the option to auto fix (we can even push checks without auto fix)

Check the following discussion about creating custom repository to detect and autofix:
- https://github.com/OCA/pylint-odoo/issues/375

Check the following discussion about deprecating duplicated checks if pre-commit supports:
- https://github.com/OCA/pylint-odoo/issues/267

Check the following plan to create a freeze branch in pylint-odoo with the current behavior in pro to create a new version with new focus and clean code, delete old unused checks, deprecate py2 and so on:
- https://github.com/OCA/pylint-odoo/issues/381

If you agree, Could you help us to create the repository in OCA, please?

--
Moisés López Calderón
Mobile: (+521) 477-752-22-30
Twitter: @moylop260
hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner
Twitter: @vauxoo

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 10:51 - 28 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Thank you for taking care of this Moises.

Question: how does this coordinate with the OCA repo template? Pre commit hooks are currently maintained there, right?

--dr

No dia 28/06/2022, às 07:46, Mignon, Laurent <laurent.mignon@acsone.eu> escreveu:

Good Idea!

Regards.

On Tue, Jun 28, 2022 at 8:17 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Yes, I agree.

Regards.

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

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

by Daniel Reis - 09:51 - 28 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Good Idea!

Regards.

On Tue, Jun 28, 2022 at 8:17 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

Yes, I agree.

Regards.

_______________________________________________
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 - 08:46 - 28 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Yes, I agree.

Regards.

by Pedro M. Baeza - 08:15 - 28 Jun 2022

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Excellent work man!

+1 for repo.

On Tue, Jun 28, 2022 at 1:42 AM Moises Lopez <moylop260@vauxoo.com> wrote:

Currently, we are using pylint-odoo project as pre-commit hooks for other kind of files

Now, we are using pre-commit for new projects.

So we can remove all the checks unrelated with python from pylint-odoo
e.g. eslint (javascript lints), XML checks, PO (translations) checks and so on

Then they could be replaced in the pre-commit configuration file with the id of the related check

e.g. eslint see https://github.com/pre-commit/mirrors-eslint

There are other custom checks in pylint-odoo as unnecessary-utf8-coding-comment
But it is duplicated with the following hook id fix-encoding-pragma from:
- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/fix_encoding_pragma.py

It even has the option to auto-fix it

Similar case for pylint-odoo check incoherent-interpreter-exec-perm:
- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/check_executables_have_shebangs.py

Similar case for pylint-odoo check wrong-tabs-instead-of-spaces
- https://github.com/Lucas-C/pre-commit-hooks/blob/master/pre_commit_hooks/remove_tabs.py

They are duplicated from pylint-odoo and they are better since they have the option to auto-fix if you want.

But there are other kinds of custom checks in pylint-odoo unrelated with python files that could be good to create a new pre-commit-hook custom for Odoo modules

In order to check XMLs, PO, CSS, CSV, and so on in the context of Odoo modules.

Currently, pylint-odoo is overloaded trying to do checks for non-python code since the core is not supporting check non-python files
And pylint-odoo doesn't have the auto-fix option

e.g. for XML files:
- dangerous-filter-wo-user
- duplicate-xml-record-id
- deprecated-openerp-xml-node
- create-user-wo-reset-password
- duplicate-xml-fields
- redundant-modulename-xml
- deprecated-data-xml-node

e.g. for CSV files:
- duplicate-id-csv

e.g. for PO files (Maybe, If we look for if exists hooks related to PO files they could be already developed from another hook project, so use it instead):
- duplicate-po-message-definition
- po-msgstr-variables

So, IMHO in OCA we need to create a new project to push all these custom pre-commit hooks and add documentation of the useful projects replacing pylint-odoo checks.

The name proposal is oca/odoo-pre-commit-hooks similar to main hooks repository:
- https://github.com/pre-commit/pre-commit-hooks/tree/main/pre_commit_hooks

And we can (or not) enable the option to auto fix (we can even push checks without auto fix)

Check the following discussion about creating custom repository to detect and autofix:
- https://github.com/OCA/pylint-odoo/issues/375

Check the following discussion about deprecating duplicated checks if pre-commit supports:
- https://github.com/OCA/pylint-odoo/issues/267

Check the following plan to create a freeze branch in pylint-odoo with the current behavior in pro to create a new version with new focus and clean code, delete old unused checks, deprecate py2 and so on:
- https://github.com/OCA/pylint-odoo/issues/381

If you agree, Could you help us to create the repository in OCA, please?

--
Moisés López Calderón
Mobile: (+521) 477-752-22-30
Twitter: @moylop260
hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner
Twitter: @vauxoo

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

--

SerpentCS Modules on Odoo AppStore

The Splendid journey of 10 years

Technology Services @ www.serpentcs.com

Business Solutions @ www.serpentcs.in

Enterprise Mobile Apps @ www.odooonline.com

Quality Assurance @ www.odooqa.com

SAP Hana @ www.prozone-tech.com

Portal & DMS @ www.alfray.in

Regards,

----------------------------------------------------------------------------------------------------------------------------

Jay Vora

Managing Director

Direct: +91-9879354457

Office: +91-9033472982

Skype: jaynvora

Twitter : jaynvora

-------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com

by Jay Vora - 07:41 - 28 Jun 2022

Re: l10n-estonia status and proposing myself as PSC

Thanks! Yet haven't received GitHub invite yet

On 25 Jun 2022, at 23:11, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hello Alexey,

I just added your user to the l10-estonia PSC. You should receive the GitHub invite soon.

Best regards,

-sbi

On Thu, Jun 23, 2022 at 8:57 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
What next steps do I need to take?

On Mon, Jun 13, 2022 at 11:02 AM Enric Tobella Alomar <etobella@creublanca.es> wrote:
+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.

Enric Tobella Alomar
Desarrollo
Av. J. V. Foix 63

08034 Barcelona

Tlf. 932 522 522 (Ext. 1621)

creublanca.es

From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC

Dear all,

It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).

Also, I'd like to apply for l10n-estonia PSC.

Kind regards,
Alexey

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

Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.

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

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

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

by Alexey Pelykh - 07:10 - 28 Jun 2022

New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Currently, we are using pylint-odoo project as pre-commit hooks for other kind of files

Now, we are using pre-commit for new projects.

So we can remove all the checks unrelated with python from pylint-odoo

e.g. eslint (javascript lints), XML checks, PO (translations) checks and so on

Then they could be replaced in the pre-commit configuration file with the id of the related check

e.g. eslint see https://github.com/pre-commit/mirrors-eslint

There are other custom checks in pylint-odoo as unnecessary-utf8-coding-comment

But it is duplicated with the following hook id fix-encoding-pragma from:

- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/fix_encoding_pragma.py

It even has the option to auto-fix it

Similar case for pylint-odoo check incoherent-interpreter-exec-perm:

- https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/check_executables_have_shebangs.py

Similar case for pylint-odoo check wrong-tabs-instead-of-spaces

- https://github.com/Lucas-C/pre-commit-hooks/blob/master/pre_commit_hooks/remove_tabs.py

They are duplicated from pylint-odoo and they are better since they have the option to auto-fix if you want.

But there are other kinds of custom checks in pylint-odoo unrelated with python files that could be good to create a new pre-commit-hook custom for Odoo modules

In order to check XMLs, PO, CSS, CSV, and so on in the context of Odoo modules.

Currently, pylint-odoo is overloaded trying to do checks for non-python code since the core is not supporting check non-python files

And pylint-odoo doesn't have the auto-fix option

e.g. for XML files:

- dangerous-filter-wo-user

- duplicate-xml-record-id

- deprecated-openerp-xml-node
- create-user-wo-reset-password
- duplicate-xml-fields
- redundant-modulename-xml
- deprecated-data-xml-node

e.g. for CSV files:

- duplicate-id-csv

e.g. for PO files (Maybe, If we look for if exists hooks related to PO files they could be already developed from another hook project, so use it instead):

- duplicate-po-message-definition

- po-msgstr-variables

So, IMHO in OCA we need to create a new project to push all these custom pre-commit hooks and add documentation of the useful projects replacing pylint-odoo checks.

The name proposal is oca/odoo-pre-commit-hooks similar to main hooks repository:

- https://github.com/pre-commit/pre-commit-hooks/tree/main/pre_commit_hooks

And we can (or not) enable the option to auto fix (we can even push checks without auto fix)

Check the following discussion about creating custom repository to detect and autofix:

- https://github.com/OCA/pylint-odoo/issues/375

Check the following discussion about deprecating duplicated checks if pre-commit supports:

- https://github.com/OCA/pylint-odoo/issues/267

Check the following plan to create a freeze branch in pylint-odoo with the current behavior in pro to create a new version with new focus and clean code, delete old unused checks, deprecate py2 and so on:

- https://github.com/OCA/pylint-odoo/issues/381

If you agree, Could you help us to create the repository in OCA, please?

--

Moisés López Calderón

Mobile: (+521) 477-752-22-30

Twitter: @moylop260

hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner

Twitter: @vauxoo

by Moisés López Calderón - 10:11 - 27 Jun 2022

Re: l10n-estonia status and proposing myself as PSC

Hello Alexey,

I just added your user to the l10-estonia PSC. You should receive the GitHub invite soon.

Best regards,

-sbi

On Thu, Jun 23, 2022 at 8:57 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:

What next steps do I need to take?

On Mon, Jun 13, 2022 at 11:02 AM Enric Tobella Alomar <etobella@creublanca.es> wrote:
+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.

Enric Tobella Alomar
Desarrollo
Av. J. V. Foix 63

08034 Barcelona

Tlf. 932 522 522 (Ext. 1621)

creublanca.es

From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC

Dear all,

It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).

Also, I'd like to apply for l10n-estonia PSC.

Kind regards,
Alexey

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

Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.

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

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

by Stéphane Bidoul - 11:10 - 25 Jun 2022

Archives

Contributors

Re: test mail

Re: test mail

Re: test mail

Re: test mail

Re: test mail

Re: test mail

Re: test mail

test mail

Tip: Always call `clean_action` when returning an `ir.actions.act_window`

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: l10n-estonia status and proposing myself as PSC

New repository oca/odoo-pre-commit-hooks and pylint-odoo deep refactoring

Re: l10n-estonia status and proposing myself as PSC

Follow us