Community mailing list archives
Re: New OCA repository to suggestby
Pedro M. Baeza
@rvalyi, I agree that in that context, 1 repo = 1 module would be ideal, but we are stil very far from this tooling and resources for being able to handle this. As Joel has said, administrative work has been a lot. That's why I say of reducing the number of projects.Regards.
2014-09-19 17:11 GMT+02:00 Raphaël Valyi <email@example.com>:
On Fri, Sep 19, 2014 at 11:19 AM, Pedro Manuel Baeza Romero <firstname.lastname@example.org> wrote:My suggestion was to avoid too much projects, but it that it's not problem, go ahead!I may be wrong, but I feel it's always easier to have tooling to configure multiple repos and show consolidated indicators of them than deal with an evolution of stale cross dependencies cross firing in a growing chaos. Also, if at some point we are able to set projects or team that gather several repos, I'm actually in favor of that. But I personally prefer not moving too far away from 1 repo = 1 module that proved to be a working design pattern in so many other successful projects already (that didn't attempted to re-invent module packaging though).--