Merge lp:~widelands-dev/widelands/copyright-file into lp:widelands

Proposed by SirVer
Status: Merged
Merged at revision: 7741
Proposed branch: lp:~widelands-dev/widelands/copyright-file
Merge into: lp:widelands
Diff against target: 365 lines (+351/-0)
1 file modified
debian/copyright (+351/-0)
To merge this branch: bzr merge lp:~widelands-dev/widelands/copyright-file
Reviewer Review Type Date Requested Status
GunChleoc Approve
Martin Quinson Pending
Widelands Developers Pending
Review via email: mp+283575@code.launchpad.net

This proposal supersedes a proposal from 2014-12-21.

Description of the change

Update the copyright file in debian packaging to document the various licenses origins of files used. Mainly to incorporate the new fonts we now bundle, but I also thought we should probably mention our third party libraries.

We have not yet documented all of these properly though, see copyright.todo for details on remaining work. There are some questions there where I'm not sure how to proceed. I'm also open for other feedback.

I think it is possible to add individual people as reviewers, so I'll add GunChleoc (since you added the fonts) and Martin Quinson since you're the Debian maintainer and probably know more about this than me. Being appointed as reviewers will presumably ping you so that you are aware of this merge proposal. Combined I believe we can answer the questions I have posted, and get the copyright file up to date. :)

To post a comment you must log in.
Revision history for this message
GunChleoc (gunchleoc) wrote : Posted in a previous version of this proposal

I used diff comments to add some more info.

Revision history for this message
Hans Joachim Desserud (hjd) wrote : Posted in a previous version of this proposal

This is surprisingly hard.

I did have some progress when I discovered that I can open fonts in FontViewer on Ubuntu and it will be able to disply embedded information such as copyright information.

Revision history for this message
SirVer (sirver) wrote : Posted in a previous version of this proposal

ping. hjd, what is the state of this branch?

Revision history for this message
Hans Joachim Desserud (hjd) wrote : Posted in a previous version of this proposal

>ping. hjd, what is the state of this branch?

Hello hello. Not much has happened since the previous commit/comment.

Like I talked about in https://code.launchpad.net/~hjd/widelands/tests-poc/+merge/250533, the main intent with this branch was to get the packaging in a better shape to make it easier to create the official Debian packages once we release build19 (rc). It is my understanding that the Debian policies require packages to give full copyright statement on their content, so since it will need to be done anyways we might as well get it done early.

This work is not critical for Widelands itself since we don't really have such obligations (unless specific licenses state otherwise) but is in general nice to give credit to other people's work which we include. I'd say we are doing a good job of this though, at least with the fonts/licenses there.

As I mentioned, I believe this work will need to be done for the offical Debian packages, which is why I wanted to start it straight away, while the new fonts were still fresh. This is also why I added the Debian maintainer as a reviewer here, hoping to get some feedback and possibly guidance.

I am a bit stuck on the questions in the todo, and I don't really know how to proceed with this. I'll leave this open for a while longer, but if I don't hear anything, I'll likely close it as a draft/experiment. While I would like to see this done properly, I don't know whether the current state of the branch does more good than harm, and I don't think it is that critical for the Widelands project to have this file 100% completed.

Revision history for this message
Martin Quinson (mquinson) wrote : Posted in a previous version of this proposal

I'm so deep under water wrt my daytime job that I am completely unable to help (or even properly read your emails) before the summer.

Sorry and good luck
Mt

----- Mail original -----
> >ping. hjd, what is the state of this branch?
>
> Hello hello. Not much has happened since the previous commit/comment.
>
> Like I talked about in
> https://code.launchpad.net/~hjd/widelands/tests-poc/+merge/250533, the main
> intent with this branch was to get the packaging in a better shape to make
> it easier to create the official Debian packages once we release build19
> (rc). It is my understanding that the Debian policies require packages to
> give full copyright statement on their content, so since it will need to be
> done anyways we might as well get it done early.
>
> This work is not critical for Widelands itself since we don't really have
> such obligations (unless specific licenses state otherwise) but is in
> general nice to give credit to other people's work which we include. I'd say
> we are doing a good job of this though, at least with the fonts/licenses
> there.
>
> As I mentioned, I believe this work will need to be done for the offical
> Debian packages, which is why I wanted to start it straight away, while the
> new fonts were still fresh. This is also why I added the Debian maintainer
> as a reviewer here, hoping to get some feedback and possibly guidance.
>
> I am a bit stuck on the questions in the todo, and I don't really know how to
> proceed with this. I'll leave this open for a while longer, but if I don't
> hear anything, I'll likely close it as a draft/experiment. While I would
> like to see this done properly, I don't know whether the current state of
> the branch does more good than harm, and I don't think it is that critical
> for the Widelands project to have this file 100% completed.
> --
> https://code.launchpad.net/~widelands-dev/widelands/copyright-file/+merge/245297
> You are requested to review the proposed merge of
> lp:~widelands-dev/widelands/copyright-file into
> lp:~widelands-dev/widelands/debian.
>

