Jump to content

Wikipedia talk:Featured picture candidates/Archive 34

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 30Archive 32Archive 33Archive 34Archive 35Archive 36Archive 37

FPs moved on Commons

I just now restored the templates for File:Lyndon Johnson signing Civil Rights Act, July 2, 1964.jpg, which seem to have been lost when the image was moved on Commons several months ago (though I can't seem to figure out what happened to the old en.wiki page for the file--I guess the issue is I don't really understand how image redirects work). Is there a relatively painless or bot-assisted way anyone can think of to check for more of these, perhaps periodically? Chick Bowen 20:01, 14 January 2013 (UTC)

I think this case was a combination of issues. The real issue was that the enwiki file page was deleted by a bot (User:MPUploadBot) after the image appeared on the main page. Then the file was moved on Commons, erasing any history of the {{FP}} template and {{POTD}} template even being there. I believe that the issue of the bot deleting the enwiki file page after appearing on the main page has been fixed. I'm not sure how we would go about getting a bot to check for Commons file moves... Jujutacular (talk) 15:43, 15 January 2013 (UTC)

FPC urgents

FPCs needing feedback



Hey, everyone. Hate to nag, but do have a look at the FPC urgents: We have a lot of nominations at the moment, and I'm doing my best to pull up the ones that need more attention. Some of them would be a shame if they failed. =) Adam Cuerden (talk) 00:51, 15 January 2013 (UTC)

Well, I guess I can say it, now that it's pretty much too late: [[1]] should have passed. Adam Cuerden (talk) 13:52, 15 January 2013 (UTC)

Is this Urgents list a healthy thing? Unlike the Commons practice of shortcutting nominations that have got overwhelming support (unanimous 10 supports in 5 days), here we seem happy to consider an image is "going to succeed" if it has only just met the threshold. There are many images that have barely achieved community support that have been overlooked for this list. What this urgent's list does is to bias eyes towards "meh" nominations.

Are these really urgent? The Ivory soap poster and Galerie des Batailles were listed here when they had 5 3/4 days left out of 9. Hardly urgent considering there are 22 nominations closer to their end than the poster. The WWI poster and the Wulingyuan image were similarly early "urgents" that were only middle-aged. In what way are those nominations any more deserving of reviewer opinion (positive or negative) than any of the other 45 nominations?

-- Colin°Talk 15:46, 15 January 2013 (UTC)

Edit out the nominations that already have the quorum or opposition, and you'll find the only other one in this timeframe represented here is one undergoing editing at the moment. They're in order from most to least urgent, and form a comprehensive list.
The explicit purpose of FPC urgents is to direct reviewers to underreviewed nominations; there is no urgency to one that already has a quorum or consensus not to promote, so it's ridiculous to suggest they should be on the list. Further, these are by no means necessarily meh nominations: If someone puts in a nomination, then others almost immediately put three nominations in above it - and, if you check, you'll find this happens fairly often in the current set - then the one below those three will have substantially reduced eyes on it.
Further, this helps to counter systemic bias by trying to assure everything gets its fair share of reviews. Everyone is quite able to oppose if they genuinely disagree with a nomination; that everyone who reviewed found a nomination supportable hardly makes a nomination "meh".
If you disagree with this, feel free to ignore FPC urgents. Adam Cuerden (talk) 20:10, 15 January 2013 (UTC)
My point is that barely achieving quorum does not mean the urgency to get more eyes on it has gone away. And a lack of reviews does not necessarily indicate a failure of the candidate review system. Images that are borderline - nothing special but no serious flaws - often fail to attract criticism or support. Your suggestion that "Everyone is quite able to oppose if they genuinely disagree with a nomination" doesn't hold due to human psychology. Many editors have a problem with being bold and critical, so just plain avoid doing anything other than supporting the obvious winners. That's the way some people are wired and we need to accept it. Such images should be allowed to fail without angst or reviewers being nagged. I strongly disagree with your language "ridiculous". Please can folk raise ideas here without being insulted. I agree with you that sometimes someone's nomination gets buried under a flood of others. When I tried to suggest some folk here pace themselves a bit, I was told I was silly.
FPC Urgents doesn't counter systemic bias. Quite a few pictures are sunk by a swift and possibly unfair oppose. Similarly, some pictures have serious flaws that aren't spotted immediately (I'm thinking of the kingfisher recently). Both problems are simply dealt with by having more eyes on all pictures. Concentrating on the images that most people have already gone "meh" to, is likely to bias such images towards promotion when in fact the unspoken consensus was that they weren't up to it [And I'm not commenting on any specific images here] Your "Everyone is quite able to" comment could equally well be phrased as ".. to scroll down to the bottom of the list and review in reverse order" or any other scheme someone wants to personally choose to review. Colin°Talk 20:44, 15 January 2013 (UTC)
FPC urgents does not allow ones that have a quorum to be listed, and I'm not entirely convinced it should: certainly, it was very useful for keeping things running during the Christmas period, anyway, when the reviewer numbers plummeted. Given we often have large numbers of nominations, I think it can be useful to provide a selection of under-reviewed ones. I'm not sure what to do with these cases
Perhaps me giving my opinion on the nominations will help explain why I think FPC urgents helps.
  • Jutland Map: Good map, probably going to need renominated or put into suspended nominations, since it took a while to fix some issues. It's a reworking of an original U.S.-military-produced map, but Wikipedian-created work is held to higher standards.
  • Wikipedia:Featured_picture_candidates/Map_of_Lorentz_National_Park (not on FPC urgents yet) undergoing work; been considering shoving this into suspended nominations, which would let it be relisted when work's done.
  • Bay of Fires: I think this one is going to pass or fail on whether it's deemed encyclopedic enough for the article it's in. Decent photo, but the EV discussion is complicated enough that it's likely to put people off. Directing more eyes may resolve this.
  • Wulingyuan: I really want to support this one, but have been having trouble viewing it due to its gigantic size, and it would be dishonest to support without a full review. If I can sort out the problems, and don't find issues, it's going off FPC urgents. I suspect others have viewing problems as well.
  • Is Your Home Worth Fighting For?: [one of mine] I always thought this one might be awkward at FPC, since it has high EV as a hard-to-find type of image, but is rather poor artistically. I'm interested to see how this goes.
  • Ivory soap: [one of mine]: I'm honestly a bit surprised this isn't passing yet. But then, it's mine.
  • Galerie des Batailles: This is a good example of where FPC urgents is really helpful: it was a bit poorly used in the article and captioned at first, but a little work fixed both, and now it's an excellent nom which missed out on some of the early interest.
Adam Cuerden (talk) 21:44, 15 January 2013 (UTC)
From my perspective, those that seem to attract comment that I have to edit my work to account for I am more than happy to renominate a second time. Indeed that might be quicker and cleaner than suspending it. Grandiose (me, talk, contribs) 22:12, 15 January 2013 (UTC)

Nomination Stats

Featured picture nominations by month, 2007-2012.

Max (overall): 182 (February 2008)
Min (overall): 38 (October 2011)
Max (2012): 122 (March)
Min (2012): 50 (August)

Happy New Year everyone! Stats again, updated through 2012. Raw data can be seen here. Jujutacular (talk) 04:20, 16 January 2013 (UTC)

  • Would be interesting to see numbers of promoted and declined images on that graph as well (as opposed to using a separate percentage graph). --Dschwen 18:59, 16 January 2013 (UTC)

Potential candidate feedback

Hi all, I was thinking of nominating File:E Minas Geraes C.jpeg here. While the quality is grainy and blurry, probably because no tripod can compensate for ten 12-inch guns firing at one time, there are no other images out there (that I know of, at least) of this. There are others that show the ship itself, but none that show it, or any of the five South American dreadnoughts, firing their guns, which is the defining element of this picture. Any opinions? I don't expect the reception to be positive, but it's worth a shot. Ed [talk] [majestic titan] 23:40, 17 January 2013 (UTC)

It appears to be scanned from newsprint (or similar). A better scan (i.e. from the negative or a photographic print) would probably pass, as it's an impressive picture, but it's hard to get a scan like this through, since at this point we're so far from the original photograph. Chick Bowen 01:56, 18 January 2013 (UTC)
Thanks. I don't believe that the original negative is anywhere online, and I'm not even sure that it still exists. I'll keep looking. Regards, Ed [talk] [majestic titan] 06:29, 18 January 2013 (UTC)

Tiffen

I see that Tiffen has no image. Should I shoot my Tiffen UV filter, the box it came in with Tiffen logo or the UV filter leaning on its packaging.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 03:33, 18 January 2013 (UTC)

Or should I take a picture of a Tiffen filter leaning on a cap like this picture at UV filter?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 03:36, 18 January 2013 (UTC)
I think something like your second option would be best. Would be nice if it says "Tiffen" on the filter in the picture? Jujutacular (talk) 04:38, 18 January 2013 (UTC)

Types of cameras

Can a photo by any type of camera used be added here or does it have to a high-end SLR or similar? Simply south...... walking into bells for just 6 years 19:45, 17 January 2013 (UTC)

I am not really a reg at FPC, but I beleive that more expensive cameras and lenses take higher quality photos. Thus, you are more likely to meet with success with pictures from better equipment. I have only one FP and it is from a point and shoot. My FP is based on encyclopedic value. It serves as the main image on about 5 different pages.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 19:59, 17 January 2013 (UTC)
Actually, we have a number of FPs taken with PowerShot or similar level cameras (high-end point-and-shoot, in other words, below SLR in price range). File:Lucky Diamond Rich face.jpg and File:Lactarius indigo 48568.jpg come to mind, but there are many more. Chick Bowen 20:01, 17 January 2013 (UTC)
This is the wrong question to ask! The type of camera which was used to take the picture is not part of the featured picture criteria. Full stop. The criteria are only concerned with the image itself. --Dschwen 21:35, 17 January 2013 (UTC)
My only photographic FP (that is, taken by me, not things like restoration of Mathew Brady photos) was taken on a relatively low-end point-and-shoot camera. I did have to take around a hundred shots to get it, though. Adam Cuerden (talk) 03:59, 18 January 2013 (UTC)
It's the wrong question to ask, but having said that, it's still difficult to get the required image quality with a low-end camera. Certainly not impossible though, and high EV can compensate for lack of quality. A high-end SLR can in some circumstances make up for poor technique, but on the other hand, poor technique can also exacerbate image quality issues on a high-end camera. Bottom line is that the camera is not part of the criteria, as Dschwen said. Ðiliff «» (Talk) 14:34, 18 January 2013 (UTC)

Candidate feedback

I have encountered this image, did some tweaks to contrast and lightning and would like to see some feedback if it is FP worthy. I am not completely sure about it and appreciate the feedback. Thanks. — ΛΧΣ21 16:40, 20 January 2013 (UTC)

It is a powerful composition, which might mitigate for minor technical issues such as the slight CA, but the image is currently not in use in any article.--ELEKHHT 12:57, 22 January 2013 (UTC)
I will add it to an article into wich it can have a high encyclopedic value, and will test its potential later :) — ΛΧΣ21 20:30, 22 January 2013 (UTC)

Focus stack

I tried to focus stack. I got more blur than any of the originals. It is as if two versions were compiled on a third that was moved over by a few pixels.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 19:57, 22 January 2013 (UTC)

Hi TonyTheTiger, which software do you use? I use helicon focus with best results. You can me mail your single photo-set for a test with my software. Best regards, --Alchemist-hp (talk) 21:32, 22 January 2013 (UTC)
I am using CombineZ. The second set has some weird artifacts. I emailed a request for your email address.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 21:46, 22 January 2013 (UTC)
With Helicon Focus, I got a successful stack of three f/9 images at 300mm on a 70-300mm, but it seems inferior to a single f/45 image to me. The stacked photo does not have the same sharpness in many locations, but it did remove specs of dust. Should I upload the images (3 f/9s, 1 f/45, CombineZ stack and Helicon focus stack).--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 00:05, 23 January 2013 (UTC)
I also redid my afternoon stack with Helicon and got something fairly decent. It came from 3 f/13s at 55mm on an 18-55mm in direct sunlight. For this I have 3 f/13s, 1 f/36, CombineZ stack and Helicon focus stack.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 00:13, 23 January 2013 (UTC)
I just found the f/36 for comparison from the afternoon with sunlight. Helicon beats the f/36 in sunlight, but not the f/45 from later. My interpretation is that this software may give results equivalent to a better depth of focus than f/36, but not quite f/45 based on my two results.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 02:51, 23 January 2013 (UTC)
Are you aligning the images before you stack them? JJ Harrison (talk) 02:39, 23 January 2013 (UTC)
I am just loading the photos and telling the software to do its thing in both CombineZ and Helicon. It worked well in Helicon, but not CombineZ.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 02:51, 23 January 2013 (UTC)
Usually for me stacking is a two step process in combineZP. First tell it to align the images, and then tell it to stack them with whichever algorithm looks best. JJ Harrison (talk) 05:18, 23 January 2013 (UTC)
I am now realizing that I was only doing one of the six algorithms in CombineZ.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 07:03, 23 January 2013 (UTC)
P.S. CombineZ seemed to align them by itself (not much aligning really necessary since I was on a tripod). Some of the algorithms worked out pretty well. I just need to control my lighting better. Also, I might do better with more than 3 source files.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 17:02, 23 January 2013 (UTC)

While I'm fully aware I acted foolishly insofar as I didn't get the alt ready on Commons - despite having it prepared - until well after the nomination started - there are reasons for this, but I'd rather not go into them, suffice to say my life got suddenly a bit hectic for a bit - I would appreciate if people would have a look, as I do think this is a lovely artwork, and I think it'd waste everyone's time if I go to my default of "say nothing, renominate in two weeks or so". Adam Cuerden (talk) 17:04, 23 January 2013 (UTC)

White background

Why are all the camera FPs (File:Sony A77.jpg, File:Sony-Alpha-A700-Front.jpg, File:Canon EOS 5D Mark II with 50mm 1.4 edit1.jpg, File:Canon EOS 400D.jpg, File:Lens aperture side.jpg) done with a white background. How is it done?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 18:41, 16 January 2013 (UTC)

It makes the subject of the picture stand out nicely without any distractions and looks good when embedded in a page with a white bg. There are two options
  1. Masking the background and filling it white through image processing (Gimp, Photoshop). You can add a fake drop shadow to make it look less like it is floating in a void. It is difficult to achieve results that do not look cheap!
  2. Proper lighting. Use a plain white background such as a piece of poster carton. Don't lay it flat, but have it bend upwards behind the subject to create an even background with no corners or horizons. Then make sure the bg is lit bright enough to make it truly white.
--Dschwen 18:56, 16 January 2013 (UTC)
O.K. I just tried it at Wikipedia:Featured picture candidates/Canon EF 40mm f/2.8 STM.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 22:50, 17 January 2013 (UTC)
How do I make the background whiter?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 13:52, 19 January 2013 (UTC)

A very good book on lighting, which I have read, is ISBN 0240812255 "Light Science and Magic: An Introduction to Photographic Lighting". Something to spend your Christmas Amazon vouchers on, perhaps. It discusses lighting objects and portraits. Photographing products to a professional quality is not easy, as you are discovering with your FPC. Just getting them spotlessly clean is a nightmare. Even with the best lighting, you will find it essential to be able to tweak the levels afterwards, and to remove dust spots. For this reason, I strongly recommend shooting raw and using a program like Lightroom. It will make more of a difference to your images than buying another lens. You don't need Photoshop for this kind of image. There are free focus stacking programs if you want to experiment with that too. While Lightroom can help lift the whites to whitest, I don't recommend using an image editor like Photoshop or Gimp to cut out an object and fake the background/shadow. There are some FPs that have done that but it is very hard to do well and easy to spot unless you are only looking at a thumbnail.

As for advice with your shots, FP is not the place to learn. Individual editors may help but please don't post FPCs that aren't at the quality shown by existing examples. There are loads of forums and Flickr groups that specialise and are more suited to helping you learn how to take a certain kind of photograph than Wikipedia. -- Colin°Talk 21:22, 22 January 2013 (UTC)

On the other hand, Commons Quality Images is a place you can put up pictures you think are nearly there. If they're not up to scratch, they'll get summarily rejected, but you'll always get a reason, and if you learn from each rejection, it'll help your photography a lot. --99of9 (talk) 10:42, 24 January 2013 (UTC)
Not sure about QI for feedback. It is more aimed towards a quick tick or cross style of response. And the quality requirement is supposed to be as high as FP (but without the wow). You might get a terse reason but no help towards fixing it. Commons:Photography critiques is the relevant place, but I don't know how well staffed it is. But really, the internet is full of places where photographers can learn their skills and get feedback and criticism. This is an encyclopaedia, not a photo tutorial. Colin°Talk 11:36, 24 January 2013 (UTC)

If a picture on Commons is a Featured Picture, does one have to do anything special for it to be a Featured Picture on Wikipedia? It seems to me the FP Criteria for Commons and Wikipedia are quite different. Stigmatella aurantiaca (talk) 13:50, 24 January 2013 (UTC)

Do you have to do anything special? Well, not really, other than nominate it here. Perhaps the key difference though is that the image needs to have good Encyclopaedic Value (EV) to be featured here, which is indicated to a large degree by the image being included in a significant capacity in at least one Wikipedia article and it being stable in its article usage. The full criteria are at WP:WIAFP. --jjron (talk) 15:50, 24 January 2013 (UTC)
It has to be used in an article and have strong encyclopedic value. Additionally, commons requires images to be a minimum of 2 megapixels in resolution while FPC here requires a minimum of 1500 pixels in the smallest dimension.--Muhammad(talk) 15:54, 24 January 2013 (UTC)

FPC resolution requirements

I see that new noms are suggested to by 1500x1500 pixels. Are current FPs that are below this threshold suppose to be nominated for delisting?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 15:29, 24 January 2013 (UTC)

No. The size change was and is not retrospective. While size can be a factor, any delist should be based on other reasoning. --jjron (talk) 15:44, 24 January 2013 (UTC)
Give it time Jjron, in the past pretty much every tightening of guidelines has been used as an excuse to nominate older images for deletion and there's no reason to think that this will be any different. It should be made explicit that rule changes aren't retroactive and to that end there should be a subpage linked to from the guideline page that documents the old and new rules so that people know what rules to use if it comes up. Doesn't have to be retroactively done but for future rule changes. Cat-fivetc ---- 16:25, 24 January 2013 (UTC)
You're right, which is why I'm being pretty blunt in the 'no' response, but I can foresee the day when someone comes along with mass delist noms based on size. Perhaps not a bad idea to create a new subpage explicitly documenting changes to the criteria though, perhaps with a simple summary of the discussion that led to it and when it was done. I guess it would basically be off in the FPC Criteria page history anyway if someone did want to trawl through it and get such a page going. --jjron (talk) 04:58, 25 January 2013 (UTC)
At the same time, though, we do see raising standards over time, so it may well be that some older noms aren't good enough anymore. But we should do so in a selective fashion, getting rid of ones that seem alien to the idea of a modern FP before ones that are merely a bit smaller. Adam Cuerden (talk) 05:12, 25 January 2013 (UTC)
Absolutely, but any delist nom based solely on being "too small" based on the current criteria would get an automatic Keep at least from me. --jjron (talk) 05:49, 26 January 2013 (UTC)
Oh, agreed, except maybe if it was something like "too small to see the details that are necessary to its encyclopedic value", like if was so small you couldn't make out most of the components of a clockwork machine or something. And there's also some cases where an image could be delisted on size alone. For example, File:Sand sculpture.jpg or File:BrisbaneByNight2004.jpg - two images from the first month of standardised FPC archives - are so small as to seem laughable next to any modern FPC. But before you reach that point where the image cannot be imagined as an FPC anymore, size considerations are insufficient reason. Adam Cuerden (talk) 06:00, 26 January 2013 (UTC)
Another good example is File:Dragonfly eye 3811.jpg, which, looks rather shoddy next to a more modern FPC on the same subject, such as File:Calliphora_vomitoria_Portrait.jpg. So I suppose there's that as well - if much better FPs on similar subjects are coming in, the old ones may be ready to delist. Adam Cuerden (talk) 06:20, 26 January 2013 (UTC)

Exif data

The topic of purged Exif data came up at Wikipedia:Featured picture candidates/File:Common Leopard Phalanta phalantha.jpg which made me look and see if the nomination guidelines had anything on pushing people to nominate images with full Exif data, I'm specifically thinking camera, shutter speed, aperture, ISO. Number 7 on the FP Criteria lists geotagging but not basic information which is much more helpful for evaluating an image. This seems like a pretty simple change but does anyone disagree? Cat-fivetc ---- 16:32, 24 January 2013 (UTC)

It isn't necessarily deliberate. When folk muck about with an image in PhotoShop or Gimp, etc, then this sort of thing can get lost. Also we accept images that aren't created by Wikipedians, such as those from Flickr. The Exif data doesn't really affect the quality of the image or the ability for it to be used on Wikipedia or by anyone who licences our work, which is all that matters. -- Colin°Talk 16:53, 24 January 2013 (UTC)
I'd be against making it a requirement for those reasons but we already have GPS data on the suggested list of things for an image to have and how an image was made seems as important as the pinpoint location of where it was made. On that note, in a pinch if the nominator is the photographer they can add precise or imprecise location data and/or image creation details in the description page and/or the caption if they want. Obviously that's not going to apply to people who are using government or third party images which (regretfully) don't come with that information but it doesn't seem to much to ask where possible. Cat-fivetc ---- 17:01, 24 January 2013 (UTC)
I don't see what's wrong with the status quo. We can encourage photographers to use it (and not all FPs are photographs) but I don't see it's a reason to oppose by itself (so it might be evidence of inappropriate digital manipulation). If anything I think we should remove the Geotagging advice. A commenter can always mention it, rather than add all sorts of other "best practice" type stuff to the criteria. Grandiose (me, talk, contribs) 20:22, 24 January 2013 (UTC)
That works too but it isn't just geotagging, there's a bunch of things that aren't strictly necessary on that page. I'd be happy to have a go at if people are willing to discuss after the fact, otherwise we're just going to get bogged down on each item as we go down the list. Cat-fivetc ---- 02:17, 25 January 2013 (UTC)
Geotagging is of significant encyclopaedic value. It is absolutely something to encourage for certain classes of photograph. So I support its inclusion as the sort of thing that should appear on the image description page. Stuff about panorama frames, camera models and f stops is merely "nice to have" but really nothing to do with the encyclopaedia. Colin°Talk 08:15, 25 January 2013 (UTC)
I'd argue that having a solid description giving the general location (down to the building, ridge, field, lake, studio, or whatever) where the photo was taken is necessary and having GPS data down to 50 feet or better is just icing on the cake. That being said, I see no issue with having GPS as something that's recommended where possible but if that's the case then so should Exif at least the basic set of Exif data. Cat-fivetc ---- 23:11, 25 January 2013 (UTC)
I'd say both geotagging and exif data are nice to have, but in almost all cases should not be 'deal breakers' in terms of deciding the merit of an FP nom. As Cat-five says exif info can be helpful to evaluate an image, for example this discussion arose out of my vote on that image where I was trying to confirm whether the DOF we were seeing was essentially the best we could expect, or if it was a poor choice on the part of the photographer (knowing the macro photography skills of the photographer concerned I assumed he would have chosen well, which he later confirmed, but the exif would have saved the initial uncertainty). The metadata can also be good when you see a superbly executed photo and you are interested to know the settings used to help develop your own skills. On the flipside, I would have to say I have seen images shot-down at times significantly because people have decided a photographer has chosen settings poorly after viewing the exif, although it's also true to say in many cases the exif simply confirms initial suspicions of poor choices. But including it can be a bit of a double-edged sword. And while the exif can be useful to us reviewers at FPC, in terms of Wikipedia itself, frankly most people wouldn't know what it was all about, and more to the point simply wouldn't care. The geotagging is probably more encyclopaedically useful, but even then I suspect few people would ever actually click through. And sadly both are probably further examples of where I feel we favour non-Wikipedian generated content, even if it's almost unconsciously. But the key point I think (and one that I feel is too often overlooked by reviewers) is that image pages should include a clear and detailed description of the image, which is really what Criterion 7 is all about. --jjron (talk) 06:13, 26 January 2013 (UTC)

January 30

Just to note, there's a LOT of underreviewed images ending January 30; indeed, we seem to be falling behind all over the place this week. Adam Cuerden (talk) 08:39, 25 January 2013 (UTC)

I just found File:Inflatable habitat s89 20084.jpg when I was going through a portal. It's fun looking, large enough to be an FP, and only has some slight damage (as best as I can tell). Just throwing it out there. Cheers, Sven Manguard Wha? 20:03, 25 January 2013 (UTC)

Also: File:Moon colony with rover.jpeg. Sven Manguard Wha? 20:04, 25 January 2013 (UTC)

These would be excellent choices for new restorationists - outside of the black sky having been worn down by greasy fingers on the left edge of the inflatable image, which will require a little care, but not much, it's all just simple dust specks and the occasional scratch, both of which can be easily fixed with the clone tool if you zoom in enough and use a suitably-sized clone stamp. Adam Cuerden (talk) 23:28, 25 January 2013 (UTC)

I wonder, how does one tell dust specks and stars apart? --125.25.147.169 (talk) 15:55, 28 January 2013 (UTC)
You can tell when they're on buildings and people. Leave anything plausible alone, of course. =) Adam Cuerden (talk) 18:31, 28 January 2013 (UTC)

Would this be FP quality?

I just came across File:Male human head louse.jpg and think it's rather intriguing. I have no idea of how photo quality is judged, though. There seems to be some ghosting which is probably hard to avoid at such magnifications, and the crop is rather tight on the right. Does this have FP potential? Also, it's currently inconvenient for me to log in so if someone thinks this pic has a good chance it'd be great if they could help nominate it. Thanks. --125.25.147.169 (talk) 15:51, 28 January 2013 (UTC)

I'd certainly support it, and it shows the characteristic grabbing of the hairs very well. Adam Cuerden (talk) 03:50, 31 January 2013 (UTC)
 Nominated. Adam Cuerden (talk) 05:44, 31 January 2013 (UTC)

Bulbs for light tent

lamps available for my light tent

I have come to the conclusion that I need to have better control over my lighting and am putting together a light tent. As a first attempt, I picked up a $12 popup on eBay. I have some clamp on desk lamp lighting fixtures. I have read an online DIY guide and I just need to understand what is meant by “Full Spectrum” light bulbs. I have some 60watt soft white bulbs. Are these full spectrum?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 16:58, 23 January 2013 (UTC)

This has had a little additional editing by Bransmeister, so I'd appreciate if people'd have another look. =) Adam Cuerden (talk) 09:02, 31 January 2013 (UTC)

