Salut,Dupa o lunga perioada de asteptare, am aici raspunsul la un mail trimis pe debian-legal.
M-am interesat destul de mult in legatura cu chestia asta si am ajuns la concluzia ca GPL este potrivit pentru un dictionar.
Exista totusi retineri in legatura cu ceea ce doresc _eu_ sa fac cu dictionarul, in sensul ca, anumite persoane considera ca nimeni nu poate avea dreptul asupra unei colectii de cuvinte (cum sunt in dictionarele de ortografie, _nu_ cele explicative); unii spun, chiar daca e extrasa dintr-un dictionar cu licenta.
Pe de alta parte pare rezonabil ca dictionarul explicativ sa fie sub licenta.
GPL-ul ar putea avea o clauza clarificatoare sau doua:- "is (not) considered derivative work an application that uses the dictionary at runtime". - "is (not) considered linking if an application uses the external dictionary, so that application should (not) be GPL-ed"
In legatura cu GFDL-ul, se pare ca NU este considerata free nici daca se pun clauzele.
Ar mai fi o problema. Trebuie ca toti cei ce au contribuit la dictionar sa fie de acord cu schimbarea. Cred ca va fi suficient sa pui un anunt pe pagina principala ca schimbi licenta si daca cineva nu e de acord sa trimita un mail ca munca lor sa fie scoasa (si probabil ca va fi refacuta, desi nu cred ca vor fi oameni care sa nu fie de acord) si ca tu consideri ca daca nu protesteaza nimeni timp de 1 an atunci consideri ca sunt toti de acord.
Pe timpul primului an probabil ca ar fi buna dubla licentiere. Iar apoi sa renunti la GFDL, ramanand doar cu GPL.Chiar si dupa aceasta data cred ca ar trebui sa fi de acord sa se retraga contributii urmand ca pe periaoda a inca 3 ani sa accepti retragerea.
Considerand ca in timp de 4 ani toti contributirii isi dau seama daca vor sau nu sa fie de acord cu trecerea iar tacerea o consideri accept (si anunti ca asa va fi considerata) se poate considera ca e completa trecerea.
Cam in aceiasi maniera a trecut si mozilla ;-) (desi cred ca ei au ramas cu dubla licenta, lucru care ar putea fi folosit si aici) si cred ca e o metoda viabila.
Pentru dubla licentiere un text de forma urmatoare poate fi folosit."This package is double licensed. You can consider either of the licenses to be applicable to you (not at the same time), but you must retain both of the licenses when distributing it yourself."
Desi cred ca cel mai bine sa se renunte total la gfdl asap :) .Ar fi bine sa explici pe site (chiar pe prima pagina un link) de ce se face trecerea de la o licenta la alta si de ce e mai bine pe GPL.
Astept raspuns. -------- Original Message -------- Subject: Re: Which license for a dictionary or GFDL with clause == free? Date: Mon, 28 Mar 2005 23:03:19 -0800 From: Josh Triplett <firstname.lastname@example.org> To: Eddy Petrisor <email@example.com> CC: firstname.lastname@example.org, email@example.com References: <4247C5D4.firstname.lastname@example.org> [CCed to Andrew McMillan; please see item 3 below. Feel free to ignore the rest of the message.] Eddy Petrisor wrote:
I need an advice regarding a licensing issue. The story is: There is this dictionary on line for my native language(Romanian). This is not just a dictionary that contains a word list, but an explainatory dictionary which contains definitions for every word that exists in Romanian (or at least 99%). Currently the dictionary is licensed under the GFDL license, which, as all of us know, is non-free. As the dictionary is so complete I intend to expand the aspell, ispell, *spell -ro dictionaries with words extracted from the afore mentioned dictionary.
Sounds like a perfectly reasonable thing to do.
Now comes in the tricky part: The copyright holder believes in free software, but he doesn't want his work to be used in proprietary projects. So he wants some sort of license that would be simillar to GPL, but fitted for a dictionary.
OK; that goal is definitely doable, through the use of a copyleft Free Software license. Please note that the GPL doesn't need to be "fitted" to different classes of works. It can apply to programs, documentation, literature, images, sounds, videos, 3d models, and any other form of material. It can most definitely apply to a dictionary, and this would be an excellent choice. Also note that almost all copyleft licenses are incompatible by nature, so the GPL is most likely the only good copyleft license which is GPL-compatible, which is a good property to have for such a work, as it is likely to be combined with other works in various ways.
1. What kind of license should I use in order to be able to expand the spelling dictionaries?
Any Free Software license will support this goal.
2. Would GPL with a clarification clause would suffice?
The GPL alone, without a clarification clause, should suffice. [Andrew: this is the part I CCed you about.]
3. Would GFDL with a clause would suffice? (Note: I am asking because I found this in whereami.8 man page:This manual page was written by Andrew McMillan <debian@mcmil- lan.net.nz> for the Debian GNU/Linux system (but may be used by oth- ers). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts.
This is not a free license. This text is boilerplate from an old Debian manpage template, from before we realized the issues with the GFDL, and we are still dealing with the problems caused by that unfortunate template. This template has since been revised to use the GPL, and we have been contacting the authors of manpages licensed under the GFDL to get them to relicense. I have CCed Andrew McMillan for this purpose; Andrew, would you have any objections to relicensing this manual page (and any others you may have written that are licensed under the GFDL) under the GNU General Public License, version 2? It is theoretically possible to take the GFDL and rescind all the problematic clauses making it non-free. However, nobody has written such an exception statement, and such a statement would probably be moderately complex. In addition, the resulting license would be quite cumbersome, as well as incompatible with the GPL. Furthermore, assuming the author does not make use of the non-free features of Invariant Sections or Cover Texts, they are not really using any GFDL-specific license features anyway, so there is little point in using the GFDL. If the author is concerned about compatibility with the GFDL, he can certainly dual-license the dictionary under *both* the GPL and the GFDL.
4. Is it possible for him to release periodical wordlists under another type of license, like the creative commons? (I feel that he cares more for the words' definitions than the word list itself)
He can certainly release wordlists under a separate license. As the sole copyright holder (which I assume he is), he can license his works under any license or set of licenses that he chooses. However, the Creative Commons licenses are not currently a DFSG-Free choice, due to a few minor license issues which Debian is attempting to resolve with Creative Commons. We hope that they will become DFSG-Free licenses in the future, but for now a wordlist under one of these licenses would not solve the problem at hand. If he releases the entire dictionary under a Free Software license such as the GPL, there is no need to go to the additional effort of licensing the words separately, unless he wishes to grant additional permissions to the wordlist that he does not grant over the dictionary. (It is also useful to note that raw lists of words with no definition may not be copyrightable at all, depending on the creativity put into the selection of which words to list. It sounds like the author is goinng for a complete list of all words, which is most likely not copyrightable.)
5. Is there a suited license for wordlists (that keeps the list non-proprietary)? Is there a suited license for an explainatory dictionary?
See above; the GPL should work just fine for a wordlist and for a dictionary. Hope this helps, - Josh Triplett -- Regards, EddyP =========================== I had a favourite quote, but I forgot it. And it was insightful.
Description: PGP signature