1. Mailing Lists
  2. Contributors
  3. Re: OCA module not showing in app store due to name conflict

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: OCA module not showing in app store due to name conflict

Re: OCA module not showing in app store due to name conflict

Avatar

Re: OCA module not showing in app store due to name conflict

by
Elico Corp, Eric Caudal
- 03/03/2017 08:28:28

I wouldnot either. They have always worked with us in good faith.
Problem is it is always better a bad agreement than a good lawsuits...
All the more that we are probably talking few thousands euros profit (if it gets there...) while costs and risks in this kind of actions are unpredictable.

They look to be rather suspicious and a thorough analysis of their code from Odoo would easily lead to the right conclusions.

 I'd rather have the company properly warned or banned (temporarily or not) as an example from the apps store with the proper publicity towards counterfeiters.


------------------
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore)
Odoo Gold Partner // Best Odoo Partner APAC 2014 and 2016
 
 
 
------------------ Original ------------------
Date:  Fri, Mar 3, 2017 03:08 PM
To:  "Contributors"<contributors@odoo-community.org>;
Subject:  Re: OCA module not showing in app store due to name conflict
 
I wouldn't include Odoo SA directly in the suit, since they "hopefully"
didn't allow it by purpose, but i would tell them (as OCA) that i
insist in having dependencies checked and suspicious modules
automatically remove (or even better not allowed in the first place)
and allow them to act before OCA hands in the law suit. However as an
ordinary OCA member i'd also recommend to make up a law suit just to
put an example. 

