> Aber soweit ich weiß müsste ich noch meinen Code anpassen um ihn klar > als GPL Code zu markieren.
Sinnvollerweise solltes Du das machen: Im Nachwort der GPL finden sich diese Instruktionen: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. Letzteres macht man am besten in einer Datei README. Dort sollte man auch Angaben zur Lizenz machen, also den obigen Abschnitt reinkopieren. Oder auf eine Datei AUTHORS verweisen. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". Dies wird übrigens expliziet von der GPL gefordert; z.B:. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. Wenn Du Änderungen an GPL Software durchführst, die nicht von Dir stammt, dann mußt Du Änderungen dokumentieren. Ein ChangeLog, wie man es in allen GNU Projekten findet, ist dafür hinreichend. Im GNU Projekt führen wir noch eine weitere Datei, namens AUTHORS, in der wir festhalten, wer überhaupt Änderungen gemacht hat. Das ist sehr praktisch; beispielsweise: Program: GnuPG Homepage: http://www.gnupg.org Maintainer: Werner Koch <w...@gnupg.org> Bug reports: <bug-gn...@gnu.org> Security related bug reports: <security at gnupg org> License: GPLv3+ Authors ======= Ales Nyakhaychyk <nyakhaychyk ....> Translations [be] [...] Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. _______________________________________________ fsfe-de mailing list fsfe-de@fsfeurope.org https://mail.fsfeurope.org/mailman/listinfo/fsfe-de