Community mailing list archives
Re: git mailmap, CLA and blame, licenseby
We will keep localization as it is now, for all countries: chart of accounts, taxes, configuration by default. So, you will be able to use all countries in v9 for accounting.
For a few countries, we will do much more: bank interfaces, legal reports in the format of the countries, country best practices...
For countries that are not in our priorities, the CoA and taxes will be in the core and other features should be implemented in community modules (like in v8)
Thank you Anthony,Regarding localization, maybe I missed it, but what are the localizations that will be included in version 9 ? If a localization is not selected and the community moves it to a different project, should the community make a PR against master to remove it or Odoo SA will do it ?Thanks!--
Maxime ChambreuilIn the past Openerp SA was strongly criticized for neglecting legal aspect of copyright and code ownership. I'm sorry for that. This time we want to make things perfectly clean and thorough. About CLA: Friday with Olivier Dony did setup a CLA process. Everything is explained here. https://github.com/odoo/odoo/blob/8.0/doc/cla/sign-cla.md I created a runbot module to check the cla. https://github.com/odoo/odoo-extra/blob/master/runbot_cla/runbot.py About mailmap: This week-end i attacked myself to the daunting task of code attribution the goal is to identify every line of master HEAD (and maybe 8.0 HEAD). The benefits is that we will get a perfectly clean "git blame" and "git shortlog -nse". You can check my work here: https://github.com/odoo-dev/odoo/blob/8.0-mailmap-al/cla-stats.txt Script to generate it: https://github.com/odoo-dev/odoo/blob/8.0-mailmap-al/cla-stats Git mailmap file https://github.com/odoo-dev/odoo/blob/8.0-mailmap-al/.mailmap If you have any suggestion or correction about the mailmap file, contact me or make a pull request on my branch. Once the mailmap file is complete we will merge it into master. Why are they so few external code contributors 3% ? - Odoo: framework + ALL addons + web client and website is only 150k lines of code. The same size as django (which only a framework). - Because Odoo is a good framework, it very modular so that developpers prefers creating their own module and extend it instead of patching the addons code. Only when it's not possible people makes patch to change the core. - We get bugfixes and typos but it's only a few lines. And usually bugfixes are rewritten to cover all the use cases. - We often rewrite bug chunk of code: - new qweb report (all rewritten), - new wms (all rewritten) - new api (many lines rewrite, all is expected to be converted). - new accounting (all rewritten, in progress) - There might be error or misattribution i'm waiting for your feedback. Why are they so few external xml contributors 20% ? I excpect it's more than that. We need the carefully check all l10n_* commits. However in master we will rewrite every l10n module as part of our new accouting system. Why are they so MANY po contributors ? Translation takes the most diskspace of the repository and it's almost 99% community contributed. Dont forget that. About License: The offcial statement of Odoo has been published on the website. My personnal belief (as antony not Odoo) is a that a switch to LGPL is very much welcome as wee moved from an ERP to and ERP and Web framework. - Odoo may now become a web framework, along django, rails etc... Companies and developers will only consider investing on a platform that protects their intellectual property. - Partners and community members MAY become ISV instead of beeing service providers only. Some of them already do and it's a grey area. It's now easily possible and encouraged. Nobody is forced to change anything we keep the best of both world. - We hope to attract theme and graphic designer to the platform like other open source cms/e-commerce (wordpress, drupal, joomla, magento, prestashop ...). It's very exciting time for Odoo.