Contributors mailing list archives
Re: Recommended Contributor Tooling (RCT)by
David Arnold BA HSG / Analista
315 304 13 68/ email@example.com
devCO - empresa de consultoría de sistemas (en fundación)
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
On Tue, Oct 20, 2015 at 10:22 PM, Florent Aide <firstname.lastname@example.org> wrote:Hi all, I'll answer some point below. 2015-10-20 22:08 GMT+02:00 Raphaël Valyi <email@example.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.