Bicycles

The new file

I thought there was potential in Wikipedia:Featured picture candidates/Bicycle diagram if only some of the issues could be ironed out. I've now done that an uploaded an edit to File:Bicycle diagram-en (edit).svg. However, I haven't put it in articles yet, as I wanted to confirm people thought it was an improvement (I think this is unlikely to be universal). I went through discerning what about each oppose could be easily changed, and did that. There's a change list in the file description. Thoughts? Grandiose (me, talk, contribs) 18:01, 31 January 2013 (UTC)

At first glance I immediately noticed that the rims are not circular and are uneven width, as are the tyres, and the spokes are unevenly spaced. Otherwise it looks okay. Matthewedwards (talk · contribs) 19:51, 31 January 2013 (UTC)
To be fair, the tyres shouldn't be circular - they should be partially flattened at the bottom. Other issues hold. Adam Cuerden (talk) 20:08, 31 January 2013 (UTC)

Today's POTD

Does anyone else see a stitching error in the current POTD? To me it looks like there's one between the second and third peaks from the left--a ghost of the mountain visible in the sky. Am I wrong? If others concur, I'll try to do a quick edit, but then what? Would we forget about POTD and start a normal Delist and Replace, or is it worth pinging Howcheng for emergency action? I'm also willing to accept that I'm just seeing it wrong, since there was no mention in the original nomination. Thoughts? Chick Bowen 00:22, 1 February 2013 (UTC)

I did a rough edit if it helps make clear what I mean. Chick Bowen 00:39, 1 February 2013 (UTC)
  • I don't know what is supposed to be done in such a case, but just thought I should mention that there are quite a few errors and your edit has missed some just to the right of the ones you fixed. --Muhammad(talk) 01:10, 1 February 2013 (UTC)

Macro images

I am trying to deterimine what factors are keeping me from producing FP quality images. Since my best contributions to WP will probably be basketball, I have two bodies (Canon Rebel T3i and Canon Rebel T4i). Would I be able to produce FP quality images if instead I put all my money in one Canon EOS 7D, which costs the same as my two bodies combined? Is it my lenses? I don't have any macro lenses and have been working with EF 70-300mm f/4-5.6 IS USM and Canon EF-S 18-55mm lens. Is it my accessories such as tripods, flashes and a light tent purchased on eBay? My Manfrotto 190XProL seems stable enough to me. I am satisfied with my Speedlite 430 EX II. Is it impossible to do consistent FP level work with my equipment or is it just me?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 23:22, 2 February 2013 (UTC)

If your doing basketball photography, provided you don't have press access getting you right courtside, then you'd need fairly expensive lenses for closeups... check out this article: [2]. The bodies should be fine, I think. Remember with action shots, more pictures the better, pretend your camera is a video camera and just hold down the shutter and shoot as fast as possible.. lol — raekyt 08:08, 3 February 2013 (UTC)
By fast as possible do you mean fps or shutter speed?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 15:26, 3 February 2013 (UTC)
For sports photography, both. The big ass lenses you see the pro camera people with along the side-lines, they're very large apature lenses that allow them to take faster shutter speed photos in lower light, and are generally stupidly expensive. If you want to do good sports photography, then you need to learn about these kinds of lenses, there are some larger apature lenses that are not multi-grand expenditures. And for rapid-fire taking pictures, more pictures you take more likelyhood of getting a good one. — raekyt 20:25, 3 February 2013 (UTC)
The main reason keeping your from producing FP quality macro images is technique. If you are serious about producing good close-up product images, then a macro lens and perhaps some lighting equipment would make a difference. But you need to learn more and read more - esp about lighting - and practice lots. The camera is most definitely not the problem here. There is zero difference in image quality between your T3i and T4i so I hope you didn't buy the latter hoping to take better pictures. And I don't know why you think buying the out-of-date 7D would improve your picture quality. Moving up to a prosumer camera will give you improvements to the exposure and focus systems that may improve your hit-rate of successful pictures, but don't in themselves equal higher quality images. But there are times in the product release cycles, like now, when such cameras are lagging behind the latest consumer models in terms of sensor tech. And the speed and accuracy of focussing is determined by both the camera and the lens, so buying a better camera and sticking a cheap kit lens on it makes no sense. Your T4i is a fine camera and we have plenty FPs taken with lower spec cameras.
My 2p: buy kit because you want to take and enjoy the pictures that require it, not in order to get an FP. Colin°Talk 09:55, 3 February 2013 (UTC)
Actually, I bought the 2nd body (as well as a monopod, tripod, 40mm pancake, 430EX II speedlight, larger SD cards and a new bag) when a one-time windfall enabled me to double my camera equipment budget. The budget only has $77.67 left, so I won't be buying much new stuff for a while. The 2nd body was chosen mainly because i jumped me from 3.7 fps to 5.0 fps, which is important for basketball. I decided not to sell the first body for situations where I might be on one end of the court and need different lenses for the near and far courts.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 15:38, 3 February 2013 (UTC)
I also think technique is honestly the issue here. The most recent focus stacked version had a weird angle. The white balance was off. The lens was dirty. The focal length was too short imo. The version before that combined with maybe a few hundred pixels in margin and focus stacking would be perfect. There have been many featured pictures taken with quite humble equipment. I'd sell one body though - pointless having two so similar. The 7D is a better body than the t4i for it's ergonomics, durability and fast action capabilities. But the sensor is the same as your bodies anyway. At any rate, upgrading to a newer crop sensor wouldn't improve your photos at all. Improvements to high iso capability and the like are totally irrelevant in an iso 100, tripod mounted, lighting controlled studio situation. Spend your money on lenses (a few good ones, not loads of mediocre ones) or lighting gear - they don't depreciate as quickly. JJ Harrison (talk) 12:28, 3 February 2013 (UTC)
Also, there are plenty of featured pictures taken with both of your lenses. JJ Harrison (talk) 12:30, 3 February 2013 (UTC)

FPC in 2012

Anybody willing to do a 150-200 word write up for the Signpost about the state of FPC in 2012, including more unique images or patterns, please contact me. — Crisco 1492 (talk) 10:31, 9 February 2013 (UTC)

I guess I could, although I was on wikibreak for part of it. Adam Cuerden (talk) 14:24, 10 February 2013 (UTC)
We could also collect some thoughts here for Adam or whoever ends up writing it. Here are mine: in photography: 1. JJ has really raised the bar for nature photographs, and I think has had a positive influence on some of our other photographers; 2. we had more action shots of performers and athletes, and 3. after a number of broad, panoramic urban landscapes in previous years, our architectural images have moved toward very precise, high-res images of single buildings. In historical images, I think we're seeing more heavily edited images, with less tolerance for dust and damage. Oh, and the resolution criterion was raised in July, though I think that really reflected a trend in the FPC discussions going back another year or so. Chick Bowen 00:22, 11 February 2013 (UTC)
I haven't counted the exact number, but there were more than a few successful nominations of space related photography in 2012 including subjects in astronomy and space vehicles. --Pine 19:23, 12 February 2013 (UTC)

Main Page Today

Just saw the image on the main page. I thought it was agreed that we'd avoid controversial images like those on the main page. --Muhammad(talk) 04:32, 13 February 2013 (UTC)

I'm biased since it was my nomination, but can you explain how it is controversial? We have had nude artwork on the front page before. This is hardly a graphic or provocative image. Chick Bowen 05:10, 13 February 2013 (UTC)
(edit conflict)For reference, other nudes that have been on the main page: Wikipedia:Picture of the day/August 31, 2006, Template:POTD/2012-02-07. Selections are made on a case-by-case basis and are independent of the selection for featured status. This is probably more suitable for discussion at WT:POTD, or User talk:Howcheng or User talk:Crisco 1492. Jujutacular (talk) 05:20, 13 February 2013 (UTC)

Criterion 7 clarification

Propose changing the start of Criterion 7 from "Has a descriptive, informative and complete file description." to "Has a descriptive, informative and complete file description in English." This does not prohibit additional descriptions in other languages, but since we're on English Wikipedia at least one of the descriptions should be in English if the photo is to be featured here. --Pine 18:09, 3 February 2013 (UTC)

  • The image page absolutely needs to be in English for enwiki for EV reasons, in particular the description section. Featured content is meant to be showcasing our best work, and they're hardly doing that if an English speaking person can't read them. Of course it can also have other language versions too, it's just that one has to be in English. The actual filename isn't so important as you don't need to be able to read that if an English description is provided, and given that the images are generally sourced from Commons which is a multilingual repository and it doesn't need multiple versions of the file named in each language. Nominators should be checking this prior to nomination, it's pretty straightforward, but there seems to be a whole raft of noms going through atm not satisfying this (I just tagged another three). Whether it needs to be stated in the criteria I'm not sure, rather seems like stating the obvious, but given my previous statement maybe it's not so obvious, so if it helps make things clearer for people... --jjron (talk) 14:14, 7 February 2013 (UTC)
YesY Done This seems uncontroversial and the last contribution to this discussion was ten days ago. I made the following diff: https://wiki.riteme.site/w/index.php?title=Wikipedia%3AFeatured_picture_criteria&diff=538777566&oldid=514075536. --Pine 21:53, 17 February 2013 (UTC)

I'm a little surprised this hasn't had a single vote, given it passed on Commons by the Rule of the 5th day - e.g. Such overwhelming, unanimous support that it gets closed early. Adam Cuerden (talk) 16:44, 14 February 2013 (UTC)

Doesn't strike me as having extremely high EV for the article's it's in.... — raekyt 16:47, 14 February 2013 (UTC)
How else would you illustrate the connection between St. George and Britain than by showing him being used in British patriotism? Adam Cuerden (talk) 04:22, 16 February 2013 (UTC)
But we don't have an article about that specifically? It's just one of the many recruitment posters they issued, one of the earlier ones, or the first one, or if any are more notable/discussed/most widely distributed or whatever would be more EV in those articles. Only has very minor EV in Patronages of Saint George or Saint George, where it's arguably not even worth including in the second one. And again very minor EV in History of the United Kingdom during World War I, only one it could have any real EV in is Recruitment to the British Army during the First World War, and that's where I think maybe the first posters of the war for recruitment would have most EV, not just one that happens to be graphically flashy. — raekyt 04:43, 16 February 2013 (UTC)

Notifying the Video Game project

There seems to be an increase of video game-related pictures being promoted to Featured status and yet its hard to have it noticed for the project since there no notification on when they are up. I just want to make sure that there can be more announcements for these nominations in the future. GamerPro64 16:26, 8 February 2013 (UTC)

