/usr/share/doc/openbve-data/copyright is in openbve-data 1.4.0.5+dfsg-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 | Format: http://dep.debian.net/deps/dep5/
Upstream-Name: Openbve Stable
Upstream-Contact: Michelle Boucquemont <reschanger@gmail.com>
Source: http://trainsimframework.org/downloads.html (openbve_stable.zip)
Comment: From http://trainsimframework.org/credits.html
Files: *
Copyright: 2008-2012 Michelle Boucquemont
Anthony Bowden
Jens Rügenhagen
License: openbve-permissive
Files: Data/Languages/ca-ES.cfg
Copyright: Marc Riera Irigoyen
License: openbve-permissive
Files: Data/Languages/de-*.cfg
Copyright: Jan Henning
License: openbve-permissive
Files: Data/Languages/hu-HU.cfg
Copyright: "phontanka"
License: openbve-permissive
Files: Data/Languages/nl-NL.cfg
Copyright: Dirk-Jan Breunissen
License: openbve-permissive
Files: Data/Languages/zh-CN.cfg
Copyright: 黃皓俊 Alvin Wong
License: openbve-permissive
License: openbve-permissive
From 'http://trainsimframework.org/index.html', current:
.
openBVE is a cross-platform, free-as-in-freedom train simulator
placed in the public domain. This means that you can make any
modifications to it you like and share your modifications with
others.
.
From 'Readme.txt', current:
.
This program is placed in the public domain. This means that you
can make any modifications to it you like and share your
modifications with others.
.
From 'http://trainsimframework.org/index.html', earlier versions:
.
Dedication to the public
.
This program, along with all website content, is dedicated to the
public. I do not pose any restrictions or requirements on how this
material can be used, and explicitly encourage redistribution and
modification for any purpose.
.
From 'Readme.txt', earlier versions:
.
Dedication to the public
.
This program is dedicated to the public. I do not pose any
restrictions or requirements on how this material can be used, and
explicitly encourage redistribution and modification for any
purpose.
Comment:
Below are some of the accompanying statements that Openbve and the
upstream developers have made regarding how the work can be used,
this provides greater insight and context into the wishes of upstream,
beyond the simple and permissive "public domain" wording.
.
It's notable that the intent and appreciation for sharing and
openness has always present with upstream, as can be seen from the
name "Open...". Openbve was itself a reaction to "freeware", but
non-distributable (and non-fixable) version of "BVE Train Simulator".
.
Although the intent has been constant, the PD wording has evolved,
attempting to remain short. Upstream have welcomed input where it
as been offered on the licence-terminology; as can be seen in the
discussion and the preference would be for copyright law to not
exist (international treaties dictate otherwise for the moment).
.
History
.
In 2008, in preparation for Debian packaging, discussion was started
with upstream for the upstream bugtracker/forum and is copied below
for context. (It was at the time the closest introduction to the
licence and intent behind the Openbve project).
.
More information on the thinking behind the "license free" intend has been
saved in this 'debian/copyright' file, the essence of which is:
.
Post by michelle on Sat, 14th Feb 2009, 18:00, UTC
.
I have been approached by some individuals over the time, including
from the GNU project and the Ubuntu Foundation (as it appears at
least), and was told that they lack a means of "legal security" for
reuse without an explicit license. You can read my above post on
details about my attitude regarding this matter, but as a start, I
have decided to put the following line on the homepage and will also
include it in any later release:
.
" This program, along with all documentation provided, is dedicated
to the public. I do not pose any restrictions on how this material
can be used, and explicitly encourage redistribution and
modification for any purpose. "
.
Full thread from which the above is taken:
---------------------------------------------------------------------
http://openbve.freeforums.org/licence-t39.html
== Licence ==
.
Post by Sacro on Sat, 26th Apr 2008, 16:39, UTC
.
Just out of curiosity, what licence applies to OpenBVE? It'd be nice
to know if it's GPL or BSD or whatever as I'm quite interested in
helping out.
.
Sacro
.
== Re: Licence ==
.
Post by michelle on Sun, 27th Apr 2008, 07:43, UTC
.
My attitude differs from so called "free software" licenses. I try to
explain:
.
With proprietary software, the developers usually try to restrict what
you are allowed to do with the software to the uttermost extreme that
is legally possible. This falls under the category of copyright.
.
Then there is something that is sometimes called green copyright. So
called free software falls in this category. As with proprietary
software, a license is used to tell users what they are allowed to do
and what not. The difference to proprietary software is that so called
free software licenses are usually much more permissive, yet the
author decides what you are allowed to do and what not. So called free
software is usually attributed to derive from "freedom" instead of
"free of charge". Still, if the author employs a license telling other
people what they can or cannot do, this inherently cannot have
anything to do with freedom.
.
Then there is something called public domain, which I consider to be
an inherently good thing as everyone has eventually the same rights as
the author. However, releasing a work into the public domain is not
legally meaningful in many countries. Also, releasing a work into the
public domain (if possible) depends on the generosity of the author,
and this decision is made by the author.
.
My attitude is even one step further: I am opposed to copyright, thus
I marked the game with the legally not meaningful phrase of
"anti-copyright". It is legally meaningless, because in every country
that has some form of copyright, it would require these laws to be
abandoned. Still, why do I have this attitude?
.
With a license, I would be telling other people what they can or
cannot do. I am not such a person. I will not make any silly
restrictions on how you can use this program, I will not tell you to
put my name on any derived work, I will never ever give "permission"
for you modify or redistribute the software, because I don't think
that it is up to me telling you what you can or can't do. You should
make this decision for yourself.
.
I hope this briefly explained the situation.
.
User avatar
michelle
.
== Re: Licence ==
.
Post by michelle on Sat, 14th Feb 2009, 18:00, UTC
.
I have been approached by some individuals over the time, including
from the GNU project and the Ubuntu Foundation (as it appears at
least), and was told that they lack a means of "legal security" for
reuse without an explicit license. You can read my above post on
details about my attitude regarding this matter, but as a start, I
have decided to put the following line on the homepage and will also
include it in any later release:
.
" This program, along with all documentation provided, is dedicated
to the public. I do not pose any restrictions on how this material
can be used, and explicitly encourage redistribution and
modification for any purpose. "
.
michelle
.
== Re: Licence ==
.
Way to go Michelle!
.
Good to hear from another lonely soul out there who gets the true
meaning of freedom.
.
BVEColorado
---------------------------------------------------------------------
.
Managed content
.
In Openbve=1.4.0.0 in-program managed content was introduced, Openbve
has gone out of their way to ensure that anything to be included in
the managed content repositary is explicitly distributable. Although
this does affect Debian/Ubuntu directly, is shows an understanding
of the problems that can be present without having explicit statements:
.
http://trainsimframework.org/develop/managed/licenses.html
Managed add-ons - Accepted licenses
.
All packages that you want to make available under managed content
must contain a LICENSE file in the root directory of the
package. The LICENSE file must contain either one of the following
texts:
.
-----------------------------------------------------------------
This add-on is placed under the following license:
.
YOU ARE ALLOWED TO MAKE VERBATIM COPIES OF THIS ADD-ON.
.
There are no terms and no conditions. This applies worldwide and
is unlimited in duration. If additional permissions are granted,
they are covered in a separate license.
-----------------------------------------------------------------
.
-----------------------------------------------------------------
THIS ADD-ON IS PLACED IN THE PUBLIC DOMAIN.
.
If this is not legally possible, you are given permission to
use the add-on in any way you want (including redistribution
and modification). There are no terms and no conditions.
This applies worldwide and is unlimited in duration.
-----------------------------------------------------------------
.
This do not affect plugins packaged in Debian, but are what is
necessary should a developer wish to make their content available
from the new in-program managed content downloading system.
Files: Data/mask.bin
License: openbve-permissive
Copyright: 2008-2012 Michelle Boucquemont
Comment:
'Data/mask.bin' is a raw bitmask used along with 'Data/icon.bmp' for
the Window Manager icon setting:
.
Sdl.SDL_WM_SetIcon(bitmap, mask)
.
The file is (128 bytes) == (1024 bits) == (32 x 32 bits), in the raw bitmask/
bitarray form designed for sending straight to:
.
http://www.libsdl.org/cgi/docwiki.cgi/SDL_WM_SetIcon
.
"points to a bitmap with bits set where the corresponding
pixel should be visible. The format of the bitmap is
as follows: Scanlines come in the usual top-down order.
Each scanline consists of (width / 8) bytes, rounded up."
.
The following Python can be used to print the contents in ASCII-art form:
.
python -c "import struct; \
print ''.join(map(bin,struct.unpack('32I',open('Data/mask.bin') \
.read(128)))).replace('0b','\n').replace('0',' ').replace('1','**')"
Files: debian/*
Copyright: 2009-2012 Paul Sladen
License: permissive
Copying and distribution of this package, with or without
modification, are permitted in any medium without royalty.
|