Re: [Openerp-community] Licenses guidelines for OCA modules

Also agree to option b. Not to mention that if there should be an update to license it must be done in each and every .py file which is kind of nonsense and very impractical On Mon, Jan 5, 2015 at 5:21 PM, Leonardo "LeartS" Donelli < leart...@gmail.com> wrote: > I agree with Pedro. Copyright noti

Re: [Openerp-community] Licenses guidelines for OCA modules

I agree with Pedro. Copyright notices are bad/useless - Often outdated and incorrect (because copy pasted without modifications, for example) - Don't (can't) reflect the complicated situation of OCA modules autorship/contributions - useless from a legal point (see: http://hackerboss.com/get-rid

Re: [Openerp-community] Licenses guidelines for OCA modules

Avoiding heavy characters case is perfectly fine, better indeed and less stress for the eyes. Alejandro Santana alejandrosant...@anubia.es ~ ANUBÍA, soluciones en la nube, S.L. www.anubia.es El 5/1/2015 15:59, "Sandy Carter" escribió: > Avoid the # box, I find it very irking to have that many h

Re: [Openerp-community] Licenses guidelines for OCA modules

Avoid the # box, I find it very irking to have that many heavy characters like that. Besides: E265 block comment should start with '# ' (single space after the first hash). How about: # -*- coding: utf-8 -*- # # License, author and contributors information in: # __openerp__.py file at the root f

Re: [Openerp-community] Licenses guidelines for OCA modules

Le 05/01/2015 12:09, Yannick Vaucher a écrit : b. We define a minimal header template like this as an altenative (mostly taken from David Beal's proposal) I think this is the simplest option. I'd even drop line 2 "# Author: ". We should also not put the licence in __openerp__.py but rather in a

Re: [Openerp-community] Licenses guidelines for OCA modules

I put authorship, contributors and copyright info only in __openerp__.py. On other .py files I just use: # -*- coding: utf-8 -*- #License, author and contributors information in: # #__openerp__.py file at the root fo

Re: [Openerp-community] Licenses guidelines for OCA modules

I see perfect to reduce the overhead of the headers, because it's a nonsense, so I would say option b, but a recurring conflicting issue is about the copyright: this part doesn't reflect at all the reality of the code because: - People copy/paste from Odoo code and let Odoo copyright, which is

[Openerp-community] Licenses guidelines for OCA modules

Most developers dislike redundancy, thus, all are tempted to reduce the size of source code by reducing or completly removing redundant license from source files. [1] Moreover, when writing a module you often have py files with only few lines, thus the header takes a lot of place. I think it is t

Re: [Openerp-community] Per-field permissions

At first I was excited but then I tested some of it on runbot.odoo.com. It seems that this functionality was available in version 6.1 but is not in version 7.0 forward. Maybe it caused a performance issue? --Stephen On Mon, Jan 5, 2015 at 7:07 AM, Ludwik Trammer wrote: > I think point 2 is ac

Re: [Openerp-community] Per-field permissions

> > I think point 2 is actually solved in the openerp 7 itself. Refer > http://stackoverflow.com/questions/11580150/field-readonly-and-groups-attribute > also refer > https://answers.launchpad.net/openobject-server/+question/178779 > This would solve the first point from my letter, I believe. Unfo

Re: [Openerp-community] Maintainers needed for aeroo reports in OCA

Yeah, I was the one that it's going to do it, due to Kaspar Vilkens doesn't want to adhere to OCA. I'll do it next week. Regards. 2015-01-05 9:54 GMT+01:00 Holger Brunn : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > I remember this being discussed, but I cannot find the discussion >

Re: [Openerp-community] info on French localization in odoo 8

Hi, I feel confident enough with bzr-git transitions, would you like my help? I think I can pull the bzr branches and make PRs to the new github repo. Lionel Sausin 2014-12-17 16:54 GMT+01:00 Alexis de Lattre >: The main part of the l10n localisation is still on Launch

Re: [Openerp-community] Maintainers needed for aeroo reports in OCA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > I remember this being discussed, but I cannot find the discussion > in my mail archive... I think you mean this thread: https://github.com/OCA/reporting-engine/issues/1 - -- Therp - Maatwerk in open ontwikkeling Holger Brunn - Ontwerp en imple

[Openerp-community] Maintainers needed for aeroo reports in OCA

Hello, I remember this being discussed, but I cannot find the discussion in my mail archive... Is someone planning on proposing aeroo reports to OCA/reporting-engine? If not, I will make PRs to remove all addons depending on aeroo in the OCA code base. Best wishes for 2015 to everyone. -- Alex

Re: [Openerp-community] Odoo web multi-lang CSS

Hi, Would you suggest your module to the OCA here : https://github.com/OCA/web ? Regards, Joël On Wed, Dec 31, 2014 at 8:58 PM, Mohamed M. Hagag < mohamedhagag1...@gmail.com> wrote: > > Sorry the repo link ;) > > > https://github.com/mohamedhagag/dvit-odoo8 > > > > > On 12/31/2014 09:50

Re: [Openerp-community] Per-field permissions

Hi, I think point 2 is actually solved in the openerp 7 itself. Refer http://stackoverflow.com/questions/11580150/field-readonly-and-groups-attribute also refer https://answers.launchpad.net/openobject-server/+question/178779 On Fri, Jan 2, 2015 at 7:56 PM, Ludwik Trammer wrote: > *Note: I've al