Thank you for letting us know. I don't think it is standard practice here to notify any Wikiprojects of nominations, but it's a good idea. Jujutacular (talk) 23:49, 8 February 2013 (UTC)
IF a bot can do it somehow, then it would be ok, but I doubt anyone would do it due to time constraints otherwise. Probably be good idea to increase participation if we did notify relevant wiki-projects though (and the article's talk pages that the picture is on). — raekyt 23:16, 9 February 2013 (UTC)
To add a concern though, if we did do this, then we'd have to become pretty strict about disqualifying things if they fail criteria, right now we sorta fudge things a bit, and let it drag on until it closes nautrually if it fails, but if we're advertising alot of invested parties that may vote because they like an image irregardless of promotion criteria, then the regulars would need to step in and procedurally close things. — raekyt 23:19, 9 February 2013 (UTC)
Well, do remember that the criteria do have exceptions. We shouldn't (for example) disqualify a video game shot that someone gets free licensed because the game's maximum resolution is less than 1500x1500. There can be reasonable discussion about whether something is an exception in some cases, and we should let such discussions happen. Adam Cuerden (talk) 23:27, 9 February 2013 (UTC)
I'm aware of the exceptions, but I was talking more broadly than just this one project, if we started notifying all relevant projects/pages of a new nomination, there may be people who don't know the criteria coming and voting for things that shouldn't pass due to failing criteria just because they like it or have invested interests in it... — raekyt 00:01, 10 February 2013 (UTC)
True. But perhaps if we just ask any notifications - outside of the institutionalised ones like WT:MILHIST - include a link to WP:Featured picture criteria it'd work. Adam Cuerden (talk) 00:39, 11 February 2013 (UTC)
Sounds strongly like Wikipedia:Canvassing to me, which has been highly frowned upon here in the past. There's a reason we don't notify 'interested' wikiprojects and other parties, and that's because we've seen disastrous consequences in the past when they've flooded a nomination with unjustified votes (anyone else remember the stoushes over the Wikipe-tan nominations for example?). Now that promotions have tipped very strongly towards simple vote counting as opposed to the older technique with more judgement made by closers to evaluate arguments, there would be little to prevent this getting out of hand. I therefore strongly oppose this being done in any form. --jjron (talk) 14:01, 11 February 2013 (UTC)
WP:CANVAS is a bad-faith attempt to skew consensus by notifying only people who you think will support your position. Neutrally notifying all relevant parties, isn't canvasing. It's quite common and happens all the time. — raekyt 15:21, 12 February 2013 (UTC)

Indeed! If we simply worded every notification with a boiler plate paragraph about things to keep in mind when commenting at FPC, I think this could be useful. For example, we might have avoided this incident if the relevant projects had been notified. Jujutacular (talk) 18:28, 12 February 2013 (UTC)

Whilst more participation would be great, notifying wikiprojects would skew the process too much in my view, particularly with very popular projects. JJ Harrison (talk) 02:48, 15 February 2013 (UTC)
Yes. The whole point is that people in a wikiproject are more likely to support the nomination without particular concern to the criteria (have seen it happen many times), which is what makes it a form of canvassing. I know this is not always the case, and indeed sometimes they can offer a valuable input and counterpoint to a nomination, a recent example being Wikipedia:Featured picture candidates/High Pressure Area over the Great Australian Bight. On the other hand they can also bring across wikiproject infighting as well, which I think was also evident in that particular example. (And re the Ebony Thomas case, this is an example where nominator and reviewers (and yes I was one of them) perhaps did not exercise due diligence - a simple Google image search pretty much conclusively shows this isn't her. Also a case where our 7 day rule didn't do it's job of weeding out things like this; not sure about the article usage, but from time of image upload to nomination was about 6mths, so plenty of time for someone involved in that area to click to the misidentification, and FWIW I suspect the new lead image in the article is also not her. Perhaps this also a case of where a propensity we seem to have of promoting images of lower EV as indicated by their article size/popularity needs some thought - even now this article is only a couple of hundred words long, was edited only ten times last year, and hasn't been edited in six months!). --jjron (talk) 07:46, 24 February 2013 (UTC)

I can see no reason other than disuse that this would warrant a delisting, so I figured I'd let the rest of you know about it, and hope that someone sticks this in a few articles. Sven Manguard Wha? 18:19, 16 February 2013 (UTC)

Could ask on M4 carbine if they want it back in the article... otherwise if no new home can be found then yea, Delist. — raekyt 18:42, 16 February 2013 (UTC)
This version of the same image File:M4FiringWithCasingInAir.jpg is still used in the M4 carbine article. As best I can tell the only difference is it's been slightly cropped. I have no idea why it's being used in preference to the featured version. I'm going to revert it and we'll see if it holds. --jjron (talk) 03:08, 17 February 2013 (UTC)
FWIW it appears this replacement in the article happened on 13 Jan 2008 here. --jjron (talk) 03:58, 17 February 2013 (UTC)
OK, a week and fifteen article edits down the track, including edits by the two main article contributors, this image remains in its place in the article. I think we can put this one to sleep for the time being. --jjron (talk) 07:57, 24 February 2013 (UTC)

Focus stack vs. Multi Shot Noise Reduction

A couple weeks ago, you guys introduced me to a technique called focus stacking. I was speaking with Canon Technical support tonight and someone introduced me to multi shot noise reduction. The canon manual does not really explain what the technique is. If it isn't too much trouble, can someone explain the difference between focus stacking and multi shot noise reduction.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 06:01, 7 February 2013 (UTC)

I guess it is similar to the "multiframe noise reduction" (aka "hand-held twilight") in my Sony camera. See this review for examples. The camera takes several (e.g., six) shots in rapid succession, aligns the images to cope with you moving slightly, and then averages out the pixels. Provided the subject is stationary, the only difference between the frames should be shot noise, which is random. The manufacturer's implementation will vary in how well they cope with moving subjects without ghosting. You can do the same on your computer by taking several identical shots and processing with enfuse. It is almost the opposite of focus stacking, which aims to extract detail unique to each frame.
I experimented with it on my camera. It does indeed produce lower-noise JPG images than would normally be possible (where the alternative is increasing the ISO). Unfortunately, Lightroom does a much better job of producing a low-noise JPG than my A33 does by itself, and I found that I could get similar images from a single higher-ISO RAW file instead. If you are taking product shots on a tripod, then this technique isn't relevant - just light the subject well and choose ISO 100. -- Colin°Talk 08:32, 7 February 2013 (UTC)
  • Nothing ever saves you from complication. As new gear makes one scenario easier, it just introduces you to another scenario in which it doesn't work. :) High ISO image quality is light-years (har-har) better than it used to be, so we can now hand-hold what used to be impossible in the days of film. But there are still many things that we can't do without a bit of trickery. Star-trails for example. The only way to get decent image quality on long star trail images is to image stack, because the sensors can't cope with shutter speeds of over about 5 minutes without filling the frame with hot pixels. A similar technique (but seemingly not quite the same) in astrophotography is dark frame subtraction. You take a long exposure photo (or series, if star trailing), and then take another photo with the same shutter speed, except with the lens cap on. That takes a measurement of the innate sensor noise of the camera at that moment in time (which is dependent on temperature and a few other factors). You can then go back to your PC later on and 'remove' the dark frame noise from the other image(s), which cleans up the photo's long exposure noise substantially. Better than using noise reduction software, because it's the sensor's unique 'noise signature' for the given conditions. Ðiliff «» (Talk) 12:45, 7 February 2013 (UTC)
  • Your "dark frame subtraction" is a manual version of "long exposure noise reduction" where the camera automatically takes another picture of equal length but with the shutter closed whenever the exposure length is greater than one second. This technique/feature removes fixed-pattern noise but not shot noise. I can configure my camera to turn this feature on or off, and unlike multi-frame noise reduction it applies directly to the RAW file rather than just JPGs. However, for star trails it wouldn't be any use as you'd have a long gap between each trail segment -- so Diliff's manual version is needed to apply to all the frames. Colin°Talk 12:54, 7 February 2013 (UTC)
As you are shooting JPGs you are somewhat at the mercy of the camera. Make sure you've set your JPG quality settings to the highest you can and turn down any noise-reduction settings to see if that helps. Those images look soft rather than noisy. The softness may be a combination of several things. Firstly at increasingly high iso, the camera will be using fairly aggressive noise reduction. If you shoot RAW then you can control the amount afterwards to taste. Any out-of-focus areas show up noise more than in-focus areas, so not getting the focus spot on can be an issue. Also your lens won't be at its sharpest wide-open. Stop down a little and it will sharpen up -- but you have to balance that against higher iso or longer exposure. I've not done any sports photography but wonder if you can get away with 1/500 rather than 1/1000? There is a reason that professional sports photographers shoot with full-frame cameras and a lens the size of your thigh: a huge amount of light hitting a big sensor. Console yourself that some pro spots photos you see probably look pants at 100% too -- you only see a downsampled vesion on a web page or in a grainy newspaper. -- Colin°Talk 15:09, 7 February 2013 (UTC)
What is Canon customer support thinking when he says to turn up noise reduction? You are telling me to turn it down. Why? P.S. what does "look pants at 100%" mean?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 16:08, 7 February 2013 (UTC)
Pants is UK English slang; it's roughly equivalent in meaning to – though somewhat less formal than – rubbish. TenOfAllTrades(talk) 16:20, 7 February 2013 (UTC)
I might add that rubbish is also UK vernacular, if not slang, although somewhat easier to figure out. Saffron Blaze (talk) 12:49, 26 February 2013 (UTC)

Cute Chicks

Stylish Chicks I'm hoping to nominate this image for POD once I am able to log-in. Since this is not my image, but an editor who I admire, I do not wish to call attention or solicit any harsh critiques.-So I'm posting it here just to ask if anyone thinks this would be a good nomination?
What strikes me here is that most bird photos I've seen are taken in nature and this one has the colorful nursery/knitted pattern. The title is silly and can be changed.24.0.133.234 (talk) 18:08, 18 February 2013 (UTC)

I do agree that it would be interesting to feature pictures of animals raised in a wildlife rescue setting, but I don't know that this is the best example. The composition of the frame is a bit unbalanced, and I find the drab white-wall background to be a little boring. The image is also below the minimum resolution requirements -- see the featured picture criteria. Hope this helps :) Jujutacular (talk) 22:56, 18 February 2013 (UTC)
That helps a lot thank-you. Below resolution is not something that I could fix but I will check to make sure that any other photos that I consider for POD are the right number and my eye is untrained to what you see as far as composition but that is prob. what other POD editors would see there too.24.0.133.234 (talk) 13:01, 19 February 2013 (UTC)
  • I tried to resolve the problems with the composition and the background by cropping:16:9 crop 4:3 crop. The author may have a higher-resolution version. I agree that the tits and the baskets are cute, but if the photo showed more of the birds' tails it would be more encyclopedic. —rybec 02:16, 5 March 2013 (UTC)

Already FP, but a sharper, larger image?

I just came across a public domain image that's already FP, but it's 2.89 times larger in size. The colors are the same and the crop is the same. How should I go about handling this: do I upload the larger image and nominate it/delist-nom the original? Or should I just upload the new image over the FP image? Or what? Thanks! – Kerαunoςcopiagalaxies 03:04, 1 March 2013 (UTC)

I should add that this is an FP across-the-board image (Commons, various languages, you name it), and my source is different and the original image is different in that mine is the original photograph, the current FP is a crop of a press release/publicity handout. – Kerαunoςcopiagalaxies 03:08, 1 March 2013 (UTC)
Commons has a pretty strict rule against uploading over the top of a featured picture. Thus, you'll have to go through the delist process (file a single nomination under the delist section, and then add the new image and make your own vote "delist and replace." This should be straightforward, although unfortunately delist nominations have been poorly attended lately. Chick Bowen 03:40, 1 March 2013 (UTC)
Thanks Chick. I'll do that. It didn't seem like saving-over would be the right thing. – Kerαunoςcopiagalaxies 05:11, 1 March 2013 (UTC)
Don't forget the "other versions" field. rybec 00:57, 5 March 2013 (UTC)

Abuse of FP urgents

I'm not at all happy about this edit to the FP Urgents. Nominators should not be allowed to promote their own images as urgent, particularly when they've had plenty discussion (10 contributors). This image is the very definition of "meh" and, as I've already commented before, FP urgents has a natural bias to shift deservedly failing "meh" images to scraping a pass. The requirement to have "consensus" for promotion rather than a 2/3 majority, say, further makes it likely that a scraping pass will occur on an image with significant opposes -- because people naturally don't like to oppose and would rather avoid conflict and say nothing. As I'm involved I won't undo the edit to the urgents template but think someone else should. -- Colin°Talk 21:23, 3 March 2013 (UTC)

Um, no. Nominators are the only ones likely to put it into there, unless (as I was doing for a while) someone is systematically putting things into urgents by date (and when I did that, I did include mine in the systematic list, because you must admit, it would be very foolish for me to do it for everyone else's, then expect someone to notice I had done everyone's but mine, and mine were unlisted.).
Perhaps we should make more of an effort to systematically populate FPC urgents again, but criticising someone for making use of it? No. Adam Cuerden (talk) 21:49, 3 March 2013 (UTC)
Well if nobody other than the nominators are making any effort with it, and it merely serves as a "please support me as I'm almost out of time" last gasp plea, then it is time to retire this dubious means of advertising mediocre candidates. Colin°Talk 23:16, 3 March 2013 (UTC)
Frankly the edit summary I included said it all - this is the very definition of something that should go in FPC Urgents. Just because it was a nomination you vehemently opposed is no reason to come here complaining, and FWIW the end result totally disproves your diatribe above given that the only two extra votes after it was listed were opposes. You had already had plenty of comment on this candidate before this attack, and I'm starting to feel that your constant denigration of my contributions as seen here is going beyond opposition to just the image/s. The heading of this section "Abuse of FP urgents" says just that. As best I can remember this is only the second image I've ever added to FPC Urgents - and yet you come on here and accuse me of abusing it? Next thing you'll be accusing me of abusing FPC by making occasional nominations. Your tactics are really getting out of hand. --jjron (talk) 14:24, 4 March 2013 (UTC)
I've no idea what you are talking about wrt "constant denigration of my contributions" as I'm truly struggling to recall what images of yours I've commented on before. I'm guess I have commented before because that's true of most people's contributions here. WP:AGF. Yes, the edit summary said it all: "1/2 a vote off 5". FP urgents was created for neglected nominations (something I still disagree with because typically nominations get neglected for a reason) not for nominations with 10 folk commenting but only 1/2 a point away from success. That's abuse. Tell me, if you'd got your 5 supports and there were 4.5 opposes, would you nominate it for urgents to see if perhaps any more opposes could be found? What you you think if I did that? The whole FP urgents concept is broken -- we should let "meh" nominations fail and nominators should have the good grace to accept that. Colin°Talk 15:40, 4 March 2013 (UTC)
Dred Scott

I'm kinda on the fence with this, and because PPR is dead I thought I'd bring it here. The photograph is fairly high resolution and has been restored by several editors. It seems to be the only extant photograph of Scott, whose Supreme Court case was fairly important in US history. However, the pose is rather awkward and something seems to be off with his eyes. Do others think this image would qualify it for FPC despite the technical shortcomings? — Crisco 1492 (talk) 15:36, 5 March 2013 (UTC)

This might sound like an odd question, but is the subject alive? I believe it was not uncommon to photograph the dead and the subject died in 1858, only a year after the case. Basing it on the odd look he has. Grandiose (me, talk, contribs) 20:11, 5 March 2013 (UTC)
I wonder if [3] would be better? Although it's not a photo... Adam Cuerden (talk) 21:10, 5 March 2013 (UTC)
Oh, he was definitely alive. Death photos made clear that they were of the dead. The trouble with this one is simply that it was so badly damaged in the first place that the editors have had to invent a lot. That creates some weird bits, such as the blurry line between the hair and the (largely artificial) background. As for the eyes, what you're seeing is motion blur--Scott, presumably unused to posing for photographs, was unable to keep his eyes still during the duration of the exposure (which would have been quite long). Chick Bowen 21:13, 5 March 2013 (UTC)
Yeah, if he were dead at the time of sitting I doubt his suit would have been as frumpled. There's a bit of a back story, but this looks like it's for the below picture.
I doubt a sketch would have as much EV though... as an aside, PBS was wrong: there is another photo — Crisco 1492 (talk) 22:31, 5 March 2013 (UTC)
  • It looks very blurry at full resolution. The subject has a similar expression and general appearance in the other photo. Perhaps his eyes are so wide because he was trying extra hard to keep them open for the reason Chick Bowen explained. As for the awkward pose, his head was probably held still with a clamp . I heard someone talking about the Dred Scott case recently. They were saying it was only the second time the U.S. Supreme Court decided on the constitutionality of a law, the first time being Marbury vs. Madison. —rybec 00:14, 8 March 2013 (UTC)
  • I've done a bit of work with photos from that era, and something looks horribly off about it. I think that it's been saved as a very low-quality JPEG, then possibly blurred a bit to remove the artefacts, or something like that. Look around his eyes, and at the bottom left of his jacket. If we can find a better scan, I will commit to doing the restoration, though. Adam Cuerden (talk) 05:03, 11 March 2013 (UTC)
    • Think I see what happened: There's been a lot of hands in this pie, and none of them saved losslessly. JPEG artefects accumulate over successive saves. I'll see what I can do. Adam Cuerden (talk) 05:07, 11 March 2013 (UTC)

Messed up candidate page

Hi everyone, I was wondering if anyone knows what i've done wrong with my nomination. You can view it here http://wiki.riteme.site/wiki/File:George-W-Bush.jpeg

I haven't transcluded it as I was worried it might mess up the page. RetroLord 11:50, 10 March 2013 (UTC)

Size

I must have missed out on something, but is there any reason why 1000 pixels in width or height became 1500 pixels in width and height? What's with the change in the conjunction? — Crisco 1492 (talk) 23:21, 24 February 2013 (UTC)

See Wikipedia talk:Featured picture candidates/Archive 33#Proposal to change size critiera [sic]. This was originally phrased as "1500px on the shorter side," and the current wording was considered a simplification for clarity. The idea is to avoid overly skinny portraits or short and wide panoramas (like this one) that aren't truly high resolution. At least, that's my sense; I was away at the time and tried to catch up when I got back. Chick Bowen 04:33, 25 February 2013 (UTC)
It looks like a small cabal, led by Colin and Diliff pushed the issue through and bullied anyone who disagreed with them into toeing the line, see the "Respecting the Consensus" section for ample proof of that. Several nominations since the change has shown proof that despite the assertions otherwise, good nominations that before-hand would have been considered good FPC candidates are getting criticized because they fall under their own guidelines. I'll also remind everyone that the term is guideline, not rule, so hitting people over the head with it over several, or even several hundred, pixels as the only criteria for opposing should in itself be opposed. Cat-fivetc ---- 01:52, 26 February 2013 (UTC)
Eh, it's probably for the best, honestly. We can always IAR if we need to, but it's better to be bigger if we can. Adam Cuerden (talk) 02:10, 26 February 2013 (UTC)
I'm all for a larger images and in a perfect world for a guideline saying as such but people misguidedly treat the guidelines as hard rules. Maybe the better idea would be to add a line to the criteria saying that no single guideline should in itself be a reason to oppose an image, although I have to imagine that the hardliners would see that as an unacceptable loosening of the rules which would allow "inferior" images to gain FP status. Cat-fivetc ---- 03:52, 26 February 2013 (UTC)
Cat-five, I ask you to strike your comments about cabal and bullying per WP:NPA and refrain from making similar comments again or you will find yourself relieved of your editing facilities. My record shows I have championed images smaller than the criteria where justified. In fact, on Commons recently, I was a lone voice defending one of JJ's bird pictures that was a bit small (largely due to the wide-aspect crop and very difficult shooting conditions with a long lens). The statement "that no single guideline should in itself be a reason to oppose an image" is nonsense. People may oppose over whatever they like, if they feel strongly about it. One of the most common reasons to oppose is that folk dislike the crop/framing, which is merely one aspect. And others are free to agree or disagree with them. And people may nominate a picture that fails any aspect of the guidelines (within reason per WP:POINT) if they feel strongly about it. And others are free to agree or disagree with them. Colin°Talk 08:39, 26 February 2013 (UTC)
First of all, I resent your threatening to have me banned, except for my calling you a cabal, which was out of line and which I apologize for, my comments were aimed at your behavior on the page not at you as users. That being said, I also should not have stated that you were bullying another user, I still think you two were unneededly harsh towards people who did not disagree with your decision, a decision you did not seem to have any inclination to even consider reconsidering but to call your behavior bullying was out of line so I apologize and I have struck that part of the comment. Cat-fivetc ---- 00:48, 27 February 2013 (UTC)
I agree with Colin (no, not because we're leaders of a cabal) - that was completely uncalled for Cat-Five and the same cheap shot that is regularly fired at wikipedians who merely agree with each other about something and try to apply consensus to improve things here. It was discussed at length with a large number of contributors and only a very small minority had any disagreements with the proposal. Those who did disagree did not have particularly persuasive arguments IMO. Reasons why we thought so were provided and discussed. Apart from Breathe, who provided a laundry list of issues that both Colin and I responded to at length and got no further discussion in reply, and Samsara, who has shown himself over the last couple of years to be far more of a contrarian bully than Colin or I, there really wasn't any significant disagreement with the proposal. That, in my opinion, is solid consensus. And I take issue with the suggestion that we 'bullied' people into 'toeing the line', since really only Breathe and Samsara offered any real disagreement, and they did NOT change their minds - therefore nobody 'toed the line' as a result of our discussion. I also think it's disingenuous to say that images previously considered to be 'good' are now failing simply because of the image resolution change to the guidelines that took place. Expecting higher resolution was something that was already taking place in the voting community, and we simply adjusted the guidelines to match a realistic minimum standard based on what cameras were capable of producing in 2012. Ðiliff «» (Talk) 11:27, 26 February 2013 (UTC)
Per my comment above, I apologize for the cheap shot. I as much as anyone understand the special meaning that has word has here on Wikipedia and even if that weren't the case it was, as you put it, a cheap shot and one that I regret making. Cat-fivetc ---- 00:48, 27 February 2013 (UTC)
  • In this case, perhaps make it explicit that are slightly under the guideline can still be considered? That's one of the reasons I preferred "or", as it took into consideration the various shapes and sizes available. — Crisco 1492 (talk) 11:03, 26 February 2013 (UTC)
  • But what other shapes does the existing guideline not cater to? Apart from panoramas, I can't think of any. And with panoramas, usually by definition they are multiple images stitched together, so the usual arguments about elitism resulting in point and shoot cameras being excluded because they can't provide the necessary definition is even less of an issue - there's nothing to stop panorama shooters from providing an image whose short edge (usually height) is the equivalent of the long edge of a single frame. Ðiliff «» (Talk) 11:16, 26 February 2013 (UTC)
I would not be opposed to adding to the exceptions something like "and very narrow crops (other than scenic panoramas)". This would handle both the above orchid and JJ's bird. And the bird is handled by the technical difficulty clause already. The vast, vast majority of narrow crop images are scenic panoramas, for which the standard is high and expects a decent amount of detail. Ultimately, I think sometimes folk like to argue about perceived problems than actual ones. Even with the current guidelines, anyone nominating the above orchid could simply state that they are aware it is below the resolution criteria but that the crop is tall and thin for a very good reason, so an exception should be made. Colin°Talk 11:40, 26 February 2013 (UTC)
  • I'm rather surprised that that photo was voted FP actually. It's not a bad photo but the crop is awful IMO, and a more reasonable aspect ratio would have improved it. That photo could still have been shot as a vertical panorama though. I'm not saying every photo needs to be, but it could have been. I don't really accept that there's no way to avoid these low res images when the subject is static. And as Colin says, any guideline CAN be ignored if there is a fair and genuine reason for doing so. But it doesn't follow the guidelines should be adjusted to allow for these uncommon situations. Ðiliff «» (Talk) 11:46, 26 February 2013 (UTC)
Or how about "Exceptions to this rule may be made where justified on a case-by-case basis, such as for historical, technically difficult or otherwise unique images" -- bold is the new text. That introduces some common-sense that some people seem unable to apply without explicit guidance, and avoid introducing a laundry-list of exceptions. Leaving aside whether that flower is an FP, there will be rare examples where a useful or artistic severe crop may be justified from a straight-from-camera photo. -- Colin°Talk 12:47, 26 February 2013 (UTC)
I'm happy to support the inclusion of that, but previously I didn't really think it was necessary either. Ðiliff «» (Talk) 12:55, 26 February 2013 (UTC)
I see absolutely no problems with that wording, that would IMO give some grounds to reply to votes that are flagrantly hardline without caring about the circumstances of the image while still allowing us to stick to the hard standard most of the time. For better or worse it may some day get to the point where we need a laundry list though, if only because leaving the rules loose and open to interpretation causes these kinds of issues to repeatedly pop up. Cat-fivetc ---- 00:48, 27 February 2013 (UTC)
  • I appreciate a bigger size whenever possible; giving allowance in case to case(No further arguments on that JJ's bird here). But I see a technical error in the existing guideline (as "1500px on the shorter side"). We've so many proportions like 1:1, 2:1, 3:2, 4:3, 16:9 and even more wider. So I think a guideline specifying area (as in Commons) may be more suitable (also with allowance for rare cases). We can also include an aspect ratio clause (eg: Aspect ratio should not be bigger than 16/9 except panoramas and x/y for panoramas). JKadavoor Jee 05:50, 27 February 2013 (UTC)

Using a total pixel measurement system

I realize that currently the software does not show us the current number of pixels which forces every user to do the math by hand so with that in mind I have three proposals that are more or less based on the ideas that have been discussed here. Feel free to add your own proposal or just call mine silly but at least for me having a firm idea of what the end goal is helps.

Note: I'm using X and Y as shorthand for the horizontal and vertical lengths of the image respectively

Option A: Stick with the status quo style system of x*y dimensions as the current system for lack of a better option while working through [[ Wikipedia:Village pump (technical)]] and Bugzilla to try to get a better system implemented that would at least show the total pixels on the image description page and ideally might even make it available to a variable.

Option B Implement a total pixel based system now using the new nomination template to ask the nominator to input the x,y side sizes. It would mean two extra steps for the nominator and a nice neat and easy to see template or just one line of text could quickly and easily show participants whether an image met the pixel requirements or not.

Option C Stick to the status quo system, reject change, and go back to arguing whether side x was 1 pixel too short despite the image being a panoramic or side y was too short for a tall vertical image. I don't know if we have any FP's of them at the moment but in terms of subjects the Grand Canyon and the Louvre respectively come to mind as subjects that might have problems in a strict X,Y based measurement system but would be fine in a more flexible total pixel system.

If People are up for option A or B I'm happy to take the lead on it unless someone else wants to do it. This is not a straw pool but just a way to generally organize what's been discussed. Cat-fivetc ---- 06:45, 27 February 2013 (UTC)

I gather it is 1500px on the short size so a square 1500x1500 crop would be 2,250,000px. As someone pointed out either in the archived discussion on changing the size requirements or higher up on this page, bad crops to achieve a 1500x1500 or whatever square already fall under several other criteria to oppose if the image is visually/aesthetically unappealing and/or the encyclopedic value is hurt by too tight or too lose of a crop on one or more sides. Cat-fivetc ---- 07:58, 27 February 2013 (UTC)
But a 2250x1500 picture (3:2 format), 2000x1500 picture (4:3 format) and 2667x1500 picture (16:9 format) are much higher in resolution than 2,250,000px. That is why I say the current criteria is (although it is simple as Colin said) not doing any justice to all works (justice means exactly equal consideration to all). I agree with your argument that we can oppose basing or other grounds if feel necessary. But that is a different point. IMHO, pictures need (except panoramas; I'm very weak on that topic) a minimum resolution of 3M in the 2000x1500 picture (4:3 format). So a square crop will have 1732px on each side and 1800x1667 for pictures in 3:2 format. JKadavoor Jee 11:37, 27 February 2013 (UTC)
These other aspect ratios (with the same 1500px min dimension) are not "much higher in resolution". They have more pixels for sure but for a given picture, changing aspect involves cropping not resizing. When one downsamples an image (or didn't zoom sufficiently to begin with), then width and height are equally diminished. The word "resolution" is used carelessly in English but properly concerns sharpness and the ability to resolve fine detail (which in turn is proportional to how large the image can be displayed). So assuming the picture is focussed and sharp, measuring the shortest dimension gives you how much detail there is for a given size. Measuring the other dimension (and thus establishing the MP) only tells you what the aspect ratio is -- something that is of artistic and value concern but quite distinct from detail. Colin°Talk 18:32, 27 February 2013 (UTC)
Any system will have images it disproportionately affects. We have a huge range of images here from square crops of flowers to long scenic panoramas to tall pictures of carpets or orchids. We also have a huge range of circumstances from "studio" macro or portrait shots to shooting with a 500mm lens on the high seas. We also have to make sure the system doesn't unnecessarily inconvenience nominators or reviewers -- hence for now the 1500px system is easier than a MP system. I think the px system is fairer since the MP increase/decrease with the square of the side. So, even a moderate crop can result in significantly lower MP. On the other hand panoramas can achieve high MP even if one dimension is very low and below the levels of detail we've come to expect. Since px/MP are a proxy for image detail and printed height/width, a px threshold is in proportion to this detail or size whereas a MP threshold is not.
The issues of good/bad/appropriate aspect ratios are quite separate from size thresholds. I hope people are reasonable enough that if the best crop for an image is 1450px then not to demand a little more sky/sea to get it over the threshold.
So I feel the current system is easy to understand and judge. I'm not aware of anyone arguing over 1px here or there, but if there are image that are borderline and are being judged unfairly, then feel free to post a request here for additional comments. Colin°Talk 08:50, 27 February 2013 (UTC)
As someone who recently nominated an image slightly under size (but pretty much unavailable in any larger size for any practical purpose) and had it pass, I think that appropriate exceptions are being made. Adam Cuerden (talk) 12:33, 27 February 2013 (UTC)
I agree here with Adam, we've recently made exceptions, and also some with JJ's birds. What exactly is WRONG with the current version? If total pixel count isn't visible on the image page then it's to much of a burden on the end-user I think to figure out if their image meets our minimum requirements or not, so until that's added, if ever, we can just forget that as a requirement imho. As for the size of 1500, I always advocate for larger, since I think a FP should be able to be used for more than just web display, this resource (Wikipedia) allows for all kinds of uses, one being PRINT, and I think FP's should be, as being our best work, printable at 300dpi in a 4 color process and look good and not be thumbnail. — raekyt 17:26, 27 February 2013 (UTC)
Exactly; encourage high resolution whenever possible, consider case-to-case generously. JKadavoor Jee 04:18, 28 February 2013 (UTC)


//
// Calculate Megapixels on image pages
//
function calculateMegapixels() {
 var data = $('.fileInfo').text();
 pixel_filter = /([\d,]+) × ([\d,]+)/;
 if(pixel_filter.test(data)) {
  pixel_filter.exec(data);
  var wt = RegExp.$1, ht = RegExp.$2
    , w = parseFloat( wt.replace(/,/,'') )
    , h = parseFloat( ht.replace(/,/,'') );
  $('.fileInfo').append( $('<span></span>').text(' (' + ((w*h)/(1024.0*1024.0)).toFixed(2) + ' Megapixel)' ) );
 }
}
if( wgAction == 'view' && wgNamespaceNumber == 6 ) $j(document).ready(calculateMegapixels);

There you are. --Dschwen 18:10, 27 February 2013 (UTC)

Now get it added automaticly to every image description page or into MediaWiki... It's not that we can't make a script to do it, it's that the end-user, the average-joe doesn't have access to that, and we shouldn't require them to add scripts to be able to tell if their pictures qualify or not. — raekyt 15:13, 28 February 2013 (UTC)
I've just popped that script into my scripts here and on Commons. Thanks. However, I'm certain the calculation is a simply /1,000,000 and not the 1024x1024 number used for bytes. The fact that MP ratings on cameras don't exactly match the multiple of the largest image size is due pixels lost round the edge of the sensor, plus some generous marketing rounding. Colin°Talk 19:26, 28 February 2013 (UTC)


Well, I didn't want to use Marketingmegapixels, but the real stuff. It feels like a cheap attempt to game the system to insist that your 1000x1000 image meets a 1MP requirement. --Dschwen 21:34, 28 February 2013 (UTC)
Huh? A megapixel is a million pixels. This isn't one of those contexts where e.g. 'mega-' is erroneously used to mean 2^20 of something by convention. That mostly happens with disk space as counted by computer software. Your script measures mebipixels. :P JJ Harrison (talk) 03:17, 1 March 2013 (UTC)
There is nothing "real" about 1024. Just because computer memory is measured that weird way doesn't mean other systems are. I haven't found any sources to support the idea that megapixels are anything other than 1,000,000 pixels. Colin°Talk 19:15, 1 March 2013 (UTC)
When I grew up a mega still was 2^20, but if you young whippersnappers insist it on being 10^6 so be it ;-). --Dschwen 20:53, 1 March 2013 (UTC)
You were lucky, when I were a lad there was no mega of anything - memory, disk or pixels. In fact, my camera took no batteries. Colin°Talk 21:12, 1 March 2013 (UTC)
Not even for the meter? —rybec 01:01, 5 March 2013 (UTC)
Nope. It had a selenium cell on the front that detected light levels. You had to turn a knob to line up a little loop with the meter's dial and then read off the appropriate shutter-speed/aperture combination. By then your subject had got bored and wandered off. Colin°Talk 16:41, 12 March 2013 (UTC)
My first real camera took two button cells and they lasted over a year. But I guess Colin wins this "age pi$$ing contest" ;-) --Dschwen 16:31, 12 March 2013 (UTC)
  • Even if we don't change any standards here, maybe it should be suggested, wherever the appropriate place to suggest it is, that this be added to the common js file because it's an unobtrusive, helpful, and useful bit of extra information to have. Even if nothing official is ever done with it, it's a nice bit of extra information to have and more people than just read this talk page might appreciate it. Cat-fivetc ---- 00:54, 1 March 2013 (UTC)

Nominations

I would like to nominate the following for featured picture:

I would also like to nominate all the following, which I have copied from Photochrom:

I do not have permissions to create the nomination page, so if anyone is interested perhaps they could do it on my behalf 86.146.107.128 (talk) 20:30, 13 March 2013 (UTC)

  • PS, I've just noticed that, by an amazing coincidence, one of these, the Shakespeare Memorial Theatre, is currently up for nomination. I was not aware of that when I posted the above. That is a bit spoooky! 86.146.107.128 (talk) 20:39, 13 March 2013 (UTC)
Note that several of these are already FPs in some form. I'll mark those off. The remaining are probably worth it, although I suspect a new restoration would be wise for most of them. We've gotten better with photochroms over time. Adam Cuerden (talk) 03:23, 14 March 2013 (UTC)
Thanks, I did not know that many of those were already FPs. But why are there so many duplicates? Shouldn't we get rid of the duplicates and just have one copy? 86.177.107.46 (talk) 20:46, 14 March 2013 (UTC)
No, not duplicates but original scans and restored versions. Any idea why the filenames of the unprocessed images were chosen so poorly? --Dschwen 21:48, 14 March 2013 (UTC)
Sorry, no idea. I had no involvement with the creation or uploading of any of these. I just came across them and was struck by how attractive and interesting they were. Having perviously complained at the Main Page about the number of featured photos of birds, and having been told that there was a shortage of featured picture candidates, I thought I would nominate these to help bump up the numbers. 86.177.107.46 (talk) 00:19, 15 March 2013 (UTC)
OK. We have plenty of candidates but it does happen from time to time that we'll get a lot of the same kind together. We here at Featured Pictures don't directly control which photos are chosen for the main page although I think the general practice is that the main page shows featured pictures in the order of their nomination here, which might be why you see so many of one kind of photo in a row. Unless you're a banned user, you would be very welcome to create an account and start participating as a nominator and voter on the candidates page. --Pine 02:29, 15 March 2013 (UTC)
I know it's roughly the order promoted; Howcheng tries to save back things for holidays, and separate things out a little bit when there's a lot of the same together, but I don't know how far ahead he plans. Adam Cuerden (talk) 03:59, 15 March 2013 (UTC)

[Unindent] As for the horrible naming system of the unprocessed images... I suspect they were uploaded by the person who made the photochrom article, and, for that person, them being an unprocessed photochrom was the only thing they cared about. The problem is that the LoC use uncalibrated scans, meaning that that can be, in itself, misleading. Adam Cuerden (talk) 04:00, 15 March 2013 (UTC)

Oh, and on another subject, we haven't discussed the first image. I honestly thought this was already an FP, and will double-check the likely cats to make sure. It's a great image, a little under the size requirements, but I suspect that we'd be happy enough to IAR for a now-rare piece of relatively small electronics. Adam Cuerden (talk) 04:09, 15 March 2013 (UTC)

Issue

File:Dogcart3.jpg Is an FP, but does not appear in any FP gallery. Any idea what's going on there? Adam Cuerden (talk) 03:26, 14 March 2013 (UTC)

I guess it was missed after its nomination or it was missed when the last re-categorization was done. I think that image could go in Wikipedia:Featured pictures/People/Others or in Wikipedia:Featured pictures/Vehicles/Land. --Pine 03:42, 14 March 2013 (UTC)
Added it to Wikipedia:Featured pictures/Vehicles/Land. Armbrust The Homunculus 09:37, 14 March 2013 (UTC)

Oppose based on license

Would it be valid to oppose promotion of images based on chosen license, (yep the GFDL-1.2 thing again). I still think this license is detrimental to the project, and we're promoting images that are supposed to be our best work on a free encyclopedia but these images are basically not free. I also think we should be more on-par with commons:Commons:Image_guidelines for featured picture quality. So I'm wondering, is this a valid reason to oppose promotion? — raekyt 15:30, 4 March 2013 (UTC)

Slightly different point, but I *do* think we should still allow America-only copyright free stuff, for instance, British works from before 1923, but which aren't out of copyright in Britain due to Britain lacking a statutory cutoff year. Because otherwise, we fail to incentivise good-quality copies of such works, which en-wiki encourages otherwise. Since we have automatic ways to tag them for transfer to Conmmons on a specific date (see the parameters for {{PD-US-1923-abroad}}), that would be a bad thing. Adam Cuerden (talk) 18:50, 4 March 2013 (UTC)

  • I'm getting a bit tired of this now. SO we are still looking for useless reasons to oppose perfectly good pictures despite this being rejected again and again? How about we spend that time taking pictures and upload them at the licenses of our choice for wiki's benefit instead? --Muhammad(talk) 19:10, 4 March 2013 (UTC)
  • Both Wikipedia and Commons are founded on the principles of Free Cultural Works, which means anyone can reuse the content (whether charity, non-profit, commercial, government, personal, religious, atheist, communist, capitalist, Friend of America, Axis of Evil, cool or uncool). The GDFL licence (designed for software documentation, not pictures or encyclopaedias) was originally accepted because there was nothing better. There are now are better licences. It is widely accepted that the GDFL is an unsuitable licence for images and is being used as a nearest-alternative to an CC BY-NC licence, which is not "free" in the way WP/Commons understands the term. The GFDL for images potentially harms all re-users whether they are the scout-group leader wanting to include one of our images in a quiz or a medical charity wanting to use them in a patient leaflet. Those who persist in using it as a sole licence do not fully "get Wikipedia" IMO but I agree they are contributing valuable content. I don't think individuals opposing is an appropriate way of dealing with it as it would just be disruptive. The main reason I started the discussion on Commons FP criteria over this was to end the festering sore cause by the same individual actions and hot-head responses there. Nobody forces you to support such images if you don't regard them as Wikipedia's "best work". Raising this issue for discussion does not deserve the rude response above. Colin°Talk 20:06, 4 March 2013 (UTC)
  • I think it is a perfectly legitimate reason for opposing. If we sometimes oppose with no reason at all, or with childisg reasons, why can't we oppose based on the fact that an image cannot be used outside Wikimedia? Anyway the correct way of dealing with the subject is, of course, to eliminate GFDL-1.2. A first step in the right direction could be, as we did in Commons, to prevent pictures with such license to be nominated. Yes, it is all right to make money with our creations. But no, we can't have it all... -- Alvesgaspar (talk) 21:32, 4 March 2013 (UTC)
    • They're not allowed to be uploaded here anymore since 2009. Only stumbling block is we allow images from Commons, and common's allows them to exist. It's really on Commons now to eliminate the license like we did 4 years ago. I don't see why we should allow featured pictures of something we won't even allow to be uploaded locally? — raekyt 00:48, 5 March 2013 (UTC)
  • Here I agree with Raeky and Colin. Commons also doesn't encourage such a restrictive licensing. They have only three options at their Commons:Special:UploadWizard; CC-BY-SA (recommended), CC-BY, and CC0. Here, all of our pages have the footnote "Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details." Why not we can discourage something we really want to discourage (restrictive licensing)? But I don't agree with the "individual choice to oppose" (from my experiance in Commons). It only attracts revenge votes; making that page a war-place. I think it is better to make a decision as in Commons ("Licensing - Images licensed with solely "GFDL 1.2 only" and "GFDL 1.2 and an NC-only license" are not acceptable due the restrictions placed on re-use by these licenses."). JKadavoor Jee 07:27, 5 March 2013 (UTC)
    • Well then can we have the conversation to disallow these again? — raekyt 13:08, 5 March 2013 (UTC)
      • If someone with a bot can sort through the 3,312 featured pictures we already have to get some idea of the impact this would have? I suspect only a small number are under this license. — raekyt 13:10, 5 March 2013 (UTC)
        • There is a gallery available for Commons. May be PierreSelim can help in this case too. But I think it is not very important for the time-being unless we plan a mass delist which is not practical and not necessary now. We can consider it when a better candidate come (case to case). See this discussion too. JKadavoor Jee 15:07, 5 March 2013 (UTC)
      • I think this is the time to bring that conversation here too. But I too suggest to do all homework (like collect the number of existing FPs that may affected, etc.) prior to the start. It was a very hard discussion, lot of longtime-inactive-members came to oppose; but the decision of the closer was very critical: "consensus isnt defined as 2/3rds nor is it the majority opinion, for the record 19 opposing votes out of 51 votes is only 37% which is within the descretionary range for rfa. Weight of arguments presented based on policy is also part of deciding consensus. I considered policy there is no specific policy that preculeds projects determining their own requirements, so then I considered accepted practice(policy by default). The long term accepted practice is that projects like FP, QI can make restrictions greater than that of the overall community participation requirements, FP already restricts who can vote, QI already restricts source, they both set minimum size limits. I also considered what FP is, FP is the means to identify "our best work" the proposal put forth the argument that our best work should also inculde best practice when it comes to licensing. The support argument was that GFDL is being deliberately misused to restrict reuse(not freely available), compared to the oppose arguments of acceptable license but that never addressed the issue of misuse. What I'm expressing is a carefully considered outcome based on the agruments put forth and that is our best work(FP) can and should excluded works where the deliberate misuse of licensing makes an image not freely available. Gnangarra 02:00, 19 October 2012 (UTC)" JKadavoor Jee 15:59, 5 March 2013 (UTC)
  • We need to clarify something that I misunderstood when the Commons discussion was started. The "GFDL 1.2 Only" licence is a reaction to the historical licence migration process from GFDL 1.3 to a dual licence with CC BY-SA that occurred in the past and no longer applies. Any content uploaded with GFDL 1.3 since November 2008 can't be automatically migrated to CC BY-SA. So the issues with 1.2 currently apply to 1.3 and to any future GFDL licence unless GNU in their wisdom decide to remove some of its onerous terms. So a discussion that focussed on "GFDL 1.2 Only" would achieve very little -- folk would just switch to "GFDL 1.3" which has identical problems. The issue is with all GFDL licences. -- Colin°Talk 20:01, 5 March 2013 (UTC)
  • There was an interesting article in The Guardian recently: Even Google won't be around for ever, let alone Facebook. A librarian, discussing the Google Books project, asked the Google co-founders "I'm wondering what happens to all this stuff when Google no longer exists." We should be asking "I'm wondering what happens to all this stuff when Wikipedia no longer exists." In addition, when we no longer exist as Wikipedian. Part of the attraction of licences like CC is that the re-user is given permission to do something without having to ask. Typical copyright licensing requires negotiation. Muhammad has, in the past, suggested that on request he will permit folk to use his images without the GFDL requirements as long as they aren't greedy big corporations looking for a free ride. But if Wikipedia or User:Muhammad Mahdi Karim or User:Colin no longer exist (or are inactive) that is not possible. The greedy big corporations can get stock images for tuppence ha'penny these days anyway, and with all the benefits of indemnity protection that WP/Commons can't offer. Colin°Talk 20:01, 5 March 2013 (UTC)
  • One more point. The "number of existing FPs that may affected" that Jkadavoor mentioned: the answer is zero. Nobody proposed this would be retrospective on Commons and I don't think it should be retrospective here either. Wrt new FPs, only a handful of editors use this licence, compared with dozens of active editors and the whole multitude of Flickr and other free sources. Colin°Talk 22:34, 5 March 2013 (UTC)
    • I agree, but I would propose a moratorium on such licenced images in the POTD que that hasn't appeared on the main page since this license has been determined to be not in the spirit of the open freedoms of the project. Existing FPs can stay, disallow promotion of GFDL-only licenced images, and halt any in que for POTD with license would be my proposal. — raekyt 22:42, 5 March 2013 (UTC)
    • Agree (with Colin); it was a response to Raeky's argument that the case in Wikipedia is different. Further, I think most of the contributor's (if still alive and able to respond) will change their mind and add another suitable license as an alternate choice. I fully agree with Colin that we should plan with a long-sight to future where Jkadavoor or any other user not able to respond to any queries or requests due to their death or inactivity. Raeky, I think you can go on with this proposal. JKadavoor Jee 05:41, 6 March 2013 (UTC)

Proposed change

I am closing this discussion as no consensus, as an uninvolved administrator, and after lengthy consideration. Featured pictures are judged against guidelines which, by their very nature, exclude some pictures which are permitted for use on Wikipedia. However, numerous contributors to this discussion do not support these particular proposed guidelines. There is no policy requiring their adoption. Therefore, the proposal has not reached consensus. This closure is without prejudice to the above discussion regarding opposes based on the license used. Warofdreams talk 01:14, 26 March 2013 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


  1. Disallow promotion of GFDL-only licensed images as Featured Pictures.
  2. Grandfather existing Featured Pictures with this license, i.e. not demote them on license alone.
  3. Prevent any such licensed images in the POTD que from appearing on main page after enactment of this change.

Reasoning: Wikipedia in 2009 depreciated use of these licenses, and disallowed local hosting of them, see Speedy deletion criteria F3. Commons's Featured Picture project has also disallowed promotion of such licensed images in October 2012. The license choice, is an attempt to circumvent the open access freedoms that Wikipedia was founded on, which is one of the five pillars that this project stands on. — raekyt 14:23, 6 March 2013 (UTC)

Comment this proposed change affects exactly three users on Wikipedia: User:Hasin Shakur, User:Muhammad Mahdi Karim and User:Jjron. The first has contributed just two pictures and one featured picture. The other two have contributed many pictures and have many featured pictures between them. Out of the 356 pictures nominated in 2012 that achieved feature picture status, only 11 (3%) had the GFDL licence. Colin°Talk 20:28, 9 March 2013 (UTC)

Discussion

  • Support per reasoning above. — raekyt 14:24, 6 March 2013 (UTC)
  • Support though I'm neutral on the POTD issue -- sounds like an administrative hassle and would be simpler just to accept any FP, old or new. What do those running POTD think wrt any hassles this might entail (separate from whether they personally agree with it)? Also the comments wrt deprecated licences and speedy delete issues applies to "GFDL 1.2-only" licences, not to GFDL in general. For the sake of avoiding confusion, it might be best to express the 1st clause as "Disallow promotion as Featured Pictures any images having GFDL as the sole licence or GFDL multi-licensed only with an -NC licence." The main issues against the GFDL for images are set out and discussed at the Commons discussion linked above. -- Colin°Talk 15:40, 6 March 2013 (UTC)
  • I don't know about Howcheng, but I think a POTD blacklist would be instruction creep to the utmost degree. There's already enough considerations and little love. — Crisco 1492 (talk) 14:55, 7 March 2013 (UTC)
  • Support per the discussion on Commons. JKadavoor Jee 15:48, 6 March 2013 (UTC)
  • Conditional support if Colin's suggested changes are made. The reason is that an image that has {{gfdl}} on it and nothing else could be considered GFDL-only (through plausible misreading of Raeky's wording) in the sense that that's the only template on it. We are discussing those images that explicitly prevent relicensing, right? As for POTD, changes to the FPC and POTD processes should be kept separate. Chick Bowen 18:01, 6 March 2013 (UTC)
    • Could you clarify what you mean by "relicensing"? Colin°Talk 21:28, 6 March 2013 (UTC)
      • I mean GFDL 1.3 images that are eligible to be relicensed as CC are still permitted. I don't know if there are any left, but the deal that the WMF made with the FSF to allow relicensing did not, as I understood it, expire. Chick Bowen 22:34, 6 March 2013 (UTC)
        • Can you give an example, do these still exist? — raekyt 01:06, 7 March 2013 (UTC)
          • I don't know of an example--it would be hard to find one without writing a script. There might not be any. There aren't supposed to be. I don't regard this as a big deal--it's just that I understood you to be suggesting that the FP project should be as restrictive of licensing as WP itself, and I wouldn't want us to accidentally make it more restrictive (beyond, of course, the requirement of free images). This is why I preferred Colin's more precise wording. I would prefer, though, to keep POTD separate, hence the conditional support. Sorry if I wasn't clear in the first place. Chick Bowen 03:43, 7 March 2013 (UTC)
            • I think this re-licensing aspect is a distraction -- GFDL 1.3 images can no longer be auto-migrated to CC as there was a date deadline for that. If there were some GFDL 1.3 licences uploaded before the deadline that didn't get auto-migrated, I would be very surprised as I would have thought a bot did the migration. And anyway, even if there were some migration still to occur, we'd just let it occur and then nominate it once it has a CC licence too. So let's ignore this aspect. It is why I think the "GFDL-only" aspect is confusing and I can't fully support that -- someone could dual licence with "GFDL 1.2-only" and "CC BY-SA" (or "Art Libre") and that would be perfectly fine. -- Colin°Talk 08:44, 7 March 2013 (UTC)
  • Support points 1 and 2 (per discussion), Oppose point 3 (meaningless) -- Alvesgaspar (talk) 18:10, 6 March 2013 (UTC)
  • Support per above. -- King of 22:48, 6 March 2013 (UTC)
  • Support 1&2, Oppose 3 Per the above with the caveat that even though we hope that at least one person will look at the license during voting and/or before the image is promoted, if an image slips through the cracks it probably isn't worth delisting just for that reason so it should be treated as if it were an already existing FP. That may seem like an edge case but it avoids all sorts of arguments and headaches that could pop up. Cat-fivetc ---- 04:14, 7 March 2013 (UTC)
  • Question So this proposal would still allow GFDL+CC-BY-NC licensed images? --ELEKHHT 04:22, 7 March 2013 (UTC)
  • No; I think. "If you want to ask why unfree/non-commercial material is not allowed at Wikimedia Commons or if you want to suggest that allowing it would be a good thing please do not comment here. It is a waste of your time. One of Wikimedia Commons' basic principles is: "Only free content is allowed." This is just a basic rule of the place, as inherent as the NPOV requirement on all Wikipedias." I think this is quite applicable here to. Adding CC-BY-NC as a license is merely to confuse potential end users. JKadavoor Jee 05:05, 7 March 2013 (UTC)
  • No. The spirit of the rules is to prohibit images which are not truly "free." For example, at Commons, a prohibition on (post-2009) GFDL-1.3 was added later, because the spirit of the vote on GFDL-1.2 was clearly to include that as well. We don't argue over technicalities, and loopholes shall not exist. -- King of 06:19, 7 March 2013 (UTC)
  • But both of them have at least one valid license (CC-BY-SA or FAL). I can't understand the logic behind adding CC-BY-NC and CC-BY-SA together. :) JKadavoor Jee 07:57, 7 March 2013 (UTC)
  • Adding a -NC licence is fine. As long as there is one truly free licence for images (such as CC BY-SA or Art Libre (aka FAL)). Having more licence options isn't necessarily confusing or bad. If someone makes a derivative work, they could choose to take the -NC licence for their new work. Without the CC BY-NC-SA, they would be forced to take CC BY-SA for their new work per the "share alike" aspect. Of course, if you don't want the re-user to create an -NC derivative work, then don't add an -NC option and use a share-alike licence. If one uses CC0 licence (effectively public domain) then there is no share-alike restriction and creators of derivative works can do what they like, including full copyright. Colin°Talk 08:44, 7 March 2013 (UTC)
  • Strong Oppose. Lets stop undermining people that are actually actively contributing new content to the project, eh? And furthermore this is not, and should not be, a clone of the inferior Commons FPC. Referring to some discussion there is meaningless and is rightly ignored. If that's where you want to contribute and the rules you wish to follow, then no one's stopping you from doing so, but it doesn't give you the right to come here and ram your rules down everyone else's throat. And people wonder why we're down to a handful of photographers making quality original contributions. --jjron (talk) 14:49, 7 March 2013 (UTC)
    • This has nothing to do with picking on specific contributors, it's about following the principles that this project was founded on. An article contributor doesn't have the option of contributing their text under a more restrictive license, in hope of being able to make money off of it. People are free to contribute or not, part of making a contribution is accepting that their work needs to be freely licensed for all uses, including commercial. The GFDL license, which is not acceptable to use locally, only on Commons, puts a serious restriction on free use. There are loads of great photographers that would contribute if we allowed non-commercial licenses, hell we could turn Wikipedia into Getty Images 2.0, and let people buy access to everything here, sell access at $10 a pop per article you want to read! We'd get more contributors, sure but that's not what this is about. The photographers your referring too if you look at their image pages, they all link to their personal websites/store fronts where they SELL rights to their images, they're effectively using this process and Wikipedia as free advertising. Again NOT what this project was founded on. If they wan't to contribute they need to use a license that is compatible what we allow on Wikipedia. The fact that Common's allows something, fine, doesn't mean it's acceptable here for uploaded content. So why should we promote something we wouldn't even allow to be hosted locally? — raekyt 15:49, 7 March 2013 (UTC)
    • Well; all I can see is an angry response from a contributor whose interest may have affected: "My images are published on Wikipedia and other Wikimedia projects under the GFDL license. If you want less restrictive terms for reproduction of my images off the Wikimedia projects please contact me for details. As well as the alternative licensing I will often be able to provide images at higher resolution or quality settings if required, or may have related images that I have not made available to Wikipedia." JKadavoor Jee 16:34, 7 March 2013 (UTC)
  • Strong oppose as a photographer and one of FPC's most active contributors, such useless rules will make me rethink my contributions. As long as the license is valid on commons as free, we should have no objection with it as the license does not explicitly prohibit commercial use. For those who say large companies would buy stock images rather than use wiki ones, I have had my images used in violation of the terms by many such as Forbes and National Geographic. If I get paid for such uses, I can buy better equipment and create better images for wikipedia. Most of the little I make goes towards lenses and park/travel expenses. --Muhammad(talk) 18:21, 7 March 2013 (UTC)
Let's work this out. You use "GFDL 1.2-only" so that big corp can't use your images. Yet you say big corp has used your images regardless. All this shows is that like many hindrances to use/reuse folk come up with (DRM, region-coding DVD, etc) they don't prevent misuse and just get in the way of the honest guy. But your example doesn't prove the point, which is that large companies can buy micro-stock images for prices that make the risks and hassles of using a WP/Commons photo unattractive to anyone with any sense. A discussion on what WP regards as appropriate licensing for its best images really isn't concerned with how you fund your hobby. If WP wants to pay you to take photos, you know already there are grants -- and if those aren't forthcoming then well you have your answer as to whether Wikipedia wants to pay you for its photographs. Colin°Talk 18:53, 7 March 2013 (UTC)
Because I use GFDL, I could write to these companies and ask them to pay up for their violations (which they did). Most honest people ask permission and I usually waiver the strict licensing at my discretion. Were I to die (as you pointed out earlier), my will, will hopefully donate these images under a CC license so that permission is no longer required. --Muhammad(talk) 19:12, 7 March 2013 (UTC)
Well let's hope nobody dies any time soon -- far more likely is that folk just move on from Wikipedia, as they do for various reasons, leaving no way of contacting them. Companies that pay up would do so likewise for CC BY-SA violations too. As for paying for your hobby -- your current kit is perfectly capable of taking featured pictures and if it is worn out then that isn't due to photographs uploaded to Wikipedia/Commons as the camera has a life of ten-of-thousands of photos. The truth is that photography is an expensive hobby, with new gear we all lust after, and most of us fund it like any hobby from our own funds. What we give to WP is a donation. We don't take grants from Wikimedia and then upload photographs with restrictive licences so we can make more money from them as well. Colin°Talk 08:53, 8 March 2013 (UTC)
  • Oppose I don't think this helps Wikipedia. Adam Cuerden (talk) 20:07, 7 March 2013 (UTC)
  • Strong Oppose I don't think this helps anybody. Benjamint 20:27, 7 March 2013 (UTC)
  • Comment The above two comments ("I don't think this helps Wikipedia/anybody") aren't arguments; just statements of belief. You might as well have written "I like the colour green" for all that it has added to the discussion and for all that it will count in the end. Wikipedia is fundamentally free content, which absolutely means we must respect the rights of anyone to use, reuse and derive from our work without legal or practical hindrance. Note The Definition of Free Cultural Works requires a licence to be practical, which the GFDL is not for images or short texts. Many may wish Wikipedia was something else, like a non-commercial online encyclopaedia full stop. But it isn't. It is free content. Therefore, how can "our best" images be licensed at odds with the core values of Wikipedia? I'd like to hear your arguments, not your wishes or vague beliefs. Colin°Talk 21:26, 7 March 2013 (UTC)
  • Comment -- I endorse Colin's evaluation about the the two above oppose votes and add two more. Let me quote what I think are emotional and unhelpful reactions which have nothing to do with the matter under discussion: (1) Lets stop undermining people that are actually actively contributing new content to the project, eh? And furthermore this is not, and should not be, a clone of the inferior Commons FPC (from jjron) [not very elegant or objective, is it?]; (2) as a photographer and one of FPC's most active contributors, such useless rules will make me rethink my contributions (from Muhammad) [this sounds like a threat to me]. Of course, this problem will eventually be solved when Commons decide to deprecate those type of licenses or Wikipedia decide not to accept them from Commons. But it may some time I'm afraid... -- Alvesgaspar (talk) 22:19, 7 March 2013 (UTC)
    • Allow me to explain then. The goal of an en-wiki Featured Content process is to encourage high-quality material to use on en-wiki (hence why we have an encyclopedic value test, and a use in article test). The goal of Commons FPC is to get high-quality material for a free-use content repository. For Commons' goal,. GDFL 1.2 isn't appropriate. For en-wiki's goal, it's perfectly fine. Therefore, I see no reason whatsoever to restrict away GDFL 1.2, and, as it would drive off good contributors, it would actively hurt the goals of en-wiki FPC. I reiterate my oppose, and upgrade to strong oppose. Adam Cuerden (talk) 22:28, 7 March 2013 (UTC)
      • Then how do you explain the fact that we speedy delete images uploaded with that license here? It's hard to argue that the content license fits with en-wiki's goals when we delete it. — raekyt 22:42, 7 March 2013 (UTC)
      • The goal of en-wiki is to be "a multilingual, web-based, free-content encyclopedia project". You seem to be wilfully ignoring the free-content bit, and all that entails. This isn't just a website with some interesting articles and nice pictures to look at. As you say, Commons is solely an image (and some other non-text media) repository. But Wikipedia is free encyclopaedic content, which includes articles and images. And that content is widely reused. As for "driving off good contributors", we don't decide what is our best work based on the threats of a handful of photographers, who in the grand scheme of images used on Wikipedia, account for far less value than they think. Our "free content" license requirements already put off potential good contributors and we live with that no problem. Colin°Talk 23:14, 7 March 2013 (UTC)
  • Support per above reasoning. -- Lycaon (talk) 07:04, 8 March 2013 (UTC)
  • Comment I've no wonder while seeing all these ‘’strong opposes’’ without any valid arguments; it had happened several times, here, and in many similar places. We've a guideline Wikipedia:NPOV: “Arguments mustn't take sides, but should explain the sides, fairly and without bias. This applies to both what you say and how you say it.”; but who care.
    Trying to answer the “arguments” above:
    Commons and Wikipedia are entirely different entities. We are only interested in Wikipedia. (per jjron)
    Commons and Wikipedia are not entirely different entities; they are part of the common entity, Wikimedia. All the policies and guidelines are inherited from the same parent.
    As long as the license is valid on commons as free, we should have no objection with it as the license does not explicitly prohibit commercial use. (per Muhammad)
    Commons is maintaining some old licenses for backward compatibility and a wide variety of licenses for different purposes of media. But for “own contributions” nowhere in the Upload Wizard it displays a GFDL. Further, at Commons:Copyright_tagsdeed.en#GNU_Licenses it says: “Please note: The GFDL is rather impractical for images and short texts, because it requires the full text of the GFDL to be published along with the image. This is prohibitive for print media: in order to use a single image in a newspaper, a full page containing the GFDL would have to be printed. To resolve this, please dual-license your work under GFDL and an equivalent Creative Commons license like CC-by-sa-3.0 (see below). This helps to make your work usable not only freely, but also easily.”
    That is advice for new images for commons. Our job is to decide whether or not an image illustrates an article well enough to be considered the best. --Muhammad(talk) 08:52, 8 March 2013 (UTC)
    But still I can see you upload files with a GFDL license only. Do we appreciate contributors who disrespect the guidelines? JKadavoor Jee 10:20, 8 March 2013 (UTC)
    The goal of an en-wiki Featured Content process is to encourage high-quality material to use on en-wiki. (per Adam Cuerden)
    What is high quality media? See Wikipedia:Featured_picture_criteria #4: “Has a free license. It is available in the public domain or under a free license. Fair use images are not allowed. To check which category a particular image tag falls under, see the list at Wikipedia:Image copyright tags”. It is not clearly mentioned there (assuming good faith on the contributor); but at Upload Wizard, under option “This file is my own work.”. JKadavoor Jee 07:38, 8 March 2013 (UTC)
  • The purpose of FPs is to recognize the best of wikipedia's work, not wikimedia's. While it may be ok for wikimedia to disallow FPs based on this license, wikipedia should not concern itself with licenses. As long as the image is considered free (able to be uploaded on commons), it should be considered ok for wikipedia. Our job is to decide whether an image illustrating an article does so well enough to be considered unique. The license it has does not hinder its encyclopedic value. --Muhammad(talk) 08:52, 8 March 2013 (UTC)
    • Don't mix the words "Wikimedia" and "Wikimedia Commons". Wherever I say "Wikimedia", I mean Wikimedia; not Commons. Remember "Wikipedia" is just a "Wikimedia Project" like "Commons". JKadavoor Jee 09:54, 8 March 2013 (UTC)
    • "wikipedia should not concern itself with licenses". Buzz. Wrong answer. This is a free content project. Colin°Talk 08:55, 8 March 2013 (UTC)
      • While I do sympathise with Muhammad regarding his desire to control use of his images, and I actually dislike the fact that Wikipedia is a 'free content' project when it places higher importance on licensing and use outside of Wikipedia than it does on encylopaedic value within the scope of Wikipedia, fundamentally I agree with your arguments Colin. As it stands, the proposal here is in keeping with the goals of Wikipedia, such as they are. And this proposal doesn't stop contributions of GFDL licensed content to Wikipedia and Commons, it simply stops the content being featured. Therefore the opposition to the proposal seems to be motivated primarily by vanity. Of course Muhammad and others are contributing to Wikipedia for other reasons too, but I think it's important to keep the reasons for contributing content to Wikipedia, and the reasons for submitting content to FPC as separate arguments. Ðiliff «» (Talk) 09:09, 8 March 2013 (UTC)
        • A very good point of view, for me. Chances that I too think it is worthless to contribute freely to Wikimedia. But then I prefer to simply walk out than do stick here and try to corrupt the system for my interests. JKadavoor Jee 10:09, 8 March 2013 (UTC)
  • A very Strong oppose. What for a stupid discussion, what for a stupid reason!?! GFDL 1.2 is still allowed, a not perfect license for all, but an ALLOWED license!!! For Wikipedia is a CC-BY-NC license valid enough. Do we need more??? What about the commercial interests of our photographers? Is the interest of stranger commercial users more important then the interest of our photographer? Our Photographer donate the images to the Wikipedia, not the parasite commercial users! Think about my words ... and sorry for my bad English . We can be happy to have a GFDL 1.2 only image then nothing. It is simply my unshakable conviction. --Alchemist-hp (talk) 09:32, 8 March 2013 (UTC)
    • But it doesn't stop you from contributing to Wikipedia, it just stops the images from being featured. And as I said above, even though I don't agree with all of the goals of Wikipedia, this is what they've decided and it isn't going to change even if we argue about it here. It's like going to court and saying "I don't agree with this law! It's stupid and it's my belief that the law should be changed!". Well, you might even be right, but nobody in the courtroom has any control over it, they simply apply the law as well as they can. Ðiliff «» (Talk) 09:59, 8 March 2013 (UTC)
  • Comment. As happened last year with the image size proposal, it's clear that those trying to shove this through will simply attempt to flood everyone opposing it with the same responses repeated ad nauseum, or by specifically and personally targeting those people as individuals. Proof? Simply look at the extensive replies, often personal, directed at all the oppose !voters, while those in opposition allow supporters to place their !vote in peace. This is obviously in order to try to shout down the opposers' points of view, and more importantly to intimate anyone else considering opposing who may be a bit more reticent to jump into the fray to entirely refrain from commenting. Very sad. Very, very sad. --jjron (talk) 13:34, 8 March 2013 (UTC)
    • That's an interesting phrase: "everyone opposing it" wrt the image size discussion. Two people opposed who hadn't shown any interest in FP before, left their single comment and didn't respond further (one didn't hadn't made more than a handful of edits to WP for years before and hasn't made any edits since). The other was Samsara and folk can examine their contribution to the discussion and make their own mind up. As for this discussion, all I see is those who stand to lose out on future gold stars getting hot headed and rather exaggerating their own self importance to the project. Colin°Talk 14:16, 8 March 2013 (UTC)
  • Strong oppose. GFDL is a free License. Point. Its no perfect but ist a free License. Ralf Roletschek (talk) 16:00, 8 March 2013 (UTC)
  • Oppose. Basically per Adam; I fail to see how this benefits the project. In fact, this would have a negative effect, discouraging people from contributing high quality images. SpencerT♦C 17:30, 8 March 2013 (UTC)
  • In fact, if otherwise (if allow GFDL); it will encourage more people to go that way. Finally, we've only GFDL contributions. We get more "quality" contributions, if we allow "All rights reserved outside Wikipedia". JKadavoor Jee 06:55, 9 March 2013 (UTC)
  • Exactly, if we allowed NC clause licenses for pictures we would, a guarantee you, get HUGE amounts of HIGH quality pictures. But the project has determined we can't and won't do that. GFDL-1.2 ONLY clauses like above is a backdoor approach to a NC clause... That's why it shouldn't be even allowed to exist even on Commons, that's why Commons FP process disallows it, that's why we speedy delete images with that here locally... It's not within the spirit of this project. If people want to make money from their images there's plenty of websites for that, wikipedia is not one. What you contribute here should be FREELY licensed, and that means sacrificing commercial profit from your contributions, otherwise it's not really a contribution but more like an advertisement for a product your selling. — raekyt 07:02, 9 March 2013 (UTC)
  • What insulting nonsense. Anyone that I've known of using this license is 100% happy with the usage of their freely given image in any Wikimedia project worldwide, in an original or modified form, and is perfectly happy to sacrifice commercial profits from these contributions for the benefit of the project. What they usually object to is some multimillion dollar business making commercial profits off their contributions without paying a cent for it. Then they come here and are accused that their contributions are an "advertisement for a product your selling" (sic). It beggars belief that you are so desperate to feather the nests of these organisations, and yet would probably be the first to jump up and down to defend their copyright claims. --jjron (talk) 05:16, 10 March 2013 (UTC)
  • Oppose Simply because I think pragmatic is better for Wikipedia than idealistic in this case. Home grown high quality contribution is important to solicit other image donations. I've done a lot of said soliciting behind the scenes myself. The GFDL is a free license, and the images can be used commercially. The barrier isn't even high for online use. It's just a mild pain in the ass for print use. FYI, at a minimum 7.5% of all featured pictures are GFDL-1.2. JJ Harrison (talk) 09:43, 9 March 2013 (UTC)
    • Thank you for your thoughtful response, which makes a change from the heat/no-light elsewhere. I've a wikifriend who solicits some huge donations from organisations and they are asked to donate CC. I feel the acceptance by the community of a back-door -NC licence is hypocritical. Indeed, the only folk using GFDL for images are a few dinosaur wikipedians/Commons. As for whether GFDL "is" or "is not" free, well that comes down to one's interpretation of whether it is "practically free", as required by the Definition of Free Cultural Works. Whether you think it is "just a mild pain in the ass" isn't important -- it is what potential reusers think or believe, and what those using it want to achieve. The latter group want to restrict reuse, which is fundamentally against the aims of this site and not something to celebrate with our featured process. The former group, on reading the GFDL will left wondering how on earth this can apply to them and what to make of it -- thus unable to use it. Colin°Talk 10:54, 9 March 2013 (UTC)
    • "at a minimum 7.5% of all featured pictures are GFDL-1.2" - May be; because GFDL was the only license that is considered as the most suitable license in our old days. In June 2009, Wikipedia has made the change from the GFDL license to CC-BY-SA as its preferred choice. We have similar discussions in our old days too. And so many other wikis followed our track. It is a pity that our most reputed members still refuse to accept this change. JKadavoor Jee 12:06, 9 March 2013 (UTC)
    • The percentage of featured pictures being GFDL is historical, you have to go back several years to find any numbers being submitted at all. In 2012 the percentage dropped to 3% and was due to only three users on Wikipedia: User:Hasin Shakur, User:Muhammad Mahdi Karim and User:Jjron. The first has contributed just two pictures and one featured picture. The other two have contributed many pictures and have many featured pictures between them. These three contributed 11 pictures out of 356 FPs in 2012. There has been a little peak in January this year, with 8 FPs by Muhammad and 1 by Jjron. So this proposal affects just two regulars at FP, both of whom use their file description pages to advertise. Colin°Talk 20:28, 9 March 2013 (UTC)
      • So Colin continues his trumped up claims and personal attacks. Of course most people won't bother checking his claims, so I'll quote what my image pages actually say: "This image has been released for use worldwide under the licensing specified below. If you require different licensing (e.g., for commercial publishing), or a larger or higher quality version of this image, it may be available from the author. You can contact the author by clicking here and leaving a message, or by sending me an email." (two links go to my talkpage and to the Wiki email page). So this is advertising is it? Unlike many other contributors I don't even link to an external website, Facebook feed, etc in order to try generate off-Wiki business (all perfectly acceptable BTW if you care to read up on it). In most cases people who do contact me seeking alternative terms get an essentially copyright free version in whatever form they require. --jjron (talk) 04:53, 10 March 2013 (UTC)
        • You've said before that you use GFDL to restrict those who can re-use your content, denying it to certain groups and charging others. This isn't free content and should not be celebrated by a featured picture star. You are welcome to your point of view regarding control over your pictures. I have absolutely no problem with the point of view. It just doesn't align with the fundamentals here on Wikipedia and we shouldn't be happy about that here. Colin°Talk 08:56, 10 March 2013 (UTC)
  • Comment Several people have suggested that this proposal doesn't help Wikipedia. Perhaps they think WP will have fewer great images or that the Featured Picture forum will lose lots of contributors. The fact is that only two regulars at FP contribute all the GFDL images going back over a year. When Commons eliminated GFDL images from FP, there was a 40% increase in nominations compared to the same period last year -- I'm not suggesting these were related at all but it shows that Commons FP has never been healthier and suffered no loss. Colin°Talk 20:28, 9 March 2013 (UTC)
  • Strong Support (to balance those Super strongest possible oppose nonsense out ;-) ). Of course this helps the project. We should not put material licensed to make free reuse deliberately hard on a pedestal. This is clear as glass to me and I cannot understand how somebody can be either so in denial or still try to rationalize this in spirit non-free nature of GFDL applied to images. This has to stop now before the minds of other potential contributors get poisoned with this license. --Dschwen 22:09, 9 March 2013 (UTC)
  • Comment Looks like the Commons debate all over again, with some of the same people opposing with weak arguments, if any (I do note there are a few argumented opposes too :-). Raeky, Colin, Jee and Daniel all make very good points with which I wholeheartedly agree.
    I must say I do not really understand the outcry − we are not talking about forbidding GFDL-only uploads (though that would be a good thing too, but let’s leave that aside), just about not featuring it. Some folks here seem to be telling us “you can’t have the best of both worlds − pictures that are both good and free” (on which I disagree). Well, these people cannot have the best of both worlds either − pictures both with a crappy backdoor to disallow commercial usage (while they still can) and featured on the main page. Media that make reusers jump through hoops are against the spirit of our projects, and are thus not the best we have, period. Jean-Fred (talk) 23:10, 9 March 2013 (UTC)
  • Oppose, agree with Jjron (talk · contribs) and Adam Cuerden (talk · contribs), above. — Cirt (talk) 05:10, 10 March 2013 (UTC)
  • Oppose I dislike the idea of treating an image differently in different places. If you convince the community to disallow the GFDL 1.2 project-wide, that will change FP along with everything else. If you can't convince the community to disallow the GFDL 1.2 project-wide, you have no standing to restrict when or where it can be used. Sven Manguard Wha? 01:23, 11 March 2013 (UTC)
    • That happened, you can't use GFDL 1.2 ONLY on en-wiki, and any GFDL license isn't available to choose during the upload process at en-wiki. Ergo, we restrict it HERE. Commons's is a separate project. — raekyt 03:04, 11 March 2013 (UTC)
      • The WTFPL isn't included in upload process but it is just as valid and even freer as the CC BY-SA. --Guerillero | My Talk 04:03, 11 March 2013 (UTC)
        • But we don't speedy delete images under that license, we do with GFDL 1.2 ONLY, which is the license I'm most concerned about. — raekyt 08:33, 11 March 2013 (UTC)
        • We don't CSD those images; we move them to commons. See {{GFDL-1.2}} --Guerillero | My Talk 17:55, 11 March 2013 (UTC)
          • From the begining of this discussion you've been mentioning that we speedy delete GFDL images. {{GFDL-1.2}} clearly mentions that speedy delete can only be done if the image is uploaded to commons. Further on the same template mentions, "The deprecation of this template does not prevent the use of GFDL 1.2-only files on the English Wikipedia, nor should this consensus be used as a precedent in discussions on other projects.". Which makes me ask myself why the speedy delete situation was even brought up. --Muhammad(talk) 19:57, 11 March 2013 (UTC)
  • Oppose a libre license is a libre license. Are we going to restrict FPs to only Creative Commons licensed works next? Not liking the terms of the license is not a valid argument. --Guerillero | My Talk 01:48, 11 March 2013 (UTC)
    • What a wilfully simplistic interpretation of a licence. Have you read the "On the GFDL wording" section below? A free licence must be practically free and appropriate to the media it covers. GFDL for images fails on both accounts. Colin°Talk 08:34, 11 March 2013 (UTC)
    • There is a misunderstanding here: The point of this proposal is not to put forward CC licenses over other free licenses ; it is to restrict FPs to “free in practice” licences (the only known offender being using only the GFDL 1.2, or GFDL 1.2 + unfree licenses). Folks who dislike Creative Commons (whatever the reason) are welcome to use other free licenses, like the FAL for example (there are indeed some folks on Commons who uses it for this very reason). (and noting the slippery slope in your argumentation). Jean-Fred (talk) 10:21, 11 March 2013 (UTC)
  • Comment What is Wikimedia’s current policy on licensing? Is it http://wikimediafoundation.org/wiki/Press_releases/Dual_license_vote_May_2009 ? Why? Is it because of http://wikimediafoundation.org/wiki/Press_releases/Dual_license_vote_May_2009QA ? I doubt whether Wikimedia has a hidden agenda to encourage their contributors to make restrictive licensing as much as possible while pretending that they follow http://freedomdefined.org/Definition in front of public. It is only my doubt while seeing those opposes from the well known admins who are supposed to be very well versed in Wikimedia policies. JKadavoor Jee 06:35, 11 March 2013 (UTC)
    • The WMF is silent on this sort of thing for the most part. --Guerillero | My Talk 17:34, 11 March 2013 (UTC)
      • Probably; so I did some searches which lead me to http://meta.wikimedia.org/wiki/Licensing_update/Questions_and_Answers#Images : "If the migration occurs, will it change what image licenses are allowed to be used on WMF projects? Not immediately. It is possible that, at some future point, GFDL 1.2 media may be disallowed. However, this will only happen if CC-BY-SA is modified to make it more explicitly a "strong copyleft" license for embedded media, requiring the surrounding content to be licensed under CC-BY-SA. Currently both licenses are somewhat ambiguous in this regard." This means we are in a testing time where WMF is acquiring confidence in CC-BY-SA. I assume WMF already achieved it from its decision to replace CC-BY-SA+GFDL with CC-BY-SA as the preferred choice of license. So we can either decide to discourage further GFDL craps or tolerate them for the time being till WMF kick them out. JKadavoor Jee 06:36, 12 March 2013 (UTC)
        • There is no significant demand for an image licence that is "strong copyleft" -- that infects the containing media. Some people might wish to impose their free ideals on others but the reality is that it is impossible. GNU software is strong copyleft at the level of linking source code (or libraries) into an executable -- which is the equivalent of creating a derivative work. But it is not strong copyleft at the level of a collection of discrete components. Thus one can sell a computer or O/S or DVD that contains GNU software applications alongside commercial software applications that aren't free (in the GNU sense). Thus a book containing a CC BY-SA image doesn't need to be CC and such a licence, I predict, will never happen. I certainly wouldn't use it. Colin°Talk 08:23, 12 March 2013 (UTC)
  • Comment There's a lot of wilful doublethink going on by people caiming nonsense like "a libre license is a libre license". This mantra-garbage is busted by our comrades who use the GFDL for their images. At least they are honest and straight-talking enough to admit they (all two of them) use it to restrict who can reuse their work. So enough of this crap about GFDL being a free content licence for images. It isn't used as such and it doesn't have that effect. Colin°Talk 10:05, 11 March 2013 (UTC)
    • I'm sure that a 1984 Reference wins you the votes --Guerillero | My Talk 17:34, 11 March 2013 (UTC)
      • My own personal Godwin's Law (note the correct spelling) is that once people start commenting on argument technique rather than the issue at hand, they are wasting my time. For the benefit of non-timewasters, doublethink is quite an appropriate English word for how folk can simultaneously claim GFDL is a free licence and yet specifically choose it because it is not a free licence and allows them to restrict the reuse of their images. -- Colin°Talk 19:01, 11 March 2013 (UTC)
  • Super strongest possible oppose To balance out the other nonsense :P I think this proposal is an incredibly presumptuous crusade by Colin which wholly lacks any kind of legitimacy. The FPC talkpage is simply not the forum - you cannot have FPC policies which are inconsistent with the policies of the English Wikipedia project. Leaving aside any discussion of the merits of the GFDL, this is a decision and discussion which belongs elsewhere at a far more generalised level. If I really strain, I can almost see the validity of commons FPC having banned the GFDL licence, since they are after all catering to all sorts of projects, but for FPC it's just wrong. EN:FPC is purely dedicated to the English Wikipedia - a project which fully supports GFDL (as well as fair use - which, incidentally, in principle should be eligible for FPC but in practice will never have sufficient resolution to pass) - and so should be governed by the licensing polices of this, specific, project. I think this fundamental flaw in the proposal is illustrated by the more recent themes in Colin's arguments which focus on slagging Muhammad and Jjron as the "only" two users of GFDL - not only is this very rude and myopic, it is a completely inappropriate perspective. This policy is not dictating what those two users can or cannot nominate, it is dictating to all English Wikipedia users - it is of consequence to numerous current users as well as incalculable future users and therefore it must be considered at a global level. --Fir0002 03:04, 12 March 2013 (UTC)
  • You cannot have FPC policies which are inconsistent with the policies of the WMF: "All contributions are licensed under the Creative Commons Attribution-Share Alike 3.0 (except Wikinews, which is licensed under Creative Commons Attribution 2.5), meaning that their content may be freely used, freely edited, freely copied and freely redistributed subject to the restrictions of that license.". JKadavoor Jee 06:10, 12 March 2013 (UTC)
  • I already mentioned it below ("The main problem is that Wikipedia not updated the “texts” in several pages according to the resent changes in their policies."). Please read the entire discussion instead of making a quick comment and run. JKadavoor Jee 10:47, 12 March 2013 (UTC)
  • Once again the mistake is made that FPC criteria must somehow be enshrined at the level of deletion policy -- we don't delete out-of-focus images and we don't delete images for having excess noise. That argument is busted and was busted at the Commons debate - which rather surprised I think those who kept repeating it. Nobody at the image-size discussion said "If 200x300px is good enough for upload to Wikipedia, and makes a fine thumbnail illustration in an article, then it is good enough for FP". We are not debating "FPC policy" -- calling it policy is simply misleading. It is a set of criteria about what makes an excellent image on a free content encyclopaedia -- if it isn't really free content then how can it be excellent? I don't know why you think an PF criteria discussion affects "all English Wikipedia users". Most of Wikipedia is illustrated with images that fall far below the bar at FP and they illustrate just fine. What nonsense. Anyway, I should point out I didn't start this proposal and didn't want it to start here as I knew it would cause more heat than light. Those who use the GFDL licence do so to restrict reuse, and that is why ultimately it will be banned for upload to this free content project. It would be nice if FPC was ahead of the game. As for "the project fully supports GFDL" -- well no, it regards GFDL unsuitable for the project and only really kept for legacy reasons. .. Colin°Talk 08:42, 12 March 2013 (UTC)
  • "That argument was busted on Commons" is not itself an argument. Please explain your rationale. If your rationale is analogising it to resolution then it is deeply misguided. The licence of an image, unlike its resolution or other technical characteristics, is not intrinsically part of the image. The question of the acceptability of the licence is determined by the philosophy, policies and practices of the project it is being used in and is very different from the attributes you describe. The appropriate analogy here would be FPC autonomously deciding that it would ban/censor pornographic and other offensive material. And you know this very well as your last few sentences make clear. Please pursue your agenda of banning GFDL content in the appropriate arena, not here. FPC is not here to "get ahead of the game" and be used as leverage for a project wide ban of GFDL - it is here to identify the best images from the project. --Fir0002 09:27, 12 March 2013 (UTC)
  • Criterion 4 of WP:WIAFP is "Has a free license." So the licence is part of the criteria and not ignored wrt FP. Criterion 3 of WP:WIAFP is "Is among Wikipedia's best work." This is something for the FP community to define for itself and nothing to do with WP policy. The definition of Wikipedia is "a multilingual, web-based, free-content encyclopedia project operated by the Wikimedia Foundation..." The free content aspect is the sticking point for many who argue that Wikipedia should be (or think it is) a "free to read Encyclopaedia" or that the content be "for educational use only". There's some merit in that argument. But ultimately, Wikipedia has decided its content is free as in The Definition of Free Cultural Works. This requires all content "can be freely studied, applied, copied and/or modified, by anyone, for any purpose". The "by anyone" rules out Jjron's argument that he doesn't want certain people using his images and the "for any purpose" rules out the non-commercial/educational restrictions others want. There are only a few permissible restrictions allowed, such as attribution and copyleft. These are the terms we agree to when we submit work here. The GFDL was a pragmatic choice at the time WP was created as there was no alternative licence. But WMF were deeply unhappy with (read the links above) and CC was largely created to better serve WP/Commons and other similar groups. It may be that the community decide GFDL is still a pragmatic choice (and so don't ban it) but that doesn't mean they think it is a good choice for images. The fact that all those using it do so in order to restrict reuse, is utterly counter to the fundamentals of the project. Therefore I believe the FP community should not regard images so licensed as examples of "our best work". We can do this (if we wish) and do not need to change policy to do so. So a better line of argument would be to persuade us why the GFDL is a great licence for images and why images with that licence are among our best work. I don't believe it can be done, hence the deflection. As for the porno argument, well if the FP community wanted only "safe for work/children" images that would imo for it to decide -- but I doubt the argument would get much support because WP:NOTCENSORED is regarded as a fundamental. There's nothing stopping someone creating a "Featured buildings" or "Featured butterflies" or any other arbitrary criteria they wish, provided they get enough support for it to work. The idea that our criteria has to be as wide as our deletion policy is just false. Colin°Talk 09:59, 12 March 2013 (UTC)
  • I am a bit confused. At one instance we are told this proposal is a broad policy change and now you claim it is just a modification of the FPC criteria. If it is a policy change, this is not the right place to have it. If it is a discussion on the criteria, I think the majority of the participants have shown their disdain for the change. --Muhammad(talk) 11:27, 12 March 2013 (UTC)
