Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Recommended Contributor Tooling (RCT)
by
rvalyi@akretion.com
On Tue, Oct 20, 2015 at 10:22 PM, Florent Aide <florent.aide@xcg-consulting.fr> wrote:
Hi all, I'll answer some point below. 2015-10-20 22:08 GMT+02:00 Raphaël Valyi <rvalyi@akretion.com>: [...] > So I feel like you are discovering the topic and trying to impose your views without knowing your subject... > We are not trying to tell the OCA to adopt Voodoo at all or our side (but we are not against), we are just telling the OCA should not submit > itself to pressures from lobbies to impose their own tooling, before even they exist or get any adoption. I think the OCA should consolidate the best practice as acknowledged by its prominent members, it should not try to impose dogms from projects that don't even have any adoption yet. Should I understand our docker build is the subject of this remark?
Hello Florent,
I was only answering here to David Arnold because he was first rejecting Docker Compose to orchestrate the PG and Odoo images at least on a dev machine (like we do in Voodoo) while at the same time he would suggest solutions totally unrealistic such as embedding a Docker Compose container inside a Docker container, meaning running into all the data corruption issues of the Docker in Docker hack.
I never critized your work or even the work of Eric, I just mentionned ours is different and there are so many different approach to this topic that unless you run into blattant contradiction ad David did many options are valid and I don't want to the the OCA impose arbitrary decisions on such moving targets.
Regards.
Reference
-
Recommended Contributor Tooling (RCT)
bydar@devco.co-
Re: Recommended Contributor Tooling (RCT)
byXCG Consulting, Houzéfa Abbasbhay