Re: Licensing and the library version of git

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/27/06, Petr Baudis <pasky@xxxxxxx> wrote:
> You may like trying to force GPL onto the app but many apps are
> stuck with the license they have and can't be changed since there is
> no way to contact the original developers.

At this point, git-shortlog lists exactly 200 people (at least entries
like Unknown or No name are all linux@xxxxxxxxxxx ;-).

Inability to integrate with Microsoft Visual Studio is going to have a
lot of impact on the cross platform use of git.  Is a conscious
decision being made to stop this integration or is this just unplanned
side effect of the original license? If this is an unplanned side
effect, the quicker we move, the easier it is to fix.

Note that only the code going into the library needs to be LGPL. That
should significantly reduce the number of authors that need to be
contacted.

A first step to fixing this would be to add an immediate requirement
that all new code that is targeted to library functions be licensed
LGPL. That will at least stop the problem from getting any worse.

--
Jon Smirl
jonsmirl@xxxxxxxxx
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]