http://www.gnu.org/licenses/license-list.html
Hmm... ne, ne mozes menjati GPL softver a tvoj deo/promenu licencirati kao LGPL ili MPL, stagod.. ukoliko je deo istog projekta, bar ako hoces da se drzis semantike.. problem cu objasniti u sledecem citatu...
A zasto da ne? Koja je poenta "slobode" ako nisi slobodan da to ucinis? :-)
E vidis - ovo je najveci problem. Mehanizam eksternog linkovanja >mora< biti definisan eksplicitno u GPL licenci (pogledaj www.xvid.org -> definisan je mehanizam eksternog linkovanja kroz VFW32 i DShow interfejse, kada se moze govoriti o nezavisnim modulima!) ako nije... e onda si na "sivom" terenu, kako GPL nije ugovor nema nikakvo sudsko tumacenje jer ga niko nije ni testirao na sudu, pa samim tim postoji i pravna nesigurnost da tebe neko u buducnosti moze da tuzi jer nisi ispostovao uslove licence.
Ne mogu sad da iskopam link gde su RMS-a pitali sta se smatra kao "derrived work" - i on sam nista nije jasno definisao, vec je ispalo srpski "moz' da bidne, a ne mora da znaci" - tj. ne postoji jednoznacan nacin evaluacije kada je nesto "larger work" ili "derrived work" a kada nezavisni modul - i u tome jeste problem o kome ja pricam, pricamo o vrlo "sivom" terenu uredjenom necijom dobrom voljom ili ubedjenjem?!
Nije jasno definisano - pozvacu se na:
http://www.cs.helsinki.fi/u/ca...aching/oss/papers/jarvinen.pdf
"What constitutes combining two parts into one program? This is a legal
question, which ultimately judges will decide. We believe that a proper criterion
depends both on the mechanism of communication (exec, pipes, rpc, function
calls within a shared address space, etc.) and the semantics of the communication
(what kinds of information are interchanged).
If the modules are included in the same executable file, they are definitely
combined in one program. If modules are designed to run linked together in a
shared address space, that almost surely means combining them into one program.
[15]"
It can be argued that these explanations are rather vague and do not give support
in many real life situations. They also state that these issues are ultimately decided in
courts. Due to the fact that the GPL is not very similar to proprietary licenses, there
are no guarantees that the court will rely on above-mentioned principles. Despite of
these kinds of instructions, the courts have to interpret the actual wording of the
license agreement in the first place.
Dakle.. jos uvek vrlo nesigurna posla...
20 godina za source kod, posle cega on postaje PD...
Hmm... moze samo da prisvoji tu njegovu trivijalnu i logicku nadogradnju softvera - ne i originalni prior art - isto vazi i kada je GPL softver u pitanju, posto neko moze na osnovu ideje iz GPL softvera da napravi neku inovaciju i da nju kao takvu patentira, jer je patent apstraktan - opisuje proces na daleko apstraktnijem nivou nego C/C++ kod koji je zasticen GPL licencom.
Ne znam da li negde u GPL licenci pise nesto tipa "ovaj kod ne sme da se koristi kao osnova za patent" - ali kako GPL licenca nije ugovor, ti nisi pravno obavezan da se pridrzavas iste ako taj kod citas / koristis pa ga posle obrises, itd...
http://www.digicortex.net/node/1 Videos: http://www.digicortex.net/node/17 Gallery: http://www.digicortex.net/node/25
PowerMonkey - Redyce CPU Power Waste and gain performance! - https://github.com/psyq321/PowerMonkey