BTW: one of the best lawyers in the field is Dr. Till Jäger (co-founder 
of ifross institute (http://www.ifross.org/personen). He and his guys
at ifross a worldwide well known specialists on law with focus and
free, libre and open source software.

Am Freitag, den 03.03.2017, 02:38 +0000 schrieb Graeme Gellatly:
> Sorry but if its the same people its simple.  OCA needs to get a
> lawyer/legal advice/SFLC involved and should expect all of the
> proceeds from the sales of ripped off modules illegally licensed. 
> Preferably with exemplaries and maybe consider joining Odoo SA to
> that suit for allowing it in the first place. You'd expect by now a
> company like this one would be banned forever.   I just checked that
> companies modules and didn't find an original module.  Everything I
> checked was either copied from an open source contributor or taken
> from forum advice. (after 4 I gave up checking)
> 
> On Fri, Mar 3, 2017 at 2:08 PM, Eric Caudal <eric.caudal@elico-corp.c
> om> wrote:
> > If they already have a bot checking OCA dependencies, it is quite
> > simple. Their algorithm should flag as well as suspicious the
> > modules with commented OCA dependencies.
> > 
> > 
> > 
> > Eric Caudal - Sent from my mobile device
> > 
> > 
> > -------- Original message --------
> > From: David Lasley <dave@dlasley.net> 
> > Date: 2017/03/03 02:23 (GMT+08:00) 
> > To: Contributors <contributors@odoo-community.org> 
> > Subject: Re: OCA module not showing in app store due to name
> > conflict 
> > 
> > I opened a third ticket on website_faq after auditing their modules
> > - it also has dependencies commented out.
> > 
> > I also requested a proactive audit by Odoo SA.
> > 
> > — Dave Lasley
> > 
> > > On Mar 2, 2017, at 10:08 AM, Jay Vora <vora.jay@serpentcs.com>
> > > wrote:
> > > 
> > > Interestingly, that firm has sold many modules!
> > > 
> > > On Mar 2, 2017 11:23 PM, "David Lasley" <dave@dlasley.net> wrote:
> > > > I went ahead and issued the reports, probably should have done
> > > > that instead of just recommending.
> > > > 
> > > > I will update this thread with findings.
> > > > 
> > > > Note there are two independent issues opened, one for
> > > > theme_louma and one for auth_verify_signup_email
> > > > 
> > > > — Dave Lasley
> > > > 
> > > > > On Mar 2, 2017, at 9:38 AM, David Lasley <dave@dlasley.net>
> > > > > wrote:
> > > > > 
> > > > > I have had a few infringing apps removed from the store at
> > > > > this point. I agree that Odoo SA needs some automation in
> > > > > place, but they are also very receptive regarding this via
> > > > > the apps@odoo.com email. 3-4 days and the modules were
> > > > > confirmed as license violations & removed from the store. I
> > > > > recommend we do the same here.
> > > > > 
> > > > > — Dave Lasley
> > > > > 
> > > > > > On Mar 2, 2017, at 12:23 AM, Sylvain GARANCHER (SYLEAM)  > > > > > lvain.garancher@syleam.fr> wrote:
> > > > > > 
> > > > > > Hi,
> > > > > > 
> > > > > > According to someone that bought it, another module on apps
> > > > > > from the same author (https://www.odoo.com/apps/themes/10.0
> > > > > > /theme_louma/) contained OCA dependencies. This is
> > > > > > forbidden, but these dependencies are commented to bypass
> > > > > > Odoo's automated check.
> > > > > > Here, the module has the same name, and the same
> > > > > > description...
> > > > > > 
> > > > > > I think Odoo should double check all modules proposed by
> > > > > > them.
> > > > > > 
> > > > > > Regards,
> > > > > > Sylvain
> > > > > > 
> > > > > > 2017-03-02 7:52 GMT+01:00 Mihai FEKETE <Mihai.FEKETE@forbio
> > > > > > m.eu>:
> > > > > > > Hi Yoshi,
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > We had the same situation with hr_public_holidays, the
> > > > > > > one from Oca was overwritten in Apps Store by one module
> > > > > > > with the same name made from a partner, here we had
> > > > > > > understanding from the partner and he removed the module
> > > > > > > from apps, but here, since the code is not public to see
> > > > > > > if they just copied it, this should be threated by Odoo
> > > > > > > when they register the modules, since the same name
> > > > > > > exists and authors are different…
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > Mihai Fekete
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > From: Yoshi Tashiro [mailto:tashiro@roomsfor.hk] 
> > > > > > > Sent: Thursday, March 02, 2017 8:23 AM
> > > > > > > To: Contributors <contributors@odoo-community.org>
> > > > > > > Subject: OCA module not showing in app store due to name
> > > > > > > conflict
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > Hello,
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > 
> > > > > > > Just noticed that this module https://github.com/OCA/serv
> > > > > > > er-tools/tree/10.0/auth_signup_verify_email (for 10.0)
> > > > > > > does not appear in the app store because of this
> > > > > > > https://apps.openerp.com/apps/modules/10.0/auth_signup_ve
> > > > > > > rify_email/.
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > 
> > > > > > > They seem to share the same descriptions by coincidence… 
> > > > > > > Wasn’t sure if the once that’s showing in the app store
> > > > > > > was legitimate, but just thought I’d share.
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > 
> > > > > > > ---
> > > > > > > 
> > > > > > > 
> > > > > > > Yoshi Tashiro
> > > > > > > 
> > > > > > > 
> > > > > > >  
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Mailing-List: http://odoo-community.org/groups/contributo
> > > > > > > rs-15
> > > > > > > Post to: mailto:contributors@odoo-community.org
> > > > > > > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Mailing-List: http://odoo-community.org/groups/contributo
> > > > > > > rs-15
> > > > > > > Post to: mailto:contributors@odoo-community.org
> > > > > > > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > > > > > > 
> > > > > > 
> > > > > > ***********************************************************
> > > > > > *********************
> > > > > > Ce message et toutes les pièces jointes (ci-après le
> > > > > > "message") sont établis à
> > > > > > l'intention exclusive de ses destinataires et sont
> > > > > > confidentiels. Si vous
> > > > > > recevez ce message par erreur, merci de le détruire et d'en
> > > > > > avertir
> > > > > > immédiatement l'expéditeur. Toute utilisation de ce message
> > > > > > non conforme à sa
> > > > > > destination, toute diffusion ou toute publication, totale
> > > > > > ou partielle, est
> > > > > > interdite, sauf autorisation expresse. L'internet ne
> > > > > > permettant pas d'assurer
> > > > > > l'intégrité de ce message, SYLEAM décline toute
> > > > > > responsabilité au titre de ce
> > > > > > message, dans l'hypothèse où il aurait été modifié.
> > > > > > 
> > > > > > This message and any attachments (the "message") is
> > > > > > intended solely for the
> > > > > > addressees and is confidential. If you receive this message
> > > > > > in error, please
> > > > > > delete it and immediately notify the sender. Any use not in
> > > > > > accord with its
> > > > > > purpose, any dissemination or disclosure, either whole or
> > > > > > partial, is prohibited
> > > > > > except after formal approval. The internet can not
> > > > > > guarantee the integrity of
> > > > > > this message. SYLEAM cannot therefore be liable for the
> > > > > > message if modified.
> > > > > > ***********************************************************
> > > > > > *********************
> > > > > > _______________________________________________
> > > > > > Mailing-List: http://odoo-community.org/groups/contributors
> > > > > > -15
> > > > > > Post to: mailto:contributors@odoo-community.org
> > > > > > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > > > > _______________________________________________
> > > > > Mailing-List: http://odoo-community.org/groups/contributors-1
> > > > > 5
> > > > > Post to: mailto:contributors@odoo-community.org
> > > > > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > > > > <span id="cid:AB2149B0-AA31-4EFB-95E5-CF8F78E6A78B@dlasley.ne
> > > > > t">
> > > > _______________________________________________
> > > > Mailing-List: http://odoo-community.org/groups/contributors-15
> > > > Post to: mailto:contributors@odoo-community.org
> > > > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > > > 
> > > _______________________________________________
> > > Mailing-List: http://odoo-community.org/groups/contributors-15
> > > Post to: mailto:contributors@odoo-community.org
> > > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > _______________________________________________
> > Mailing-List: http://odoo-community.org/groups/contributors-15
> > Post to: mailto:contributors@odoo-community.org
> > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > _______________________________________________
> > Mailing-List: http://odoo-community.org/groups/contributors-15
> > Post to: mailto:contributors@odoo-community.org
> > Unsubscribe: http://odoo-community.org/groups?unsubscribe
> > 
> _______________________________________________
> Mailing-List: http://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: http://odoo-community.org/groups?unsubscribe
-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

Reference