Contributors mailing list archives

Browse archives


Re: Move purchase_request* and purchase_work_acceptance*

Acsone SA/NV, Denis Roussel
- 21/12/2021 11:49:32
I agree with Pedro.

The amount of modules is not the only factor to take into account.

The aim of a repository is also to group functionally modules that do 'quite' the same things and has a specific meaning (I don't like *-workflow stuff as it is too generic - @kitti don't create  purchase-extra-workflow as it adds abstraction and has no meaning).

To find modules, we have our shop that leads to the good repository (we maybe need to do marketing on this)

On Tue, Dec 21, 2021 at 11:27 AM Pedro M. Baeza (Tecnativa) <> wrote:
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:

- Avoid potential conflicts between them.
- Reduce tests size.

On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.


Post to:


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