Community mailing list archives
Re: Plagiarism in the Odoo App Storeby
Good Question Gunnar.
Best way would be to give a good example yourself as institution with view and support for the opensource community.
i.e. The main difference between GPL v.3 and AGPL v.3 is the following:
"The GNU Affero General Public License is a modified version of the ordinary GNU GPL version 3. It has one added requirement: if you run a modified program on a server and let other users communicate with it there, your server must also allow them to download the source code corresponding to the modified version running there."
Now have a look at things which have been available for the community before and vanished away suddenly to raise money. i.e. theme_clean discussion. The indiego campaign is long time over already. Everything was AGPL and available for the community and suddenly all that stuff vanished away and appeared again (quite expensive) at the odoo shop, even it was the best resource for people to create their own templates. Since months people are asking when this template will be given back to the community. Furthermore there is no way to download the source codes! If yes where?
To avoid such problems with people who try to use Free Open Source Code in proprietary software and probably resell it even as proprietary software and no one can see the source code or what is going on there, the FSF actually recommends using the AGPL and it does NOT recommend using the LGPL as it is this LGPL which will make also ODOO very open that the software can "closed down ", which means it can be used in proprietary code without making that code accessible for others and exactly that should be avoided!
In any way, as long as there are no consequences than this will simply continue. Even banning won't help as in the age of internet names, emails etc change easily but the people behind it might never change!
IMHO it would have been much much easier to keep those people out if ODOO would still be AGPL rather than LGPL which opens up some kind of grey zones people will use as loopholes for their proprietary code. Legal cases might take much much longer than with a clean AGPL or even better GPL v.3 understanding where the does and don'ts are defined very clear and understandable.
Perhaps the best way to to get rid of those people would be to republish their code under AGPL and waiting until they come with legal ideas - which might never happen. ;-) Their proprietary code also has to be AGPL if it depends on any AGPL part!
The most important thing for the community would actually be to name the company who is using AGPL parts in their proprietary products without making the source code accessible for others. This would warn also others not to build i.e. on their modules. Customers could be warned to to not use that company for their purposes as they too could face legal cases if the would use the code they provide under a false or not appropriate license.
But in General the best way would be to give a very good example yourself and provide the source code you build on the AGPL parts of ODOO also to others in general!
On Wed, Nov 4, 2015 at 9:22 AM, Gunnar Wagner <firstname.lastname@example.org> wrote:
On 11/3/2015 7:22 PM, Martin Trigaux wrote:
>> As said Eric, when you notice such license enlightenment (republishing a *GPL module under a closed source license is not permitted),
>> please contact email@example.com so we can investigate.
wouldn't it be 'community style' to publish such infringements on this list as well (I mean in addition to contacting the 'authorities" via firstname.lastname@example.org?
So the community can deal with it as well? I'd also like to know what are the consequences for such a deed from S.A.'s & Community side?
<blockquote cite="mid:email@example.com" type="cite">On 03/11/15 08:22, Caudal Eric wrote: > Hi Luke, > you should contact Odoo SA with specific details and they will > investigate the licence infringements (and hopefully expel any work from > them for a while in the apps store). > For information, it is valid to republish AGPL into AGPL and add your > authorship if you added some features. > It is not valid to republish AGPL in another license, all the more > closed (there are probably some possible republishing options but > license must be compatible with AGPL IMO) > Best regards > > On Tue, Nov 3, 2015 at 2:57 PM Luke Branch > > wrote: > > I've noticed a huge amount of plagiarism in the App store with > companies taking open-source AGPL-licensed modules, making a very > slight modification and then republishing them as their own under a > paid license. > > For my own modules I wouldn't mind so much if they remained > open-source under the license they were released under, but when > someone clearly disregards the license and republishes under > whatever EULA they want, this is not ok in my opinion. > > Has anyone else noticed this with their own modules, and is there > anything that Odoo SA will implement to discourage this behaviour? > > Regards, > > Luke > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org <mailto:email@example.com> > Unsubscribe: https://www.odoo.com/groups?unsubscribe > > -- > > Eric Caudal (from my mobile) > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org > Unsubscribe: https://www.odoo.com/groups?unsubscribe > -- Martin Trigaux Odoo (Formerly OpenERP) https://odoo.com https://github.com/mart-e
Gunnar Wagner | Iris Germanica Co., Ltd. | Jin Qian Gong Lu 385, 8-201, Feng Xian District, 201404 Shanghai, P.R. CHINA
+86.159.0094.1702 | skype: professorgunrad | wechat: 15900941702