Revision history for this message
Hans Joachim Desserud (hjd) wrote : Posted in a previous version of this proposal

No problem Martin, that's completely understandable. Thanks for letting us know. :)

In the meantime, I'll just put this branch on ice, and we'll get back to it when we have a better idea on how to proceed. I'll try to adjust the review status so that it doesn't show up in the list of active reviews.

Revision history for this message
SirVer (sirver) wrote :

With b19 getting closer it is probably time to revisit this branch and get it in.

Revision history for this message
bunnybot (widelandsofficial) wrote :

Hi, I am bunnybot (https://github.com/widelands/bunnybot).

I am keeping the source branch lp:~widelands-dev/widelands/copyright-file mirrored to https://github.com/widelands/widelands/tree/_widelands_dev_widelands_copyright_file

You can give me commands by starting a line with @bunnybot <command>. I understand:
 merge: Merges the source branch into the target branch, closing the merge proposal. I will use the proposed commit message if it is set.

Revision history for this message
bunnybot (widelandsofficial) wrote :

Travis build 332 has changed state to: passed. Details: https://travis-ci.org/widelands/widelands/builds/104037101.

Revision history for this message
GunChleoc (gunchleoc) wrote :

Added a comment regarding the todo file.

Revision history for this message
bunnybot (widelandsofficial) wrote :

Continuous integration builds have changed state:

Travis build 368. State: passed. Details: https://travis-ci.org/widelands/widelands/builds/104407410.
Appveyor build 275. State: success. Details: https://ci.appveyor.com/project/widelands-dev/widelands/build/_widelands_dev_widelands_copyright_file-275.

Revision history for this message
SirVer (sirver) wrote :

I gave all of the TODOs a shot - all licenses in questions are BSD-ish, so I feel that even if we did not get it completely right, it should not be the end of the world.

PTAL.

Revision history for this message
bunnybot (widelandsofficial) wrote :

Continuous integration builds have changed state:

Travis build 379. State: canceled. Details: https://travis-ci.org/widelands/widelands/builds/104469110.
Appveyor build 286. State: success. Details: https://ci.appveyor.com/project/widelands-dev/widelands/build/_widelands_dev_widelands_copyright_file-286.

Revision history for this message
GunChleoc (gunchleoc) wrote :

LGTM

review: Approve
Revision history for this message
SirVer (sirver) wrote :

@bunnybot merge

> Am 25.01.2016 um 10:16 schrieb GunChleoc <email address hidden>:
>
> Review: Approve
>
> LGTM
> --
> https://code.launchpad.net/~widelands-dev/widelands/copyright-file/+merge/283575
> Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands/copyright-file into lp:widelands.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~widelands-dev
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~widelands-dev
> More help : https://help.launchpad.net/ListHelp

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/copyright'
2--- debian/copyright 2016-01-22 07:20:01 +0000
3+++ debian/copyright 2016-01-24 17:46:16 +0000
4@@ -22,6 +22,354 @@
5 On Debian systems, the complete text of the GNU General Public
6 License version 2 can be found in "/usr/share/common-licenses/GPL-2".
7
8+Files: src/third_party/eris/*
9+Copyright: 2013 Florian Nücke, 1994–2013 Lua.org, PUC-Rio.
10+License:
11+Eris
12+Copyright (c) 2013 Florian Nücke.
13+
14+Permission is hereby granted, free of charge, to any person obtaining a copy
15+of this software and associated documentation files (the "Software"), to deal
16+in the Software without restriction, including without limitation the rights
17+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
18+copies of the Software, and to permit persons to whom the Software is
19+furnished to do so, subject to the following conditions:
20+
21+The above copyright notice and this permission notice shall be included in
22+all copies or substantial portions of the Software.
23+
24+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
25+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
26+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
27+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
28+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
29+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
30+THE SOFTWARE.
31+
32+-----------------------------------------------------------------------------
33+
34+Lua 5.2.2 from http://www.lua.org/ with patches http://www.lua.org/bugs.html
35+slightly modified to access internal library functions for persistence.
36+
37+Copyright © 1994–2013 Lua.org, PUC-Rio.
38+
39+Permission is hereby granted, free of charge, to any person obtaining a copy
40+of this software and associated documentation files (the "Software"), to deal
41+in the Software without restriction, including without limitation the rights
42+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
43+copies of the Software, and to permit persons to whom the Software is
44+furnished to do so, subject to the following conditions:
45+
46+The above copyright notice and this permission notice shall be included in
47+all copies or substantial portions of the Software.
48+
49+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
50+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
51+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
52+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
53+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
54+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
55+THE SOFTWARE.
56+
57+Files: src/third_party/minizip/*
58+Copyright 1995-2013 Jean-loup Gailly and Mark Adler.
59+Licens: zlib license (BSD like)
60+ zlib.h -- interface of the 'zlib' general purpose compression library
61+ version 1.2.8, April 28th, 2013
62+
63+ Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler
64+
65+ This software is provided 'as-is', without any express or implied
66+ warranty. In no event will the authors be held liable for any damages
67+ arising from the use of this software.
68+
69+ Permission is granted to anyone to use this software for any purpose,
70+ including commercial applications, and to alter it and redistribute it
71+ freely, subject to the following restrictions:
72+
73+ 1. The origin of this software must not be misrepresented; you must not
74+ claim that you wrote the original software. If you use this software
75+ in a product, an acknowledgment in the product documentation would be
76+ appreciated but is not required.
77+ 2. Altered source versions must be plainly marked as such, and must not be
78+ misrepresented as being the original software.
79+ 3. This notice may not be removed or altered from any source distribution.
80+
81+ Jean-loup Gailly Mark Adler
82+ jloup@gzip.org madler@alumni.caltech.edu
83+
84+Files: i18n/fonts/Culmus/*
85+Copyright: 2010 by Yoram Gnat (gyoramg@users.sourceforge.net).
86+License: This package is distributed under the terms of GNU General Public License
87+version 2 (see file GNU-GPL).
88+---------------------------------------------------------------------
89+
90+"Taamey Frank CLM" fonts are copyright (C) 2010 by Yoram Gnat
91+(gyoramg@users.sourceforge.net). All rights reserved.
92+
93+As a special exception, if you create a document which uses
94+this font, and embed this font or unaltered portions of this
95+font into the document, this font does not by itself cause
96+the resulting document to be covered by the
97+GNU General Public License. This exception does not however
98+invalidate any other reasons why the document might be covered
99+by the GNU General Public License. If you modify this font,
100+you may extend this exception to your version of the font,
101+but you are not obligated to do so. If you do not wish to do so,
102+delete this exception statement from your version.
103+
104+Files: i18n/fonts/Nakula/*
105+Copyright: Nakula Devanagari font © 2006 University of Cambridge. Designed and developed by IMRC, India. Latin and Cyrillic glyphs from the font Nimbus Roman No9 L Regular, © 1999 (URW)++ Design & Development; Cyrillic glyphs by Valek Filippov © 2001-2002.
106+License:
107+These fonts are free software; you can redistribute them and/or modify them under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
108+
109+These fonts are distributed in the hope that they 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.
110+
111+Files: i18n/fonts/Sinhala/*
112+Copyright: 2004,2008 Anuradha Ratnaweera and Harshani Devadithya, 2006 Harshula Jayasuriya, 1994, The Wellcome Trust, London
113+License:
114+ LKLUG font is free software; you can redistribute it and/or modify
115+ it under the terms of the GNU General Public License, version 2, as
116+ published by the Free Software Foundation.
117+
118+ This program is distributed in the hope that it will be useful, but
119+ WITHOUT ANY WARRANTY; without even the implied warranty of
120+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
121+ General Public License, version 2, for more details.
122+
123+ The Debian packaging is (C) 2004,2008, Anuradha Ratnaweera, and is
124+ licensed under the GNU General Public License, version 2.
125+
126+ You should have received a copy of the GNU General Public License,
127+ version 2, in the file `COPYING', or on Debian based systems in the
128+ file `/usr/share/common-licenses/GPL-2'; if not, write to the Free
129+ Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
130+ MA 02110-1301 USA.
131+
132+Files: i18n/fonts/MicroHei/*
133+Copyright WenQuanYi Board of Trustees 2008-2009
134+License: Apache 2.0
135+ Apache License
136+ Version 2.0, January 2004
137+ http://www.apache.org/licenses/
138+
139+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
140+
141+ 1. Definitions.
142+
143+ "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this
144+ document.
145+
146+ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
147+
148+ "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common
149+ control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the
150+ direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
151+ outstanding shares, or (iii) beneficial ownership of such entity.
152+
153+ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
154+
155+ "Source" form shall mean the preferred form for making modifications, including but not limited to software source code,
156+ documentation source, and configuration files.
157+
158+ "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not
159+ limited to compiled object code, generated documentation, and conversions to other media types.
160+
161+ "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a
162+ copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
163+
164+ "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which
165+ the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship.
166+ For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by
167+ name) to the interfaces of, the Work and Derivative Works thereof.
168+
169+ "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to
170+ that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner
171+ or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition,
172+ "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including
173+ but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are
174+ managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is
175+ conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
176+
177+ "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor
178+ and subsequently incorporated within the Work.
179+
180+ 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a
181+ perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works
182+ of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
183+
184+ 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,
185+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made,
186+ use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable
187+ by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with
188+ the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim
189+ or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or
190+ contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the
191+ date such litigation is filed.
192+
193+ 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without
194+ modifications, and in Source or Object form, provided that You meet the following conditions:
195+
196+ 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
197+
198+ 2. You must cause any modified files to carry prominent notices stating that You changed the files; and
199+
200+ 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and
201+ attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative
202+ Works; and
203+
204+ 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must
205+ include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to
206+ any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the
207+ Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display
208+ generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for
209+ informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You
210+ distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot
211+ be construed as modifying the License.
212+
213+ You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions
214+ for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use,
215+ reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
216+
217+ 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the
218+ Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.
219+ Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have
220+ executed with Licensor regarding such Contributions.
221+
222+ 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the
223+ Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of
224+ the NOTICE file.
225+
226+ 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each
227+ Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
228+ implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
229+ PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume
230+ any risks associated with Your exercise of permissions under this License.
231+
232+ 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise,
233+ unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be
234+ liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as
235+ a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill,
236+ work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has
237+ been advised of the possibility of such damages.
238+
239+ 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer,
240+ and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this
241+ License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf
242+ of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred
243+ by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
244+
245+ END OF TERMS AND CONDITIONS
246+ APPENDIX: How to apply the Apache License to your work
247+
248+ To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]"
249+ replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment
250+ syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed
251+ page" as the copyright notice for easier identification within third-party archives.
252+ Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file
253+ except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless
254+ required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS,
255+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing
256+ permissions and limitations under the License.
257+
258+Files: i18n/fonts/*mmrCensus*
259+Copyright SIG, http://www.myanmarlanguage.org/site-info/SIG-Myanmar-Language
260+License: SIL Open Font License, Version 1.1 (http://scripts.sil.org/OFL)
261+ PREAMBLE
262+ The goals of the Open Font License (OFL) are to stimulate worldwide
263+ development of collaborative font projects, to support the font creation
264+ efforts of academic and linguistic communities, and to provide a free and
265+ open framework in which fonts may be shared and improved in partnership
266+ with others.
267+ .
268+ The OFL allows the licensed fonts to be used, studied, modified and
269+ redistributed freely as long as they are not sold by themselves. The
270+ fonts, including any derivative works, can be bundled, embedded,
271+ redistributed and/or sold with any software provided that any reserved
272+ names are not used by derivative works. The fonts and derivatives,
273+ however, cannot be released under any other type of license. The
274+ requirement for fonts to remain under this license does not apply
275+ to any document created using the fonts or their derivatives.
276+ .
277+ DEFINITIONS
278+ "Font Software" refers to the set of files released by the Copyright
279+ Holder(s) under this license and clearly marked as such. This may
280+ include source files, build scripts and documentation.
281+ .
282+ "Reserved Font Name" refers to any names specified as such after the
283+ copyright statement(s).
284+ .
285+ "Original Version" refers to the collection of Font Software components as
286+ distributed by the Copyright Holder(s).
287+ .
288+ "Modified Version" refers to any derivative made by adding to, deleting,
289+ or substituting -- in part or in whole -- any of the components of the
290+ Original Version, by changing formats or by porting the Font Software to a
291+ new environment.
292+ .
293+ "Author" refers to any designer, engineer, programmer, technical
294+ writer or other person who contributed to the Font Software.
295+ .
296+ PERMISSION & CONDITIONS
297+ Permission is hereby granted, free of charge, to any person obtaining
298+ a copy of the Font Software, to use, study, copy, merge, embed, modify,
299+ redistribute, and sell modified and unmodified copies of the Font
300+ Software, subject to the following conditions:
301+ .
302+ 1) Neither the Font Software nor any of its individual components,
303+ in Original or Modified Versions, may be sold by itself.
304+ .
305+ 2) Original or Modified Versions of the Font Software may be bundled,
306+ redistributed and/or sold with any software, provided that each copy
307+ contains the above copyright notice and this license. These can be
308+ included either as stand-alone text files, human-readable headers or
309+ in the appropriate machine-readable metadata fields within text or
310+ binary files as long as those fields can be easily viewed by the user.
311+ .
312+ 3) No Modified Version of the Font Software may use the Reserved Font
313+ Name(s) unless explicit written permission is granted by the corresponding
314+ Copyright Holder. This restriction only applies to the primary font name as
315+ presented to the users.
316+ .
317+ 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
318+ Software shall not be used to promote, endorse or advertise any
319+ Modified Version, except to acknowledge the contribution(s) of the
320+ Copyright Holder(s) and the Author(s) or with their explicit written
321+ permission.
322+ .
323+ 5) The Font Software, modified or unmodified, in part or in whole,
324+ must be distributed entirely under this license, and must not be
325+ distributed under any other license. The requirement for fonts to
326+ remain under this license does not apply to any document created
327+ using the Font Software.
328+ .
329+ TERMINATION
330+ This license becomes null and void if any of the above conditions are
331+ not met.
332+ .
333+ DISCLAIMER
334+ THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
335+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
336+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
337+ OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
338+ COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
339+ INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
340+ DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
341+ FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
342+ OTHER DEALINGS IN THE FONT SOFTWARE.
343+
344+Files: i18n/fonts/DejaVu/*
345+Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream Vera is a trademark of Bitstream, Inc.
346+License: Vera Fonts License, BSD like
347+Permission is hereby granted, free of charge, to any person obtaining a copy of the fonts accompanying this license ("Fonts") and associated documentation files (the "Font Software"), to reproduce and distribute the Font Software, including without limitation the rights to use, copy, merge, publish, distribute, and/or sell copies of the Font Software, and to permit persons to whom the Font Software is furnished to do so, subject to the following conditions:
348+The above copyright and trademark notices and this permission notice shall be included in all copies of one or more of the Font Software typefaces.
349+The Font Software may be modified, altered, or added to, and in particular the designs of glyphs or characters in the Fonts may be modified and additional glyphs or characters may be added to the Fonts, only if the fonts are renamed to names not containing either the words "Bitstream" or the word "Vera".
350+This License becomes null and void to the extent applicable to Fonts or Font Software that has been modified and is distributed under the "Bitstream Vera" names.
351+The Font Software may be sold as part of a larger software package but no copy of one or more of the Font Software typefaces may be sold by itself.
352+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL BITSTREAM OR THE GNOME FOUNDATION BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.
353+Except as contained in this notice, the names of Gnome, the Gnome Foundation, and Bitstream Inc., shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Font Software without prior written authorization from the Gnome Foundation or Bitstream Inc., respectively. For further information, contact: fonts at gnome dot org.
354+
355+
356 Files: i18n/fonts/Widelands/Widelands.ttf
357 Copyright: 2006-2010, Peter Schwanemann (Peter (AT) drehatlas (DOT) de)
358 License: SIL Open Font License, Version 1.1 (http://scripts.sil.org/OFL)
359@@ -136,3 +484,6 @@
360 .
361 On Debian systems, the complete text of the GNU General
362 Public License version 2 can be found in "/usr/share/common-licenses/GPL-2".
363+
364+
365+

Subscribers

People subscribed via source and target branches

to status/vote changes: