Contributors mailing list archives
Re: OCA Coding Standards and recommended IDEsby
Objective: make a great Odoo ecosystem.
Actual Materials: team of specialists working so hard to make such ecosystem technically viable.
Reality: we are not as much as we need.
We are more like the Linux kernel "little tools that do things great".
I very much appreciate your reasoning here and it is very understandable!!!
Throughout all my comments, inputs, feedbacks etc. it becomes clear, that I'm very committed to change the point you tagged "Reality" from an ecosystem point of view. Odoo is not Microsoft or Apple, but, yes, I believe it has Docker potential, or at least something similar. Why? Because it has a real impact on the business landscape of the real goods industries... I'm committed to work towards unleashing this potential and I perceive that many from the "inside" don't share this vision or probably do not understand or acknowledge the needs. It is sad, because it possibly closes down the opportunity to improve the point you tagged "Reality". It is sad also, that many initiatives to make the whole thing (OCA) more dynamic (and in consequence more attractive to talent!!!!!!!!!!) are cut down at the very root.
Maybe it is time to let new things happen and give them a chance and just observe throughout the way if they are for the good or the worse. This is the kind of dynamic evolution I wish OCA to adopt. It will be very attractive to the greate slumbering (young) talent in the Odoo ecosystem. Remember, most of you are veterans! I'm just a (joung) spokesman in this show, defending a more dynamic future of the OCA. You need to attract the new generation, which are in their 20ies around the world, they will change the ERP market of tomorrow, so please make a move forward and listen to them!
At the bottom line, the point you tagged "Reality" is even the best prove, that things are being done wrong. It becomes obvious if you compare the 802 watchers, the 3252 stars and the 2866 forks of the odoo repository, that's roughly a tenth of the docker ecosystem. But I ask retorically: Does OCA activity correspond to a tenth of the activity in the docker ecosystem?
I hope those lines make you, dear reader inside the OCA, think.
Anyhow, those are just my 2 cents.
El vie., 16 oct. 2015 a las 16:23, Nhomar Hernandez (<email@example.com>) escribió:
On Friday, 16 October 2015, David Arnold <firstname.lastname@example.org> wrote:>The only way to think to benefit to everybody, is think pythonistic. "Program Once and very good ;-)"I disagree on this point and support Oleg's point. To understand his concerns you need to adopt a more holistic perspective. It's not a question about yet another python package.I understand that many of you have objections about standard tooling, because you already use something. But this does not help anyone. You need to understand that such recommendation is not for you, the experienced programmer. The tremendous value lies in a more dynamic ecosystem. It's not about you, who is acquainted with OCA, it is about you, the one, who just heard about odoo two days ago. Outside-In perspective, not Inside-Out. More Contributors. Easyer onboarding. Better productivity. More dynamic. Who can seriously tell me that those are not VERY valuable goals, that can be easily achieved by this move?? Or did I miss something?Yes you miss something.Objective: make a great Odoo ecosystem.Actual Materials: team of specialists working so hard to make such ecosystem technically viable.Reality: we are not as much as we need.Then, your holistic point is good, your intention is good, but basically we are not Microsoft or Apple which will mantain a set of "wao tools" for the masses.We are more like the Linux kernel "little tools that do things great".If somebody think they can afford such deal "great!" But I personally prefer a very well tested Python package agnostic to any brand/ide which can be improved by 100% of our ecosystem, than a half finished set of plugins which will be maintained by the partial community which use one or other privative tool (remember even if I love pycharm and accept sublime are good the actual versions are not 100% open source and that's fine for me but it is a fact you need to consider).Then if somebody like it and want to contribute correctly, again, program under Python standards use standards tools and then use the development for the plugin they want I named at least 10 options.Regards.A "recommendation" or just a "hint" neither is binding. OCA is a soft authority. Everyone's free - you have been warned! :)Best Regards, DavidEl vie., 16 oct. 2015 a las 14:53, Nhomar Hernandez (<email@example.com>) escribió:Regards.The only way to think to benefit to everybody, is think pythonistic. "Program Once and very good ;-)"In our team we have people that use several different IDE, by myself I use VIM and pycharm and tried sublime but we have a lot of others, ninja-ide is other very good one, gedit, etc, etc, etc....The best technical way is think as "a python package" and not as a "plugin for X IDE", then if you want develop a plugin for the tool you use which use the features on mqt, then cool! we can considere have such project, BUT taking care that the python package is aways who makes the job.Recommend a tool is not correct, due to this is so so subjective and it do not add any value by itself whta really add value is the fact that you can improve such mqt project proposeing solutions with issues found in such IDES (but those solutions should be proposed without brake any actual feature with another tool).Hello Oleg.Actually we have a huge job already done around a python package which include a huge set of tools IDE's agnostic, which you can include in your decided IDE as a normal python tool (like Flake8 or Pylint config files).Dear Contributors,I would like to bring up discussion about coding standards and also recommended for developers IDEs.1. Regarding coding standards that is already well described here https://github.com/OCA/maintainer-tools/blob/master/CONTRIBUTING.md2. Additionally I would like to suggest to OCA to standardized development environment. Of course, not to force everybody to work in some particular IDEs, but define list of supporting one. So my recommendations for IDEs based on experience in my company are:- PyCharm- Sublime TextNote that point 2 also requires development of standard helper configuration for IDE/Editors validator. And most likely snippets.Fr example, for Sublime there is plugin https://github.com/dreadatour/Flake8Lint that adds pep8 validator. And also for snippets there is https://github.com/sotogarcia/sublime-odoo-snippetsHow about creating OCA forks that will help developers to quickly install necessary addons to one of supported editors and start writing code according to standards? Are there already plans on doing this or some work in progress?
Sent from my mobile.