I can't explain Raeky's use of the word "policy" in that comment and agree it is confusing -- this is just a criteria change. Both the WP:CENT advert and the proposal itself make it quite clear the proposal is only on the FP criteria. There's a slight majority opposed to the change currently. We'll see. Once again, the arguments on the oppose side are weak and just expose the discord between what the site is founded on and what a few individuals wish it were. Colin°Talk 11:53, 12 March 2013 (UTC)
  • If this proposal is meant to change FPC criteria then it need not be advertised at WP:CENT. Maybe it's just me but when have we expected non-participants to assist in changing the criteria? And, since this is just a change to FPC criteria, I will reiterate, all such changes require a 2/3 majority. --Muhammad(talk) 12:21, 12 March 2013 (UTC)
  • Comment: Criterion 3 of WP:WIAFP is "Is among Wikipedia's best work." --> YES: this is PD or CC-0 ... and now goodbye Wikipedia ... For me a stupid and absolute nonsense argument. We are voting here for valued images for our encyclopedia, not for licenses. "Storm in a Teacup???" --Alchemist-hp (talk) 18:51, 12 March 2013 (UTC)
    Comment -- It is not our encyclopaedia. It is everybody's encyclopaedia, in the sense that its (whole) content is supposed to be free. -- Alvesgaspar (talk) 19:15, 12 March 2013 (UTC)
    Question and why not PD or CC-0 ??? It is much more free then CC-BY-xx. --Alchemist-hp (talk) 22:34, 12 March 2013 (UTC)
    Because CC BY-xx meets the Definition of free cultural works for images, which is the definition of free content Wikipedia is built on. And so does the Free Art Licence. The very people, and the only people, who use the GFDL as their sole licence are the ones explaining why they don't want their images to be reused commercially for free or to control who gets to reuse them, which is not a permitted restriction. So anyone claiming the GFDL is a "libre" licence for images is, frankly, talking out of their arse. Colin°Talk 23:19, 12 March 2013 (UTC)
    This is another diversion. PD and CC-0 are not necessarily much more free. PD has (as far as I know) no SA clause (and thus no means of keeping the works free). And neither license helps promoting the idea of free culture. But in the end this is not an argument for GFDL at all. --Dschwen 16:39, 13 March 2013 (UTC)
    Further it is clear that most of the people oppose this proposal are who dislike Wikipedia policy on use of non-commercial licensed images. Diliff and Saffron Blaze already expressed that they respect it as the policy of Wikimedia even though they dislike the fact that Wikipedia is a 'free content' project and it places higher importance on licensing and the use of its contents outside of Wikipedia than it does on encyclopaedic value within the scope of Wikipedia. But all others are trying to close their eyes and ears in front of this reality and repeats “any libre license is a libre license”. It reminds me the story of The Naked King. Please show your child-like wisdom that Diliff and Saffron Blaze already have. JKadavoor Jee 05:20, 13 March 2013 (UTC)
  • Strong Support Licencing isn't just about Wikipedia, it's about our re-users. Encouraging more userfriendly licences amongst our best images will help to spread free licenced content. Regards, Peter Weis (talk) 15:14, 13 March 2013 (UTC)
  • Support per Colin. Feature pictures -- indeed, all images -- should have an appropriate free license. GFDL is a free license, but not one intended for licensing images, and not appropriate for images. An inappropriate license is no better than a non-free license, and should not be acceptable. cmadler (talk) 02:03, 15 March 2013 (UTC)
  • Oppose. Our project strongly supports the use of a license that's not much use for commercial purposes, which like all other viral licenses is "like a cancer that attaches itself in an intellectual property sense to everything it touches" — you can't use CC-by-sa images or text without lots of care unless you want to risk losing virtually all rights over your work. That's a far bigger impediment than simply requiring the printing of the license text. Since we actively promote a license that erodes rights if used incautiously, we shouldn't denigrate images simply because they have a comparably smaller practical problem in addition. Finally, note that my own works are PD-self, and I'm not capable of taking FP-quality pictures; this nomination is my only recent involvement with FPC. Nyttend (talk) 04:41, 16 March 2013 (UTC)
    • These licenses are used for the expressed explicit intent to prevent commercial use of the images licensed under it. This is clearly, unambiguously against the expressed goals of the foundation, and their representatives. This license is a holdover from before better licenses was available that the foundation decided to adopt site-wide. It's not an option to choose when uploading images here anymore. It exists because there's content here licensed under it, and the project hasn't decided what to do with it yet. Your statement is strongly against the fundamental foundations of this project, being a 100% free and open encyclopedia, that includes commercial use and reproduction. — raekyt 04:49, 16 March 2013 (UTC)
      • And why must I embrace a philosophy that undermines commercial use while praising itself as the more moral choice? Our current license is no better than the one that this proposal opposes — indeed, perhaps worse, since it presents fewer difficulties for unsuspecting reusers. I participate on Wikipedia because I want to publish information that I find in reliable sources, not because I want to help undermine intellectual property rights. Nyttend (talk) 05:02, 16 March 2013 (UTC)
        • Then why should we give gold stars to content that isn't playing by the same rules that you play by by contributing textual content? (You don't have a choice to contribute your article's text under GFDL-1.2-Only or GFDL Only, you have to also release it under CC-BY-SA-3.0, note the text right above that Save Page button.) The foundation has their policy for commercial use and not allowing non-commercial licenses, so if a user is willfully trying to bypass that, why recognize it with a ribbon? — raekyt 05:15, 16 March 2013 (UTC)
    • "Our project strongly supports the use of a license that's not much use for commercial purposes…" No. Our project strongly supports the use of a license that's not much useful for non-educational purposes. But commercial doesn’t mean non-educational; non-commercial doesn’t mean educational. Please read the quote from Erik Möller below: "It's been Wikimedia's long-standing position that allowing commercial re-use contributes to its educational mission (the negative impact of stupid commercial uses is outweighed by the positive impact of educational, commercial uses), and that position is unlikely to change." JKadavoor Jee 06:19, 16 March 2013 (UTC)
    • Copyleft is not a particularly well-understood concept. There are in fact two types of copyleft: strong and weak. In the context of free software, they would be the GPL and LGPL. Namely, they are identical except for the aspect that the LGPL allows proprietary software to link to it, while GPL does not; both licenses prohibit distribution of modified copies of the free software under a proprietary license. In the context of images and content, the ShareAlike provision is a weak copyleft. It requires only that modified versions (known as Adaptations) of the image need to be released under the same license, while including the image in a larger work (known as a Collection) is fine, even if the collection is not released under the same license. "You can't use CC-by-sa images or text without lots of care unless you want to risk losing virtually all rights over your work" is patently false for two reasons. One, what I just mentioned, using it in a collection is fine. And two, let's say you include a proprietary photo in your book without the permission of the photographer. Does that mean the photographer now owns the copyright to your book? Of course not! He's entitled to damages, but the copyright of the book remains with you. CC-BY-SA is an additional freedom, so if someone violates its terms while including it in a larger work, it doesn't cause the whole work to be CC-BY-SA. Also, the "cancer" thing promulgated by Ballmer — let's just assume what he's saying is valid, OK? But he is referring to free software, not free culture. And what's the difference? You might be writing proprietary software around free software, and when you get caught in the act, you'd have to either release your software under a free license or stop distributing it. Free content is different. If you include it in a book and fail to provide attribution, then you can just put in the attribution, or at worst remove the image. In software, you can't just remove or change a component arbitrarily. -- King of 07:20, 16 March 2013 (UTC)
      • Why not, free content for new "whole" free content. Plese read the FAL license! :-) --89.246.51.223 (talk) 07:27, 16 March 2013 (UTC)
      • I think this illustrates what KoH said above. More interesting is the contributor’s response about it: "I feel sorry for the kids getting half baked education from these texts. It neither creates any interest in the subject nor promotes inquiry and discussion. It was for this reason that I hated school." :) JKadavoor Jee 11:05, 16 March 2013 (UTC)
        • Nyttend, I do rather think you've got the wrong end of the stick here. As explained, the CC licence doesn't infect the work that contains it -- there are no image licences (GFDL, CC, FAL, etc) that do this because they would be useless. The whole point of a free licence is the freedom use it. There are absolutely no situations where the GFDL is preferable to CC/FAL/etc for the end-user. Indeed, it is rather doubtful IMO, that the GFDL constitutes an image licence at all, leaving anyone trying to use such a licensed image at risk of copyright violation. I strongly suggest you do some reading and strike your comments. Colin°Talk 20:14, 16 March 2013 (UTC)
  • Strong support. Per Peter Weis. I'm a proponent of increasing the freedom of use of content placed on Wikimedia. Of course, if excessively stinging forced right-waiving licenses were to be enforced, I can imagine that some would be more reluctant to contribute. If this didn't completely cripple the content donations to Wikimedia, I'd like to see CC0 be enforced.
