Thread: [Tuxpaint-devel] GFDL images
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Albert C. <al...@us...> - 2005-06-12 19:52:15
|
I'm thinking Tux Paint needs a goat: http://commons.wikimedia.org/wiki/Image:Billy_goat.jpg The license info is: Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. That should be fine, as far as freedom is concerned. It's not a proprietary goat. What about credit though? Where does it go? Where does a copy of the GFDL go? |
From: Ben A. <sy...@sa...> - 2005-06-12 23:39:43
|
On Sun, 2005-06-12 at 15:51 -0400, Albert Cahalan wrote: > I'm thinking Tux Paint needs a goat: > > http://commons.wikimedia.org/wiki/Image:Billy_goat.jpg Hm. Tread carefully with that GFDL'd goat. Debian has problems with the GFDL. And it's not just invariant sections that are at issue, apparently. Ben |
From: Albert C. <al...@us...> - 2005-06-13 01:18:00
|
On Sun, 2005-06-12 at 20:39 -0300, Ben Armstrong wrote: > On Sun, 2005-06-12 at 15:51 -0400, Albert Cahalan wrote: > > I'm thinking Tux Paint needs a goat: > > > > http://commons.wikimedia.org/wiki/Image:Billy_goat.jpg > > Hm. Tread carefully with that GFDL'd goat. Debian has problems with the > GFDL. And it's not just invariant sections that are at issue, > apparently. Sheesh, it's not a satanic goat. This is all really, really, sad and pitiful. >From time to time I come across images that are under one the the Creative Commons licenses. How about those? |
From: Ben A. <sy...@sa...> - 2005-06-13 18:18:17
|
On Sun, 2005-06-12 at 21:16 -0400, Albert Cahalan wrote: > Sheesh, it's not a satanic goat. > > This is all really, really, sad and pitiful. I agree it is a sad situation, but probably not for the reasons you think it is. Oh, wouldn't the world be so much simpler if people would just compromise their principles and "go with the flow"? It's no big deal, though. If it should be included, go ahead. To make life easier for me, though, would you please keep track of individual media file licenses? Then if I need to make a "goatless tuxpaint stamps" package for Debian, I can do it relatively easily. Hm, for that matter, shouldn't the copyright notices and licenses of media files we have imported into the stamps package be kept along with the files, just to satisfy the requirements of the licenses? Right now, all we seem to have is URLs to original sources & authors in the CHANGES.txt file. Thanks, Ben |
From: Bill K. <nb...@so...> - 2005-06-13 18:25:51
|
On Mon, Jun 13, 2005 at 03:17:39PM -0300, Ben Armstrong wrote: > Hm, for that matter, shouldn't the copyright notices and licenses of > media files we have imported into the stamps package be kept along with > the files, just to satisfy the requirements of the licenses? Right now, > all we seem to have is URLs to original sources & authors in the > CHANGES.txt file. Agreed. In some cases, I have "#" comments in the corresponding '.txt' file that goes along with each PNG image. It'd probably be good to have a comprehensive license file somewhere in 'docs' though. -bill! |
From: Albert C. <al...@us...> - 2005-06-13 20:04:19
|
On Mon, 2005-06-13 at 15:17 -0300, Ben Armstrong wrote: > On Sun, 2005-06-12 at 21:16 -0400, Albert Cahalan wrote: > > Sheesh, it's not a satanic goat. > > > > This is all really, really, sad and pitiful. > > I agree it is a sad situation, but probably not for the reasons you > think it is. Oh, wouldn't the world be so much simpler if people would > just compromise their principles and "go with the flow"? That's not a nice way to put things. I'm quite sure that nearly all wikipedia image contributers would be happy with most licenses that require that the images remain non-proprietary, as ensured by the GPL and many of the Creative Commons licenses. The GFDL is chosen pretty much by default, because dual-licensing is a pain. No principles need be compromised. Many contributers, probably "most" but not "nearly all", would even be happy with public domain or a BSD-style license. > Hm, for that matter, shouldn't the copyright notices and licenses of > media files we have imported into the stamps package be kept along with > the files, just to satisfy the requirements of the licenses? Right now, > all we seem to have is URLs to original sources & authors in the > CHANGES.txt file. I tried including DOD media ID numbers for many of the images, but they got clobbered by some sort of automated translation. |
From: Bill K. <nb...@so...> - 2005-06-13 20:31:20
|
On Mon, Jun 13, 2005 at 04:03:19PM -0400, Albert Cahalan wrote: > I tried including DOD media ID numbers for many of the images, > but they got clobbered by some sort of automated translation. >:^P Crud. Okay, so yeah, let's not put them in the .txt file, but cobble them together in some separate text file under docs/. That'll solve a few issues at once. :^) -bill! |
From: Ben A. <sy...@sa...> - 2005-06-13 23:39:08
|
On Mon, 2005-06-13 at 16:03 -0400, Albert Cahalan wrote: > That's not a nice way to put things. > > I'm quite sure that nearly all wikipedia image contributers > would be happy with most licenses that require that the images > remain non-proprietary, as ensured by the GPL and many of the > Creative Commons licenses. The GFDL is chosen pretty much by > default, because dual-licensing is a pain. > > No principles need be compromised. > > Many contributers, probably "most" but not "nearly all", would > even be happy with public domain or a BSD-style license. Unfortunately, in a license, the intent of the author doesn't count for anything unless it is explicitly stated. There can be no "reading between the lines" of licenses. If these authors would be happy with their work re-licensed under the GPL, they need to dual-license. We can't be left to guess. Ben |