Bureaucrats, developer, Administrators
9,842
edits
Talk:Licenses: Difference between revisions
m
Must remember to get permission from apache to modify their license
(legalese - first draft - but complete and deals with some problems Wikipedia has with GFDL and "outing") |
m (Must remember to get permission from apache to modify their license) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Must remember to get permission from apache to modify their license, since it is copyrighted in itself. We wouldn't want to have a pirated license text would we ;) ? | |||
---- | ---- | ||
If you are considering any other license scheme than [[GPL]], which it said you were, [[LGPL]] must be the very next one considered, as it is viral but only to the library or schema level, i.e. does not infect anything that uses that code or library or schema at arm's length as long as it does not modify it. [[GFDL]] is actually more like LGPL because GFDL has [[Invariant Section]]s and other [[Secondary Section]]s to which the normal viral rules don't apply. These are like the calling code, or larger framework, that might rely on LGPL libraries. | If you are considering any other license scheme than [[GPL]], which it said you were, [[LGPL]] must be the very next one considered, as it is viral but only to the library or schema level, i.e. does not infect anything that uses that code or library or schema at arm's length as long as it does not modify it. [[GFDL]] is actually more like LGPL because GFDL has [[Invariant Section]]s and other [[Secondary Section]]s to which the normal viral rules don't apply. These are like the calling code, or larger framework, that might rely on LGPL libraries. | ||