As Featured content is the figure head and pride of Wikimedia, I am convinced that this content should be in close accordance with the founding principles of high freedom of use. If this means that we have to put aside quite a few very excellent images (such as Mohammed's) from being promoted to Featured pictures, so be it. Greater freedom is the greatest of my priorities. Nicolas Perrault III (talk) 15:19, 16 March 2013 (UTC)
  • Oppose – I'm no photo license expert and have not contributed to FPC, but it seems to me that this change would leave GFDL-1.2 images treated in two different ways, depending on when they were nominated. If the license is deemed to no longer meet FP standards, how can keeping older photos using it as FPs be justified when they don't meet the criteria? Either the license is good enough for FP or it isn't; this proposal tries to have it both ways, and I can understand why current nominators are upset that their work will be treated differently than past images. This reminds me of a situation that the FA process faced long before I joined the site, when inline citations were introduced as a mandatory requirement; the older articles were improved or delisted and more were kept FAs than you would have thought possible. Maybe if the criteria were applied consistently, some of the current FPs could be relicensed in a way that everyone would support? Regardless, I can't support any proposal that leads to differing criteria depending on age. If a painful change is needed, do it all now and get it over with instead of leaving an issue that will be brought up in the future and cause even more division. Giants2008 (Talk) 01:41, 18 March 2013 (UTC)
    • We already have a situation, images are treated in two different ways, depending on when they were nominated. The FPC criteria are constantlky evolving and many images that passed a few years ago would not pass today. The size requirements were raised a while ago whothout performing a mass delist of images that are too small. These non-arguments are starting to get very frustrating. --Dschwen 02:15, 18 March 2013 (UTC)
      • How convenient! Any argument contrary to you standing point is a non argument. FWIW then, I strongly reject the support non-arguments. Hey, this is actually fun :) --Muhammad(talk) 03:11, 18 March 2013 (UTC)
        • Any argument contrary to you standing point is a non argument... No. Any argument that is easily refuted, makes wrong assumptions, or is just a misleading diversion that has nothing to do with the point at hand is a non argument. The opposers have delivered many of those. But by all means Muhammad, make your life easy by sticking your head in the sand. --Dschwen 03:39, 18 March 2013 (UTC)
    • I'd say this is the least disruptive way to propose a change in criteria, and historically how we've done it. It becomes a logistic problem sorting through the 3,312 current featured pictures to find ones that don't meet current standards. As time goes on, we do demote pictures that was promoted long long ago when standards was VERY lax.. And probably as time goes on as we require higher and higher resolutions that those that are now may be demoted as well. In a decade we could have a FP minimum size of a gigapixel or something, hard to say, and the existing 2 megapixel images we have now would be clearly targets for delisting. In a few years Commons may delete/purge all GFDL images, and then those that are FP here would also be deleted. We can't predict the future, right now leaving whats done isn't a problem. Stopping it from continuing to happen is what we're discussing. It's photographers, who do not like the core principles of free access that this project was started on, and want fancy ribbons of recognition (and their product they're selling) shown on wikipedia's front page, that we're discussing stopping. We don't let businesses put ads on wikipedia's front page, but effectively if you've limited commercial use of your image (which is against our policies) and we promote it as a FP then it will show up on the front page. And these photographers are very brazen in their image description pages to even link to their websites and e-mails and state, for commercial licenses contact them for pricing... It's an advertisement. It's against core principals, it's a clear unambiguous work-around to the no non-commercial clauses in our licencing, and taking advantage of an antiquated, depreciated and inappropriate license that was designed for software, to apply to an image. — raekyt 03:35, 18 March 2013 (UTC)
      • And again you simply build a non-existent strawman argument to attack image contributors and prove your non-point. This nonsense has already been debunked, but like all purveyors of piffle you simply continue to repeat it until it becomes 'true'. Your problem is that your original argument that you veiled as an attempt to ban GFDL licensing held some sway with casual observors, but as time has gone on you've simply outed yourselves as actually wanting to ban certain contributors (yes, we've been named time and again). It's strange that you want to curtail the efforts of people actually contributing useful content to Wikipedia, etc. You must feel so good about the handful of images you've freely contributed to the project (and so humble of you to create your very own category on Commons to host them all!). But wait, they're licensed under the GFDL too [6], [7]! Oh dear. Egg on your face there? Now awaiting the inevitable doubletalk justifications for this. --jjron (talk) 13:38, 18 March 2013 (UTC)
          • Haven't seen it "debunked" show me where (a) the foundation accepts non-commercial licenses, and (b) that the users who use GFDL-1.2-ONLY do not want to restrict commercial use? I never said I was a great photographer, or a big contributor, and those images was uploaded with the default licencing on Commons, and no-one said there was a problem with using GFDL AND CC combined. — raekyt 17:41, 18 March 2013 (UTC)
        • Don't make this personal, this is very unhealthy for the discussion climate. --Dschwen 15:16, 18 March 2013 (UTC) P.S.: Guess what, my first uploads were licensed under the GFDL as well. But I added another more suitable license as well (just like Raeky). Attacking him for the volume of his uploads is an absolute low. Want to try to say that to my face too? Shame on you. --Dschwen 15:19, 18 March 2013 (UTC)
        • Jjron, before making smart-alec comments at Raeky, perhaps you'd carefully read the licence terms for both pictures. They are dual-licensed with the friendly comment "You may select the license of your choice." and always have been. If folk, losing their chance of a bronze star, don't wish to contribute to a free content project with an appropriate licence for the content they are uploading, then that is their choice. Just as it is their choice if folk only accept -NC licences for their work or want full copyright control for their work. All these choices are perfectly valid and reasonable. But they are the choice of the (potential) content supplier alone. To pretend that those who support this change are the ones making the restriction is clever but twisted logic and an example of deflection tactics rather than being straight and honest. And I agree that your personal attack of Raeky's contributions is a real low. Shame on you. Colin°Talk 16:10, 18 March 2013 (UTC)
        • John; is it you complained against personal attack in the beginning of this discussion? Why not you complained when Wikimedia added a CC-BY-SA license in some of your works as part of its policy update? JKadavoor Jee 17:12, 18 March 2013 (UTC)
  • Comment Note point 2 under meta:Licensing update. Then how it is possible to upload GFDL only contents here? I think the permission for "GFDL 1.2 only" contents is only for existing media contents. JKadavoor Jee 06:04, 19 March 2013 (UTC)
  • Comment Even the author of the license doesn't recommend GFDL for this type of works. See http://www.gnu.org/licenses/licenses.html (Licenses for Other Types of Works): "We don't take the position that artistic or entertainment works must be free, but if you want to make one free, we recommend the Free Art License." I wonder how a license that not recommended by the author of that license itself is suitable for "our best works". JKadavoor Jee 05:48, 21 March 2013 (UTC)

