Skip to content

Conversation

@adasatorres
Copy link
Contributor

There is already an addon that provides this same functionality in the project-agile repository. This addon should not exist here, as it creates conflicts between the two. Due to its precedence, it is preferable to keep it in the other repository and implement any necessary improvements there.

@adasatorres
Copy link
Contributor Author

#1538

@pedrobaeza pedrobaeza added this to the 16.0 milestone Jul 15, 2025
Copy link
Contributor

@leemannd leemannd left a comment

Choose a reason for hiding this comment

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

Hello, shouldn't we keep the module in older versions and prevent it to be migrated? There are maybe people that are using it. Removing it from the repository will make it disappear when they update the submodule.

I'm more in favor of updating the README to ensure people don't migrate it.

@pedrobaeza
Copy link
Member

The problem is that there can't be in OCA 2 modules with the same name, or some automation will fail, like the apps store.

@leemannd
Copy link
Contributor

I agree. It can lead to failure.

I have taken time to:

What I am currently thinking is that the repository project-agile is hosting only one finished module that is project_scrum.
From what I understand, it was created to land project agile/scrum and JIRA like modules. They have never been merged.

We currently keep this other repository for only one module. Seeing that I must confess I am more in favor of bringing into this repository the features from the other one.

Aside that I don't know the automations, especially the one from the app store. Will it fails also if we set one of the two modules as uninstallable?

@pedrobaeza
Copy link
Member

I'm not able to answer that right now. @petrus-v is checking the modules of the apps store.

@petrus-v
Copy link
Contributor

petrus-v commented Aug 5, 2025

I don't know that much the source code, I've just start to maintain some part of it, I think it's possible that the product description will blink between both modules:

Personally I don't use the app-store and I'm wondering if some of us use it to install their odoo? The main impact it probably marketing. My main concerns is regarding module published on pypi.org. It makes no sense to have two modules with the same name maintains in different repositories. Even without pypi it will be very confusing to know which one is the good one you want to maintain as developer.

Personally moving a module by removing the repository or disable the module with a clear message that it has been move somewhere else is acceptable. If we want to maintain 2 different modules with different functional approach you can see 2 options:

  • contact the former author and see if you agree to on a same way to work
  • Rename your module to avoid naming conflict and could be nice to explain in module description what's the different approach with the former module

@pedrobaeza
Copy link
Member

@petrus-v a lot of people like me use the app-store to discover OCA modules by searching through keywords.

@petrus-v
Copy link
Contributor

petrus-v commented Aug 5, 2025

I'll try to keep track, once this is merged and https://github.com/OCA/project-agile/ a PR is merged to make sure appstore is properly updated. Please ping me if you feel there are something wrong while moving those modules.

(Time to refresh all OCA modules is around 24h)

Copy link

@edescalona edescalona left a comment

Choose a reason for hiding this comment

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

LGTM

@leemannd leemannd dismissed their stale review August 7, 2025 06:53

Dismissing my review. I don't want to block fixing a technical issue.

Personally I don't see the point in having the submodule project-agile which hosts only one module. I personally think that if we have project_scrum that has landed into this repository it means that people are not aware enough of this other repository.

I am in favor of keeping project_scrum in this repo and to remove project-agile.
If you want to keep project-agile I think we should update the description of this repository to add a pointer to project-agile.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants