<DIV>Hi Tomos</DIV>
<DIV> </DIV>
<DIV>I do think this kind of discussion do not belong to the english mailing list. </DIV>
<DIV> </DIV>
<DIV>The issues you are raising are not only relevant to the english wikipedia. Articles could be copied from other languages than english to the japanese wikipedia, so that makes it at a minimum wikipedia-l issue, and since you are mentionning wiktionary, I guess it should go to foundation-l.</DIV>
<DIV> </DIV>
<DIV>There are more and more discussions about copyrights. They spread over several mailing lists. It would be nice that they are all at the same place, especially as Tomos wisely remind us "when someone translate a gfdl article from one language to another language, history from original authors is usually lost - unless the translator thinks of mentionning the origin of the content. Even when the origin of the article is mentionned, it is tough for a user to go to the original article and consult the original list of contributors as defined at the moment of the translation. In short, most of the time, when trade of content is done, we do not respect the gfdl requirements."</DIV>
<DIV> </DIV>
<DIV>Since translations happen quite often between all languages, I think any discussion of change of cp status or addition of new status or recommandation to have PD content rather than gfdl, should be project wide.</DIV>
<DIV> </DIV>
<DIV>Note : I would like to know whether all wikimedia projects are under gfdl, or if some are not, or if it is planned that some will not be</DIV>
<DIV> </DIV>
<DIV>Greetings</DIV>
<DIV> </DIV>
<DIV>Message: 5<BR>Date: Fri, 28 May 2004 10:36:04 +0000<BR>From: "Tomos at Wikipedia" <WIKI_TOMOS@HOTMAIL.COM><BR>Subject: [WikiEN-l] Re: w to properly use articles from an outside<BR>GFDL source?<BR>To: wikien-l@wikipedia.org<BR>Message-ID: <BAY19-F12GW2WX6DIID00004020@HOTMAIL.COM><BR>Content-Type: text/plain; format=flowed<BR><BR>There is another solution to this problem in discussion at Japanese <BR>Wikipedia and Wiktionary. It is a bit easier than the migration to GNU Free <BR>Content License, though I would love to see it happen soon.<BR><BR>We may introduce another license - so-called "intra-site public domain <BR>license" or "intra-wikimedia public domain license." What the license says <BR>is something like this:<BR><BR>"by contributing to Wikipedia, you allow others to use your contributions <BR>within Wikipedia's projects as if they are in public domain."<BR><BR>Copying and pasting of GFDL texts are against GFDL in a small way. And it <BR>happens in many contexts. (Moving
Village Pump discussions to appropriate <BR>talk pages, dividing an article into two pieces, using a boilerplate texts, <BR>using {{subst:}}, etc.)<BR><BR>It is a bigger concern in Japanese Wikipedia, partly because fair use <BR>usually have to include attribution according to the Japanese copyright law, <BR>and because we do not yet have solid evidence to think that substantial <BR>compliance in spirit is safe enough. In other words, if a troll says, "hey, <BR>you violated my copyright, because you copied and pasted my contribution <BR>into another page without following GFDL, and I am going to sue you," that's <BR>not something we can laugh at.<BR><BR>The introduction of the PD license is also a way to reduce interlingual <BR>troubles - the required level of compliance at Japanese Wikipedia is a bit <BR>more strict/ literal than that suggested at en:Wikipedia:Copyright. But some <BR>English Wikipedians may not know about it, and bring an image or translate <BR>an article to
English Wikipedia from ja. without fulfilling the requirement. <BR>That, again, is a violation of GFDL, and therefore likely a copyright <BR>violation.<BR><BR>If we introduce the "intra-wikimedia public domain license," we don't have <BR>to worry about it.<BR><BR>If English Wikipedia can also introduce similar license, that would make <BR>things more convenient.<BR><BR>Also, just in case it matters, we would still promote the GFDL-compliant <BR>preservation of attribution, the purpose is just to reduce the risks from <BR>legal technicalities, not to trivialize the attribution altogether.<BR><BR><BR>Regards,<BR><BR>Tomos<BR><BR></DIV><p>
<hr size=1><font face=arial size=-1>Do you Yahoo!?<br>Friends. Fun. <a href="http://messenger.yahoo.com/">Try the all-new Yahoo! Messenger</a>