Nope, go ahead. Jpatokal 11:36, 11 October 2007 (EDT)
I just added a "Compatible licences" section. Should anything else be listed? ~ 220.127.116.11 09:47, 10 October 2007 (EDT)
What about "PD" - Public Domain - ? ~ 18.104.22.168 08:02, 11 October 2007 (EDT)
PD isn't really a "license", because it's entirely unconditional. But yes, we should mention that PD works are allowed. Jpatokal 11:36, 11 October 2007 (EDT)
asking permission to use forum reply at Wikitravel
I have received a valuable knowledge from other person on a forum/blog outside Wikitravel. Does someone have a template for a message asking whether pieces of that text can be used at Wikitravel? And I think this a good question for our FAQ here. --DenisYurkin 08:31, 26 January 2008 (EST)
I have the following text--how good is it for the above purpose?
Hi (person name).
Do you mind if I use some pieces of your post (its URL) to contribute to an article on Rome at Wikitravel, a free online travel guide written and edited entirely by travelers from around the globe?
I just realized an issue in this: with template like this, we promise attribution but don't actually add original author's name into "Based on work by ...". What we can do with this? --DenisYurkin 03:51, 9 February 2008 (EST)
Nothing. It Would Be Nice If(tm) we could add names to the attribution list somehow, but I don't think the Mediawiki software allows it. Jpatokal 06:39, 9 February 2008 (EST)
But the license requires us do provide attribution whatever it takes from us in terms of software (or manual work), doesn't it?
Our copyleft has been rather neglected over the years, and is currently confusing and inadequate to explain how licensing works on Wikitravel (IMHO). I'd like to propose these revisions to the copyleft. Here's the revised version in my sandbox: User:Peterfitzgerald/Copyleft. These changes, I think, should at the very least clarify how we have been doing things over the past several years, and would provide a basis to make necessary updates to several other outdated policies (most notably, en:Wikitravel:How to re-use Wikitravel guides). Do these changes seem reasonable? Have I gotten anything wrong? --PeterTalk 02:35, 21 February 2008 (EST)
Personally, I believe that the current page assumes a great deal of understanding of licensing from a reader--and is hard to understand by others. Q&As like "how can I re-use texts from forum replies" would seriously help, in my belief. --DenisYurkin 04:19, 21 February 2008 (EST)
Fair enough, I've now added more basic information for contributors to the FAQ section. I think it's important to keep the "licensing" section clear and precise, regardless of how confusing it may be for the uninitiated. The problem is that the article serves different groups of readers—those looking to redistribute & create derivative works, and those simply trying to understand what they need to do to start contributing. Hopefully the new FAQ entries should help with this. I will mention, though, that a side benefit of moving our site licensing from CC-by-SA 1.0 only for text to CC-by-SA any, is that it would significantly simplify our site licensing and make these issues less confusing. --PeterTalk 19:09, 21 February 2008 (EST)
Thanks; q&as like these are definitely helpful. --DenisYurkin 04:17, 22 February 2008 (EST)
Any objections to implementing the revisions as I made them at in my sandbox? Otherwise, I'll make them live (and will be sure to preserve Denis' last edit). --PeterTalk 16:29, 23 February 2008 (EST)
Alright, implemented. --PeterTalk 16:32, 24 February 2008 (EST)
Should we protect this page against anon edits longer term? It's a serious spam magnet lately, and being one of our most important pages, do anon's really ever need to edit it? – cacahuatetalk 18:45, 7 May 2008 (EDT)
I protected the local spam blacklist recently, because of the same reason. However, it feels like the spammers target the different Wikitravel sites in turn - sv: was swamped a few months ago, but with loads of cleaning and blocking spam accounts and IP's, they stopped and currently they seem to be here. The reason I doubt, in this case, is that protecting a page is not something we do happily. Could the spammers spam to make us protect or lock the page and thus prevent contributions? Some sort of hidden agenda? Personally, I do not think so, not as long as the spam do not enter the guide articles. In other words - meta pages, which are fairly stable and with few edits in itself, could be temporarily protected from anonymous contributions. Riggwelter 17:12, 8 May 2008 (EDT)
Yeah, I'm generally against a lot of page protections, but this is just such an important page and I doubt the need for anons to edit it without discussing on talk page first anyway – cacahuatetalk 19:07, 8 May 2008 (EDT)
This is a really important page, and for that reason alone (combined w/ the spam problem), I am sympathetic if not enthusiastic for an anon-level protection. But I'd like to add that it's really important that everyone keep in mind that this is an editable & collaborative policy, not some sort of set-in-stone law of Wikitravel. If we do protect, we should remain amenable to temporary un-protects to help anon editors revise this policy upon requests. And we should consider only protecting for a month or so, to see if the spammers move along. --PeterTalk 14:07, 12 May 2008 (EDT)
Wise words, and I concur. Besides, it is apparent that the spammers' interest is rather periodic. Riggwelter 14:54, 12 May 2008 (EDT)
Maps created with GMT
Is it possible to upload maps created with the Generic Mapping Tools (GMT)? On wikimedia commons there is the template GFDL-GMT for such maps. I am aware that I cannot upload images under GFDL, but maybe under another license? Specifically I'd like to upload a modified version of this map with roads/rails added. Bamse 04:29, 24 February 2009 (EST)
It appears to me that we cannot use GMT material, as they state that "GMT is [released under the GNU General Public License."  There's a part of that, though, that doesn't make much sense to me. I thought the GMT was a set of tools for manipulating data, not the data itself? If so, then others could distribute and modify the tools under the GNU FDL. But if the data was public domain... Anyway, it seems to me that we cannot use GMT content, but I don't understand this fully—perhaps someone else could better answer your question. --PeterTalk 13:48, 26 February 2009 (EST)
My reading of the situation is that the licensing of the output files is restricted only by the license of the map data set itself. For the Bolivia example given, the map data is public domain, so the output image plus any additional user modifications could be licensed any way you like. The GPL applies to the GMT program itself, but we're not distributing the program; same way that the GNU C compilers themselves are GPL'd, but that doesn't automatically apply to a program built with them - only the license on the source code of that program matters. - Dguillaime 16:37, 27 February 2009 (EST)
That makes sense to me. --PeterTalk 16:44, 27 February 2009 (EST)
I understand that text from the NPS websites are public domain. Does the same apply to pictures, maps, and other media? Thanks! 22.214.171.124 14:57, 15 February 2010 (EST)
See the "Ownership" section on http://www.nps.gov/disclaimer.htm. There are a number of pictures and maps on the NPS web site that they have licensed from private individuals, so those cannot be freely re-used, but provided that there isn't an author or copyright specified the default for NPS content is that it is released into the public domain. -- Ryan • (talk) • 15:08, 15 February 2010 (EST)
I would like to propose that we incorporate the new CC0 license wavier into our licensing options. It's very similar to public domain, but designed to be applicable in jurisdictions that prohibit public domain releases. Image:Sarahan view.jpg is an example of an image whose original source is released under CC0. LtPowers 16:30, 16 August 2010 (EDT)
By all means, although I don't think it necessary to add to the drop down menu on the upload form. I believe that this license, interestingly enough, granted me the option to release the image into the Public Domain, which I did ;) --PeterTalk 23:59, 18 August 2010 (EDT)
That's an interesting interpretation. The legalities of that are beyond my ken, though, which is why I would prefer a CC0 template that removes that uncertainty. LtPowers 09:10, 19 August 2010 (EDT)