Code review comment for lp:~numerigraphe/openobject-addons/trunk-l10n-eu-nace

Hello,

Also we should adopt convergent standard here whenever possible. Like in
Brazil our "NACE" is actually called "CNAE". To have an OpenERP that will
play nice with several localizations at the same time or modules that
work across localizations, we should first work together to make those keys
uniform even if data would be loaded by some localization extension modules.

On Wed, Dec 21, 2011 at 12:10 PM, Olivier Dony (OpenERP) <email address hidden>wrote:

> Hi Lionel,
>
> The 2 nomenclature modules (l10n_eu_nace, l10n_fr_naf_ape) your are
> proposing would be a great addition to OpenERP Apps, but we'd rather not
> include them in the standard distribution (not to mention that l10n_eu_nace
> weighs 24Mb).
>
> BTW, I think it's great that you included the source of the RAMON
> nomenclature with a conversion script, rather than simply the resulting XML
> output.
>
> Thanks for your understanding and your excellent work in the community, it
> is greatly appreciated!
>
> PS: for reference, our merge proposal acceptance policy is available at
> http://bit.ly/openerp-contrib-mp
> --
>
> https://code.launchpad.net/~numerigraphe/openobject-addons/trunk-l10n-eu-nace/+merge/85315
> Your team OpenERP Localization Experts is requested to review the proposed
> merge of lp:~numerigraphe/openobject-addons/trunk-l10n-eu-nace into
> lp:openobject-addons.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-localization
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openerp-expert-localization
> More help : https://help.launchpad.net/ListHelp
>