Contributors mailing list archives
Re: Results of the 2015 Contribution Surveyby
AGPLv3 is not suitable for a CMS whereas LGPLv3 is"
Nevertheless, both parties agreed as well to protect the end user against license related legal proceedings. AGPLv3 constraints should apply to the developers of modules, not end-users.
We agreed that an end-user can run Enterprise Edition Proprietary modules and AGPLv3 modules together if said modules do not depend on each other and depend only on core LGPLv3 modules. In other words, any module must be compatible and respect the license of its dependencies defined in the “depends” key of its manifest file.
The end-user cannot be held responsible of the choice of license from the developer. The later is fully responsible to properly license his/her work.
the purpose of the CLA is to allow the OCA to protect the contributors' interests
Hello Cori,Please find below the list of current Board Members:
- Joël Grand-Guillaume, Camptocamp (C2C)
- Eric Caudal, Elico Corporation
- Stéphane Bidoul, Acsone
- Maxime Chambreuil, Savoir-faire Linux (SFL)
- Sylvain Le Gal
- Luc Maurer, Camptocamp
- Sébastien Beau, Akretion
- Pedro M. Baeza
- Alexandre Fayolle, CamptocampDominique Chabord is neither a member nor a contributor of the OCA.The license has been debated long enough last year. I understand you were not part of it. So I suggest you take a look in the mailing list discussions and the blog post on the OCA website:If you have additional information to justify re-opening the debate, please share them.If you are not happy with the OCA decision on this matter, I encourage you to join the OCA Board, so you will be able to take decisions and explain them to the community.Regards,2016-01-15 5:23 GMT+01:00 Cocopapa <firstname.lastname@example.org>:Hi Maximeyou wrote:Please share yours.I think you are completely missing the point what is really the major problem with OCA!No time is for sure no real answer to those problems but I think what Dominique Chabord of SiSalp brought up in another post hits really the point.BUT, OCA has decided, as a shared-copyright holder of all OCA AGPL modules to allow proprietary modules along with OCA AGPL modules with Odoo 9, provided the dependency between proprietary and AGPL is not explicitly documented in __openerp__.py of the proprietary module ;-). That means for me that OCA grants the permission for license violation on all OCA AGPL modules.It brought up a very serious concern and verified many concerns already made by others on the mailing-lists in the past years.Who is the OCA really?Who is the actual legal body of the OCA that such statements like of Dominique Chabord can be made public!https://www.odoo.com/groups/community-59/community-16127681?mode=date&date_begin=2015-12-31&date_end=2016-01-31The fact that OCA grants permission for license violations is IMHO a criminal act if that gets even promoted like that publicly.What does the C in OCA really stands for?I thought the OCA helps to secure AGPL v.3 developers interests, but now we are very very confused and even more sceptical than before about the future of a Free and Open Source Odoo Community Version after OCA promotes license violations and formally grants the violation right to any developer which means also to ODOO S.A. so they don't need to follow any licenses as they get fully backed by the OCA.---Under those circumstances I am really worried about the future of a feature rich Odoo Community version. I actually would even recommend all developers who love and work for a Free Open Sourced Odoo Community Version to form a new Entity which does not get influenced by OCA or ODOO S.A. . Under those circumstances it is really no wonder that not more people like to publish their code under OCA, as they would open it up for multiple license violations. For sure for us OCA is an absolute no go after the statement which Dominique just made. I am really sorry for that!I hope many other will help to form a new organisation which is not influenced or depending on ODOO S.A.. OCA seems to be only a branch of them to keep the community down. We discussed this already with some other friends and developers and came to the point that there is really the need to find a new way for the community to interact with each other without fear that the OCA or ODOO S.A. is promoting License violations.With kind regardsCoriOn Thu, Jan 14, 2016 at 9:23 PM, Maxime Chambreuil <email@example.com> wrote:Hello,The survey also shows it was answered mostly by current contributors and mostly developers. It also shows that we can't ask more to those people (no time).I tend to think we should focus on organizing events and encourage more new people to join and contribute, but that's my personal analysis.Please share yours.
This is what happens when you don’t drink coffee, I left out sections specifically aimed at eliminating barriers and making contributions more effective.It’s hard to comment on these because they specifically ask what can be done better, but not how urgently or strongly the change is needed. Some people may be suggesting something just because they’re asked. But it’s an interesting contrast to the graphs which were saying that people are quite competent with git, etc. I’m curious how other people interpret these answers together…
IMPORTANT NOTICE: This email is intended only for the use of the Person(s) to whom it was addressed. It may contain information which is privileged & confidential. Any dissemination, distribution, copying, or other use of this message, or any of its contents or attachments by any person other than the intended recipient may constitute a breach of civil or criminal law and is strictly prohibited. If you are NOT the intended recipient please contact the sender and dispose of this email as soon as possible.Hi Cocopapa,Based on the results in the survey publication only about 12% of people believe that OCA is too close to Odoo SA. The question was posed in the negative, which is why you may have interpreted it differently.The answers in the graphs suggest that people do know: how to use Github, how to find modules or how to test modules.A few of the long answer questions do confirm your hypothesis. 6/22 for the initial long answer section and 1/7 in the “comments” responses support your concerns. If this trend is true of all the data — which is unlikely, as I believe the responses chosen for publication were put there to show a variety of opinions as opposed to a random sample — then we’re talking about 14% are confused over how to get started/what to do and 11% are concerned with how close the OCA is with Odoo SA and protecting the interests of contributors. But because these responses are chosen on purpose, I presume that even fewer people fall into those two groups.Someone correct me if I am wrong. My suggestion for future surveys is not to use a display of data containing double negatives (“I don’t know…” + “fully disagree” = I do know).
IMPORTANT NOTICE: This email is intended only for the use of the Person(s) to whom it was addressed. It may contain information which is privileged & confidential. Any dissemination, distribution, copying, or other use of this message, or any of its contents or attachments by any person other than the intended recipient may constitute a breach of civil or criminal law and is strictly prohibited. If you are NOT the intended recipient please contact the sender and dispose of this email as soon as possible.Thanks for the results.
They show that OCA should be more actually an own body no more so much depending on ODOO Main Company and their roadmap.
It would be in deed very interesting to hear more about the OCA Roadmap.
Do you have at all one? If not why not?
Many developers who answered seem to be afraid of contributing. Either because of that their work gets used afterwards in commercial projects by ODOO S.A. or also because they don't understand how to contribute at all!
Perhaps it would be a good idea if you publish a tutorial step by step guide on how to use all those tools like github travis etc and how to contribute.Dear Contributors,Please find below the results of the 2015 Contribution Survey:If you have any questions or want to share your analysis and things the OCA should do, please reply in this thread.Cheers,