Another solution is maybe possible : let the code in AGPLv2, and put the doc
in GPLv2. It seem to be possible (cf
http://linuxfr.org/~naparuba/29363.html#1104785 in french sorry).
We just have to put a LICENCE file in the doc directory and put the GPLv2
HEADER in all docbook files.
Jean
Ps: that why I have licence problems....
On Wed, Feb 10, 2010 at 11:47 AM, nap <[email protected]> wrote:
> A solution can be to pass in the GPLv2 and later in the first time. If we
> manage to go in the Nagios project, it won't be a problem anymore, and if we
> cannot, we rewrite all the doc (arg...) and we can move to GPLv3 and even
> AGPL.
>
> http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
>
>
> Jean
>
>
> On Wed, Feb 10, 2010 at 11:33 AM, nap <[email protected]> wrote:
>
>> Hi,
>>
>> I'm looking at the Nagios' documentation import, but it's in Gplv2.
>> Shinken was written in AGPL so I think we just cannot import it and it can
>> be a problem in the future if we want an inclusion of Shinken in Nagios
>> project. So we must think about leave the licence in AGPL but wrote our own
>> doc and have problem with Nagios inclusion, or change the licence to Gplv2
>> to easy import doc, no problem for Nagios inclusion, but leave the Affero
>> effect (if a user access to Shinken in the network, he must have access to
>> the sources).
>>
>> We can maybe drop the Affero licence and take the classic Gplv2. Affero is
>> trully important for PHP like applications, but I'm wondering if it's a so
>> good idea for Shinken.
>>
>> What do you think about this?
>>
>>
>> Jean
>>
>
>
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Shinken-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shinken-devel
