Compatibility of FOSS licenses License compatibility

-



1 compatibility of foss licenses

1.1 gpl compatibility

1.1.1 copyleft licenses , gpl
1.1.2 gfdl , gpl
1.1.3 cddl , gpl
1.1.4 cc by-sa , gplv3


1.2 creative commons license compatibility
1.3 json license





compatibility of foss licenses

license compatibility between common foss software licenses according david a. wheeler (2007): arrows denote 1 directional compatibility, therefore better compatibility on left side on right side.


licenses common free , open-source software (foss) not compatible each other, , can make legally impossible mix (or link) open-source code if components have different licenses. example, software combined code released under version 1.1 of mozilla public license (mpl) code under gnu general public license (gpl) not distributed without violating 1 of terms of licenses; despite both licenses being approved both open source initiative , free software foundation.


license compatibility between copyleft license , license one-way compatibility, making copyleft license (gpl, , other copyleft licenses) incompatible proprietary commercial licenses, many non-proprietary licenses. one-way compatibility characteristic has been criticized apache foundation, licenses under more permissive apache license, such non-copyleft licenses being less complicated , making better license compatibility.


an example of license has excellent compatibility other foss licenses artistic license 2.0, due re-licensing clause allows redistribution of source code under other foss license.



you may distribute modified version source (either gratis or distributor fee, , or without compiled form of modified version) […] provided @ least 1 of following: […]


(c) allow receives copy of modified version make source form of modified version available others under


(i) original license or


(ii) license permits licensee freely copy, modify , redistribute modified version using same licensing terms apply copy licensee received, , requires source form of modified version, , of works derived it, made freely available in license fees prohibited distributor fees allowed. [emphasis added]



the common development , distribution license (cddl)—a weak copyleft license in-between gpl license , bsd/mit permissive licenses—tries address license compatibility problems permitting, without re-licensing, mixing of cddl-licensed source-code files source-code files under other licenses providing resulting binary can licensed , sold under different license long source code still available under cddl.


gpl compatibility

to minimize license proliferation , license incompatibilities in foss ecosystem, organizations (the free software foundation, instance) , individuals (david a. wheeler), argue compatibility used gpl important feature of software licenses. many of common free-software licenses, permissive licenses, such original mit/x license, bsd licenses (in three-clause , two-clause forms, though not original four-clause form), mpl 2.0, , lgpl, gpl-compatible. is, code can combined program under gpl without conflict, , new combination have gpl applied whole (but other license not apply).


copyleft licenses , gpl

copyleft software licenses not inherently gpl-compatible; gplv2 license not compatible gplv3 or lgplv3. if tried combine code released under either of later gpl licenses gplv2 code, violate section 6 of gplv2, source of incompatibility. however, code under later licenses can combined code licensed under gpl version 2 or later. software released under gplv2 allow use terms of later versions of gpl well, , have exception clauses allow combining them software under different licenses or license versions.


gfdl , gpl

the free software foundation-recommended gnu free documentation license incompatible gpl license, , text licensed under gfdl cannot incorporated gpl software. therefore, debian project decided, in 2006 resolution, license documentation under gpl. floss manuals foundation followed debian in 2007. in 2009, wikimedia foundation switched gfdl creative commons cc-by-sa license main license projects.


cddl , gpl

another case gpl compatibility problematic cddl licensed zfs file system gplv2 licensed linux kernel. despite both free software under copyleft license, zfs not distributed linux distros debian (but distributed freebsd , mac os) cddl considered incompatible gpl ed linux kernel, free software foundation , parties relations fsf. legal interpretation—of if , when combination constitutes combined work or derivative work of gpled kernel—is ambiguous , controversial. in 2015, cddl gpl compatibility question reemerged when linux distribution ubuntu announced include openzfs default. in 2016, ubuntu announced legal review resulted in conclusion legally safe use zfs binary kernel module in linux. others accepted ubuntu s conclusion; instance lawyer james e.j. bottomley argued convincing theory of harm cannot developed, making impossible bring case court. eben moglen, co-author of gplv3 , founder of sflc, argued while letters of gpl might violated spirit of both licenses adhered to, relevant issue in court. on other hand, bradley m. kuhn , karen m. sandler, software freedom conservancy, argued ubuntu violate both licenses, binary zfs module derivative work of linux kernel, , announced intent achieve clarity in question, going court.


cc by-sa , gplv3

on october 8, 2015, creative commons concluded cc by-sa 4.0 one-way compatible gplv3.


creative commons license compatibility

the creative commons licenses used content, not combinations of 7 recommended , supported licenses compatible each other. additionally, one-way directional compatibility, requiring complete work licensed under restrictive license of parent works.



json license

json developer douglas crockford, inspired words of president bush, formulated evil-doers json license ( software shall used good, not evil. ) in order open-source json libraries force (troll) corporate lawyers (or overly pedantic) pay license state. subjective , moral license clause led license incompatibility problems other open source licenses, , resulted in json license not being free , open-source license.








Comments

Post a Comment

Popular posts from this blog

CACHEbox ApplianSys

-
cachebox230 server appliance cachebox s caching engine employs code squid project. in 2005 launched becta approved protex content filtering service in collaboration east of england broadband network, represent more 2800 schools across 10 authorities. in 2006, acquired assets , customer base of rival freedom2. has since expanded activity north american schools market , caching device requested schools 2015 e-rate funding.
Read more

Kinship systems Apache

-
hide painting depicting apache girl s puberty ceremony, naiche (chiricahua apache), ca. 1900, oklahoma history center the chiricahua language has 4 different words grandparent: -chú maternal grandmother , -tsúyé maternal grandfather , -chʼiné paternal grandmother , -nálé paternal grandfather . additionally, grandparent s siblings identified same word; thus, 1 s maternal grandmother, 1 s maternal grandmother s sisters, , 1 s maternal grandmother s brothers called -chú. furthermore, grandparent terms reciprocal, is, grandparent use same term refer grandchild in relationship. example, person s maternal grandmother called -chú , maternal grandmother call person -chú (i.e. -chú can mean child of either own daughter or sibling s daughter.) chiricahua cousins not distinguished siblings through kinship terms. thus, same word refer either sibling or cousin (there not separate terms parallel-cousin , cross-cousin). additionally, terms used according sex of speaker (unlike english terms broth...
Read more

Western Apache Apache

-
a western apache woman san carlos group western apache include northern tonto, southern tonto, cibecue, white mountain , san carlos groups. while these subgroups spoke same language , had kinship ties, western apaches considered separate each other, according goodwin. other writers have used term refer non-navajo apachean peoples living west of rio grande (thus failing distinguish chiricahua other apacheans). goodwin s formulation: apache peoples have lived within present boundaries of state of arizona during historic times exception of chiricahua, warm springs, , allied apache, , small band of apaches known apache mansos, lived in vicinity of tucson. cibecue western apache group, according goodwin, north of salt river between tonto , white mountain apache, consisting of ceder creek, carrizo, , cibecue (proper) bands. san carlos. western apache group ranged closest tucson according goodwin. group consisted of apache peaks, arivaipa, pinal, san carlos (proper) bands. arivaipa (also ara...
Read more