I'm new to this list. You probably know me for my outright (and sometimes not so diplomatic ) speaking on the general community lists.
I have also developed an own docker sugar, based on bash, here: https://github.com/DevCOco/odoo-docker
which has some sweet spots. If you're interested, you can try it out. The "help" command would guide you.
Due to the recent rush in the general mailing list, I want to propose an open design process, a practice, basically copied from the docker ecosystem, where I have taken part in various smaller occasions.
I would like to tag this initiative "Dev & Deploy Tooling Initiative". I want this to be a home for different approaches to peacefully coexist and eventually converge.
I want to take significant charges as to the steering of such process (because I feel, that's where I can excel, granted the blessing and backup of the existing authorities).
If this is good, I would ask you to give it a formal blessing and institutionalize what's necessary. Once this is approved, I wold be happy to prepare a comprehensive design document of the iniciative, a roadmap obviously not missing a "state of the art gathering".
So I kindly ask the members of this PSC to decide on this initiative. I understand the risks, given my reputation, but on the other hand, I think everyone who is willing to contribute, is protected by the OCA guidelines.
I'm also open to couple this responsibility to some kind of patronage, to mitigate the last point.
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.