Community mailing list archives

community@mail.odoo.com

Re: FW: access to code under AGPL v3

by
Eric Caudal
- 01/19/2016 07:47:17

Well I think it might be the goods moment to announce it.

The OCA board is looking for a volunteer efficient trustable and of course free to take care of our website ...


On Tue, Jan 19, 2016, 14:12 Andreas Becker <andi@lisandi.com> wrote:
Thanks Joel

for correcting the links.




I think if there are no Free members you should really correct the wording on your website! http://prntscr.com/9rxuoe

This membership directory specifies different categories of Membership and functions - Delegates/Board

All lists all members also for 2015 and you can see also the board of 2015 and the delegates as the links below don't work again!
Board 2015 it shows "No result found."
Delegation 2015 it shows "No result found."
Members for 2015 (a lot) but the link shows "No result found." actually! - some names are doubled under All!
Members for 2016 (not so many) 18 Members
and 
Free Members

Those Free Members are also listed here and Camptocamp is listed here!

Our Members Directory



otherwise people and customers visiting that page might interpret that you don't have to pay anything!
Why not calling them Founding Members ;-)


===========

Copyright and license are different.

Exactly my talking and they should not get mixed up!

Every repo and modules in the OCA should have its own license defined (mostly AGPL everywhere currently, like https://github.com/OCA/rma/blob/9.0/LICENSE). If not, you can make a PR to correct that and it'll be accepted without doubt

This License is identical with the one of GNU AGPL v.3 License and they don't allow exceptions afaik!

This also means that also all OCA Version 9 modules are licensed under AGPL - right?

mostly AGPL everywhere currently

What does "currently" mean? Will there be a change of License already planned in future i.e. switching OCA AGPL modules to LGPL?

============

Take the rma repository as an example:

License file shows the following:

GNU AFFERO GENERAL PUBLIC LICENSE
Version 3, 19 November 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
This is 100% the GNU AGPL v.3 License like it should be - OK!

Unfortunately a customer usually only sees a module out of that repository and most often he don't see the repository main directory as there isn't a link to it available in most modules.

So IMHO the licens should always be specified inside the module itself __openerp.py

example:

product_warranty

# -*- coding: utf-8 -*-
#########################################################################
# #
# #
#########################################################################
# #
# Copyright (C) 2009-2011 Akretion, Emmanuel Samyn #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
# the Free Software Foundation, either version 3 of the License, or #
# (at your option) any later version. #
# #
# This program is distributed in the hope that it will be useful, #
# but WITHOUT ANY WARRANTY; without even the implied warranty of #
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
# GNU General Public License for more details. #
# #
# You should have received a copy of the GNU General Public License #
# along with this program. If not, see <http://www.gnu.org/licenses/>. #
#########################################################################
{
'name': 'Product warranty',
'version': '8.0.1.0.0',
'category': 'Generic Modules/Product',
'author': "Akretion,Odoo Community Association (OCA),Vauxoo",
'website': 'http://akretion.com',
'license': 'AGPL-3',
'depends': ['product'],


  1. Under the Copyright section of that module the OCA does not get mentioned! It is only mentioned that until 2011 Akretion was holding the copyright.
  2. As there is an end date itals means that the copyright already expired and this module can be used by anybody as it is under public domain!
  1. Better would be:
    Mentioning always the OCA with its full name under the copyright section and keeping the year openend.

  1. The odoo community Association gets mentioned as author but author and copyright holder are not the same IMHO. There can be one who holds the copyright to it and also contributors can be authors.
-----

2. example

# -*- coding: utf-8 -*-
##############################################################################
#
# Copyright 2015 Eezee-It
# Copyright 2013 Camptocamp
# Copyright 2009-2013 Akretion,
# Author: Emmanuel Samyn, Raphaël Valyi, Sébastien Beau,
# Benoît Guillot, Joel Grand-Guillaume
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Affero General Public License as
# published by the Free Software Foundation, either version 3 of the
# License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU Affero General Public License for more details.
#
# You should have received a copy of the GNU Affero General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
##############################################################################
{
'name': 'RMA Claim (Product Return Management)',
'version': '8.0.1.1.0',
'category': 'Generic Modules/CRM & SRM',
'description': """
Management of Return Merchandise Authorization (RMA)
====================================================
This module aims to improve the Claims by adding a way to manage the
product returns. It allows you to create and manage picking from a
claim. It also introduces a new object: the claim lines to better
handle that problematic. One Claim can have several lines that
concern the return of differents products. It's for every of them
that you'll be able to check the warranty (still running or not).
It mainly contains the following features:
* product returns (one by one, mass return by invoice)
* warranty control & return address (based on invoice date and product form)
* product picking in / out
* product refund
* access to related customer data (orders, invoices, refunds, picking
in/out) from a claim
* use the OpenERP chatter within team like in opportunity (reply to refer to
the team, not a person)
Using this module makes the logistic flow of return this way:
* Returning product goes into Stock or Supplier location with a incoming
shipment (depending on the settings of the supplier info in the
product form)
* You can make a delivery from the RMA to send a new product to the Customer
.. warning:: Currently, the warranty duration used is the one configured on the
products today, not the one which was configured when the product
has been sold.
Contributors:
-------------
* Emmanuel Samyn <esamyn@gmail.com>
* Sébastien Beau <sebastien.beau@akretion.com.br>
* Benoît Guillot <benoit.guillot@akretion.com.br>
* Joel Grand-Guillaume <joel.grandguillaume@camptocamp.com>
* Guewen Baconnier <guewen.baconnier@camptocamp.com>
* Yannick Vaucher <yannick.vaucher@camptocamp.com>
* Javier Carrasco <javier.carrasco@eezee-it.com>
""",
'author': "Akretion, Camptocamp, Eezee-it, MONK Software, "
"Odoo Community Association (OCA)",
'website': 'http://www.akretion.com, http://www.camptocamp.com, '
'http://www.eezee-it.com, http://www.wearemonk.com',
'license': 'AGPL-3',
'depends': [
'sale',
'stock',
'crm_claim',
'crm_claim_code',
'crm_claim_type',
'product_warranty',
],

Here the contributors get listed in a separate part of that __openerp.py file.
But again under the actual copyright section the OCA gets not mentioned and the specific authors get mentioned as an additon to the copyright part.
Have a look under "author" here also MONK Software gets; mentioned but they don't appear under the copyright or author part below the copyright section, while the OCA gets mentioned also as author.

Better would be IMHO:
List all Copyright holders under the copyright section at the top of that file so that they get actually be read first by people accessing the file. Add "Odoo Community Association (OCA) to that part and customers/developers/hosters can easily see, that it is a module where OCA holds the copyright and therefore they don't need to fear to get sued (as Maxime explained previously). As long as they don't get mentioned here under that copyright section it is not obvious who is actually holding the copyright!

---------

Example 3

# -*- coding: utf-8 -*-
#########################################################################
# #
# #
#########################################################################
# #
# Copyright (C) 2009-2011 Akretion, Emmanuel Samyn #
# #
#This program is free software: you can redistribute it and/or modify #
#it under the terms of the GNU General Public License as published by #
#the Free Software Foundation, either version 3 of the License, or #
#(at your option) any later version. #
# #
#This program is distributed in the hope that it will be useful, #
#but WITHOUT ANY WARRANTY; without even the implied warranty of #
#MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
#GNU General Public License for more details. #
# #
#You should have received a copy of the GNU General Public License #
#along with this program. If not, see <http://www.gnu.org/licenses/>. #
#########################################################################
--

Eric  Caudal (from my mobile)