[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [phpGroupWare-developers] phpGroupWare and GPLv3
From: |
Dave Hall |
Subject: |
Re: [phpGroupWare-developers] phpGroupWare and GPLv3 |
Date: |
Thu, 05 Jul 2007 08:19:31 +1000 |
On Wed, 2007-07-04 at 15:32 -0500, Chris Weiss wrote:
> On 7/4/07, Dave Hall <address@hidden> wrote:
> > I hope that in the coming weeks we can release a new 0.9.16.01x GPLv3
> > version of phpGroupWare.
>
> What's the drawback of leaving it as "v2 or later"? seems there are
> benefits to this due to the v2 and v3 incompatibility.
>
> I see drawbacks to full-on changing to v3 as well, such as the 3rd
> party libs we use that are not yet v3 and not "v2 or later" (are there
> even of these?), we will have to stop using them.
This is one of the things which needs to be checked. As Kai unchanged
the license headers to make such checks harder, we will have to look at
CVS history too.
>
> I say we leave Stable alone and evaluate the "need" in HEAD. If the
> libs allow v3 then we can change head.
>
RMS has asked all GNU packages to relicense ASAP. As it means that we
also fix our headers and conduct a full license audit of both branches I
think it is a good thing - even if it is time consuming.
> However, I don't think v3 has any effect on us at all. tivoization
> isn't really and issue, and being PHP, neither is DRM, and given the
> lack of corporate interest the rest of the issues are moot as well.
> The only benefit I see to us might be the new Apache license
> compatibility, which could open up some 3rd party stuff for
> integration.
The Apache stuff is beneficial, the ability to use GPLv3 and "v2 or
later" code/libs. I also think that the more projects that switch
early, the sooner GPLv2 only code will die off, especially if they
bundle with GPLv2 or later code which switches.
Cheers
Dave