Motion to close discussion as "no consensus"

It is clear this proposal divides the FP community and there is no progress towards consensus. Those who use this licence are naturally upset at the potential loss of little brown stars. Some fear contributors may leave. That FP does not celebrate truly free content and rewards those who impose restrictions on reuse, is disappointing but not surprising. For many, this project's content priority is that it is "free to read/look", not that it is "free to use". This proposal should be closed now as "no consensus to change", as keeping it open further does not seem to be helpful and is unlikely to change anyone's set mind. -- Colin°Talk 16:24, 18 March 2013 (UTC)

  • Seems to be the case. I have my own conflicting opinions on the subject, but don't care enough about it to have contributed to the heat. :-) I agree though that the only real conclusion to be reached is no consensus. Too many strong opinions and very little middle ground. Ðiliff «» (Talk) 17:29, 18 March 2013 (UTC)
  • Would prefer an external admin to close it and render an opinion, since I believe many of the opposes are based on faulty assumptions. It's not a !vote. — raekyt 17:35, 18 March 2013 (UTC)
  • Support closure as no consensus. As I have mentioned before, changes in FPC criteria are based on vote count and we have never needed an external admin to close such discussions. The opinion of one admin is NOT greater than the sum of the participants' opinions. --Muhammad(talk) 17:52, 18 March 2013 (UTC)
  • Agreed, with everyone refusing to budge. -- King of 21:18, 18 March 2013 (UTC)
  • Agree too. We can close this discussion. --Alchemist-hp (talk) 21:36, 18 March 2013 (UTC)

Request at WP:AN/RFC made.

I requested an uninvolved admin to review and close, the debate has become too heated on both sides for us to make an objective close ourselves. — raekyt 06:37, 19 March 2013 (UTC)

