Skip to content

[ADD] Proposal new repository Complaint and Infringement Management (CIM)#100

Merged
pedrobaeza merged 1 commit intoOCA:masterfrom
moval-agroingenieria:moval-add-repo-cim
Jun 26, 2025
Merged

[ADD] Proposal new repository Complaint and Infringement Management (CIM)#100
pedrobaeza merged 1 commit intoOCA:masterfrom
moval-agroingenieria:moval-add-repo-cim

Conversation

@moval-agroingenieria
Copy link
Copy Markdown

We have developed a module named cim_channel, which addresses the requirements set by recent European regulations mandating organizations to provide an internal channel for reporting complaints and whistleblowing.

Following discussions with the community, we believe that a new repository is the appropriate path forward. We propose naming it Complaint and Infringement Management (CIM).

We have added the necessary entries under the conf and psc directories, and our company has been designated as the repository maintainer.

The source code is available at: https://github.com/MovalAgroingenieria/cim

Copy link
Copy Markdown
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question, you setted moval-agroingenieria as PSC, but it is related to a Person or the whole team? I would prefer to assign PSCs to persons.

@moval-agroingenieria
Copy link
Copy Markdown
Author

One question, you setted moval-agroingenieria as PSC, but it is related to a Person or the whole team? I would prefer to assign PSCs to persons.

We use moval-agroingenieria to represent our entire development team. However, if individual maintainers are preferred, we can update the PSC entry and assign our technical manager as the designated point of contact.

@rousseldenis
Copy link
Copy Markdown
Contributor

One question, you setted moval-agroingenieria as PSC, but it is related to a Person or the whole team? I would prefer to assign PSCs to persons.

Agree, that's defined in bylaws

@etobella
Copy link
Copy Markdown
Member

One question, you setted moval-agroingenieria as PSC, but it is related to a Person or the whole team? I would prefer to assign PSCs to persons.

We use moval-agroingenieria to represent our entire development team. However, if individual maintainers are preferred, we can update the PSC entry and assign our technical manager as the designated point of contact.

Please, do it, I will prefer to assign PSCs as persons, not entire development teams.

@rousseldenis
Copy link
Copy Markdown
Contributor

@moval-agroingenieria

@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza
Copy link
Copy Markdown
Member

@moval-agroingenieria can you move to individual agents as requested?

Copy link
Copy Markdown
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@moval-agroingenieria Please apply the requested changes.

Comment thread conf/repo/cim.yml Outdated
Comment thread conf/repo/cim.yml Outdated
@etobella
Copy link
Copy Markdown
Member

Can you squash all commits in a single one?

Copy link
Copy Markdown
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unblocking the PR, however, @einiesta has no collaborations within the OCA. I don't know if this is a problem

@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza pedrobaeza merged commit 4285d1f into OCA:master Jun 26, 2025
1 check passed
@moval-agroingenieria moval-agroingenieria deleted the moval-add-repo-cim branch June 27, 2025 07:13
@moval-agroingenieria
Copy link
Copy Markdown
Author

Nice: https://github.com/OCA/cim, thanks for the approval.

We're refining the code to comply with code quality guidelines. We'll submit a PR next week.

@einiesta
Copy link
Copy Markdown

einiesta commented Jun 27, 2025 via email

@pedrobaeza
Copy link
Copy Markdown
Member

OCA CLA is not archived in OCA/OCB. That's for Odoo CLA (being OCB a "copy" of odoo/odoo). It's archived internally, and tag on the OCA Odoo that synchronizes with GitHub.

@einiesta
Copy link
Copy Markdown

Ok, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants