This is a sorta-technical sorta-copyright issue. InstantCommons is great stuff, it spreads free content with correct attribution in a marvellous manner.
But Commons contains a certain number of non-free files, specifically Wikimedia logos and so forth. I just noticed (on a wiki using InstantCommons) that these are served up through it just the same.
Is there any relatively simple way to stop this happening? (Including not caring.)
- d.
On Mon, Jul 26, 2010 at 12:24 PM, David Gerard dgerard@gmail.com wrote:
But Commons contains a certain number of non-free files, specifically Wikimedia logos and so forth. I just noticed (on a wiki using InstantCommons) that these are served up through it just the same.
Is there any relatively simple way to stop this happening? (Including not caring.)
Either not caring, or moving the Wikimedia logos to meta and configuring meta as a second foreign file repo to the Wikimedia projects. I think both options have been proposed before.
Bryan
On 26 July 2010 11:48, Bryan Tong Minh bryan.tongminh@gmail.com wrote:
On Mon, Jul 26, 2010 at 12:24 PM, David Gerard dgerard@gmail.com wrote:
But Commons contains a certain number of non-free files, specifically Wikimedia logos and so forth. I just noticed (on a wiki using InstantCommons) that these are served up through it just the same. Is there any relatively simple way to stop this happening? (Including not caring.)
Either not caring, or moving the Wikimedia logos to meta and configuring meta as a second foreign file repo to the Wikimedia projects. I think both options have been proposed before.
The second sounds like way too much faff (and has been consistently rejected on "don't be silly" grounds). I suppose some categories could be determined to indicate "don't InstantCommons." Not caring is probably the best option unless it become some sort of active problem.
- d.
On Mon, Jul 26, 2010 at 4:09 AM, David Gerard dgerard@gmail.com wrote:
On 26 July 2010 11:48, Bryan Tong Minh bryan.tongminh@gmail.com wrote:
On Mon, Jul 26, 2010 at 12:24 PM, David Gerard dgerard@gmail.com wrote:
But Commons contains a certain number of non-free files, specifically Wikimedia logos and so forth. I just noticed (on a wiki using InstantCommons) that these are served up through it just the same. Is there any relatively simple way to stop this happening? (Including not caring.)
Either not caring, or moving the Wikimedia logos to meta and configuring meta as a second foreign file repo to the Wikimedia projects. I think both options have been proposed before.
The second sounds like way too much faff (and has been consistently rejected on "don't be silly" grounds).
<snip>
Personally, I'd rather we did move the 5500 Wikimedia-only images to Meta. Making Commons 100% free content would be clearer to reusers and make more general sense than having a site that is 99.92% free content. Of course, such a move would take considerable effort for relatively small gain, and thus far few people have been interested in doing this (i.e. most people think it is "silly").
-Robert Rohde
When there is a need and consensus to move all logo´s to Meta I would be happy to do so...
On Mon, Jul 26, 2010 at 2:17 PM, Huib Laurens sterkebak@gmail.com wrote:
When there is a need and consensus to move all logo´s to Meta I would be happy to do so...
Don't worry about doing it yourself, I'm sure we could get a sysadmin to import the images through the server. They might even be able to do it in a way that would preserve the file history.
Hi Casey.
I was thinking about a bot that also imports the history, but on the server is much beter offcourse.
On Mon, Jul 26, 2010 at 4:09 AM, David Gerard dgerard@gmail.com wrote:
The second sounds like way too much faff (and has been consistently rejected on "don't be silly" grounds). I suppose some categories could be determined to indicate "don't InstantCommons." Not caring is probably the best option unless it become some sort of active problem.
Possible, but not currently.
-Chad
On Mon, Jul 26, 2010 at 6:24 AM, David Gerard dgerard@gmail.com wrote:
This is a sorta-technical sorta-copyright issue. InstantCommons is great stuff, it spreads free content with correct attribution in a marvellous manner.
But Commons contains a certain number of non-free files, specifically Wikimedia logos and so forth. I just noticed (on a wiki using InstantCommons) that these are served up through it just the same.
Is there any relatively simple way to stop this happening? (Including not caring.)
Probably. I think not caring is the best bet, though. It's up to reusers to ensure that they comply with copyright law. Maybe they'll be using the logos for fair use -- I don't see why we should worry about that any more than we worry about InstantCommons users reusing CC-BY-SA images without linking to their licenses.
2010/7/26 Aryeh Gregor Simetrical+wikilist@gmail.com:
Probably. I think not caring is the best bet, though. It's up to reusers to ensure that they comply with copyright law. Maybe they'll be using the logos for fair use -- I don't see why we should worry about that any more than we worry about InstantCommons users reusing CC-BY-SA images without linking to their licenses.
I agree with Aryeh above and believe this is not a technical issue. If someone reuses an image on their wiki, it's their responsibility to check the relevant license allows it, not ours. We most certainly shouldn't be trying to block seemingly illicit uses of images through technical means, because the false positives will get people pissed off, and rightfully so.
If the Commons community wants to move these images to Meta or wherever to make the situation less confusing, I'd encourage that, but that's not a technical issue either. Setting up Meta as a secondary remote file repository would be quite trivial and require no extra coding.
Roan Kattouw (Catrope)
On 31 July 2010 18:13, Roan Kattouw roan.kattouw@gmail.com wrote:
If the Commons community wants to move these images to Meta or wherever to make the situation less confusing, I'd encourage that, but that's not a technical issue either. Setting up Meta as a secondary remote file repository would be quite trivial and require no extra coding.
Can you set up multiple remote file repositories in MediaWiki as it stands? I thought you could only set up one! How does one do this? How is precedence established? etc.
- d.
You've been able to do that for quite some time. See the docs on $wgForeignFileRepos. And it uses them in the order you define them.
-Chad
On Jul 31, 2010 10:20 AM, "David Gerard" dgerard@gmail.com wrote:
On 31 July 2010 18:13, Roan Kattouw roan.kattouw@gmail.com wrote:
If the Commons community want...
Can you set up multiple remote file repositories in MediaWiki as it stands? I thought you could only set up one! How does one do this? How is precedence established? etc.
- d.
_______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia....
wikitech-l@lists.wikimedia.org