Tools mailing list archives

tools@odoo-community.org

Avatar

Re: [TOOLS] Hello and Proposal to decide upon.

by
dar@devco.co
- 22/10/2015 20:44:54
That's perfect, I'm also in favor of separating concerns. The other tool is quite optional tooling, so there is no need to base soemthing upon that... and thus not necessary to include into OCA.

El jue., 22 oct. 2015 a las 14:21, Alexandre Fayolle (<alexandre.fayolle@camptocamp.com>) escribió:
For the record, I'm not favorable to including tools written in golang
as part of the OCA projects, as this causes maintenance issues (the
exceptions being to tools to interface odoo with other languages e.g. by
providing an API over odoo's xmlrpc interface)

Alexandre

On 22/10/2015 20:55, David Arnold wrote:
> Dear Tools PSC,
> 
> You might wonder, if this is cannibalizing with my independent
> initiative about a golang command line interface
> (https://www.odoo.com/de_DE/groups/community-59/community-14523754?mode=thread&date_begin=&date_end=)
> 
> The answer is NO. The golang project, is just a fun project to see if it
> works and how far I would get. This initiative is about OCA docker base
> images only. It aims to funnel them through an open design process.
> 
> Best Regards, 
> 
> David
> 
> El mié., 21 oct. 2015 a las 10:33, David Arnold (<dar@devco.co
> <mailto:dar@devco.co>>) escribió:
> 
>     *Hello Everyone*
>     *
>     *
>     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 want to take responsibility in leading a design process in the
>     advent of a converging oca docker image architecture. I probably
>     don't have public record on the odoo framwork, besides of this
>     contribution: https://github.com/savoirfairelinux/server-tools/pull/3/files,
>     but I basically grew up with docker and contributed on various
>     occasions with smaller stuff such as
>     here: https://github.com/docker/machine/pull/2003 or other bug
>     hunting, there.
> 
>     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.
> 
>     
> 
>     *Saludos Cordiales*
>     David Arnold
>     ​ 
> 
>     David Arnold BA HSG / Analista
>     315 304 13 68/ dar@devco.co <mailto:dar@devco.co>
> 
>     *devCO - empresa de consultoría de sistemas (en fundación)*
>     http://www.devco.co
> 
>     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.
> 
> _______________________________________________
> Mailing-List: http://odoo-community.org/groups/tools-22
> Post to: mailto:tools@odoo-community.org
> Unsubscribe: http://odoo-community.org/groups?unsubscribe
> 


-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
http://www.camptocamp.com

_______________________________________________
Mailing-List: http://odoo-community.org/groups/tools-22
Post to: mailto:tools@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

Reference