A mistake I'm afraid. The discussion here by both the supporters and opposers have deemed a no-consensus closure. I really don't get who gives you the authority to request such a closure. I have thus removed the request. --Muhammad(talk) 06:50, 19 March 2013 (UTC)
My change has been undone. I strongly protest the unilateral decision being taken here when the results are quite clear --Muhammad(talk) 07:24, 19 March 2013 (UTC)
Only uninvolved people are closing our FPC too. Then what is wrong with requesting an uninvolved admin? JKadavoor Jee 07:34, 19 March 2013 (UTC)
Our FPC are being closed on a vote basis. I have no objection with such a closure. What I anticipate with the closure that Raeky is insistent on, is one which throws away the majority oppose or promotes this without a 2/3 consensus. Raeky has insisted that a closure should not be based on votes and despite the opposition and the fact that the proponents of this proposal have agreed a no-consensus, Raeky continues to try to stamp this view --Muhammad(talk) 07:52, 19 March 2013 (UTC)
Although it's painfully obvious by your licencing choices that you do not wish to follow the same rules as everyone else here at Wikipedia, but what part of Consensus is not a vote process. Wikipedia is not a Democracy. Do you not understand? This is clearly outlined in WP:NOT, and anyone who actually contributes here with content knows this. We've long ago adopted a !vote process for FPC nominations to simplify things, but that does not mean that we decide everything here at FPC via !vote, show me where that was decided? You're looking for the best outcome to side in your favor, and that's a vote count. But when you weigh the actual merit of all the Oppose votes, the story is very different. I started this proposal, so I do have a little bit of a right to request an outside party to close it. It's not controversial for outside parties to close disputes, it's very VERY common. My request was completely neutral. I'm not the only person who thinks we need an outside close. SO give it a rest. — raekyt 08:04, 19 March 2013 (UTC)
FPC Criteria have always been modified on a vote basis. It's stupid to have stricter rules for images to be featured than to have for the criteria that judge those images. As it stands, the oppose numerically outweigh this proposal and it's quite clear that you are fishing for a positive outcome for your proposal, hoping for an admin who sides with your thinking. At the moment, you are the only one that wants an outside closer. SO give it a rest --Muhammad(talk) 08:29, 19 March 2013 (UTC)
You selectively ignoring the two posts above yours in the section above this one? — raekyt 08:32, 19 March 2013 (UTC)
Muhammad, you're making a fool of yourself. I do this often so recognise the signs. I would be extremely surprised that any admin would close it differently to "no consensus" and rather hoped Raeky would see that too and concede. But it is his right to request an impartial outsider to review the discussion as we are often very poor judges of debates we are party to. Previous FP criteria discussions may have included a straw poll and folk, like here, may have used the bold support/oppose text to make their position simple, but ultimately opinions and views need to be weighed, not just added up. A small number of people have given their opinion on this discussion without !voting, as is quite reasonable. This is always the case on Wikipedia. Even FP candidates are judged by consensus, though in practice we accept the opinions are rather subjective and the result is usually determined arithmetically. An FP result could be made differently if canvassing or clearly invalid opinions were given. Why don't you wait to see what the admin says, rather than fretting unnecessarily. Colin°Talk 08:52, 19 March 2013 (UTC)

Examples

  • Some examples - not exclusive (with ** as a wildcard)
    • "GFDL 1.2 Only" Not acceptable as the only licence is GFDL which is impractical for images.
    • "GFDL 1.3" Same problem as above.
    • "GFDL" + "CC **-NC" Not acceptable as the additional licence isn't "free" - it prevents commercial re-use.
    • "GFDL" + "CC **-ND" Not acceptable as the additional licence isn't "free" - it prevents the creation of derivative works.
    • "GFDL" + "CC BY-SA" Acceptable, and this is the dual licence Wikipedia uses for text.
    • "GFDL" + "Free Art Licence" (aka Licence Art Libre) Acceptable. The FAL is very similar to "CC BY-SA".
    • "GFDL" + "Free Art Licence" + "CC BY-NC-ND" Acceptable as at least one licence option is free for images. Adding other non-free licences does is not a problem.
    • "CC BY-SA" Acceptable.
    • "Free Art Licence" Acceptable.
    • "CC0" Acceptable.
    • "Public Domain" Acceptable.
Colin°Talk 08:44, 7 March 2013 (UTC)
The "unacceptable" ones would be obvious, since the NC/ND clauses are not allowed on a license alone, and if we rule out GFDL then if there isn't another acceptable license it wouldn't be allowed. Wording can be "Any GFDL licensed image that doesn't also have another valid license is prohibited from being promoted as a Featured Picture." or something similar... — raekyt 13:26, 7 March 2013 (UTC)
Seems better. JKadavoor Jee 14:21, 7 March 2013 (UTC)

Important before Closure

The commons discussion was closed without a 2/3 majority. For the FPC process here and all major decisions, a 2/3 majority is required before any major policy changes are made. --Muhammad(talk) 18:26, 7 March 2013 (UTC)

FPC nominations use pure !vote counting, changes to criteria uses WP:CONSENSUS where arguments prevail over majority. — raekyt 20:13, 7 March 2013 (UTC)
At FPC we have always favoured a majority and I strongly emphasize that any changes made without the 2/3 majority will be considered null. It's stupid to have stricter rules and requirements for images to be featured, than to alter the rules themselves. --Muhammad(talk) 20:35, 7 March 2013 (UTC)
The rules governing how pictures are featured are quite independent of the rules governing how Wikipedian's determine consensus. We do not vote on Wikipedia so those expecting some admin to tally up the supports and opposes will be greatly disappointed. Convince us with the strength of your argument. That's all that matters. Colin°Talk 21:33, 7 March 2013 (UTC)
"Debates rarely conclude on the basis of merit; typically they are ended by outside intervention, sheer exhaustion, or the evident numerical dominance of one group." From WP:Consensus. Saffron Blaze (talk) 22:05, 7 March 2013 (UTC)
That's why with things like this it's generally a good idea to request a close at WP:AN/RFC after a fair amount of time has passed for debate on it. Where the closing admin will weigh the merits of everyone's arguments and decide the consensus based on policy. Just a "I don't like it" !vote will have little merit to the consensus. — raekyt 22:09, 7 March 2013 (UTC)
We've had many policy changes done here which required a majority. If a 2/3 majority does not support this I'd not consider the proposal passed. It is a waste of all our times if we discuss something like this for a long time only for one person (the closer) to do what they think is best. We had a similar process to closing FPC noms and quite a large number of the participants were not satisfied with this method of working. --Muhammad(talk) 03:33, 8 March 2013 (UTC)
I'm sorry you don't see the need for WP:CONSENSUS and outside uninvolved party closing disputes... — raekyt 03:47, 8 March 2013 (UTC)
Decision-making involves an effort to incorporate all editors' legitimate concerns, while respecting Wikipedia's norms. It is good to respect the opinion of majority as far as their opinion respect Wikipedia's norms. Otherwise? I had read the opinion of one of our most active contributor in a discussion: “I prefer if Wikimedia allow CC-BY-NC-ND; it will attract more quality contributions.” Can we make such a policy change even if with a 100% support? It is a matter whether our current policy respects our norms. No; so we have to correct it according to our norms. That’s why this proposal. Here argument on what is our correct policy is important than mere majority. JKadavoor Jee 08:34, 8 March 2013 (UTC)
  • FP should not be a walled garden and should follow wikipedia's norms for a large policy discussion. That means that people outside of the "group" should be encouraged to contribute, the discussion should be closed by an outside sysop, and there needs to be a super-majority in support. --Guerillero | My Talk 02:03, 11 March 2013 (UTC)
    • The wording "super majority in support" has nothing to do with WP:CONSENSUS, and specifically when it comes to policy decisions. It's arguments that matter, you can have a 10% support rate for a policy decision, and if it's well reasoned, and the opposers are not based on policy, it can pass. This isn't a !vote process, but a policy decision. The number of people who oppose is irrelevant if they're not backed up by a good reason why. It's obvious that a GFDL 1.2-ONLY license that specifically states that you must print the full license text when you use it with it, and links to where you can BUY rights to use the image, is against policy. GFDL 1.3 and later, also have the same problems. — raekyt 08:38, 11 March 2013 (UTC)
    • That decision was made by 17462 Wikimedia volunteers with a 75.8% support. Please read the last lines at http://wikimediafoundation.org/wiki/Press_releases/Dual_license_vote_May_2009QA : "Does this license change affect both text and images, or only text? It will affect both text and images, except for images which are licensed under "GFDL 1.2 only". Those will not be dual-licensed." The only reason for keeping GFDL 1.2 is because our existing contributions with a GFDL 1.2 can’t be dual licensed. But it should not be a loop hole for uploading new contributions. JKadavoor Jee 09:10, 11 March 2013 (UTC)
    • "FP should not be a walled garden and should follow wikipedia's norms" Rubbish. That sort of thinking was blown out the water when we had the Commons discussion. Of course FP can have higher standards than the norm on Wikipedia. That's what distinguishes FP. We can set standards for sharpness, composition, size and freeness of licence. FP can set whatever standards we like. Colin°Talk 09:55, 11 March 2013 (UTC)

Note

I have added this discussion to WP:CENT. -- King of 09:40, 8 March 2013 (UTC)

Kindly remove it. IMO this is canvassing --Muhammad(talk) 12:34, 8 March 2013 (UTC)
It has nothing to do with canvasing, it's a broad policy change. Read WP:CANVAS. — raekyt 12:41, 8 March 2013 (UTC)
Muhammad, this is standard for an important decision. If he'd posted at Wikipedia:WikiProject CreativeCommonsRocks or Wikipedia:WikiProject DeathToGFDL then perhaps it would be canvassing. Colin°Talk 13:06, 8 March 2013 (UTC)
Yeah, Muhammad's right. This is not "proposed changes to Wikipedia policy". If it was a dispute over whether images with a particular license should be uploaded then it may have a place there as it would be a policy change. This is not. --jjron (talk) 14:18, 8 March 2013 (UTC)
  • No canvassing at all. The annoucement was a broad one and everybody is free to partcipate in any discussion. In the present case, and although we are not discussing a change of policy, this discussion may trigger the debate on the apparent incompatibility between the ways of Commons and Wikipedia (which seems very necessary now). -- Alvesgaspar (talk) 14:58, 8 March 2013 (UTC)
Yes; I too think the opinions of article editors and other non-photographers are more important than our regulars. JKadavoor Jee 15:48, 8 March 2013 (UTC)
This is a very interesting point of view. Why would this be the case? Is it that you think the opinions of regulars here are unimportant? Is it that you think outsiders may be more likely to support your position? It's really a strange thing to say. It's not that outsiders may not be able to provide valuable input, but why is that more important than anyone else's? You see, despite the continual maligning of me throughout this debate – and unlike some others contributing to this discussion that seem to regard Wikipedia more as a social media platform than online encyclopaedia – I have extensive article contributions, many, many thousands entirely unrelated to my images. So in fact I am an article editor. So I'll tell you what I do with image use in articles. If I don't have something worthwhile to add of my own I may go and seek out something. If I find it on Wikipedia or Commons that is good. I check that it's not a 'non-free' image, and if not I insert it. I don't give a hoot whether the free license is GFDL or anything else - you see, anything but those non-free images can be freely used anywhere on the project. As an article editor that's all I care about. Why would I possibly care less whether it's GFDL or anything else? Someone has uploaded it to allow me to freely reuse it. Pure and simple. This is not an issue for article editors. And if you're wondering about the stunning lack of response from non-regulars despite advertising by King and Colin, well there's your answer. --jjron (talk) 13:23, 13 March 2013 (UTC)
Glad to know you have extensive article contributions. It will be always nice if more article editors participate in the reviewing process. But unfortunately not many article editors showing any interests here (in WP:FPC). I don’t know the exact reasons; but I assume WP:FP is not an important resource for them (unlike COM:FP, QI and VI). While editing an article they look for images at COM:Categories and galleries; not here because the images here are already used ones. They look here only when to make a complaint. The lack of response here is also another symbol of their lack of interests here. The WP:FP gallery may be useful for other language editors (while translating the article here to their local wiki) and readers (who need good pictures for their research or any other purposes). I agree with you that the editors never look on the license; because they assume everything available here is free. People in Commons understand it; so they refrained from promoting GFDL works. What about thinking for separate FPCs for individual projects or raising a RfC on their talk pages for every nomination here? I hope that will improve the quality of reviews. JKadavoor Jee 17:30, 14 March 2013 (UTC)

On importance

Just to put things into perspective. Check out Commons Category:Images from norden.org uploaded by Fæ. This recent mass upload is still ongoing but as of now has transferred 3,682 professional images to Commons under a CC BY licence from "Nordic Cooperation". Try this search for Nature on the original site. That's just one example of organisations releasing their work under truly free licences, not to mention Flickr and other image repositories. As a source of high quality images for illustrating Wikipedia articles, the efforts of the folk that hang about FPC don't appear on the radar. It is a great forum and does indeed attract folk to contribute high quality content. But let's not kid ourselves about how important any of us are. Colin°Talk 10:32, 8 March 2013 (UTC)

I don't necessarily disagree with your conclusion regarding importance, but the supporting argument is weak. At least 80% of those Nordic Corp photos are six to seven year old portraits of barely notable people. Very few of the nature gems have made their way over. I hope that is not deliberate. Saffron Blaze (talk) 13:07, 8 March 2013 (UTC)
Still uploading as we talk. I've no doubt that Fæ intends to upload everything suitably licensed - which appears to be everything. It is easier to search the source site for content than to browse the huge category. -- Colin°Talk 14:16, 8 March 2013 (UTC)

Great, but until they're usefully used in Wikipedia articles they're of little or no use here. How many typical users of Wikipedia are going to trawl that huge category on a different site to find a suitable image? Approaching zero! That's the point about Wikipedia as a site used by millions daily, and enwiki:FPC. FPs here are recognised as high quality images that are being usefully employed in articles on Wikipedia easily available to all those millions of users. Please check the top of the page. This is Wikipedia, not Commons. --jjron (talk) 14:30, 8 March 2013 (UTC)

I've found a better way to browse the images: this page of images has a menu on the LHS. I've asked Fæ if these could be incorporated as sub-categories. Actually, I've a good mind to browse the images myself to see what would be included in articles. And I'm sure some other Wikipedia's for those countries would benefit even more. It is just one example. Of many. Colin°Talk 14:40, 8 March 2013 (UTC)

May I introduce Geoffrey R. Gallice to you; a graduate student at the University of Florida's Entomology and Nematology Department. He has 1,854 contributions to Wikimedia so far; all are transferred by our volunteers from his flickr account. This is his blog. We have several such contributors behind the curtain, who never argue for any appreciation or grant; but continue their free contributions that make Wikipedia how it looks now. (Further, as jjron argued, there is no need to use all pictures in articles to count any value for them. Most of our pages have a link to a relevant COM:Category or wiki species where a reader can find more relevant pictures. Sorry, if I’m linking various wiki projects; I can’t even think about they can stand independently.) JKadavoor Jee 15:43, 8 March 2013 (UTC)

His website: https://sites.google.com/site/neotropicalbutterflies/photography says for non-commercial purposes only. Saffron Blaze (talk) 15:56, 8 March 2013 (UTC)
That seems only a request. I had contacted him several times for high resolution files here. He never refused; never changed his CC-BY license in Flickr. Anyway, thank you for the point. JKadavoor Jee 16:06, 8 March 2013 (UTC)

It was just an example; we have so many non-Wikimedian authors. JKadavoor Jee 05:58, 9 March 2013 (UTC)

The GFDL licence is only used by two regulars at FP: User:Muhammad Mahdi Karim and User:Jjron, who between them had 11 featured pictures in 2012. The collapse of Wikipedia will not occur if this licence is removed from the criteria. Colin°Talk 20:28, 9 March 2013 (UTC)

...but will occur if it's not (right?). --jjron (talk) 12:56, 13 March 2013 (UTC)

Sympathy

