Contributors mailing list archives
Re: OCA Dev & Deploy Tooling PSCby
Did you solved at least 1 issue?
David Arnold BA HSG / Analista
315 304 13 68/ firstname.lastname@example.org
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.
I agree with Nhomar. Only when you have made plenty of contributions, you can then talk with full knowledge about how can this be improved, but you need that walk.Regards.2015-10-21 16:08 GMT+02:00 Nhomar Hernandez <email@example.com>:On Wed, Oct 21, 2015 at 12:23 AM, David Arnold <firstname.lastname@example.org> wrote:Hi,
I want to suggest and solicit the creation of OCA Dev & Deploy Tooling PSC.
I want to take responsibility in the PSC and ensure thereby a technical and well-informed discussion.
I further want promote convergence and best practices in the OCA on this topic, keeping an eye on the needs of newcomers.
If this finds approval, I would like to convocate an open design process on the creation / convergence of a comprehensive set of base docker images, that are suitable for production and Dev and compatible with existing (anybox) as well as embrace new tooling.
In a next step, I would like to focus on the Dev sugar, because this is where there is a real perceived lack of coolness ;) in the existent tooling.
In some future I would like to open up discussion about possible deployment techniques. However, I feel this is many steps ahead still & with anybox, we have a "running horse". ("Never change a running horse")
I would like to have anyone especially interested in this topic and with sufficient technical knowledge in the field to express his interest in taking responsibility in the PSC.
I'm furthermore committed to aport to a better OCA culture. (I admit, I'm not happy with the current state.)
David.Again, I do not know how explain this.If you are not commited to make the first design/development, I really do not understand which is the process you want to propose.You want bring to some place a set of expert to solve the issues you see, then put the free in some other place just after you give a bless? (that's what I understand here with your proposals).You have the tools available (and some of them unfinished yet) but if you do not give spefic feedback or specific code to them it is difficult to grow up, the code is not done by itself just with good willing....In other hand, Can you try to give/test existing projects? because all what I read is complex to understand and is show a lot o leak of knowledge, which probably are solved already.Did you "at least" give some 1 or 2 +1 in any project related to OCA already?Dd you try the runbot with OCA PR?
Did you solved at least 1 issue?I mean: I'm furthermore committed to accept that we maybe we need a better OCA culture. (BUT I admit, I'm not happy with your current way of work.)But I think mantainer-quality-tools is the place already, maintainer tools is other one.... Why push in other direction/project than the one that help us all and impact directly the benefit of 100% of repositories availables?:-1: for me.--