|
| 1 | +Format: http://dep.debian.net/deps/dep5/ |
| 2 | +Upstream-Name: Openbve Stable source |
| 3 | +Upstream-Contact: Michelle Boucquemont < [email protected]> |
| 4 | +Source: http://trainsimframework.org/downloads.html (openbve_stable_source.zip) |
| 5 | + |
| 6 | +Comment: From http://trainsimframework.org/credits.html |
| 7 | +Files: * |
| 8 | +Copyright: 2008-2012 Michelle Boucquemont |
| 9 | + Anthony Bowden |
| 10 | + Jens Rügenhagen |
| 11 | +License: openbve-permissive |
| 12 | + |
| 13 | +License: openbve-permissive |
| 14 | + From 'http://trainsimframework.org/index.html', current: |
| 15 | + . |
| 16 | + openBVE is a cross-platform, free-as-in-freedom train simulator |
| 17 | + placed in the public domain. This means that you can make any |
| 18 | + modifications to it you like and share your modifications with |
| 19 | + others. |
| 20 | + . |
| 21 | + From 'Readme.txt', current: |
| 22 | + . |
| 23 | + This program is placed in the public domain. This means that you |
| 24 | + can make any modifications to it you like and share your |
| 25 | + modifications with others. |
| 26 | + . |
| 27 | + From 'http://trainsimframework.org/index.html', earlier versions: |
| 28 | + . |
| 29 | + Dedication to the public |
| 30 | + . |
| 31 | + This program, along with all website content, is dedicated to the |
| 32 | + public. I do not pose any restrictions or requirements on how this |
| 33 | + material can be used, and explicitly encourage redistribution and |
| 34 | + modification for any purpose. |
| 35 | + . |
| 36 | + From 'Readme.txt', earlier versions: |
| 37 | + . |
| 38 | + Dedication to the public |
| 39 | + . |
| 40 | + This program is dedicated to the public. I do not pose any |
| 41 | + restrictions or requirements on how this material can be used, and |
| 42 | + explicitly encourage redistribution and modification for any |
| 43 | + purpose. |
| 44 | +Comment: |
| 45 | + Below are some of the accompanying statements that Openbve and the |
| 46 | + upstream developers have made regarding how the work can be used, |
| 47 | + this provides greater insight and context into the wishes of upstream, |
| 48 | + beyond the simple and permissive "public domain" wording. |
| 49 | + . |
| 50 | + It's notable that the intent and appreciation for sharing and |
| 51 | + openness has always present with upstream, as can be seen from the |
| 52 | + name "Open...". Openbve was itself a reaction to "freeware" but |
| 53 | + non-distributable, and non-fixable programm "BVE Trainsim" |
| 54 | + (originally called "Boso View Express", 鉄道運転シミュレーション). |
| 55 | + . |
| 56 | + Although the intent has been constant, the PD wording has evolved, |
| 57 | + attempting to remain short. Upstream have welcomed input where it |
| 58 | + as been offered on the licence-terminology; as can be seen in the |
| 59 | + discussion: the upstream preference would be for copyright law to |
| 60 | + not exist (international treaties dictate otherwise for the moment). |
| 61 | + . |
| 62 | + History |
| 63 | + . |
| 64 | + In 2008, in preparation for Debian packaging, discussion was started |
| 65 | + with upstream via the upstream bugtracker/forum, and is copied below |
| 66 | + for context. (At the time it was the best introduction to the |
| 67 | + licence and original intent behind the Openbve project). |
| 68 | + . |
| 69 | + More information on the thinking behind the "licence-free" intend has been |
| 70 | + saved here in this 'debian/copyright' file, the essence of which is: |
| 71 | + . |
| 72 | + Post by michelle on Sat, 14th Feb 2009, 18:00, UTC |
| 73 | + . |
| 74 | + I have been approached by some individuals over the time, including |
| 75 | + from the GNU project and the Ubuntu Foundation (as it appears at |
| 76 | + least), and was told that they lack a means of "legal security" for |
| 77 | + reuse without an explicit license. You can read my above post on |
| 78 | + details about my attitude regarding this matter, but as a start, I |
| 79 | + have decided to put the following line on the homepage and will also |
| 80 | + include it in any later release: |
| 81 | + . |
| 82 | + " This program, along with all documentation provided, is dedicated |
| 83 | + to the public. I do not pose any restrictions on how this material |
| 84 | + can be used, and explicitly encourage redistribution and |
| 85 | + modification for any purpose. " |
| 86 | + . |
| 87 | + Full thread from which the above is taken: |
| 88 | + --------------------------------------------------------------------- |
| 89 | + http://openbve.freeforums.org/licence-t39.html |
| 90 | + == Licence == |
| 91 | + . |
| 92 | + Post by Sacro on Sat, 26th Apr 2008, 16:39, UTC |
| 93 | + . |
| 94 | + Just out of curiosity, what licence applies to OpenBVE? It'd be nice |
| 95 | + to know if it's GPL or BSD or whatever as I'm quite interested in |
| 96 | + helping out. |
| 97 | + . |
| 98 | + Sacro |
| 99 | + . |
| 100 | + == Re: Licence == |
| 101 | + . |
| 102 | + Post by michelle on Sun, 27th Apr 2008, 07:43, UTC |
| 103 | + . |
| 104 | + My attitude differs from so called "free software" licenses. I try to |
| 105 | + explain: |
| 106 | + . |
| 107 | + With proprietary software, the developers usually try to restrict what |
| 108 | + you are allowed to do with the software to the uttermost extreme that |
| 109 | + is legally possible. This falls under the category of copyright. |
| 110 | + . |
| 111 | + Then there is something that is sometimes called green copyright. So |
| 112 | + called free software falls in this category. As with proprietary |
| 113 | + software, a license is used to tell users what they are allowed to do |
| 114 | + and what not. The difference to proprietary software is that so called |
| 115 | + free software licenses are usually much more permissive, yet the |
| 116 | + author decides what you are allowed to do and what not. So called free |
| 117 | + software is usually attributed to derive from "freedom" instead of |
| 118 | + "free of charge". Still, if the author employs a license telling other |
| 119 | + people what they can or cannot do, this inherently cannot have |
| 120 | + anything to do with freedom. |
| 121 | + . |
| 122 | + Then there is something called public domain, which I consider to be |
| 123 | + an inherently good thing as everyone has eventually the same rights as |
| 124 | + the author. However, releasing a work into the public domain is not |
| 125 | + legally meaningful in many countries. Also, releasing a work into the |
| 126 | + public domain (if possible) depends on the generosity of the author, |
| 127 | + and this decision is made by the author. |
| 128 | + . |
| 129 | + My attitude is even one step further: I am opposed to copyright, thus |
| 130 | + I marked the game with the legally not meaningful phrase of |
| 131 | + "anti-copyright". It is legally meaningless, because in every country |
| 132 | + that has some form of copyright, it would require these laws to be |
| 133 | + abandoned. Still, why do I have this attitude? |
| 134 | + . |
| 135 | + With a license, I would be telling other people what they can or |
| 136 | + cannot do. I am not such a person. I will not make any silly |
| 137 | + restrictions on how you can use this program, I will not tell you to |
| 138 | + put my name on any derived work, I will never ever give "permission" |
| 139 | + for you modify or redistribute the software, because I don't think |
| 140 | + that it is up to me telling you what you can or can't do. You should |
| 141 | + make this decision for yourself. |
| 142 | + . |
| 143 | + I hope this briefly explained the situation. |
| 144 | + . |
| 145 | + User avatar |
| 146 | + michelle |
| 147 | + . |
| 148 | + == Re: Licence == |
| 149 | + . |
| 150 | + Post by michelle on Sat, 14th Feb 2009, 18:00, UTC |
| 151 | + . |
| 152 | + I have been approached by some individuals over the time, including |
| 153 | + from the GNU project and the Ubuntu Foundation (as it appears at |
| 154 | + least), and was told that they lack a means of "legal security" for |
| 155 | + reuse without an explicit license. You can read my above post on |
| 156 | + details about my attitude regarding this matter, but as a start, I |
| 157 | + have decided to put the following line on the homepage and will also |
| 158 | + include it in any later release: |
| 159 | + . |
| 160 | + " This program, along with all documentation provided, is dedicated |
| 161 | + to the public. I do not pose any restrictions on how this material |
| 162 | + can be used, and explicitly encourage redistribution and |
| 163 | + modification for any purpose. " |
| 164 | + . |
| 165 | + michelle |
| 166 | + . |
| 167 | + == Re: Licence == |
| 168 | + . |
| 169 | + Way to go Michelle! |
| 170 | + . |
| 171 | + Good to hear from another lonely soul out there who gets the true |
| 172 | + meaning of freedom. |
| 173 | + . |
| 174 | + BVEColorado |
| 175 | + --------------------------------------------------------------------- |
| 176 | + . |
| 177 | + Managed content |
| 178 | + . |
| 179 | + In Openbve=1.4.0.0 in-program managed content was introduced, Openbve |
| 180 | + has gone out of their way to ensure that anything to be included in |
| 181 | + the managed content repository is explicitly distributable. Although |
| 182 | + this does affect Debian/Ubuntu directly, is shows an understanding |
| 183 | + of the problems that can be present without having explicit statements: |
| 184 | + . |
| 185 | + http://trainsimframework.org/develop/managed/licenses.html |
| 186 | + Managed add-ons - Accepted licenses |
| 187 | + . |
| 188 | + All packages that you want to make available under managed content |
| 189 | + must contain a LICENSE file in the root directory of the |
| 190 | + package. The LICENSE file must contain either one of the following |
| 191 | + texts: |
| 192 | + . |
| 193 | + ----------------------------------------------------------------- |
| 194 | + This add-on is placed under the following license: |
| 195 | + . |
| 196 | + YOU ARE ALLOWED TO MAKE VERBATIM COPIES OF THIS ADD-ON. |
| 197 | + . |
| 198 | + There are no terms and no conditions. This applies worldwide and |
| 199 | + is unlimited in duration. If additional permissions are granted, |
| 200 | + they are covered in a separate license. |
| 201 | + ----------------------------------------------------------------- |
| 202 | + . |
| 203 | + ----------------------------------------------------------------- |
| 204 | + THIS ADD-ON IS PLACED IN THE PUBLIC DOMAIN. |
| 205 | + . |
| 206 | + If this is not legally possible, you are given permission to |
| 207 | + use the add-on in any way you want (including redistribution |
| 208 | + and modification). There are no terms and no conditions. |
| 209 | + This applies worldwide and is unlimited in duration. |
| 210 | + ----------------------------------------------------------------- |
| 211 | + . |
| 212 | + This does not affect plugins packaged /in/ Debian, but is what is |
| 213 | + necessary should a developer wish to make their content available |
| 214 | + from the new in-program managed content downloading system. |
| 215 | + |
| 216 | +Files: debian/* |
| 217 | +Copyright: 2009-2012 Paul Sladen |
| 218 | +License: permissive |
| 219 | + Copying and distribution of this package, with or without |
| 220 | + modification, are permitted in any medium without royalty. |
0 commit comments