Since things are getting a bit heated above, I thought it worthwhile to say that I quite sympathize with John's and Muhammad's position. When I do research for a WP article, though the text itself is free-licensed, there is nothing to prevent me from using the information I have learned or the citations I have found in other writing that is copyrighted and published under my (real) name. (Obviously the edits of old photographs I do are largely uncopyrightable anyway.) Indeed, one of the main incentives for contributing to WP is to learn stuff, and that learning is transferable into my professional life. In photography there is no equivalent; I suppose one could take two slightly different shots of every subject, but every photographer knows there is always one that's clearly the best. Photographers are giving up their work entirely in a way that other contributors are not. Now, some do so without concern as cited above, but they presumably have other sources of income. No one should be judged for wanting to make money off of their work; a person needs to eat. All that said, Wikipedia is part of the free culture movement and should put genuinely free-licensed work forward as its best. That might indeed piss off some of our best photographers, and that is both our loss and theirs. But we needn't insult them on top of the injury we're doing. Sorry for the righteous lecture; I'm done now. Chick Bowen 16:37, 8 March 2013 (UTC)

  • I've no problem if Wikimedia accept CC-BY-NC or CC-BY-NC-ND as a choice of license in its sub projects. I’m happy to support if anybody raise this request in a proper forum and convince me with genuine arguments. But I don’t like people use GFDL as a shortcut to achieve this goal. It not only fails to stop all commercial uses; but stops many genuine non-commercial uses (both are against our current policy). Please be straight, truthful, and transparent in our policies and views. Making money is not very bad; but it should not be on the expense of our community, damaging the face and goodwill in front of the public. Nothing should prevent her to achieve the goal: “Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.” (I’m no way against Muhammad, not neglecting his contributions to this community so far.) JKadavoor Jee 05:44, 9 March 2013 (UTC)
  • The problem from my perspective is that this is the wrong venue to make policy changes. Just as people use GDFL to circumvent "free", people here are using FPC to forward their own agenda. Saffron Blaze (talk) 23:16, 9 March 2013 (UTC)
  • The main problem is that Wikipedia not updated the “texts” in several pages according to the resent changes in their policies. (Our current policy according to http://wikimediafoundation.org/wiki/Our_projects is: "All major projects of the Wikimedia Foundation are collaboratively developed by its users using the MediaWiki software. All contributions are licensed under the Creative Commons Attribution-Share Alike 3.0 (except Wikinews, which is licensed under Creative Commons Attribution 2.5), meaning that their content may be freely used, freely edited, freely copied and freely redistributed subject to the restrictions of that license.") Main pages have the footnote “Text is available under the Creative Commons Attribution/Share-Alike License; additional terms may apply. See Terms of Use for details.” When you click on an edit button, it says “By clicking the "Save page" button, you agree to the Terms of Use, and you irrevocably agree to release your contribution under the CC-BY-SA 3.0 License and the GFDL. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.” But GFDL alone is still there in several places like Wikipedia:Image_copyright_tags#For_image_creators. So people make benefit from it. I think these people use the 'Old' upload form. It has an option under “Upload your own work”: “None selected (add a license tag under the summery box above, or this file will be deleted)”. There they add their predefined license template. The list of license contains only CC-BY-SA+GFDL, no GFDL alone. (I didn't get the "own agenda" part. :D Isn't it good to respond than keep silence while seeing an evil? Shouldn't we respect the rules of United States if we're the proud citizens of that country?) JKadavoor Jee 07:35, 10 March 2013 (UTC)
  • Saffron's comment is mistaken. We're not making policy changes. Merely deciding what to celebrate with a bronze star. I see Muhammad and Jjron getting upset, naturally, because there's a threat to future awards that affects them personally (but nobody else). I see no arguments as to why images with GFDL should be celebrated. Just perhaps some fear that two good photographers might not contribute. That would indeed be sad, but merely a drop in the ocean as far as Wikipedia is concerned. We have lost far more content by disallowing -NC and yet the consequence of this is we have given far more to others to use. As for "their own agenda", well I'm afraid it is Wikipedia's agenda. The manifesto of which is authored by Erik Möller, Deputy Director of the Wikimedia Foundation. Some people aren't just getting the "free content" bit, though. It isn't "the encyclopaedia that is free to read". As for policy, well I'm sure before the year is out that Commons will have banned uploading new content with these restrictive terms. It would be great if FP was ahead of the game rather than continue to embarrass the community. Colin°Talk 08:27, 10 March 2013 (UTC)
  • Saffron's comment is not mistaken. If wikimedia as a matter of policy disallowed GDFL for certain media, like images, then we wouldn't be having this silly debate again. GDFL is not a suitable license for images within the "free culture" context. Fix it for the whole of wikimedia not just FPC. Anything less is suspect in my opinion. Saffron Blaze (talk) 15:05, 10 March 2013 (UTC)
  • I'm quite certain that will happen and I'll be working on that later. As I said before, I didn't start this discussion on en:WP, and didn't particularly want it to happen here, but it is happening so it might as well reach a conclusion. And I started the com:FP debate because the issue kept coming up at com:FP and needed settling. I think it is valid (though I don't agree) for someone to think the GFDL licence could be kept for uploads for some pragmatic reason, while also believing it doesn't qualify as "our best" hence not for FP. But also, I'm sure that when the debate to start banning uploads with this wretched licence begins, someone would have said "How can images with such licences be banned when the community regularly awards them "featured picture" and regards them as "our best"?" At least now we can say the community does not regard them as "our best". The fact that only two people on en:wp regularly use it shows just how minority it has become. Quite why a few other people support them in this, I don't understand. Colin°Talk 16:50, 10 March 2013 (UTC)
  • Anyone that argues GDFL is a useful license it a prat in the first place. It's a stupid fucking license even for texts. That aside, what will you do when this finally goes to global decision and GDFL by some strange twist of fate wins approval as an acceptable license? This outcome is not as implausible as it might seem, as all the -NC malcontents might get their final digs in. In that event you will be confronted with both FP projects being in some level of tension with wikimedia policy and open to additional challenges on the same question. If this had started from the top and succeeded it would have rolled on down hill quite easily for cause. Instead we are forced to push the turd up the hill.
As to our two GDFL users. If they are doing this simply to prevent re-use outside wikimedia then they should consider leaving. I have not returned to contributing files due to commercial re-use concerns. I am just not there yet with donating my work for free so others can make a profit from it. If wikimedia is a charity I should get a tax receipt for my donations. That's another debate though. Saffron Blaze (talk) 17:08, 10 March 2013 (UTC)
  • "GFDL is not a suitable license for images within the "free culture" context. Fix it for the whole of Wikimedia not just FPC. It's a stupid fucking license even for texts." - Saffron, you rocks! JKadavoor Jee 17:20, 10 March 2013 (UTC)
My understanding about Wikimedia’s stand against NC license according to Erik Möller is: "It's been Wikimedia's long-standing position that allowing commercial re-use contributes to its educational mission (the negative impact of stupid commercial uses is outweighed by the positive impact of educational, commercial uses), and that position is unlikely to change." - I think it is true. Think about an educational text book printed with my pictures for sale. Am I really wanted to discourage it? No; in my case. I wish one day CC will design a license CC-BY-EU (for educational use only). JKadavoor Jee 17:32, 10 March 2013 (UTC)
The concept of "non-commercial" is actually quite vague and open to interpretation. The classic example is a blogger using a picture on their site run from their bedroom. Sounds NC until you realise their blog has adverts. Then their blog doesn't really sound that different from a newspaper. Just scale and professionalism. Is a charity "non-commercial"? Perhaps their educational fact-sheets are. But what about the adverts they run for donations? And what if the back-page of their fact-sheets request donations? And so on. Ultimately if folk want to control reuse or make money from their pictures then don't donate them here. Full stop. There's scope to do both perhaps, but with different pictures.
Photographers are hypocritical bunch wrt free donations of their images imo. Just look at their Android phones or browser they use to look at their pictures. All work donated by programmers and used commercially. I've no problem with folk deciding to charge for their work or wanting to control reuse. But those doing this for free, as a without-strings donation, aren't stupid or mugs. Their reward is measured differently, that's all. Colin°Talk 20:22, 10 March 2013 (UTC)
No body said they were stupid. In fact many work for free now in hopes of future gains through experience, connections, quid pro quo, mutual support for commercial endeavours, etc. Saffron Blaze (talk) 20:59, 10 March 2013 (UTC)

Jjron: "I really don't understand the screwy thinking that says we should be making donations to multimillion dollar businesses. It's utterly contemptible. ... Yet you would have us giving all our work away to these morally bankrupt concerns without an even vague way of controlling it. This is bizarre. " Yeah, all the folk who made Google the billion dollar business it is now through their donations of free software. They've got screwy thinking and are utterly contemptible. And that chap who gave away the World Wide Web for free. You know it is mostly used for "morally bankrupt" porn and stuff and he has like no way of preventing that. This is really bizarre. Not. Colin°Talk 22:00, 10 March 2013 (UTC)

What Mr Berners-Lee did was noble but it wasn't without its rewards: http://www.zdnet.com/berners-lee-wins-1m-prize-3039158270/ As to Google, their new image search is in most photographer's minds a blatant violation of copyright. Saffron Blaze (talk) 01:02, 11 March 2013 (UTC)
We're getting off-topic a bit here, the point was great things have come from those who give away their stuff for free without strings. Sure these people do bad things too. Mohammed/Jjron's restrictive licensing, where they act as gatekeeper for reuse, is just completely at odds with Wikimedia's goals. Don't they realise most of the world doesn't speak English for a start -- yet their images will be used in Wikipedias of all languages, and could have been used in teaching material in all countries of the world. But they wont because a teacher preparing the lesson for tomorrow in some French-speaking part of Africa can't email Jjron for permission. -- Colin°Talk 08:31, 11 March 2013 (UTC)
If that kind of scenario was actually occurring I would genuinely be surprised. Of the 40 so request/notifications of image use I have received have all been medium/large companies. On the other hand most of the copyright violations have been bloggers trying to boost ad revenue, but there have been some rather well to do companies that have also violated the copyright provisions of CC-BY-SA. In effect I seem to be lining the pockets of people that have no interest in free culture. While acknowledging the example of the Wiki DVD, I don't know of another single example of an educational use in the spirit of "free culture" with any of my works. Saffron Blaze (talk) 17:17, 11 March 2013 (UTC)
You are forgetting that your work is licensed with a decent choice of licence that is clear for re-users to understand and appropriate for the media. They have no need to ask your permission (provided the attribution requirement is ok for their use) and that is as it should be. You are also assuming that re-use is on the web where you can detect it. It might well be in a student handout, a lecturer's slides or for a church quiz night -- all of which escape your radar. Some of the re-users below the radar will be the kind of folk who ignore the licence anyway ("if it is on the internet it must be free") but others will care and simply not use the GFDL images. Those wikipedians using the GFDL licences also won't really know the scale of the trouble they cause because the vast majority of folk will give up at the first hurdle -- there are other pictures they can use perhaps, but sadly not as good. Wikipedia is an Open Educational Resource. Colin°Talk 18:53, 11 March 2013 (UTC)
No Colin, I am not forgetting I used CC-BY-SA (stop that crap:)). I wasn't drawing a distinction between it and GDFL. I was intimating that this notion of the little 3rd world teacher using wikipedia "free culture" works may exist, but on scale that is dwarfed by commercial re-use by companies and individuals that could afford to pay for those works. In the "free culture" world this state of affairs is perfectly acceptable, as the needs of the one outweigh the greed of the many. For those that make some or all their income from photography (not me) that is a hard philosophical pill to swallow. Moreover, "free culture" actually represents a threat to commercial photography. If commons is populated with thousands of FP quality images that people can use for free then what happens to the stock photo industry? As you said... well off topic but perhaps some insight as to why some people resist "free culture". Saffron Blaze (talk) 22:04, 11 March 2013 (UTC)
We all have different philosophies in life wrt reward and that's fine. We all also have different philosophies wrt worrying about some bad guy taking advantage. I don't think "free culture" is a threat to photography in the same way that free software hasn't been a threat to commercial software -- indeed it positively thrives on it and we wouldn't be where we are without it. What does damage commercial software is apps for pennies and the counterpart in photography is microstock. Very few gets rich in either field and those who run the marketplace are the real winners. Colin°Talk 22:49, 11 March 2013 (UTC)
Can't disagree with any of that. Software thrives to some degree on open source because of the sheer complexity of even simple apps let alone operating systems. In photography the trend has been towards microstock because it is becoming easier to get decent stock images, but even that is under threat by deals that agencies are now making. Recently Getty Images licensed to Google 12,000 professional stock images. The terms of the license allows Google's customers (hundreds of millions of them) to re-use these images for commercial purposes!! The photographers got $12 for for each image that was effectively bought out. In this case I think the photographers would have got more value, if not cash, in donating them to Wiki. Saffron Blaze (talk) 13:41, 12 March 2013 (UTC)
I've no problem if somebody offers big awards to our big contributors. But begging for it not makes much sense to me. Probably they are thinking big. JKadavoor Jee 01:57, 11 March 2013 (UTC)

On the GFDL wording

There's a good chance those commenting above haven't actually studied the GFDL. It is a free licence suitable for long textual works. It is widely acknowledged as not practical for images and short texts. So here it is. Let's see how someone using a picture of a butterfly along with a paragraph of text from the Wikipedia article, sets about using in in a slide presentation.

  • "The purpose of this License is to make a manual, textbook, or other functional and useful document "free"" Hmm. I'm confused. I've got a JPG of a butterfly here. That's not a manual or textbook and I'm sure it isn't a document, whether functional or useful.
  • "We have designed this License in order to use it for manuals for free software, because free software needs free documentation" Hmm. I'm pretty sure a JPG of a butterfly isn't a manual for free software.
  • "But this License is not limited to software manuals" Ahh. Good. Now we're getting somewhere. "; it can be used for any textual work, regardless of subject matter". Oh dang. There's no text on my butterfly.
  • "We recommend this License principally for works whose purpose is instruction or reference" I just chose this butterfly because it is pretty and I like butterflies.
  • Hmm, the "APPLICABILITY AND DEFINITIONS" section talk a lot about the "Document" and "title page" and "cover texts". This is just a single image.
  • "You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License" What? You mean if I use this picture of a butterfly, I've got to add a 3,700-word legal document to my work? I've just pasted this into Word and it took 6.5 pages. If I showed this on an projector it would take 50 slides and consume about an hour of my presentation for folk to read. I just wanted a picture of a butterfly.
  • The whole purpose of a licence is to grant the reuser rights they would not normally have under copyright. If there is any doubt the licence applies to them, the reuser can't use the work at all as they may then breach copyright. Someone reading the above licence would (a) be very unsure the licence applies to images at all and (b) be practically unable to make use of it in many ways, because of the onerous requirements. The result is that the image isn't reused, and we have failed in our mission to provide free content. We should not celebrate such failure in the Featured Pictures. Colin°Talk 11:19, 9 March 2013 (UTC)
"The result is that the image isn't reused..." That is exactly what "we" need. Be pragmatic; pretend that we care contributing freely, use all possible loop holes in the system to block any possibility for a free use. JKadavoor Jee 15:22, 9 March 2013 (UTC)
What a lovely homily. The problem is you may just as well substitute you claim for someone wanting to use GFDL licensed text in a one-page flyer. "What? So I've got to attach this 3,700 word license to my flyer...". Or Powerpoint. Or whatever. Same thing. If you want to ban GFDL licensing in toto, then this is clearly the wrong forum. --jjron (talk) 05:02, 10 March 2013 (UTC)
Ah you fall into the evil trap I have set :-). All Wikipedia's text is dual-licensed with CC BY-SA, so the one-page flyer can pick that licence instead of the stupid GFDL one. But the flyer can't use the butterfly as an illustration, no way as it would then become a booklet! The problems with GFDL for short texts are well-known and why Wikitravel doesn't use it at all. So you're wrong: I don't want to ban GFDL licence in toto -- folk can add whatever extra licences they like, as long as they pick one that is truly practically free. Colin°Talk 08:16, 10 March 2013 (UTC)
Um, actually no, cos I wasn't talking about Wikipedia specifically, merely about - and let me quote - "GFDL licensed text". As if I don't already know Wikipedia text isn't solely GFDL licensed... --jjron (talk) 12:52, 13 March 2013 (UTC)
Well I was talking about Wikipedia specifically. Your example is therefore irrelevant to the discussion, yet you claim your example is "the problem" with the "lovely homily". The problems with GFDL is precisely why Wikipedia moved towards dual licensing and why new wiki projects just don't use it at all. Yes GFDL sole licensing is already "banned" for Wikipedia -- everyone must dual licence their images. If folk dual licensed GFDL with CC BY-SA or FAL, say, then that is absolutely fine. Colin°Talk 12:58, 13 March 2013 (UTC)
  • A few comments in reply to Colin:
    • Firstly 99% of users of online digital content do not care if they are breaching copyright. They see a picture, they like it, they take it, they use it. If X want's a pretty picture of a butterfly for a powerpoint, he does a search in Google Images, picks out the nicest one and sticks it in. End of story. Copyright breach? Meh. The only people who actually care about copyright are organisations and corporations (and even then most of the time the employees will breach copyright and pinch the photo off the internet - I've had countless occasions where this has happened to my images). So your little story above is almost entirely hypothetical.
    • Secondly, if you've bothered to read the CC licences, they can in fact be more onerous than the GFDL for online usage. For example, the CC-BY-SA 2.5 licence (which your good friends from Norden use) require the user to "attribute the work in the manner specified by the author". Now that is incredibly broad. In theory I could demand a five paragraph attribution clause which occupies no smaller area than 25% of the reproduced image. By contrast, using a GFDL image online is probably as simple as inserting a hyperlinked bit of text to the licence. Hardly taxing. In fact even leaving aside the extreme example I just gave, the GFDL hyperlink is probably going to be less conspicuous than a "normal" attribution line and would therefore be preferable to many users. It is therefore quite incorrect to brand the GFDL as this unparalleled horror licence with no practical operation as a free licence.
--Fir0002 03:18, 12 March 2013 (UTC)
But does that actually happen in practice? If a user really were abusing CC-BY-SA by demanding an extremely long attribution, we could always nominate their images for deletion under WP:IAR. -- King of 20:46, 12 March 2013 (UTC)
Fir0002's interpretation of attribution requirements is insufficient. The license states that attribution has to be given in a manner reasonable to the medium (as long as core data in author name etc. is not omitted). CC licenses are designed deliberately flexible for reusers. What Fir wrote above is plain old FUD. His first point is also certainly not an argument for GFDL, if anything it is one against it. We have to make reuse easier not harder, and a CC-BY license can be summarized as "Please state Photo by Fir0002 / CC-BY near the picture". But I have a suspicion that these facts are absolutely clear to everyone involved in this discussion. --Dschwen 20:54, 12 March 2013 (UTC)
While I agree lots of folk steal stuff off the internet, there are honest folk (my Photoshop is legit!) who care about licensing. I want us to help make it easy for folk to be honest, as Dschwen says. My "friends" from Norden say "Available for free use provided the source is credited (e.g. Photographer Name - norden.org)". Their image homepage says "You can search here in our image database The majority of the images may be used without restriction provided that you mention the image source." It couldn't be easier for someone to be honest with their images. Your hypothetical about their licence is irrelevant. What is relevant is that all the folk here, you included, who use GFDL do so deliberately to restrict reuse (particularly commercial) and none of you want to engage in discussing that because it is unarguably against the principles of the site. You'd rather deflect. It is rather sad, this cynical view of humanity, and all this angst about bad people using our images. Colin°Talk 21:25, 12 March 2013 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

{{Unresolved|Is there any reason to oppose delisting this image? 75.215.235.59 (talk) 04:31, 6 October 2013 (UTC) That delist process looks like something of a one-man show, with the same editor nominating it, providing half the "delist" !votes and proclaiming the result. Maybe a more experienced editor than me could take a look? In particular that IP editor apparently couldn't complete the delist process; see WT:Featured picture candidates/delist/File:Airfield traffic pattern.svg. Huon (talk) 22:35, 29 April 2013 (UTC)

That's definitely a "No consensus to delist". I've reclosed it appropriately. Adam Cuerden (talk) 00:37, 30 April 2013 (UTC)
Based on the comments, there were at least four distinct people involved. Only one person besides the nominator voted; those votes were in favor of delisting. One commenter seemed to think that a US-centric image was being promoted. 75.208.156.58 (talk) 04:32, 2 May 2013 (UTC)
NO' I questioned whether your 'reason to delist was US-centric. As it turned out, it was, since Upwind leg is used internationally. Adam Cuerden (talk) 06:00, 2 May 2013 (UTC)
Upwind is a US term and is used in other countries, but not for the climb out leg. In Australia, for example, the climb out leg is called Initial. I did not see any examples where climb out is referred to as upwind *anywhere* in the world. If you have even one reliable source, I need that, please. 75.208.156.58 (talk) 16:49, 2 May 2013 (UTC)
In any case, this discussion is moot. Regardless of the merits of a case, a successful delisting requires 2/3 support and 5 delist votes. Period. This did not achieve it. -- King of 04:01, 3 May 2013 (UTC)
  • It seems to me that the reasons Adam gave that he did not vote to delist are reasons to delist. The image does not meet any of the criteria for a featured picture. It is based on original research, it does not (and cannot) reflect a global perspective, and it was based on a mistaken idea of the standard US traffic pattern. Voting did not remain open long enough for five people to vote. Adam is an example of someone who did not participate in the discussion long enough to decide how to vote. With only two people voting at all, there clearly was a problem with the process. 75.208.123.109 (talk) 07:40, 3 May 2013 (UTC)
  • I wish someone would tell me (1) where this rule "2/3 support and 5 delist votes within 10 14 days" is written, (2) where I go to challenge the 10-day14-day limit, and (3) how this picture got featured in the first place. 75.208.123.109 (talk) 07:40, 3 May 2013 (UTC)
I agree very much with your sentiments on how difficult it is to get enough people to delist an image. That's why on Commons, I made a proposal (which was accepted) to hold delisting nominations in the same section as regular nominations, thus increasing the traffic to the nomination. My first delisting candidate has already gotten 8 delist votes in 2 days. So we could consider the option of holding delist nominations in the regular section. (However, I would not want a lowering of the vote requirements; you need enough people to establish a consensus. I imagine that this would not be difficult to accomplish if the nomination occurred in a high-traffic area.)
As a side note, 10 days is not correct, it's actually 14. -- King of 07:46, 3 May 2013 (UTC)
  • Thank you. Fwiw, the particular image that brought me here is one that requires subject matter experts. It should be a diagram which visually illustrates encyclopedic content. But its content is not backed by any published source. From reading Adam's comments, it sounds to me like he would oppose delisting the original version of the image and oppose the changes that were made to address problems raised in the nomination to delist. Those changes are now in the current commons picture which retains its status as FP that was granted to the prior erroneous diagram. There should be no doubt that the process needed more time and that people didn't even know which version was nominated or whether it could be salvaged because the picture was edited twice during the voting window. 75.208.123.109 (talk) 17:16, 3 May 2013 (UTC)
  • Where exactly in Commons did you make this proposal? What would I need to do the renominate a picture for delisting and publish the notice in "the regular section"? 75.208.217.192 (talk) 05:57, 23 May 2013 (UTC)

In any case, we do regularly delist images, and we have FPCurgents to tell people when something is unreviewed. But the IP is acting in precisely the way - claiming that comments that one isn't convinced by the nominator's rationale are reasons to delist (Shall I edit it and change my vote to "keep"? Because, while a bit stronger than I wanted to vote, it's a damn sight closer than what the IP is claiming I voted when I questioned whether his rationale to delist was biased towards American terminology, to make this perfectly clear, the IP's rationale to delist was based on "this didn't appear in an American source", I questioned whether it might be an international term, and so delisting it would be American bias. Other people made it clear it was a term used internationally. Therefore, the nominator's rationale WAS based on upholding an American bias, and I was right to object.) Frankly, once someone starts claiming I, or anyone else, for that matter, hold different opinions than what we have repeatedly told them our opinions are, they are trolling, and any further encouragement of them is feeding the trolls. Adam Cuerden (talk) 13:28, 3 May 2013 (UTC)

  • That quotation is entirely Adam's fabrication. I checked the nomination page. Adam has made a patently false claim that the rationale to delist was based on "this didn't appear in an American source". No such statement was made by anyone. Frankly, once someone starts claiming that I, or anyone else for that matter, nominated the picture to be delisted because "this didn't appear in an American source", he is trolling. 75.208.123.109 (talk) 17:51, 3 May 2013 (UTC)
I shan't be available for a bit. In unrelated news, I just stumbled upon something very upsetting, and am going to relax at a freind's for a bit. Adam Cuerden (talk) 13:29, 3 May 2013 (UTC)
  • Let's make this perfectly clear, no one except Adam ever suggested that any rationale to delist was based on "this didn't appear in an American source" and absolutely no one except Adam ever suggested that the term Upwind is used internationally for the climb-out leg. Therefore, the nominator's rationale was NOT based on upholding an American bias, and Adam was mistaken in his objection on that basis. The problem with it not being in an American source (the FAA) was that it does not appear in any reliable source in English anywhere in the world. 75.208.123.109 (talk) 17:39, 3 May 2013 (UTC)
  • No one has ever brought forth even one source that showed that the climb-out leg is referred to as Upwind in the USA or any other country on earth. Examples from the USA and other English-speaking countries show that the image is based only on a faulty understanding of the US traffic pattern and is markedly different from that for Australia and from that of New Zealand. The 'European' source was actually a safety study done by NASA. The British source was for a flight instruction school, not from a source known for its reliability (e.g., CAA). The first revision (in response to the delist nomination) changed Upwind to Departure. So if Adam is correct, the current revision of the image uses American terminology for the climb-out leg (in Australia, Initial). So sure, Adam, amend your vote to 'oppose' for the record. 75.208.123.109 (talk) 17:23, 3 May 2013 (UTC)

Oh, really?

Can we have a bit less lying? Adam Cuerden (talk) 20:28, 3 May 2013 (UTC)

  • Please cite the lie. Specifically, where is the source of the quote that you attributed to the nominator?
  • (1) Upwind is a different activity from departure. But no one denies that pilots sometimes use the wrong terminology. Hearing it does not make it correct for an encyclopedia.
  • (2) The EASA document was produced by NASA as I stated above. The diagram is for a safety report. It is not instructive.
  • (3) The Purple Aviation document is from an insignificant flight school using slash terminology. As I stated above: "The British source was for a flight instruction school ..."
  • (4) You snipped where it was shown that the Civil Aviation Safety Authority (Australia) does label the leg in the document cited and labels it as Initial as I stated above.
  • (5) The quote you cited from auburnpilot states his assessment:
User auburnpilot goes on to cite differences between the UK, Australia, and New Zealand. So if this quote is the basis for your claim that Upwind was proved to be international terminology, you need to re-read it a few more times.
  • So please, Adam, stop lying and accusing me of lying. Just work on getting the facts straight. If you have new information, I want to see it. But just because a "reliable" source from Belgium (not officially English-speaking) uses Upwind for the climb out, that does not make it global/international terminology.
  • If there is global terminology (e.g., from ICAO), so far no one has produced reliable evidence of that, whereas irreconcilable differences have been shown between the sources cited so far.
To avoid a straw man argument from Adam, I also note that no one denies that the term Upwind is used in the US and throughout the English-speaking world. The issue is where that term is applied on the diagram. On the original diagram, The leg (segment) labeled Upwind was in fact the 'climb out'/'initial'/'departure' leg, not the 'upwind' leg. So for the diagram at issue, one controversy is over how to label a particular leg. In other words, the term Upwind is used globally; it just is not use to label the same place in the pattern in each usage. As soon as you try to pin down precisely where that leg is, then there is an obvious conflict between sources; the real Upwind leg is unlabeled or omitted in the diagrams which (mis)identify the climb out leg as Upwind. It's actually more complicated than this. That's why it really takes informed voters. 75.210.33.243 (talk) 04:09, 4 May 2013 (UTC)

Could we get this resolved as to whether User:Adam Cuerden has any reason to oppose delisting this image (besides baseless, vitriolic personal attacks)? 75.210.11.206 (talk) 07:37, 23 July 2013 (UTC)

  • Comment It doesn't really matter, whether Adam Cuerden has any reason to oppose delisting the image. The fact remains, that there was not enough support for delisting the image, and therefore it's automatically kept. If you think it's still problematic, than feel free to renominate it. Armbrust The Homunculus 06:37, 27 July 2013 (UTC)
    • More so for the fact the offending image was "corrected" some time ago. As a former senior ATC in the RCAF I can say I never used upwind even if I knew what it meant. It certainly wasn't the departure corridor. And ceejayoz should get himself back to Relicnews. Saffron Blaze (talk) 02:25, 6 August 2013 (UTC)
  • The "corrected" image contains errors and unnecessary details. Many of its problems are listed on its Talk page. But what you are really saying is that the original image was technically wrong and should never have been featured in the first place. 75.210.11.3 (talk) 23:45, 31 August 2013 (UTC)
  • The point being that there are so few voters that one person's questions were more than enough to prevent the image from getting the votes to be delisted even though if it weren't already featured, it wouldn't garner enough votes to be listed. Trying to get this image delisted over the objections of someone as active and influential as Adam Cuerdan is a fool's errand. If anyone has any objections to delisting, those should be addressed before anyone else bothers to re-attempt delisting. Had Adam supported delisting, I am sure that the outcome would have be to delist. His vote does make all the difference. 75.208.126.20 (talk) 06:42, 28 August 2013 (UTC)
You're allowed to renominate things for deletion after an appropriate time. However, you can't dictate how other people should vote. And throwing a four-month hissy fit is not a good way to get people on your side. Adam Cuerden (talk) 20:13, 1 September 2013 (UTC)
  • I am not throwing a fit. Please refrain from personal attacks. I am not telling anyone how to vote. I am saying that if you do not support delisting, then a nomination to delist is a waste of everyone's time. 75.208.9.202 (talk) 22:46, 4 September 2013 (UTC)
  • If I nominate the picture for delisting, will you support delisting? I am sure that if you nominate it for delisting that it will be delisted. 75.208.9.202 (talk) 22:50, 4 September 2013 (UTC)
  • Adam raised the red herring: "Are we certain we're not just enforcing an American bias, by insisting on American terminology, or is upwind called departure worldwide?" Insisting that the delist rationale was US-centric goes beyond enforcing the rules. 75.208.47.227 (talk) 15:45, 6 September 2013 (UTC)
As I said, you really cannot tell people how to vote. Adam Cuerden (talk) 05:01, 5 September 2013 (UTC)
  • Adam wrote: "... the nominator's rationale WAS based on upholding an American bias, and I was right to object." (emphasis mine). I am not telling anyone how to vote. I am inquiring as to whether all Adam's objections have been resolved to his satisfaction. 75.208.47.227 (talk) 15:45, 6 September 2013 (UTC)
Very well. No. They have not, but I had been willing to let you just renominate the thing and stand back. But if you'd rather argue for another four months, just go away. Adam Cuerden (talk) 18:58, 6 September 2013 (UTC)
  • I do not wish to argue. I wish to learn precisely what Adam's objections are (assuming that they have to do with why the image should continue to be featured even though during the previous voting period it was edited to enforce American terminology). Even if Adam would graciously refrain from raising any objection, someone else might raise the same objections. If I cannot overcome such objections, then another nomination is a waste of time. I am not trying to win anyone over to my side. This is about improving Wikipedia. I am trying to delist as a featured picture a diagram which I believe clearly is not the best representation of the subject matter. 75.208.187.245 (talk) 06:13, 9 September 2013 (UTC)