Talk:Main Page/Archive 157

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Archive 150 Archive 155 Archive 156 Archive 157 Archive 158 Archive 159 Archive 160

Suggested another category

Under the section languages are 4 categorys (500,000, 150,000, 100,000 and 50,000 articles). I would suggested another one/two with 1 Mio./250,000. It would easier to show the increase of the non-english wikis. —Preceding unsigned comment added by 88.153.238.248 (talk) 12:06, 19 February 2011 (UTC)

Please see Talk:Main Page/Archive 153#Over one million articles, Talk:Main Page/Archive 154#Proposal: Add million-article level to Wikipedia Languages section, Talk:Main Page/Archive 155#1,000,000 +, and Talk:Main Page/Archive 155#Wikipedia size: Implementation of proposed changes for some of the more recent discussions of this perennial proposal and the reasons it has not been implemented. --Allen3 talk 12:48, 19 February 2011 (UTC)
Can we get some sort of note box like that about national varieties of English added to let people know not to post this sort of thing? --Khajidha (talk) 01:03, 21 February 2011 (UTC)

Libya

What happened to the Libya protest in the news section? Hiberniantears (talk) 01:21, 22 February 2011 (UTC)

It's the third out of the five there, "Authorities open fire on demonstrators in Libya and Bahrain amid continuing protests across the Middle East and North Africa." Sven Manguard Wha? 01:50, 22 February 2011 (UTC)
Howcheng appears to have restored an old version of the template by accident; Libya had its own blurb earlier today. StrPby (talk) 01:59, 22 February 2011 (UTC)
Re the final ITN item at this moment on Bahrain, I think we need to remove it ASAP. We were right to run with it on the 18th/19th, but the military stood down 3 days ago. —WFC— 13:15, 22 February 2011 (UTC)

Wikipedia languages

Please add Azerbaijani Wikipedia (Azərbaycanca) to "More than 50,000 articles" section. Regards.--PPerviz (talk) 02:00, 22 February 2011 (UTC)

Interwikis too.--PPerviz (talk) 02:09, 22 February 2011 (UTC)

In addition to the quantitative requirement, we also have qualitative ones. Please see Template talk:Wikipedia languages#Azerbaijani wikipedia. —David Levy 06:10, 23 February 2011 (UTC)

Nav box

Can anyone check this to see if it's good? --Highspeedrailguy (talk) 18:20, 24 February 2011 (UTC)

Good for what? It's overly colourful for my tastes, and hasn't got anywhere near as many items on it as {{Main Page toolbox}}, but it does seem to work. You have two links to Talk:Main Page though. Modest Genius talk 19:35, 24 February 2011 (UTC)

Main page: Where to ask?

The main page of Wikipedia (and not of the English Wikipedia) has some problems. The entry for languages for 10,000+ do contain the entry "Kurdî / • کوردی • " and the one for 1,000+ the entry "كوردی ". This is strange. Where am I going to ask? — Preceding unsigned comment added by Sae1962 (talkcontribs) 07:56, 25 February 2011 (UTC)

Meta:Talk:www.wikipedia.org template Nil Einne (talk) 11:47, 25 February 2011 (UTC)
You haven't posted yet, I was going to post for you but upon checking I can't find the problem you refer to nor any sign it's been fixed recently. Are you perhaps confusing کوردی with something that looks similar like کوردی  ? If so do note these don't link to the same thing I presume it probably translates in to something like 'language' in multiple related languages. I have no idea if these are different to someone who understands the script, they look the same to me however they do appear to be using a different character set or different characters since a search doesn't find them both. P.S. Strangely enough your second one actually find's the text under 10000+ (which led me to believe the second one didn't exist) while your first one, if you only copy the Arabic alphabet part finds the one under 1000+. Did you make an error in copy and pasting that here Nil Einne (talk) 10:15, 26 February 2011 (UTC)
Those two Arabic-script words are the same and both seem to say kūrdī or something similar (not knowing the language I'm not sure if that's accurate). 86.6.193.43 (talk) 17:00, 26 February 2011 (UTC)
I don't know the languages but the strings at http://wikipedia.org are different according to a copy-paste into Ctrl+F, and they link to different languages. "Kurdî / كوردی" under 10 000+ links to the Kurdish language Wikipedia at ku:, while "کوردی" under 1 000+ links to the Sorani (also called Central Kurdish) Wikipedia at ckb:. I found the language names at meta:List of Wikipedias. PrimeHunter (talk) 20:29, 26 February 2011 (UTC)
The Kurdish [1] version starts with (the start is to the right!) "U+0643 ARABIC LETTER KAF", while the Sorani [2] starts with "U+06A9 ARABIC LETTER KEHEH". I don't know the script but it appears that KAF ك changes display to look like KEHEH ک when it's part of the language name Kurdî / كوردی (the right-most character of that string is KAF ك and not KEHEH ک). PrimeHunter (talk) 20:49, 26 February 2011 (UTC)
I can read enough Arabic script to know that the two names both say "Kurdi". (PrimeHunter is correct that the letter kaf changes shape when joined to the curly thing the left, that is the 'long U' sound.) The larger wiki is for Kurmanji, the most widely spoken of the Kurdish dialects, and the smaller is for Sorani, the less widely spoken. So they are both correctly, if unhelpfully, labeled "Kurdi". Per meta:Requests for new languages/Wikipedia Kurdish (Sorani), it appears that smaller wiki split from the larger last November, as Sorani is written in Arabic script and Kurmanji is written in Latin script, and there are other linguistic differences.
Getting back to the OP, I have started a discussion at meta:Talk:List of Wikipedias#two languages listed as Kurdish with a suggested fix. To change http://www.wikipedia.org/, you would need to change meta:Www.wikipedia.org template/temp and then request a Meta admin at meta:Talk:www.wikipedia.org template to make your changes live.
As noted at Wikipedia:FAQ/Main Page#What about the first Main Page, at www.wikipedia.org?, English Wikipedia has no direct control over those pages. - BanyanTree 05:48, 1 March 2011 (UTC)

to create a new project on indian recipes

hi I want to create a new project named WIKIFOODIA. can you pls. guide me to create this one. the project contains Indian recipes. how to prepare them etc. — Preceding unsigned comment added by Nd2476 (talkcontribs) 10:51, 28 February 2011 (UTC)

Why not contribute to Wikia's Recipes Wiki instead? If you want to start your own Wikipedia-like website, a good place to start is Mediawiki. — Pretzels Hii! 11:49, 28 February 2011 (UTC)
There is also Wikibooks:Cookbook:Recipes which you could say is more closely related to Wikipedia as it falls under the Wikimedia umbrella. GizzaTalk © 01:19, 1 March 2011 (UTC)

Alternative proposal for layout of the Main Page

I'll have something that solves every problem in in about 30 mins. Sven Manguard Wha? 01:12, 24 February 2011 (UTC)
Further analysis of the aesthetics (Coming soon!) Sven Manguard Wha? 20:30, 23 February 2011 (UTC)
Sven's mockup is fine with me. And I agree with him that we should be polling on the general principle of featured lists, and not (yet) on any particular layout. Raul654 (talk) 20:35, 23 February 2011 (UTC)
What Raul said. --Dweller (talk) 20:58, 23 February 2011 (UTC)
It doesn't work with the featured sound proposal, however, at all. Adam Cuerden (talk) 21:05, 23 February 2011 (UTC)
The proposal which secured virtually 100% support from the community over several days of transparent discussion. The Rambling Man (talk) 21:07, 23 February 2011 (UTC)
Seriously, this section should be archived. Immediately. The proposal for featured sounds was based on careful analysis of how many sounds we had, making sure the proposal gave us plenty of time to ramp up featured sound promotion rates before we hit the point where we were in danger of running out. It was a conservative proposal, just like FPs had when they first went on the mainpage - FPs replaced ITN one day a week, as I recall. This proposal would not work,a nd Sven should not have proposed it without speaking to the rest of the Featured Sound team. Adam Cuerden (talk) 21:09, 23 February 2011 (UTC)
And the whole point of the FS discussion was that it used the existing space taken up by FP without lengthening the page in the way this alternative proposes, thus avoiding a good number of the difficulties of the 2008 main page redesign discussions (which went on for ages and led to no change). If FS / FL get bogged down in a main page complete redesign discussion, then nothing will happen. BencherliteTalk 21:18, 23 February 2011 (UTC)
I think that's a rather negative take on the status quo, considering the support for inclusion is a given. We now have coinciding proposals for including worthy new content on the mainpage, so getting the design right from the get-go is important, rather than having this discussion again somewhere down the road. There's no reason to penalize Featured Lists because the earlier proposal left them out, which I think was unfortunate. In fact, I'd like to know what on earth they were thinking when they did that. SandyGeorgia (Talk) 21:28, 23 February 2011 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── We (FL) had enough time to get on-board, do a huge amount of background work, prepare for accusations of lack of quality, variety etc, and were happy to follow in the wake of the widely successful FS proposal. It was gratifying to see the whole community shaking the tired main page design and FA-rules approach up a bit. We agreed to the technical aspects, we prepared many examples of our best work, opted for a small but significant start (one list per week), went along with an already-agreed proposal, only to be shot to bits. Imagine how that feels. The Rambling Man (talk) 21:34, 23 February 2011 (UTC)

I'm sure it stinks (or sucks donkey balls, as Moni3 would say). I've been in a similar situation and lost a Wikifriendship over it. It happened, it's unfortunate. But there were problems in that several proposals were put forward concurrently. The best way forward now is to put the past behind, and work for an integrated solution that makes the best sense and that will avoid future agida. I, for one, apologize sincerely to you for my misunderstandings here, but I think they resulted partially from FP and FS having left FL out, which was seriously a wrong way to go about this. SandyGeorgia (Talk) 21:38, 23 February 2011 (UTC)
No, FL wasn't really left out. We agreed that the FS proposal worked. We had a premature chat about it on this very page. I started a discussion well over a week ago about the possibilities of lists on main page, FL members were well advised as to the technical solution. The Rambling Man (talk) 21:47, 23 February 2011 (UTC)
The FS proposal mentioned FL, but we talked and agreed that it'd be too confusing to have FL in the same proposal, due to the desire to give examples of sample FLs making a combined proposal a bit long. Adam Cuerden (talk) 21:56, 23 February 2011 (UTC)
In hindsight, I think that was a rather large and unfortunate strategic mistake. There is no logical reason for FPs and FSs to go on the mainpage while leaving out FLs, and that RFC was consequently flawed from a design perspective. And I agree with TRM that it's unfair for FL to be paying the price, but a sensible integrated solution is needed. I certainly think a daily FL makes much more sense than two FPs, and this should have all been contemplated at once, in one proposal. This reminds me of the ill-fated RFC on ArbCom voting several years ago, where they put forward so many changes at once without considering the combined effect of each change (a larger ArbCom composed of members with marginal support-- it was a poorly designed RFC because it didn't account for all factors, and a well-designed proposal here would have dealt with FLs together with FPs an FSs, as they are certainly worthy of mainpage space if FSs are.) So, how 'bout if y'all voluntarily recognize that it was an ill-formed proposal, and work towards something that makes more sense wrt FLs, since they were left out ? SandyGeorgia (Talk) 22:03, 23 February 2011 (UTC)
As I said before, FLs weren't left out. The FS proposal was good, moving onto the main-page is a little like rediscovering the holy Grail. Once the possibility of something other than FA making it onto main-page reared its head, we jumped on it. The technical issues suit FL fine. One list a week suits FL fine. We don't need or want seven lists a week right now. We want to walk before we run. We don't to be accused of sub-standard featured material. We want to take our time. The Rambling Man (talk) 22:07, 23 February 2011 (UTC)
(edit conflict)(edit conflict) You're not being shot to bits at all. The all of the people here are strongly supporting FL getting on the main page, including Raul and Sandy. The issue here is the aesthetics. I've got about 20 mock ups that I'm tossing around right now, frantically, as this took all of us off guard. A solution can be found. I happen to like the way that the mock up I generated looks, however Adam is right in that it might not be realistic.
What is happening here is that we are trying to balance the needs of several parties that all grouped together to make this happen. It would be an awful shame if one of those parties got screwed in the deal.
  • Featured Pictures bought into this because the split of the FP section into two sections would allow them to drain their massive backlog. They would be able to run 12 pictures a week (assuming two days where one of the slots was an FS) or 11 pictures (with an FL and the two FS) instead of 7. If we don't split the FP section, we'd be screwing over FP.
    • Can I interject here? FP may have a massive backlog, but that's not really a problem except to certain people (not me). My preference here is for FP to have a 100% width box for panorama days. If FL & FS share a row (however many days per week that might be), that would be the ideal solution IMHO. I also happen to think 2 FPs is a bit overkill. howcheng {chat} 06:18, 25 February 2011 (UTC)
  • Featured Lists bought into the FS proposal because it gave them time to prepare and let us test the waters for them. Also, it became clear within hours that running both proposals at the same time was chaotic and created the illusion that FS and FL were competing with each other, which is categorically not the case.
  • Both FS and FL are bought into this because it gives them spots on the main page, which FP has shown to be an effective way of raising participation and quality.
  • All of this was made clear from the beginning, and FS has received a community mandate to run on Saturdays and Sundays with all of this information out in the open. The three featured processes, who already banded together to make this happen in the first place, need to stick together in this, make sure that everyone gets what they want, and do so in a way that comes out aesthetically pleasing. This sounds much harder than it actually is. I believe we can do this, and I believe that in the end just about everyone will be happy with the results. We just need to calm down and work together. Sven Manguard Wha? 21:58, 23 February 2011 (UTC)
I agree with the gist of your post, and suggest that it should be a foregone conclusion that, if FPs and FSs get mainpage space, so does FL, which is equally worthy. But the design portion of the FP/FS proposal was flawed because FL was left out, and had everything been weighed at once, the conclusion might have been different. I prefer all of Sven's mockups to the confusing notion of alternating days, and think FL most certainly is ready for a daily shot. SandyGeorgia (Talk) 22:08, 23 February 2011 (UTC)
Note, there seems little point in "emergency layout" discussions. The FL proposal should continue to its natural conclusion, and the result of the FS proposal should remain valid, unless someone can prove that it is somehow nullified. The Rambling Man (talk) 22:10, 23 February 2011 (UTC)
And note, the design wasn't flawed because it incorporated lists soon into the FS proposal. Adam Cuerden ensured it would with his technical solution. The Rambling Man (talk) 22:15, 23 February 2011 (UTC)
(edit conflict) I think that's where we need to be. FS has consensus to get some real estate on the MP. Now we're seeing if FL has the same consensus. If both are established in the affirmative, then the rest is just the details; annoying, bothersome, better handled by anyone on the planet that's not me details, but just details. The basic idea of 'FL's on the mainpage, yea or nay?' cannot be allowed to get lost in a debate on the exact specifics, which can be left to various stakeholders including Raul, SG, TRM and others to figure out, and then should be a snap to get any more consensus that would be needed for, once a solid consensus in favour of granting both processes some form of real estate is demonstrated. Courcelles 22:20, 23 February 2011 (UTC)
Then someone should inform the FS people their work and consensus was effectively a waste of time. The consensus to finally put something other than FA and FP on the main page has been established, but all the technical work, as it turns out, despite consensus, has been wasted. The Rambling Man (talk) 22:22, 23 February 2011 (UTC)
Mainpage design isn't my strongpoint: I initially stayed out of the discussion, other than questioning potential design issues at FL, because I thought FS would only be sharing some of FPs space at the bottom of the page. I misunderstood from the get-go. So I'm in the unfortunate position now of opposing the process I find most worthy of being on the mainpage along with FAs, because of what I still view to be a faulty conclusion from a proposal which did not contemplate good mainpage design with inclusion of FL from the beginning. I suspect this is the last time I'll stick my neck out to stick up for FL, though, and I should move along now. SandyGeorgia (Talk) 22:26, 23 February 2011 (UTC)
Sandy, I don't know why you'd feel such indignation. You followed Raul to oppose the proposal despite him supporting an identical proposal. We then discussed the fact that FS and FL worked together, to an extent, to develop a mix-and-match technical solution. This was still unacceptable to Raul (and you) but not to the community who supported it wholesale. FL then worked hard to ensure their similar proposal had high quality in mind, minimal expectations with one list a week, and a controlled selection system. All of this is effort is truly laudable and the FL community should be recognised for coming together (along with Sven and Adam from FS) to propose a coherent solution. Suddenly, in the middle of it all, we get spanners. I don't want this to ever be the last time you stick up for the FL community, but we've been second cousins, twice removed from FA for so long that given an opportunity to be on the main page, we grasped it with both hands, and all twelve fingers. We wanted to assure quality, we wanted to be non-controversial, we wanted a simple plug-and-play technical solution, and it all seemed fine. Then all Hell broke loose. The Rambling Man (talk) 22:34, 23 February 2011 (UTC)
No longer under consideration.
No longer under consideration.
No longer under consideration.
(undent) Explained above. FAC, DYK, ITN-- we all get criticized when we put a mistake on the mainpage, yet FL says they can only be ready on a limited basis, and there were two piecemeal proposals that resulted in an ameteurish failure to look seriously at design (compounded by misunderstandings). Either FLC is ready or it's not; if they are, let's do it with professional design. If you think your work isn't ready for prime time, and want to be featured only once a week, in spite of having more than 1,300 FLs, something is wrong, and you are asking for an exemption from scrutiny that other processes are not afforded. SandyGeorgia (Talk) 23:51, 23 February 2011 (UTC)
Indeed FL are ready on the basis of one day per week, just as the community has already accepted that FS are ready on the basis of two days per week. Your suggestion that there was an "amateurish failure" to look seriously at design is ill-informed - I have examined dozens of different design concepts for flaws, browser compatibility, screen resolution, and accessibility in the past week and you can see some of them by following the numerous links at User:RexxS/MainPageFL - and I'm only one of many editors who have put work into ensuring that this proposal had a sound, well thought-out rationale before it was proposed. The FL community has even anticipated the need for flexibility to fit in with varying design decisions made by others. Compare these candidates with these condensed versions to see that FL is capable of fitting in with other featured content, whether a short amount or large amount of text is required. If you want professional design, we'd better hire a professional web designer, because all we can actually count on is what we unpaid amateurs are willing to volunteer. If you don't think Adam Cuerden is up to the job, I'd be happy to hear who you would prefer. I think you can assume that the work is ready for "prime time" because the proposal has been made; yes, the proposal is asking for only one day per week and I really would think that the very people who have spent so much time working in the area would be the best judges of their own resources. The only thing that is "wrong" is that the FL community has made a modest proposal that they can guarantee the quality of, rather than running the risk of 'biting off more than they can chew', and it is unfortunate that it does not fit with your own view of what should have been proposed. I apologise for being blunt about that, but I hope you can accept that not everyone will agree that a scheme which varies its content from day-to-day is automatically a recipe for poor design. --RexxS (talk) 01:14, 24 February 2011 (UTC)

Content is king. Get the lists on the front page at what ever rate makes sense (in terms of rampup). The object purely on the basis of design is putting the cart way ahead of the horse. Also, it reminds me a little of the object that they should have a whole TFAR process with full complexity and structure and complicatation, right from the gitgo, rather than just getting going with what thye knew were winners and working up to some TFA like arrangement if and how warrented. Let's pilot people. Let's roll!!!

Andy and the FS people and the FL people have put thought and work in and have some sort of structure. Let's try it out, rather then getting in one of these incessant wiki yak-yak loops. It's been freaking 10 years. Let's grow or die. We are losing all kinds of content creators and emphasis on content and some fresh air like this would really be great to get us growing again.TCO (talk) 23:51, 23 February 2011 (UTC)

Just giving you fair warning. I've got a new batch of mockups coming in very soon that I believe will solve every problem. They look fantastic! Sven Manguard Wha? 01:13, 24 February 2011 (UTC)
  • How do these look? This is a flexable setup that uses enough shared resources as to make coding feasible, get's everyone what they want, and looks excellent. Sven Manguard Wha? 01:49, 24 February 2011 (UTC)
Your new mock-ups are startlingly similar to what I had in mind. (I'd planned to work on mock-ups of my own, but I now see no need.) The only major change that I recommend is splitting the featured list into a separate box with different coloring (perhaps orange), due to the lack of a thematic connection.
Excellent job! —David Levy 02:59, 24 February 2011 (UTC)
I've been informed that if I proposed that the coders would flay me alive. Sven Manguard Wha? 03:15, 24 February 2011 (UTC)
Pardon? —David Levy 03:34, 24 February 2011 (UTC)
  • I have the feeling that the FA folks is just trying to prevent FLs from appearing on the main page at all cost.—Chris!c/t 03:10, 24 February 2011 (UTC)
    • I don't get that feeling. What I do see is that we all have the same general goal (getting FLs on the Main Page, along with Featured Sounds), but different visions regarding how that will be accomplished. Dabomb87 (talk) 03:59, 24 February 2011 (UTC)
    • I have the feeling that Chrishmt0423 isn't reading. SandyGeorgia (Talk) 04:01, 24 February 2011 (UTC)
    • If my reading is correct, and it may not be since I haven't read everything that transpired in the last few hours, what Raul and Sandy did in FL is a slightly more agressive form of what Howcheng did in the FS vote. Howcheng supported, but stipulated the condition that he'd oppose if it didn't look good in the end. Raul and Sandy opposed, but stipulated they would support once they had assurances that it would look good. In the end, it's going to look good and it's going to function. The idea of an Fa conspiracy is a tad... absurd. Sven Manguard Wha? 04:15, 24 February 2011 (UTC)
      • Thank you; at least someone still AGFs. And it will have my support as soon as the design issues are resolved (which will not happen by ignoring the fact that the original proposal was incomplete, hence flawed, and didn't give adequate space to FLs). SandyGeorgia (Talk) 04:20, 24 February 2011 (UTC)


Sven, are you still working? I don't see Raul's proposal. SandyGeorgia (Talk) 06:41, 24 February 2011 (UTC)
For the life of me I can't seem to find Raul's link. I saw it before but don't remember which comment it's in or the exact layout he recommended. I won't be around tomorrow (flying) and really shouldn't have been around yesterday (midterm studying) but I can do it Saturday if you find me the link. Sven Manguard Wha? 04:14, 25 February 2011 (UTC)
You can find it mid-way down in this section of his talk page. Nomader (Talk) 18:24, 25 February 2011 (UTC)
  • I think a daily TFL would be the way to go; there are nearly 2k of them, and nearly one promotion each day, which is more than enough. I really don't like the idea of two FPs, though, even with better aesthetics the idea seems kinda... weird. Adabow (talk · contribs) 09:06, 24 February 2011 (UTC)
I'm not in favour of a daily TFL, a sentiment shared by at least one of our FL directors, probably more. I think the original proposal is best in the short term, and I don't see why it would necessitate a double FP slot on the other four days. Medium term, I believe that FL and FS could share a slot 7 days a week. Long term, daily slots for both will hopefully one day be feasible, and I have made a start on that sort of design in my userspace, based on Raul's ideas.
But for now, I think we should learn from the FA experience. FA struggles to maintain the necessary reviewer levels, but TFA runs smoothly. FLC isn't much smaller than FAC, but it is smaller, so would presumably suffer a greater hit if it were on the page daily. FSC simply wouldn't cope. For those processes to be able to sustain daily updates, they need to fuel growth, which in turn would be best achieved by main page exposure. An all-or-nothing approach is not the way forward here. —WFC— 11:04, 25 February 2011 (UTC)
  • TWO FP A DAY IS NO LONGER UNDER CONSIDERATION Clearly poor communication has plagued these discussions. The two FP a day idea effectively died with Howcheng's comment above at 06:18, 25 February 2011 (UTC). Right now the current idea we're working with is that the purple bar is the only are effected by this change, as follows: For four days, it will remain one long bar with a single FP. For the other three days, it will be split 55/45 (same as green/blue) with an FP on the 55 left side, and an FS or FL on the 45 right side. The coding would be done in such a way that splitting the boxes would be automated, and preparing FPs would be unaffected. Sven Manguard Wha? 22:10, 25 February 2011 (UTC)
This sounds good. I think the bottom mockup image should now be removed to avoid confusing people.—Chris!c/t 03:28, 26 February 2011 (UTC)

Specifics to be ironed out

Whatever design is being considered as acceptable to the community absolutely needs to include the fact that there will not be sufficient resources to generate one featured list per day for the main page. This is precisely why I wanted the initial proposal to start small and maybe grow. And it looks like Featured Sounds need only two days per week. So there's a fundamental discussion to be held. Either (a) the main page is allowed to be differently formatted on those days, (b) the main page uses consistent formatting but something else has to fill the space on the remaining four days a week, (c) we don't put FS or FL on the main page or (d) something else someone could suggest. The Rambling Man (talk)

I agree. I've broken this out into a subsection, as I believe it's an important point of discussion. My personal opinion is that we should start off with (a) until we've had time to develop and grow the processes. If it was possible to link the two boxes up for panoramas, I'm assuming it will also be possible to do this. Hopefully, the FS and FL sections will mature, and eventually be in a position to share a daily slot (one having 4 days per week, the other 3). —WFC— 19:03, 26 February 2011 (UTC)
As mentioned above, the current proposal is as follows:
  • The only section being altered is the horizontal purple box.
  • On all days except Saturday, Sunday, and Monday, the purple box will look identical to it's current form, with one box taking up the full width, containing one featured picture.
  • On Saturday and Sunday, the box will be split into two, with a width ratio of 55/45, identical to the ratio between the green and blue boxes, with the 55% side on the left, identical in width to the green box. The larger box on the left would contain a featured picture. The box on the right would contain a featured sound.
  • On Monday, the box will be split into two, with a width ratio of 55/45, identical to the ratio between the green and blue boxes, with the 55% side on the left, identical in width to the green box. The larger box on the left would contain a featured picture. The box on the right would contain a featured list.
  • The coding would be as such that the width and number of boxes would adjust automatically, based on the day. Featured Pictures would not have to change their preparation process or code.
This is based on the comments by Howcheng, by the coders, and by the community. I hope this clears everything up. Sven Manguard Wha? 21:49, 26 February 2011 (UTC)
Okay, sounds pretty good to me. The only thing that seems to be a sticking point with some of the community is that there's an expectation that FLs should go from zero per week to seven per week, i.e. one a day. I've said a couple of times that the FL community are quite capable of committing to that right now, so those in favour of a one-a-day solution are not going to be satisfied by this proposal. The Rambling Man (talk) 15:55, 27 February 2011 (UTC)
If that change were to take place, it would require a separate proposal. I can almost guarantee that such a proposal would involve a totally new design solution. Sven Manguard Wha? 23:33, 27 February 2011 (UTC)
(I'm 100% certain that TRM meant to say that the FL community aren't quite capable of one a day) I'm fully behind the proposal in this form, and look forward to seeing the designs in action in the near future. If these sections start to outgrow themselves over the coming months, we can always make a second proposal later. —WFC— 07:54, 28 February 2011 (UTC)
Oops. Yes, I did mean we can't support one per day. WFC speaks for me here. The Rambling Man (talk) 09:06, 28 February 2011 (UTC)
It should be relatively simple for FL to move to 7 days a week in future, by claiming a new location. There's going to be some code that forbids FL on FS days, to prevent a main page train wreck, but I'll leave a note in the documentation saying exactly where it is and how to remove it. Adam Cuerden (talk) 11:27, 28 February 2011 (UTC)

there will not be sufficient resources to generate one featured list per day for the main page - can you explain what, exactly, is preventing you from doing this? You have ~1800 already (so that's about 5 years worth) and even if you don't promote many new ones over the next 5 years, you can always repeat them. (It's not a big deal, I promise!) Raul654 (talk) 22:45, 28 February 2011 (UTC)

They had a thread and a discussion on it and want to start small to learn the ropes and make sure they have good content out there. It's a freaking pilot, man! An experiment. We've gone through YEARS of not having the lists on the page at all. Go read the thread where they discussed it, but at the end of the day, the people doing the work want to start partially versus completely. Who cares even if they are wrong! Let them run the simple, positive improvement over the status quo that they have hashed out.TCO (talk) 04:11, 1 March 2011 (UTC)
Well, yes, we did discuss it as a community and agreed that we are not confident that we have the numbers of people to guarantee that one-per-day would be maintainable. In time, and hopefully main page exposure will increase interest in the featured list process, we would aim to support a similar process to TFA/R but right now, we do not feel that's possible. And no, we don't want to repeat main page content. I think you (Raul) seem to be one of the few people who actually likes that idea. It seems the community is content with our simple proposal, and now the technical issues appear to have been clarified, it would appear this solution is the right stepping stone on the path to TFL/R. The Rambling Man (talk) 07:19, 1 March 2011 (UTC)
I echo the above. The main page is littered with sections where it can be argued that we are systematically pushing our resources, often with a tangible effect on the output. While I can understand why my ITN comments below may have been taken as being too harsh, it's beyond question that we would ideally like to have a quicker turnover. While I think others have been equally harsh about DYK, it's undeniable that with anywhere between 28 and 36 a day, it's a struggle to be on top of the verifibility of each one. OTD runs pretty smoothly to be fair, but to a lesser extent is open to the same issues as DYK faces. Even TFA, which for all the quirks in the scoring process is an efficient system, is nonetheless labour intensive. And as far as I can tell, it has only gotten to the position it is in today through careful management, painfully learnt lessons, and the strong overlap of contributors at FAC and TFA/R.
With Featured List Mondays (FLM), we have an opportunity to try something different, and to take the lessons from TFA into account. We have the opportunity to slowly develop and tailor the relationship between FLM and FLC. We have the opportunity to start from a position in which we can build up a hunger for more regular representation, as opposed to being told that it has to happen. In which we can, starting from a low base, develop an understanding of just how much work it will take to become daily counterpart to TFA. In which we can build up a massive stockpile of blurbs. In which we can take our time to audit all FLs, and ensure that the proportion of lists that are main-page ready catches up with the corresponding ratio for FAs (a situation that we have made great progress on in the last two years to be fair). In which we can tentatively explore whether there is a benefit to a direct relationship between FLC and FLM, for instance whether it would be a net positive or a net negative if we encouraged nominators to draft blurbs. There are so many reasons for starting it this way, and provided the main page design is tight, little reason not to. —WFC— 09:59, 2 March 2011 (UTC)
Apologies for the severe lack of jargon —WFC— 12:48, 2 March 2011 (UTC)

In the News

Seriously? Two days after the Oscars, they're still the top news over the epoch-making events in the Middle East? Seriously? Cynwolfe (talk) 14:00, 1 March 2011 (UTC)

Wikipedia is not a news site. There is no "Top News". The Oscars might be the "Top Substantially and Reliably updated article relating to a current event." That's a bit unwieldy, though.
Feel free to [recommend other articles that would fit that bill, of course. APL (talk) 15:02, 1 March 2011 (UTC)
Stories are listed in the order they occurred (most recent at the top), not in importance. ITN is not a news ticker, we do not attempt to have a continual stream of stories. We highlight articles which have been updated to reflect current events, and the quality of the update is one of the key criteria. Feel free to suggest more stories at WP:ITN/C if you think we should be posting something that we haven't. Modest Genius talk 19:40, 1 March 2011 (UTC)
"Epoch-making events"? Somebody doesn't know what the word "epoch" means. 24.159.24.36 (talk) 19:45, 1 March 2011 (UTC)
Perhaps he means it like "Man, those events in the middle east really made my epoch! I'm going to be smiling for the next ten million years." APL (talk) 01:33, 2 March 2011 (UTC)
FWIW, his usage is correct according to Wiktionary. "Epoch-making" is synonymous with "epochal". -- Doctorx0079 (talk) 01:39, 2 March 2011 (UTC)

What a stunning example of why participation in WP is not expanding. Although I've been editing in fairly narrow content areas for more than two years, I've never commented on this page before, never had anything to do with "In the News" and don't know how it's composed — and this is the stone-throwing response I or perhaps a newbie would get? A simple link to the relevant procedural guidelines with a suggestion that I become informed or involved would've been smack-down enough. And please note:

  • Epoch-making: "of major importance; likely to have a significant effect on a particular period of time." Please check your own dictionary. Somebody's not as smart as he thinks he is, so perhaps I should take that into consideration in judging the quality of response here. Also, don't assume I'm a man. I'm not.

Finally, this is also an example of placing one's head firmly up one's own posterior orifice. (Shall I define either of those last two words?) If the purpose of "In the News" is to call attention to WP articles that provide information on topics currently, um, in the news, it makes us look juvenile and parochial (sense 2) if, in an encyclopedia, an article on an American award to actors is the best example of the content we can provide to illuminate current events. Cynwolfe (talk) 15:13, 2 March 2011 (UTC)

Love that phrase, "stone-throwing." It brings to mind Biblical passages such as "let he who is without sin cast the first stone."
As for the word "he," it is (as an erudite user like you will know) a commonly-accepted pronoun which in English may be used for a person of unknown gender. This is, naturally, why you referred to the anonymous, unknown-gender poster as "he" (quote: somebody's not as smart as he thinks he is). Of course, it is also why the other replies referred to you as "he"... no one assumed anything about your gender.
Speaking of that anon, let me apologize on behalf of all civil Wikipedians for his (or her) rather impolite response. I'm glad to see that most replies from registered users were quite helpful in answering your query, and the unhelpful one seemed mostly to be indulging in a bit of good humor.
So, back to the stone-throwing allusion. If new users are driven away from Wikipedia, I, like you, wonder how many of them leave because of sarcastic references to their intelligence ("Shall I define either of those last two words?"), unnecessary offense-taking ("a simple link would have been enough" (said link having been already provided by Modest Genius, above)), and unproductive self-censure ("it makes us look juvenile and parochial" posted outside the proper forum to which MG directed you). Truly, let he or she who is without sin... Aylad ['ɑɪlæd] 17:26, 2 March 2011 (UTC)
Modest Genius was helpful and responsive. The IP address felt the need to respond with uninformed snark, which was greeted with approval by the initial respondent ALP, whose remarks you find so helpful. These remarks were not censured for their inappropriateness, and yet when I reacted in kind, I was. But don't worry, I'll never bother to point out anything on the home page again. Cynwolfe (talk) 19:40, 2 March 2011 (UTC)
Hmmm. I did think APL was being helpful.
More productively, though, maybe APL's half-jesting initial comment points us in a good direction. The label "In the News" seems to be what misleads many, many people into making similar inquiries/complaints here. Have we ever looked into renaming the section to, say, "Current Events Articles" or something that looks less like the news ticker many believe it to be? Aylad ['ɑɪlæd] 20:21, 2 March 2011 (UTC)
And now I see the discussion above that is focused on exactly that question. Oops. Aylad ['ɑɪlæd] 20:42, 2 March 2011 (UTC)

To those scoffing at those giving importance to In the News of the Front Page

Featured list proposal

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
In reading this discussion as well as rereading the featured sounds discussion, I noticed that there were not a great number of people who commented on the simultaneously proposed increase in the number of featured pictures in either discussion. That seems to me that the discussion participants may have been confused with regards to that point even after the featured sounds discussion passed, as the increase to two FPs/day wasn’t really talked about that much. I’m glad to see, with Howcheng’s comment of 06:18, 25 February 2011 (UTC), that the idea of two FPs/day was taken off the table. I think a separate discussion would have to be conducted to see if the community likes that idea.

There is general agreement to put featured lists on the main page; that part is clear. How we shall do so remains to be decided, as there is no solid consensus on that. I’ll leave the section below open for discussion on that point. Once the few best designs have been agreed upon, another RFC should be conducted to poll the community on which “they” prefer. NW (Talk) 15:38, 3 March 2011 (UTC)


The initial proposal for how it would look.

Following on from the proposal to include featured sounds on the main page alongside a second featured picture on Saturdays and Sundays, I would like to propose the regular inclusion of a featured list on the main page. There are currently nearly 2,000 featured lists, and the recent changes in featured list criteria have ensured that all new promotions meet the highest standards, and that the older lists are being actively evaluated (via our WP:FLRC process) so only the best remain featured. We propose that, on Wednesdays, the "second slot" be allocated to a featured list, replacing the second featured picture. The FL community have provided their backing to this, as have the three FL directors. This would automatically benefit from the successful FS proposal, since User:Adam Cuerden's coding for that purpose will be written so it can easily be adapted to enable the appearance of lists on the main page.

The FL community have selected a set of existing featured lists; these provide an indication of the diversity of the project's very best work in lists. The directors would be responsible for the initial selection of lists for main page inclusion; the community would have two weeks to ensure that each blurb is of the highest standard for the main page. Once the process is more mature, we aim to move toward the WP:TFA/R model, which could either be integrated with the FA version or be a stand-alone process, managed by the FL community:

The following technical details are virtually a straight copy of those produced by Adam Cuerden, who made the same proposal for the inclusion of featured sounds. The requirements for FL inclusion in the same slot on the main page are identical.

Technical details
The following discussion has been closed. Please do not modify it.
  • The new section will use a modified form of the code currently used for FPs, adapted to allow multiple content types. The layout for FLs will be similar to FPs, though minor changes could be made for aesthetic reasons.
  • The box will be able to be set to several modes by assigning a parameter. I believe that the starting modes will be:
    • Featured picture: Emulates the formatting of the other box.
    • Featured list: One list, similar to the featured article
    • Multiple sounds: It will be convenient to allow for more than one sound, so that, for example, we can give a whole symphony, instead of just one movement. I suspect the maximum will be 4 or 5.
    • Video sound: We have a small number of these, but since videos and sounds use completely different formatting, it would be useful to have a dedicated mode.
    • Panorama: Suppresses the FP/FS/FL box to accommodate a wide image in the main FP box. This should only be used on FP days.
    • Featured list: The featured list project is interested in claiming a day on the main page, and it is trivial to code basic support in to help facilitate this.
    • Further modes could fairly easily be added if later needed.
  • User friendliness and accessibility can, if necessary, be improved by using a >inputbox< on the collective page for Today's Featured Whatever. This will preload the correct formatting for the featured content.
  • The Today's Featured Picture section uses special code and formatting to make things easier for machine readers to find out what Today's Featured Picture is. I will try and retain this feature for Today's Featured Whatever. However, since multiple content types are used, I cannot guarantee complete success.
  • I'll try to come up with a suitable way to automatically separate the different types of content into their own archives. This should not be too hard, as we can always check the mode, and show, for example, only those days that use one of the sound modes.
  • In the other main page columns, the left gets 55% of the width and the right 45%. This will probably be retained (and is easy to change if something else is desired).
  • Estimated coding time, including debugging: one month.

The proposal will run for approximately seven days, and like the FS proposal, will depend on a two-thirds majority for success. If this proposal passes, coding of the FL main-page inclusion will be put up for review, including a mock-up of it in action, and a "rubber-stamping" vote at simple majority to confirm its use. Thanks for your time and interest. The Rambling Man (talk) 17:03, 23 February 2011 (UTC)

P.S. The proposal will be closed around 17:00 (UTC) on 2 March. The Rambling Man (talk) 17:05, 23 February 2011 (UTC)

Discussion of proposal

Mockup of FLs sitting below DYK & TFA

I'm definitely in favour of including lists to the main page. But I'm not certain about including it in that particular spot of the page, for some reason. Featured Sounds make sense there, I suppose, as all the multimedia is kept together in one place. I guess I just feel prosaic content belongs higher up on the page. I think it would look kinda weird to have FA in one corner, and FL in the other... That's just me though. --Dorsal Axe 17:13, 23 February 2011 (UTC)

Well, the coding proposal allows for the list to be placed on the left-hand side on the main-page, under the featured article/DYK, if that would be considered acceptable to all parties. The Rambling Man (talk) 17:19, 23 February 2011 (UTC)
I just saw the other draft on your page Rambling Man. Left alignment is better in my opinion. I support this proposal, by the way. – Novice7 (talk) 17:23, 23 February 2011 (UTC)
As I say, the proposed coding caters for both! The Rambling Man (talk) 17:24, 23 February 2011 (UTC)
Thanks for the quick response. I like the look of that mockup you posted on my talk page (might be worth posting that here). It certainly makes more sense to have it left aligned, and I'm happy to accept that. --Dorsal Axe 17:26, 23 February 2011 (UTC)
No problem. I've added a small thumb here. Not wishing to repeat myself too many times already, the proposal supports both configurations! The Rambling Man (talk) 17:31, 23 February 2011 (UTC)
(edit conflict) I absolutely agree with this proposal. – Novice7 (talk) 17:33, 23 February 2011 (UTC)
  • Support The FL process has developed beyond recognition from the sorts of lists that made the grade in 2006. Nowadays we have a large, diverse stockpile of high quality material, that is worthy of being featured on the main page. —WFC— 17:22, 23 February 2011 (UTC)
  • Support discussed above. – Novice7 (talk) 17:33, 23 February 2011 (UTC)
  • Support: There is a large selection of high quality lists covering a variety interesting topics, and they certainly have as much of a right to be on the Main Page as featured pictures and sounds. Hopefully this will inspire people to create new Featured Lists as well. BigDom talk 17:36, 23 February 2011 (UTC)
  • Support per all above. --Dorsal Axe 17:39, 23 February 2011 (UTC)
  • (edit conflict) Support The FL process has finally matured to the point where it's appropriate to include them on the main page. We've come a long way since the process first started, and I'm more than happy to support. Nomader (Talk) 17:40, 23 February 2011 (UTC)
  • Support Good work deserves to be featured, and the samples I looked at from the subpage linked above were very good work. Sven Manguard Wha? 17:45, 23 February 2011 (UTC)
  • Support Wiki needs to grow or die. I see the general having of more types of featured content on the front page, very good. Not just for what we deliver to our readers, but for how it motivates us to up our game, knowning that we will have "front page" view. I know that runs through Sandy's head all the time. It is a good influence on the content work and even spreads beyond featured work itself. Lists are something we've been figuring out, and still are (are they "good" or "bad", how do we make them best use for the reader, what are the boundaries of list and article.) I think getting stuff to front page, will end up helping us work through these things and just improve overall as a content source. The simple way of starting with just a few features, and of picking the clearest best stuff, without a lot of upfront process, makes sense. We can evolve from there, but starting simple and "certain to succeed" makes sense. TCO (talk) 17:46, 23 February 2011 (UTC)
  • I supported putting featured sounds on the main page, but I never supported a second featured picture, nor was that ever mentioned in the proposal (such things were explicitly left to be decided later). Frankly, that would look very stupid and I oppose it. I support putting featured sounds on the main page, and featured lists too, if we can find a non-wonky way of doing it. Raul654 (talk) 17:47, 23 February 2011 (UTC)
    To quote the third sentence under "Featured sounds vote" (above) "The basic proposal is that a second featured pictures section is added to the main page. On Saturdays and Sundays, this will become a Featured sound section instead." Don't know how you can say that a second featured picture was never mentioned in the proposal, Raul. BencherliteTalk 18:07, 23 February 2011 (UTC)
    Yes, I missed that part. I was looking at the mockup, which apparently only applies 2 or 3 days out of the week. What I'd like to do is find a non-stupid solution that makes everyone happy, like the 2x3+1 layout I mentioned on my talk page (featuring lists, sounds, and pics every day of the week, in their own dedicated panes). Raul654 (talk) 18:13, 23 February 2011 (UTC)
  • Oppose for now, per Raul. If the design issues are sorted out, and Raul switches to Support, my !vote can be considered the same as his. SandyGeorgia (Talk) 17:53, 23 February 2011 (UTC)
To summarize and update my position per the capped commentary below. I do not support the current proposed layout and design: I do support FLs on the mainpage. I'm glad to see discussion progressing now towards rationalizing the two proposals (Sounds and Lists) towards a mainpage design that will most benefit our readers. My "oppose for now, per Raul" was only because I will be traveling and won't likely be able to weigh in as this is finalized, and I will fully support once the design issues are worked out. SandyGeorgia (Talk) 18:45, 25 February 2011 (UTC)
Capped to start over and attempt to clarify
The following discussion has been closed. Please do not modify it.


    • Update, per significant and extended discussion at User talk:Raul654 and on this page, in subsequent sections. My suggestions (below, now struck) to cap this proposal and re-start a new proposal were based on a misunderstanding (I didn't realize the FP/FS proposal was closed, and thought we needed to re-examine the entire layout proposal to incorporate all three in an integrated design-- FP, FL and FS). It remains my contention that if Sounds go on the mainpage, certainly, Lists are worthy. However, considering this dicussion, I am now opposing for a stronger reason. There seems to be some misconception that we can fiddle with the mainpage, with poor design, to accomodate the members of the various featured processes, and this is fundamentally flawed reasoning. The mainpage is for the benefit of our readers as much as, if not more than, our editors, and poor mainpage design to accomodate processes who claim they aren't quite ready for full main page exposure just smacks of amateurism. If all of these processes are ready for the mainpage, they should be prepared to adopt a design that benefits our readers and is smooth and professional in appearance, and the entire proposal should be considered at once, not piecemeal. I regret having to oppose the inclusion of a worthy featured process on the mainpage, but y'all can't have your cake and eat it too. DYK, ITN, FAC-- we all get criticized for mistakes we put on the mainpage, so either you're ready for prime time or you're not, but it you are, it should be a well designed implementation, not fiddled with every few months. Sorry, but I think the argument that FLC isn't ready 1) is just wrong, and 2) will result in an amateurish-looking mainpage, and 3) seems to indicate they don't think they should receive the same scrutiny for mistakes as DYK, ITN, and FAC do. I suggest that you all get your heads together on design, and still say that once Raul supports, I support-- my concern is not that FL doesn't belong on the mainpage, but that the mainpage is to serve our readers, and FLs are either ready or not. I'm sorry if that means that FL is paying the price for a strategic mistake in the way FP and FS put forward their proposal, but we still must put the priority of having a professional looking mainpage above other concerns. SandyGeorgia (Talk) 23:43, 23 February 2011 (UTC)
      • Addressing more of the malarkey raised about FL not being ready for more than once a week raised below. FL has 1,900 Lists; when I came to FAC as delegate, it had 1,700 articles and 10% of them had not been reviewed yet for compliance with new inline citation requirements per the Siegenthaler incident, and TFA/R was not in place, yet we somehow managed to put an FA on the mainpage every day. With that many FLs, if FL is saying they can't have one article ready per day, considering the high number of FLs available, then they're implying a problem which might indicate they're not ready for mainpage at all. The notion that we have to accept a previous proposal, because FP and FS failed to inlcude FL in a comprehensive, sensible mainpage design is flawed. The mainpage is to serve our readers, not the insecurities of one process that wants to avoid mainpage scrutiny by putting forward only "perfect" articles once a week, in a sub-optimal mainpage design. Sven is hard at work on sensible design proposals: I hope that FL and FP and FS show more gratitude to him than FL has shown others who worked hard to promote a directorship for FLC years ago, and to get FLs on the mainpage, and that we can now consider design proposals rather than self-interest and pile-on "voting" from involved members. If any of you think that 60 supports in one discussion will hold up to broader consensus from viewership that a bad mainpage design will get, think again. SandyGeorgia (Talk) 02:36, 24 February 2011 (UTC)
        • How about this bit of malarkey then: "If the proposal gains traction, I don't see any reason we couldn't adapt the already-existing page at WP:TFA/R for inclusion of Lists once a week. 17:06, 21 February 2011 "[3]? So two days ago, there was no reason not to include FLs once a week. Today, it has to be seven days a week or nothing because "[FL] are implying a problem which might indicate they're not ready for mainpage at all" - although that problem was invisible two days ago. Of course, a cynic might offer different explanation: FL is implying nothing of the kind and the proposal of one day a week is a sensible step that ensures that the human resources available can keep the quality high; the scare-mongering of non-existent (yet implied problems) is fabricating an illusion to discredit the proposal without a shred of evidence; and the only difference between two days ago and now is that a proposal that made FLs a small part of the TFA process was acceptable, while a proposal that gave FL an independent slot is not. Fortunately, nobody here is so cynical that they would take that view. So we assume good faith and take these objections at face value. Sandy is quite wrong to claim that "FP and FS failed to inlcude FL in a comprehensive, sensible mainpage design". FP did not even take part in the process and here's a familiar quote "The basic proposal is that a second featured pictures section is added to the main page. On Saturdays and Sundays, this will become a Featured sound section instead. ... As a further beneficial side effect, the code to make that possible can easily be adapted to have other additions to the main page. The Featured List community have expressed an interest in Wednesday, for example." This is from the Featured sounds vote proposal at the top of this very page. The design details are spelt out with clarity in the section 'Technical details', so I don't need to repeat them here. I would ask, though, what parts of the design proposed by Adam does she object to? It may be helpful to point out that the proposal including the design details garnered over 50 supports, a couple of conditional supports and an oppose (if we leave aside the editor who ironically voted 'oppose' to oppose voting). I would like to know though what principle is relied on to suggest that we don't have to accept the proposal that closed yesterday with such near-unanimous support (please don't let it be IDON'TLIKEIT). What Sandy describes as the "insecurities of one project" are actually a sensible evaluation of the best way to proceed. There's no harm done if FL is not stretched to capacity in supplying one list per week. There is a real potential for problems if seven lists per week were to overstretch that capacity, and it is reckless to demand that they do so, against their own realistic estimates. Perhaps Sandy could be encouraged to take part in the FL process for a while to give her a better sense of the resources available there? Let me assure Sandy that I am certain all of the FL community are grateful to Sven (and it would surely be churlish to suggest otherwise), just as they are grateful to all who have worked hard to get FLs on the main page. I would be only too happy to start considering design proposals consistent with the whatever consensus emerges here, and I'm looking forward to Adam's preliminary efforts. And if Sandy thinks that 60 supporters are going to change their minds when a 'bad design' strawman is waved at them, she needs to think again. --RexxS (talk) 05:33, 24 February 2011 (UTC)
      • First, how about you read that whole discussion, and not selectively quote one piece of it. Factor that there was a misunderstanding about what was being proposed, and I thought FL was proposing sharing space with FA, which I had no objection to (in other words, I have never objected to FLs being on the main page, but hadn't read the FP/FS proposal). Had the whole proposal for mainpage changes been integrated and presented more coherently, those misunderstandings could have been avoided. There is no need to stretch AGF when the written word is all there.

        Second, 50 supports is nothing in a proposal of this scale, and won't hold up if we put up a bad mainpage design because of this piecemeal approach. All that is being asked for here is a coherent approach to the design change that will incorporate all featured processes onto the main page, yet the discussion is dominated by intransigence about the design issues, independent of the fact that the content has support.

        Third, yes we do all have to do the best we can to not muck up the main page design because of piecemeal and poorly supported proposals (sorry, you may think 50 is a lot, but was it posted to a general discussion board, and how many would re-evaluate if they now knew that the design is again being tweaked because one process, FL, was left out?) Deferring a rational look at the big picture will only buy problems down the road.

        Reasonable editors can disagree, but mainpage design need not be compromised. FL has significantly more Lists than FA did when I became delegate, and they have three delegates, and they have no shortage of participants. If they aren't ready with 1,900 Lists, then they aren't ready period, and there is no reason to compromise mainpage design and then have them come along three months down the road, realize they are ready, and want to change the design again. Out of 1,900, 30 per month is about 1.5%; if they don't think that they have 1.5% of their Lists in good shape, then there's a bigger problem (which I don't believe to be true, and we never put "perfect" content on the mainpage-- articles sometimes improve while on the mainpage, and DYK sure isn't perfect, nor is ITN). I am quite familiar with the process and participants, thank you, and they are in much better shape to put up a daily list then FA was three years ago, in terms of numbers of lists and participants. We should all be working to present the best possible design of the mainpage, not to cater to the concerns of one process that they might not be ready. The way these proposals were presented looks a bit disingenuous on all sides, with deals being struck as to who will share space with whom, instead of presenting a rationale proposal to get all featured content on the main page with optimal design.

        Finally, the piecemeal proposals were a poor strategy; we should separately consider whether we want additional content on the mainpage (which has support), and then adopt a coherent design. Cart is before the horse here, and the end result has been unfactual FA bashing. I liked your edit summary, btw-- lots goin' round, and most of it seems to be aimed at FA bashing on the FLC page and talk pages-- wholly unfounded, since no one from the FA process has opposed in principle, only on the design factors. SandyGeorgia (Talk) 06:22, 24 February 2011 (UTC)

        • Optionally, you could read the whole discussion. It's there at WT:Featured list candidates/Archive 15#Featured list on Main page. For example, at 22:34, 21 February 2011, here's TRM in response to you: "we never proposed to take over an FA spot. Not for a moment. We always said we'd share the second FP space on Wednesdays only". Which bit of that did you manage to misunderstand? Heck, you you could even read the FS proposal above which says the same thing, or Talk:Main Page/Archive 156#Featured sounds proposal where Adam tells us "there's about 10 to 15 templates involved in a backend, and, while I can adapt some things from the existing FP code, there's going to be a lot of adaptation needed to set up a Featured Sound/Featured Picture backend, and I suspect that I'd have to base FL or FT on completely different code. So, you know, it's just not practical for me to try and move forwards more than one proposal at a time" or "People who want other Featured content on the main page are, of course, welcome to make such proposals, but please do so under a different heading" or "if we try to discuss them all at once, we're going to get nowhere", etc. [4][5][6] I do understand that you genuinely missed what was being proposed by FS, but it is utterly unfair to characterise the FS and FL proposals as "piecemeal" when the person who is volunteering to do the coding was telling us that for practical reasons FL [should] make a separate proposal. You will also read in this proposal that this discussion is to establish the principle of featuring lists on the main page. A separate process and vote will decide on the detail of the design, and you can have your rational look at the big picture when we have agreed what should be in the picture.
        • I'll remind you again that on 21 February you had no objection to 1 day per week on grounds of "they aren't ready period" then. If the the frequency of FL appearing on the Main page is a problem for you, then discuss with TRM what frequency of appearance the FL community is comfortable with. It is not reasonable to demand "7 days a week or nothing" based only on your misconception that the main page has to have the same look every day. It doesn't. --RexxS (talk) 13:55, 24 February 2011 (UTC)
  • Have I missed something here? Where are we proposing a second featured picture? —WFC— 17:55, 23 February 2011 (UTC)
    The very first sentence of Rambling man's proposal: Following on from the proposal to include featured sounds on the main page alongside a second featured picture on Saturdays and Sundays Raul654 (talk) 17:58, 23 February 2011 (UTC)
    This was in the FS proposal, and has been agreed by the consensus of the community. We just followed in its footsteps... The Rambling Man (talk) 18:01, 23 February 2011 (UTC)
    (e/c) I have to admit to being confused as the "technical details" here are virtually identical to those of the FS proposal. The screenshots are mockups, as stated, and the coding proposed by User:Adam Cuerden in the successful FS proposal would be the same as that used for FLs. The Rambling Man (talk) 17:56, 23 February 2011 (UTC)
    If the design issues are sorted out to Raul's satisfaction, I'm a support (I also agree that pictures and sounds should be on the mainpage, but only if Lists are as well), but working out the design issues is crucial in mainpage proposals. SandyGeorgia (Talk) 18:04, 23 February 2011 (UTC)
    Well, Raul supported the design of the FS proposal, and that's identical to this one, which he now opposes as being stupid. I guess we'll have to see what the remainder of the community think! The Rambling Man (talk) 18:07, 23 February 2011 (UTC)
    You're mis-characterizing my position. I support putting featured lists and sounds on the main page, but I think the proposed layout is terrible. And I would have opposed the featured sounds proposal for the same reason too, had I read all the fine print. Raul654 (talk) 18:16, 23 February 2011 (UTC)
    It wasn't fine print. It was the second paragraph of the proposal. The Rambling Man (talk) 18:19, 23 February 2011 (UTC)
    Arguing what Raul missed or didn't in the proposal now won't be as productive as working out the design issues. There is support for including the content: the question is how. My !vote is contingent upon working this out with Raul because I will likely be traveling as the details are worked out, and if that occurs, please count my !vote as the same as Raul's. SandyGeorgia (Talk) 18:24, 23 February 2011 (UTC)
    I think the FP mention should be stricken altogether from the proposal; what we want to do on non list days is irrelevant as far as lists themselves are concerned. —WFC— 18:22, 23 February 2011 (UTC)
    Why not just HAT this proposal and start a new one with a sensible layout? Raul654 (talk) 18:26, 23 February 2011 (UTC)
    I think that's a much better way forward. It's clear that some version of the proposal has support, but we should not separate that from design, which is crucial to discussions of mainpage proposals. I agree that starting over is the way forward, focusing now on design, given that the support is there. SandyGeorgia (Talk) 18:30, 23 February 2011 (UTC)
    Well as this is Wikipedia, let's allow the community to decide. The Rambling Man (talk) 19:09, 23 February 2011 (UTC)
    I'm curious to know what you had in mind Raul. Something more akin to what we had for the 10th anniversary? --Dorsal Axe 19:08, 23 February 2011 (UTC)
    I think this makes a lot more sense than the current proposed layout. Raul654 (talk) 19:33, 23 February 2011 (UTC)
    That's the long-term goal, but this is meant to allow the first steps to be taken towards getting these established. Once the systems are in place, it can be expanded. Adam Cuerden (talk) 19:40, 23 February 2011 (UTC)
    That's a case of putting the cart before the horse. I think we're better off putting the best possible layout on the main page, and letting those systems evolve to suit the task, rather than choosing a sub-par one to suit the systems we have now. That's certainly how it worked when FA hit the main page back in '04. Raul654 (talk) 19:57, 23 February 2011 (UTC)
    Besides which, we'll be having this discussion again in a few months if we don't just Do It Now. SandyGeorgia (Talk) 20:04, 23 February 2011 (UTC)
    Yep, I think we all get the idea that you're in complete support of Raul! Since the FS proposal was allowed the dignity of being able to run to closure, it would be decent of the FA director et al to give the FL community a similar run. The Rambling Man (talk) 20:07, 23 February 2011 (UTC)
    If given the choice between bad option (the current proposal, which is a good idea with a horrible implementation) and worse one (the main page as it exists today), most people will choose the bad choice. I think they deserve a good option too. And Sandy brings up a good point, that if we don't do it right now, we're going to be stuck with a bad layout until maybe we have another big discussion at some point in the future. Raul654 (talk) 20:11, 23 February 2011 (UTC)
    Personally, I think, push-come-to-shove, with 1,989 FL's and something like six to seven more a week, and factor in an increase of participation once there is a main page slot, the FL process could produce five quality lists a week to go with the two featured sounds. (The reverse would be much more challenging, as there are less than one-tenth the number of FS). Though the utility of this idea is also because the FP people are generating pictures at a greater rate than they can run them, and it has been discussed before the value of main page slots to attracting image donations, and the detriment to the same in the year+ backlog and fairly opaque system. Courcelles 20:18, 23 February 2011 (UTC)
    While not my ideal solution, I think that's a very reasonable compromise that would alleviate my biggest objection (the two FP redundancy). Raul654 (talk) 20:47, 23 February 2011 (UTC)
    So what you're saying is that because you think the main page should have the same layout every day that any featured content has to be willing to provide content every day of the week? But as a compromise that you'd accept FL providing content 5 days a week, with FS 2 days a week? Have you considered asking the editors whose time you are volunteering whether they consider that realistic 'before making your counter-proposal? How about a counter-counter proposal: you've accepted that FS should be featured 2 days per week, (that discussion is closed above) - so it is clear that the main page will look different from day to day; why not spend some time explaining how you feel FS on two days per week and FL on one day per week ought to be realised to meet your aesthetic standards. That would at least give the community and the coders a push in the right direction to produce an acceptable solution. --RexxS (talk) 00:19, 24 February 2011 (UTC)
    Okay this is moving fast. Stop the presses, I have contingencies! (Don't stop the polling, just stop this line of discussion and give me about 10 minutes to churn out my mock up please. No reason for this to death spiral at the moment. Sven Manguard Wha? 20:14, 23 February 2011 (UTC)
    Discussion on visuals below. As I say below, I can keep on generating mockups when needed. You should be voting on the idea of FLs on the main page. We can fine tune placement later. Sven Manguard Wha? 20:37, 23 February 2011 (UTC)
  • Support In a best case scenario, we would be able to rotate the four types of featured content that never get any MP space (lists, topics, sounds, and portals) instead of running a second picture four days a week... but the proposal on the table is better than the status quo. (Not to mention the FT promotion rate is too low.) Courcelles 18:11, 23 February 2011 (UTC)
  • Support (obviously, given my involvement with FL). Featured lists have improved immensely in quality in the last few years and there is a lot of excellent material here that is likely to be of interest to our readers. BencherliteTalk 18:12, 23 February 2011 (UTC)
  • Support Looking at the example above, the list's lead he took is not really small by size. We must ensure we take FL with such size. The layout won't be ideal like above if the lead is small.-- ♫Greatorangepumpkin♫ T 18:28, 23 February 2011 (UTC)
  • Questions:
    1. I share Raul's concerns regarding the layout mock-up. Am I correct that this is merely a non-binding example (and we'll have an opportunity to propose/discuss alternative implementations later)? That was my impression during the previous discussion.
    2. Is there any special significance to Wednesday? I believe that it would make more sense to use Friday or Monday, thereby grouping together all of the special content (in a memorable/promotable manner) instead of needlessly switching back and forth.
    David Levy 18:32, 23 February 2011 (UTC)
    • Hi David, thanks for your questions. (1) the proposal above states "If this proposal passes, coding of the FL main-page inclusion will be put up for review, including a mock-up of it in action, and a "rubber-stamping" vote at simple majority to confirm its use." so yes, the mockups are precisely that, mockups, with scope to be modified. (2) No, not really, it was simply to provide natural breaks in the second FP listings. Your proposal has merit, so a Friday or Monday could well be a better bet. The Rambling Man (talk) 18:41, 23 February 2011 (UTC)
    • @David: There are many permutations of ways to lay out content, so for you and any others who want to see some examples, the page User:RexxS/MainPageFL has links to over a dozen possibilities - and that's just for the case of a Featured List in the same row as a Featured Picture. You can change your browser width and see the effect of different design decisions at different screen resolutions. I'm sure Adam Cuerden, who has kindly volunteered to code the changes if this proposal passes, would be happy to hear of any preferences from interested editors if we reach the second stage. --RexxS (talk) 00:33, 24 February 2011 (UTC)
  • Support - it should be possible to put FL on the left (by simply switching the locations of its and FP's box on those days), but that's a separate debate that can be had once the mock-up's ready. Adam Cuerden (talk) 19:05, 23 February 2011 (UTC)
  • Support - Regarding the second FP slot on the main page, that was on the FS proposal, which passed already. So, to oppose the entire FL proposal because they failed to read carefully what was in the FS proposal is unfair to us FL folks.—Chris!c/t 19:48, 23 February 2011 (UTC)
  • Support in principle. I'm no formatting expert and must bow to others on that subject, but to me FLs clearly deserve a place on the main page. You could make a strong argument that FLs, not FSs, should be getting on the main page twice a week. Giants2008 (27 and counting) 20:38, 23 February 2011 (UTC)
  • Popping-in-during-lurking-but-not-editing-sort-of-wikibreak-type strong support ... overdue. --Dweller (talk) 20:57, 23 February 2011 (UTC)
  • Support as an obvious addition to the Main Page. Both current proposals have my support. Imzadi 1979  22:48, 23 February 2011 (UTC)
  • Clearly, without-a-doubt support. About time. StrPby (talk) 23:13, 23 February 2011 (UTC)
  • Support this proposal to have a featured list on the Main Page one day per week. The FL community has spent a lot of time carefully examining resources, both in terms of number of FLs and volunteer time to prepare such material. I believe that the equity of having a range of featured material is now recognised. The community has already agreed to have featured sounds on two days per week, and I see no convincing reason why featured lists should be denied the opportunity to be featured on the Main Page as well. Additionally, I do not see it as productive for other editors to make counter-proposals in the middle of seeking consensus for the present proposal that do not respect the careful evaluations made by the FL community. The layout of the different types of featured content is obviously subject to community decision, but I would respectfully submit that this proposal is establish the principle, not the detail. --RexxS (talk) 23:58, 23 February 2011 (UTC)
  • Support — I'd say something, but I couldn't put it any better than RexxS did — KV5Talk • 01:56, 24 February 2011 (UTC)
  • Strong Oppose: The main page is not for everything...too much content makes it ridiculous-looking. No matter what, it would be better to avoid a new section and feature a list every so often in TFA. MonoALT (talk) 02:29, 24 February 2011 (UTC)
  • Support idea but only if later we have a layout prepared and consensus also supports that. /ƒETCHCOMMS/ 03:54, 24 February 2011 (UTC)
  • Support, though for now I presume this is just about havign lists in principle, rather than specifics or where it'd go. Wizardman Operation Big Bear 04:25, 24 February 2011 (UTC)
  • Support. Why not? Since there are almost 2,000 featured lists promoted, these featured lists have never appeared on the main page. JJ98 (Talk) 07:39, 24 February 2011 (UTC)
  • Support Someone get a spine and just do it! Lugnuts (talk) 07:45, 24 February 2011 (UTC)
  • Support in principle on the same basis as featured sounds. I don't quite understand the sudden layout issues, but I'm sure they can be resolved, even if it's more troublesome than people expected. Rd232 talk 08:06, 24 February 2011 (UTC)
  • Strong support The TFL principle, format is a bit off for me but that can be ironed out later. Adabow (talk · contribs) 09:02, 24 February 2011 (UTC)
  • Support THIS proposal in principle, subject to overall design considerations achieving consensus. Primarily agree with RexxS. Sandy's & Raul's concerns are muddying the waters. Support the 'idea' of FLs on MP, as well as FS; a separate discussion can be had regarding layout subsequently, if this proposal garners sufficient interest. Careful With That Axe, Eugene Hello... 12:22, 24 February 2011 (UTC)
  • Support, including the proposed layout. I prefer the FL on the left, but that's a minor point. I'd also be happy to see FLs on the main page more than once a week once the FL people feel they're ready. --Avenue (talk) 12:51, 24 February 2011 (UTC)
  • Support - I would love to see featured lists on the main page. ---My Core Competency is Competency (talk) 13:48, 24 February 2011 (UTC)
  • Support per duh. --Highspeedrailguy (talk) 18:00, 24 February 2011 (UTC)
  • Support as they are featured lists, and this will lead to further scrutiny on such lists that make it to the Main Page - the same as with FAs. As far as implementation is concerned, I kind of liked what we did for the 10-year anniversary at Wikipedia:Today's featured article/January 15, 2011 and would alternatively propose we do something like that on a biweekly or even weekly basis instead of an article. –MuZemike 21:23, 24 February 2011 (UTC)
  • Support Support the proposal on the Featured Lists people's own terms. I think its absurd that people outside FL are trying to determine how many FLs they should run a week. If they feel they should start slow then thats the way it should be. Acer (talk) 00:21, 25 February 2011 (UTC)
  • Support - We have many FLs, this'd be a great chance to showcase them alongside the other quality Featured content. —Ancient ApparitionChampagne? • 2:55pm • 03:55, 25 February 2011 (UTC)
  • Support - but i would like to see it start off with 2 FL a week, as the math works out nicer i think (3FP, 2FS, 2FL), and once more people taker part in the nomination procedures, FP should get squeezed out of the slot.--Found5dollar (talk) 14:57, 25 February 2011 (UTC)
  • I'll add my support to this one too. FL's need better publicity (and it'll give me the incentive to finish the one I'm working on). —  Tivedshambo  (t/c) 15:37, 25 February 2011 (UTC)
  • Support adding FLs to the main page. If this requires removing something else, my vote would be to junk DYK. *** Crotalus *** 16:54, 25 February 2011 (UTC)
  • Support FLs have come a long way and deserve to be featured. – SMasters (talk) 07:33, 26 February 2011 (UTC)
  • Support FLs on the main page (no issue with that at all). Not keen on two Featured pics on one day, but as that seems dead in the water, I'm happy to support. WormTT 11:37, 28 February 2011 (UTC)
  • Support In my view featured lists should have most of the time in the second slot though - I'm not sure that FPC is promoting 11 pictures a week these days anyway and the featured sound promotion rate is pretty low. JJ Harrison (talk) 08:53, 2 March 2011 (UTC)
  • Support. I am surprised that sounds get two a week and lists get one a week. Pics definitely deserve every bit of the extra four a week. I'd like a general understanding that some flexibility could be negotiated from time to time on that count—a little give and take among the genres (pipe dream). Tony (talk) 13:43, 2 March 2011 (UTC)
  • Support, if this discussion is still open :-) Lists of lists made me a Wikipedian; I love the idea. SJ+ 13:44, 3 March 2011 (UTC)

The above discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Wikipedia design

Can't somebody come up with at least the personal preference option to design your own skin? The standard is bland and boring, as are most of the other skins. There should be the option to self-design your own skin in your preferences.♦ Dr. Blofeld 20:17, 1 March 2011 (UTC)

You already can, see WP:SKIN and WP:CUSTOM. Admittedly you have to do it by modifying an existing one, but it's entirely possible. However, what does this have to do with the Main Page? Modest Genius talk 21:48, 1 March 2011 (UTC)
You don't have to base it on another skin; you can start form scratch by using MySkin, which is completely empty. Edokter (talk) — 01:05, 4 March 2011 (UTC)

Improving "Other areas of Wikipedia"

I feel that this could be easier to read -- perhaps a two-column table -- and could have better links. How do people feel about linking directly to the Wikipedia Signpost from here? I know it has long been considered a community-internal link, but the article quality is reliably excellent, and it's starting to be cited in other publications and research papers. I think we have a right to be proud of it and to promote it a bit more as part of the public face of Wikipedia. (Perhaps I should check with the Signpost editors to see if they would mind the extra traffic :-) SJ+ 13:47, 3 March 2011 (UTC)

Since when did the signpost become the public face of Wikipedia? I definitely never saw such a proposal and from some of the stuff I've seen there I would strongly oppose such a proposal. Speaking of opposition, since you're talking about improving stuff have you already searched and came across what happened last? time this was proposed? Talk:Main Page/Archive 152#Addition of Signpost Nil Einne (talk) 19:40, 3 March 2011 (UTC)

russell falls featured picture

todays featured picture looks very much like it's been photoshopped. it's possible that it's just a really poor quality camera or exceptionally slow shutter setting. regardless this picture looks like in game footage from an RPG or FPS Game. this picture can't do justice to the place it's of (presumably), and doesn't do justice to the featured picture section. i suggest that in future more care is given to picture selection, there are literally millions of better images and probably hundreds of better images of russell falls. i found this: http://www.wallpapers10.net/wp-content/uploads/2009/07/Russell_Falls.jpg

(and others) in a yahoo search taking all of 30 secs, and this picture is of smaller size, higher quality and much better composition. thats clearly my opinion but not on the merits of the place pictured, merely on the poor quality of the image used when other better photos are easily available as free for use wallpapers. user : teknotiss (for such a small thng i really couldn't be bother to log in) —Preceding unsigned comment added by 188.220.151.59 (talk) 19:13, 1 March 2011 (UTC)

It's a four-second exposure, not a photoshop. These issues were discussed at Wikipedia:Featured picture candidates/File:Russell Falls 2.jpg when it was made a Featured Picture 18 months ago. The images go up on the Main Page in a first-come, first-served basis in the order they were promoted (barring a few shufflings for anniversaries and to prevent two images of similar things on successive days). Modest Genius talk 19:37, 1 March 2011 (UTC)
ok thanks for clearing up the selection process. However it's still not a good shot of russell falls. Would anyone know why such a poor quality shot would be used? —Preceding unsigned comment added by 188.220.151.59 (talk) 19:57, 1 March 2011 (UTC)
Others disagreed with your assessment. You're welcome to participate in the selection process, thereby contributing to future decisions.
Also note that gratis and libre are distinct concepts; the "free" photographs that you found elsewhere might be the former and not the latter (in which case Wikipedia cannot use them). —David Levy 20:03, 1 March 2011 (UTC)

Well thank you david i know where to find the candidate pictures now so i can comment. I would note that being placed in an unobtrusive link inside the "More featured pictures" isn't ideal for getting people to comment on them, but thats for another thread i suppose. As for the gratis vs libre issue, well I agree, I just used that picture as an example of how many images there are and easy they are to find. It wasn't a statment of this should be used, more that this is a better shot and the current image looks bad on wikipedia's front page. — Preceding unsigned comment added by Teknotiss (talkcontribs) 20:25, 1 March 2011 (UTC)

If you want to take your own photograph of the waterfall and release the rights to it so Wikipedia can use it, we'd be most grateful...  狐 FOX  09:25, 2 March 2011 (UTC)
It's actually not incredibly easy to find a free image as plenty of people who have tried will tell you and while there are a fair number out there that we don't yet have I think you vastly overestimate how many there are particularly quality ones so your point seems somewhat moot. Incidentally the picture in question is also a featured picture on the Commons and Spanish wikipedia. Of course both have different criteria, in particular I believe the Commons is more concerned about whether it's a good photo (or whatever) rather then how well it represents the subject (which does matter to us). If I understand Commons:Commons:Picture of the Year/2009/Results/R1/ALL/Table correctly, this picture received 22 votes in round 1 of voting for picture of the year 2009 in the commons which considering the most was 61 votes and its relative position isn't something to be scoffed at. (Incidentally there was another picture of the same waterfall File:Russell Falls Mt Field National Park.jpg that got 21 votes that year). In other words, while you are entitled to your opinion, it seems quite a lot of people dont share your view of how bad this photo is. BTW while I have no experience with that particularly site, I wouldn't trust images on some random site like that to actually be free in either sense of the word. Note that the 'More featured pictures' isn't an attempt to get people to comment on candidates. While we welcome feedback we tend to keep that off the main page because readers (who the main page are for) aren't particularly interested in it. Note that by the time an image makes it to the main page, it's probably been a featured picture for over a year as somewhat has pointed out above. Nil Einne (talk) 16:33, 4 March 2011 (UTC)

"but yes, you are right"

This has nothing to do with the main page.
The following discussion has been closed. Please do not modify it.

is the phrase "but yes, you are right" grammatically correct? 190.51.160.175 (talk) 15:17, 4 March 2011 (UTC)

Substituting 'no' and 'wrong' in various combinations also works - so the phrase is grammatically correct, at least in colloquial (and possibly formal) English. Jackiespeel (talk) 15:42, 4 March 2011 (UTC)

  • This has nothing to do with the main page. Please read the very large banner that appears when you are in the edit window, as it's purpose is to direct you towards the correct place to post comments. Sven Manguard Wha? 21:51, 5 March 2011 (UTC)

I was answering the question - but could have redirected to either the 'English language talk page' on WP or the presently underdeveloped English Language wiki on Wikia. Jackiespeel (talk) 21:48, 6 March 2011 (UTC)

Or Wikipedia's language reference desk. Graham87 02:22, 7 March 2011 (UTC)

Perhaps there could be a mention in the header section to the effect that 'for language queries see (list).' We all have the occasional 'grammatical puzzle.' Jackiespeel (talk) 17:55, 7 March 2011 (UTC)

Is there any point to In The News anymore?

Issues regarding In the news

subheading added by David Levy 00:04, 3 March 2011 (UTC)

I'm going to unashamedly take this fourth opportunity (over 24 hours after my first attempt) to point out that in some parts of the world it is Thursday now. The Bahrain shootings happened last Friday, but at this moment are still on our main page as news. —WFC— 19:41, 23 February 2011 (UTC)

Yes, either it needs to be changed every six hours like clockwork or it's use is diminished considerably. Here's what the issue is:
In the News What's on my news tickers
  • Behgjet Pacolli (pictured) is elected President of Kosovo
  • A 6.3-magnitude earthquake hits Christchurch and the surrounding Canterbury region in New Zealand, causing major damage and at least 75 deaths.
  • Protests in Libya spread to Tripoli, as the government uses warplanes and mercenaries to attack the protesters.
  • In stock car racing, Trevor Bayne becomes the youngest person to win the Daytona 500.
  • The Iranian film Nader and Simin, A Separation, directed by Asghar Farhadi, wins the Golden Bear at the 61st Berlin International Film Festival.
  • Authorities open fire on demonstrators in Bahrain amid continuing protests across the Middle East and North Africa.
  • U.S. Will No Longer Defend Law Banning Same-Sex Marriage (NPR)
  • Gadhafi's Forces Maintain Their Hold On Tripoli (Essentially country is split East/West with Gadhafi controling only the west side) (NPR)
  • The confirmed death toll from Tuesday's magnitude-6.3 quake near the city of Christchurch rose to 75, and officials said it was almost sure to climb further. (NPR)
  • Democratic Party of Japan suspended the membership of Ichiro Ozawa, a shadowy political figure who once led the party, but who was indicted last month in a political financing case. (NYT)
  • Bahrain King in Saudi Arabia to Discuss Unrest (NYT)

I just ripped those headlines out, but they could be put into a different format easily. The point is that of the current ITNs, 1 and 2 are current, 3 is days outdated, 4 is two days out and not really long term news, 5 is almost a week old, and 6 is laughably old. The five I have are all recent, and can hold up for six hours until I check my news tickers again tonight and see what's changed.

Update more often or scrap the section. Those are the only two options that don't produce a net loss of quality in the main page. Sven Manguard Wha? 20:08, 23 February 2011 (UTC)

Per Sven. Update more often (and therefore be more diligent on what goes on the mainpage under ITN) or scrap. The Rambling Man (talk) 20:20, 23 February 2011 (UTC)
You're comparing ITN to news tickers, the purpose of which is to relay breaking news. The section's purpose, conversely, is to link to encyclopedia articles created or substantially updated to reflect recent/current events. Perhaps we can find a way to increase the turnaround, but the content can't be "changed every six hours like clockwork" unless the appropriate encyclopedia articles exist. —David Levy 20:24, 23 February 2011 (UTC)
I don't think this would often happen, or if Sven did it deliberately, but all five things Sven listed actually have articles that could contain the information. Too often a news ticker is over events that don't (or shouldn't) have articles... or ITN becomes "On the sports page", which as I like sports, I don't really mind, but the concepts aren't the same. Courcelles 20:28, 23 February 2011 (UTC)
Articles to link to from my selections, in order: the mentioned law, the Libya protests, the earthquake, the DPJ (and the minister), and Saudi - Bahraini relations (which should exist whether it does or does not.) Sven Manguard Wha? 20:34, 23 February 2011 (UTC)

ITN has its interesting quirks. It's not supposed to be a news ticker - and anyone who comes to us as their source of latest news is surely a rare individual. And as our processes catch up with things to deliver quality material eventually, we'll often have a much better article later, rather than sooner, which is a strength of ITN. If you catch my drift. Yes, it has its flaws, but they're part of its attraction. --Dweller (talk) 21:00, 23 February 2011 (UTC)

  • The section is called "in the news", not "today's main headlines"; ITN isn't a rolling news channel (on WP at least). People can go to wikinews if they want the day's top stories in wiki format. StrPby (talk) 23:23, 23 February 2011 (UTC)
@Sven the articles get updated as event goes on and are read over and over throughout the time they are on ITN. Just because it happened few days ago does not mean it should be removed. Go to ITN/C if you have a new item that you would like to nominate that is not on ITN yet. atleast do some research on what the section is or how its gets updated before complaining. -- Ashish-g55 02:07, 24 February 2011 (UTC)
So you're response to "the process needs to change" is "do some research on what the section is or how its gets updated before complaining". That's not at all helpful. My point is that if the ITN prompts are out of date, they reflect poorly on the main page. You could easily tweak the wording of the sixth one to reflect more current realities and then it would actually be "in the news" instead of "live, from last week's papers." Sven Manguard Wha? 03:19, 24 February 2011 (UTC)
  • Urm, yes there is. It's the only part of the main page I actually read or care about. MonoALT (talk) 02:25, 24 February 2011 (UTC)
  • I only read ITN as well. If more people edited Wikinews *cough, cough*, we could just have a bot update a small ticker at the bottom of ITN as well. But WN never ends up covering half the breaking news because not enough people edit there. /ƒETCHCOMMS/ 03:55, 24 February 2011 (UTC)
    • Every single person I talked to about Wikinews said that Wikinews was a waste of time, suffered from chronic corruption and ineptitude, and was even more hostile and partisan than Wikipedia. Why anyone would want to join that project is beyond me. Also I oppose importing content from other projects automatically. There's a whole bunch of things I'd trust bots to do on Wikipedia, but quality control is something that needs a human touch. Sven Manguard Wha? 04:18, 24 February 2011 (UTC)
      • Obviously you haven't spoken to many people, Sven. AD 14:45, 24 February 2011 (UTC)
        • I used to be a regular editor on WN, but gave up. It is a waste of time. Nobody reads it (because you can read free news just about anywhere) and, more importantly, a sizeable majority of the editors there are (or were when I left) more interested in bickering and power struggles than in writing, which means that when an article does get written, it has to wait so long for a review (because they have fully fledged flagged revs) that it's no longer news by the time it gets published. HJ Mitchell | Penny for your thoughts? 16:32, 24 February 2011 (UTC)
          • Sounds just like Wikipedia - except for the page views. AD 17:01, 24 February 2011 (UTC)
            • Actually Sven's spot on about Wikinews. Ugh, terrible place, even just reading the discussions there... Wizardman Operation Big Bear 04:38, 25 February 2011 (UTC)
    • If a bot was updating the main page with Wikinews content, perhaps more people would edit Wikinews... The ITN section itself doesn't make much sense to me. Wikipedia isn't supposed to be a news service, and Wikinews is. If there's going to be news shown, it really shouldn't be a Wikipedia effort. --Yair rand (talk) 09:29, 24 February 2011 (UTC)
      • Sven, maybe instead of judging Wikinews you should actually try it out, which you evidently have not. I was told last year that Wikinews is a horrible place. I later tried writing there, and it was fun. Is it annoying and disgusting at times? Yes, but it's about the same as here, except the smaller community makes the problems seem larger. I write news, not drama; that's the point of WN. Also, your quality control issue seems to be baseless because you don't seem to understand how Wikinews works. There is an independent review process conducted by approved experienced users and the frequency of crappy content published there is about the same as how often we get bad articles on ITN here. Why anyone would slander a project without even having tried it for his or her self is beyond me, Sven; maybe you should be asking some other people for their opinions instead of spreading around misinformation? /ƒETCHCOMMS/ 16:05, 24 February 2011 (UTC)
        • You assume that just because I don't edit there I know nothing about the project. Yes, I have not edited there, I freely admit that, but I have read the articles there, just like I've looked at the definitions in Wiktionary, the books at Wikibooks, the quotes at Wikiquote, and the collections of media at Commons. Wikiquotes is perhaps the best repository of quotes I've seen in any form. Wikibooks shows great promise. Wikitionary is pretty good but still outclassed by a few offline tomes, and if I expanded into another project from this one, I'd probably choose that. Commons, for all it's issues with communicating with the rest of the WMF family, is a damn good resource. Wikinews, however, I've never found adequate. Many of the articles on top importance stories, such as their article on the earthquakes, are okay, however my New York Times app brings me more stories that are better written and have more depth, at a rate faster than Wikinews does. When four months ago I was looking for things to do, I asked a few people about it, and the response was uniform, that behind the scenes it was often bitterly partisan, especially in the areas that I was interested in, and that their experiences made them not wish to return after their initial trials with it. I was advised to stay away from trying to write there, and my edit count there shows that I took that advice. I'm sorry that what I said caused so much drama, it could have been worded better, but I don't think that my assessment on the news quality or the backend drama is wrong. Sven Manguard Wha? 23:36, 24 February 2011 (UTC)
  • I particularly loved the time - in the middle of Jimbvo claiming historic artworks were Porn on Commons, in order to placate Fox News - that a Wkinews editor begged me to talk about historic arttworks, spent ays interviewing m for hours, then decided to give Jimbo three weeks to respond before the site spiked the story as old news because he didn't. Of course, they ran Jimbo's next press release on the topic,just left out all they got me to do. Adam Cuerden (talk) 01:11, 25 February 2011 (UTC)
  • (days old interjection) Having written about 10 pieces for it last year, I can say Wikinews does indeed suck giant balls, it does have some serious community based defects (and infact 1 giant one), however, ITN, and Wikipedia in general, has very much played its part in starving it of contributors, in the ridiculously lenient way it treats editors who obsessively and immediately write about crap which is totally NEWS and is never in a million years going to have any historic notability whatsoever, or their enablers who completely ignore basic guidance like EVENT and at Afd continually pull out fantasy nonsense like 'oh well we can always delete it in 6 months if it's not notable', which is so untrue its unreal. There are also editors out there who clearly get a massive buzz out of receiving their ITN credits, particularly single topic obsessed editors, so much so that they either don't know or don't care that this is an encyclopoedia, not a news dump, as they fire up yet another 2011..... redlink. One editor in particular doesn't even bother with the article creating part, he just continually nominates here, and then grants the credit to himself wen he gets lucky and is first on a genuine ITN topic. And that's his sole contribution to Wikipedia. Other than also violating basic image copyright (to illustrate said news stories). MickMacNee (talk) 17:21, 7 March 2011 (UTC)
  • In a few hours it'll be Friday in parts of the world. Are we seriously going to still have this thing on as news a week after the event? If this is par for the course, "In The News" should at least be renamed, either to something suitably vague such as "Recent Events", or something more descriptive, such as "Probably In the News At Some Point In The Last Few Weeks". —WFC— 06:29, 24 February 2011 (UTC)
  • Maybe "This week in the news" or as WFC said "Recent events". That's better. – Novice7 (talk) 09:41, 24 February 2011 (UTC)
WT:ITN is that way if you want to propose it. StrPby (talk) 11:16, 24 February 2011 (UTC)
We've had discussions of changing the name before, many people agree the name isn't the best but we've never had a proposal people agree on. Regardless, I've never seen any evidence for anything close to consensus for turning ITN into a newsticker and in fact plenty of people are strongly opposed to the idea. In other words, any proposal which treats ITN as a newsticker is dead in the water. Nil Einne (talk) 11:35, 24 February 2011 (UTC)
      • I never said I wanted a newsticker, only that my newstickers are far more useful that this section. As for changing the name, I think several people here liked "Recent News" as a replacement, perhaps offering up that might get consensus. Sven Manguard Wha? 21:38, 26 February 2011 (UTC)

I've never seen the point of a news section. We are not a news site, and we only report facts from stuff already reported... quite different from Wikinews, which does not have an origial research ban. Encyclopedias traditionally don't provide news, and imo only the highest quality articles should be featured on the main page. By their nature, current events are anything but. Removing ITN and maybe even linking to Wikinews will help increase participation there. AD 14:45, 24 February 2011 (UTC)

Wikipedia is not a traditional encyclopaedia. We have many articles on events that were current at the time and many of them spring up very quickly after an event and are of a decent quality. These events are often of great interest to readers, so it makes sense (imho, anyway) to highlight the decent articles on the MP. Obviously, ITN depends on there actually being an event to write an article on and so it can get stale on slow news weeks, but if we had greater participation at WP:ITN/C and more people working on the articles, ITN would be updated quicker when there is something with which to update it. Trying to make the best out of a feature you don't like doesn't mean you can't keep criticising it. ;) HJ Mitchell | Penny for your thoughts? 16:46, 24 February 2011 (UTC)
There has also been a decent amount of progress towards posting more stuff, I can only encourage more of you guys complaining to get involved and try and make it better. -- Eraserhead1 <talk> 20:59, 24 February 2011 (UTC)
Harry Mitchell is spot on about the role of ITN and about Wikinews: if WN were a business model, you'd dump it straight away. And equally, as a model for the Foundation's ideals, it's just totally misconceived, even though I admit I'd have been right behind it when it was launched years ago (sounds like a great idea until you face the big picture of news production and consumption). But worse, the English-language Wikinews is run by a pretty nasty clique, and User:Wackywace (another refugee from there?) told me on his talk page there are only six active editors. WN is a shameful waste of Foundation resources and should be closed, in all languages.

But to comment on ITN: I agree that it's not a normal news service, and surely people don't go to WP's main page to get their news. I think it is very well conceived in its anchorage to actual newsworthy articles that are being updated. I like it. It is ideal as a dynamic, fast-changing balance to the featured content on the main page. (Don't get me started about the bloated DYK section—that is very very wrong for the main page, displaying articles at the very opposite end of the quality spectrum from the featured content, with such poorly conceived and mostly boring, lame blurbs.)

However, despite my good opinion of ITN, I do wish for three things:

(1) A faster process from the breaking of the news to the updating of the article(s) to the nomination to the posting. I know it's hard to achieve (a slightly more official hierarchy of specialist admins/rosters?), but it is important to be prompt, given the speed of the news treadmill around the world nowadays. News goes stale mighty quickly nowadays, even when the primary purpose is unusual compared with standard news services.
(2) More flexibility in the number of current items, and in how long each one stays up.
(3) A smarter approach to wikilinking, as you know I've banged on about. Why aren't we funnelling people to the newsworthy pages, and perhaps to one other, very occasionally two other articles that are not already linked to from the newsworthy page? The practice of always linking country names, and bunching links together, is no longer used in articles and breaches the style guides. On this matter, what the style guides say makes plain good sense, even if the main page is not stricly speaking bound by them. Tony (talk) 11:44, 28 February 2011 (UTC)
I generally agree here. I'm neutral on this area's continued existence; as long as it is properly maintained, it serves as a tie in between Wikipedia and the rest of the world, which is a useful thing to have. To his points specifically:
1) While we can't mandate that people write about current events, it does seem to happen consistently, so that's not an issue. Tony is right in that the news is a rapidly flowing thing today. I believe that someone needs to check the section every 12 or so hours and make sure things are current. It's relatively easy to update a prompt on an ongoing event without even changing most of the wikilinks, and just as easy to look at the top stories of the past few hours and make sure that the current prompt isn't outdated. It just needs to get done.
2) Agreed.
3) Agreed. The current average in the section is 5, with most having four and some having 6 links. I'd aim for 3. If almost everything is blue, it loses the point. For example Oscars is easily reachable from any of the other prompts linked, and it's not the subject, so it should be cut. Sven Manguard Wha? 06:11, 1 March 2011 (UTC)
Could some of these issues be fixed by changing the name of the section? Something that doesn't make people think it's supposed to be a news-ticker with up-to-the-minute news?
"Topics In the News" or "Edited for Current Events", perhaps? APL (talk) 15:00, 28 February 2011 (UTC)
Perhaps 'In the news this week' or 'Currently ongoing stories'? Most people using WP regularly will know that ITN entries have a 'sticky tendency.' Jackiespeel (talk) 17:24, 28 February 2011 (UTC)
"In the news this week" would be a very accurate description, to be fair. —WFC— 08:57, 2 March 2011 (UTC)
In the news this week seems good to me. I also think Tony talks a lot of sense. -- Eraserhead1 <talk> 09:14, 2 March 2011 (UTC)
"... this week" does imply a slower turnaround. And ITN is short and neat. Tony (talk) 13:45, 2 March 2011 (UTC)
Implying the slower turnaround is half of the point. Much of the frustration at the moment is that we present stories that are stale or considerably outdated as news. This Week's News is equally short and neat, but more accurate. It would give us a stronger licence to do what in practise already happens. —WFC— 15:31, 2 March 2011 (UTC)
In my opinion, a name change will be worthwhile if (and only if) it removes the word "news." Otherwise, we'll never adequately address the misconception that it's a news ticker.
Because of the misleading name, some readers have argued the point even after we've explained the section's nature. ("But it says 'in the news' right there! So if it's not a news ticker, why do you call it that?") And they're right. —David Levy 16:35, 2 March 2011 (UTC)
"Recent Events articles"? Perhaps still a bit clumsy but describes that these events happened recently and that this section refers to the articles pertaining to said events. Including 'articles' may help in clarifying that this is recently updated encyclopaedic content rather than a news ticker. Careful With That Axe, Eugene Hello... 17:14, 2 March 2011 (UTC)
This is where the name change idea invariably falls short. We've never managed to come up with a title that fully conveys "articles updated to reflect recent events" in a non-clumsy manner.
So maybe we should stop pursuing that goal. After all, the current title conveys none of that information, so it might be a good idea to settle on something that conveys as much as possible and eliminates the problematic "news" association.
Perhaps just "Recent events" would suffice. It doesn't include a mention of article updates, but it's still an improvement over the status quo (and it isn't awkward construct). —David Levy 17:26, 2 March 2011 (UTC)
So far I think Recent events and This week's news are the two that might work. My preference would be for recent events, but this week's news might pacify those who want "news" retained. —WFC— 19:31, 2 March 2011 (UTC)
In addition to reinforcing the misconception that the section is a news ticker (and increasing the outrage regarding our failure to include various stories), the name "This week's news" would promote the additional misconception that the section is intended to report all of the top headlines from either the current calendar week or the past seven days.
The section sometimes includes events from more than a week ago (and would, in such cases, be objectively outdated instead of subjectively so). And during periods of relatively frequent updates, we would receive complaints about the absence of blurbs that scrolled off. (This already occurs occasionally, but the "This week's news" title would greatly exacerbate the problem by providing a realistic expectation that everything from the past week be included.) —David Levy 21:22, 2 March 2011 (UTC)
"Recent Updates"? Lovelac7 03:06, 3 March 2011 (UTC)
That possibility occurred to me. The problem is that it's likely to be confused with this.
If we can't convey both the "recent events" and "article updates" elements via the section's name, omitting the latter seems like the lesser evil. —David Levy 03:16, 3 March 2011 (UTC)
General comment - and just why is this discussion taking place here and not at WT:ITN where more ITN regulars are likely to see it and add input? This just reeks of trying to get a one-sided "consensus" without proper input from the community of editors who would be most affected by any change. StrPby (talk) 23:23, 2 March 2011 (UTC)
This discussion pertains primarily to the section's presentation to readers, no?
In any event, why not simply post a pointer at WT:ITN? I'll do so now. —David Levy 23:40, 2 March 2011 (UTC)
I love having news on the main page. I like "Recent events" as a title. And for the record... I think Wikinews is underused and nifty. SJ+ 13:33, 3 March 2011 (UTC)
I'm guessing that was directed at me StrPby. This started out as a rant, and was only posted because the standard processes to discuss ITN were as lively as a morgue that day. I wanted to know if I was the only person who felt that something wasn't right, and the answer was that others did too. But once the existence of the post was finally acknowledged, it evolved into a constructive discussion about practical steps that could be taken. You're right to say that no change could happen without ITN being consulted first, but suggestions of deliberate bias are wide of the mark. —WFC— 14:10, 3 March 2011 (UTC)

Perhaps I am alone in thinking thinking that ITN is appropriately named. To me, it simply means that the section contains WP articles which are 'in the news'. IMO that does not necessarily mean that it is a news ticker. I understand that many people do misunderstand the title for some reason, but I also haven't seen an better name, though as I said I think it doesn't need a better name.--Johnsemlak (talk) 16:12, 4 March 2011 (UTC)

From a stylistic standpoint, In the news is better than any other name ever suggested. And yes, when one understands its intended connotation (articles updated to reflect events in the news), it makes perfect sense.
The problem is that the latter often doesn't occur. We have no means of determining percentages, but we frequently receive messages (here and on other pages) from users under the mistaken impression that the section is a news ticker. Even some administrators have made this mistake, so it's hardly confined to newbies.
You acknowledge above that "many people do misunderstand the title for some reason," but you go on to say that you "also haven't seen a better name" and "think it doesn't need a better name." I agree that we've yet to come up with anything that sounds as good as In the news, but I don't understand your belief that the goal isn't worth pursuing. Is it your position that the intended connotation should be obvious, so we needn't worry about those who fail to grasp it?
I strongly believe that if we're forced to choose between style and clarity, the latter is far more important. —David Levy 17:12, 4 March 2011 (UTC)
In the news is the best name for the section. Unfortunately, the section doesn't live up to its name, but that's a reason to change the ITN process, not how it is called. GreyHood Talk 13:35, 5 March 2011 (UTC)
In the subsection below, you make excellent points regarding the section's shortcomings. But none of them pertain to the fact that as long as its title contains the word "news," it will be mistaken for a news ticker. Only if it were a news ticker would it "live up to its name" in many people's minds. —David Levy 17:31, 5 March 2011 (UTC)
Changing the label without changing what's behind this label will hardly solve any problems. ITN currently acts as slow news ticker, and whatever new name we could assign to it, it would look like a news ticker. So, what should we better do: a) make ITN faster news ticker, so that there will be no outdated news; b) make ITN an "encyclopedic news ticker", so that it will serve for navigation in encyclopedia and encouragement of its improvement, not only for listing the "significant news". GreyHood Talk 18:27, 5 March 2011 (UTC)
As I said, you've made excellent points, and I agree that significant reform is called for.
My belief that the section's name should be changed is unrelated to the issues that you've cited. It is not an attempt to downplay or compensate for the shortcomings listed below. It's an attempt to address a common misunderstanding that otherwise will persist, irrespective of whether we fix the other problems. We should improve both the label and the content behind it. —David Levy 19:10, 5 March 2011 (UTC)
If you're going to make ITN an encyclopaedic news ticker, to post stuff that's in the news in some way, but that is good encyclopaedic content then we would be posting things like iPad 2, because iPad is a GA. Additionally we'd also be highly likely to become very Anglo-American centric as that is where most of Wikipedia's content is focused. But I think it would be a shame to lose a pretty worldwide focused current affairs source. -- Eraserhead1 <talk> 20:00, 5 March 2011 (UTC)
In my proposal below, I've tried to give featured content and international significance equal weight in the nomination procedure. GreyHood Talk 21:58, 5 March 2011 (UTC)


ITN issues in detail

The fact that ITN is not dynamic enough (too often displaying outdated news) was discussed in the several topics at Wikipedia talk:In the news. There is a number of reasons behind the situation:
  • 1) There are not enough regular editors on ITN, while newbees and non-regular editors are often thwarted by too strict criteria (at the same time arbitrary in application, known to regulars but unwritten in the guidelines), slow and often unclear process.
  • 2) There are too few admins monitoring WP:ITN/C. Often admins have to be poked individually to post some news items (ready for posting and agreed upon), or poked to explain why the items that received enough support are still not ready for posting (due to the unsufficient update or other technical issues).
  • 3) Obviously significant news or articles on WP:ITN/R are sometimes not posted because of the lack of sufficient update or because of other technical issues. Editors like to nominate items, but simply do not put enough effort to prepare the available news for posting.
  • 4) Less significant, but still major world news (making headlines in the media internationally) are often not posted because some editors consider them insignificant, and could freely oppose in any case, despite any arguments on the contrary.
  • 5) Several major topics on ITN are strongly underrepresented, and in fact there is standing bias towards them. Economy and technology news are often not posted with the arguments like "it is business as usual" or "it's advertising". News are often not posted due to the established precedents and practices of opposing certain kinds of events.
  • 6) There is no mechanism that gives featured or good content a priority in posting. It would make sense to take opportunity to display featured, or good, or even B-class articles even if the news related to them are not exceptionally significant. Afterall, Wikipedia is not a news agency and the MP should feature more of the best content.
  • 7) Current ITN process is slow, time-consuming, and at the same time not formalized enough. The level of support or the proportion of supports/opposes required for posting is not defined clearly. Discussions may last up to five days, when the news already became stale. The ITN timer currently becomes red after 24 hours since the last posting, while the proper time should be at least 12 hours, so that to urge posting of at least 2 news items per day, which would garantee that there would be no stale news on ITN (there were suggestions to change the timer, but they had't success with recurring arguments along the line that quality should have priority over quantity). GreyHood Talk 13:35, 5 March 2011 (UTC)
I think you've done a good job of summing up all the issues. I frankly think if the section is to stay at the top of the front page within a reasonable timespan we have to get something posted on average every 12 hours, obviously sometimes it will be quicker, and sometimes slower but overall that should be the target we aim for, so number 7 is very important to get right. -- Eraserhead1 <talk> 14:08, 5 March 2011 (UTC)
I disagree – #7 would in effect make ITN exactly what we're saying it's not: a news ticker. Having a new item up every 12 hours would only reinforce the idea, imo. Strange Passerby (talkcontribsEditor review) 14:29, 5 March 2011 (UTC)
A new story every 12 hours would still mean stuff would be there for 3 days on average, that's 3x longer than the featured article is up, 3x longer than on this day, and 12x longer than did you know. And that's far less frequent an update than news sites.
Additionally a lot of the shortfall can be made up by posting other topics as well as we handle elections, disasters and sport, so we wouldn't really be significantly diluting the quality of the stories that are posted.
And lets not forget its only one story, even weeklies like the Economist add quite a few stories every week. -- Eraserhead1 <talk> 14:37, 5 March 2011 (UTC)

Proposals for ITN improvement

I've moved this to a subpage - see WT:ITN3.0. -- Eraserhead1 <talk> 08:58, 6 March 2011 (UTC)

Now an RFC. -- Eraserhead1 <talk> 09:15, 6 March 2011 (UTC)

ITN picture alignment

With the ongoing 'ITN picture/topic misalignment discussion' - how feasible would it be to have the #word# 'pictured' in 'a colour'/more instantly visible typeface' - so readily visible? (But this will be one of the regular discussions when WP celebrates its 100th birthday - along with too much sport/beasties/US/other usual suspects) Jackiespeel (talk) 17:55, 7 March 2011 (UTC)

At one point, we tried displaying "(pictured)" in bold text. This quickly proved unpopular. —David Levy 18:53, 7 March 2011 (UTC)

One of those 'complaints whichever way you do it' topics with the same six suggestions being (g). 'Anybody who uses WP regularly' knows to look around the ITN section for the relevant entry.

Aren't we about due for a 'Disgusted of Tunbridge Wells about the main page' discussion? Jackiespeel (talk) 16:56, 8 March 2011 (UTC)

Why not always bump the item related to the picture to the top and put other items in whatever order is otherwise being used? --Khajidha (talk) 19:50, 8 March 2011 (UTC)

From Wikipedia's newest articles

Well, it is in reality "From Wikipedia's newest or expanded articles". Shouldn't we correct that to be more factual? --Piotr Konieczny aka Prokonsul Piotrus| talk 21:34, 7 March 2011 (UTC)

Well, in any case it is about newly created content. No need to be over technical, IMO. At least where we have limited place on the Main page box. --Tone 22:21, 7 March 2011 (UTC)
I agree with the OP in principle, but we'd need to find a phrasing that fitted into the available space. "From Wikipedia's newest or expanded articles" would work fine on large screens, but wrap onto two lines for small ones (remember not everyone maximises their browser). Besides, they're not really the 'newest' articles anyway, usually several days old. Something like 'from recently expanded articles'? Do we even need to mention Wikipedia here? Modest Genius talk 22:58, 7 March 2011 (UTC)
I think we're getting a bit too pedantic here about the wording. I don't think the reader needs to know whether the article is completely new or just expanded. The important part is how good the content is. hbdragon88 (talk) 01:02, 8 March 2011 (UTC)
"From Wikipedia's newest content"? That would clear up any anomoly, as well as no longer implying that lists do not make it through to DYK. —WFC— 14:28, 8 March 2011 (UTC)
But not all content qualifies - adding new information to existing articles but without being a 5x expansion does not qualify for DYK. Modest Genius talk 17:59, 8 March 2011 (UTC)
That not all new content can be on DYK does not make the statement "from Wikipedia's newest content" inaccurate. —WFC— 23:32, 8 March 2011 (UTC)
(the above point about -est notwithstanding) —WFC— 23:34, 8 March 2011 (UTC)
"...newest content" seems to be the most appropriate. Expanded articles are essentially new content. –HTD (ITN: Where no updates but is stickied happens.) 15:20, 9 March 2011 (UTC)
Why does this note even have to appear on the main page? Yes, the qualifications should be listed on the nomination page, but there doesn't seem to be any need to mention them here. It doesn't really matter to the reader how the DYK items are chosen. --Khajidha (talk) 19:46, 8 March 2011 (UTC)
I think it does because DYK is intended to highlight new content and show off the fact we are constantly getting new articles and stubs becoming real articles. A common question is why some DYK items seem boring or stuff everyone knows because people think DYK is supposed to highlight interest facts that people may not know but that isn't its primary purpose nor the way it is set up. Nil Einne (talk) 14:33, 9 March 2011 (UTC)

Making a Decision on the Main Page Layout

Sorry, but it's too late for such radical changes at this time. Bring it up after the prototype's done, and then if, and only if there's majority consensus for a change will it be implemented. After coding starts, the proposal needs to fixed for the duration of coding. A radically new proposal cannot be made weeks after all the planning on the old one has been done, and coding has started.
The following discussion has been closed. Please do not modify it.
Weekends (FS inserted below FP)
Mondays (revised to insert the FL above the FP, as suggested by Strange Passerby)

Alright then, as the FS and FL proposals have now been passed, it's time for us to make a decision on the implementation.

The current proposal is as follows:
  • The only section being altered is the horizontal purple box.
  • On all days except Saturday, Sunday, and Monday, the purple box will look identical to it's current form, with one box taking up the full width, containing one featured picture.
  • On Saturday and Sunday, the box will be split into two, with a width ratio of 55/45, identical to the ratio between the green and blue boxes, with the 55% side on the left, identical in width to the green box. The larger box on the left would contain a featured picture. The box on the right would contain a featured sound.
  • On Monday, the box will be split into two, with a width ratio of 55/45, identical to the ratio between the green and blue boxes, with the 55% side on the left, identical in width to the green box. The larger box on the left would contain a featured picture. The box on the right would contain a featured list.
  • The coding would be as such that the width and number of boxes would adjust automatically, based on the day. Featured Pictures would not have to change their preparation process or code.
This is based on the comments by Howcheng, by the coders, and by the community.
We need to make a decision sooner, rather than later, so that the coders can finally get to work. I'm not saying we need to throw people under the bus and plow forward with this, but I am saying we need to keep moving forward in reaching a decision. Thoughts? Sven Manguard Wha? 22:01, 5 March 2011 (UTC)
I recall that a full-width box was the only solution that worked well for the featured picture at lower resolutions (even with non-panoramic images). I was much happier with your mock-ups that placed the additional content below the featured picture, which is precisely what I'd intended to propose.
The featured sound should share the purple box. (Both are featured files, so there's a thematic connection). The featured list, conversely, should receive a box of its own (with different coloration).
For the former, I've included one of your mock-ups. For the latter, I've included a modified version of one your mock-ups. —David Levy 22:43, 5 March 2011 (UTC)
Let's not completely rule out the use of a bus Sven! ;)
My impression is that there is clear consensus for Saturday/Sunday/Monday at the moment, and that the only real discussion to be had is over implementation. I favour a 100% width. That will ensure no disruption at all for FP, and that lists and sounds will not need to co-ordinate with pictures, which they otherwise might have if we went for a 55/45 split. More importantly, it just looks better. —WFC— 00:55, 6 March 2011 (UTC)
I agree with those rationales. Additionally, I believe that such an approach would be significantly more intuitive. From a reader's standpoint, it makes more sense for the full-time content to maintain a consistent format (with the part-time content simply being added on the applicable days) than it does for the full-time content's format to change back and forth for the sake of squeezing in the part-time content. —David Levy 01:21, 6 March 2011 (UTC)
Agree with the above but I wonder if on Mondays FL couldn't be above FP? It seems more intuitive to stick the text bits together with FP below like it currently is than to just stick FL below that almost as if an after-thought. It's not so much an issue with FS as that, as mentioned above, is similar to FP in the sense that they are featured files. Strange Passerby (talkcontribsEditor review) 01:32, 6 March 2011 (UTC)
That's a good point. I endorse the idea of placing the featured list above the featured picture.
Another advantage would be that readers familiar with the usual layout would be more likely to continue scrolling.
Also, some of the original justifications for placing the featured picture at the bottom are that it doesn't load quickly for people with slow connections and can't be seen at all by blind people and users with images disabled. (Similar issues exist with audio, of course, so it's okay to place the featured sound below the featured picture.) —David Levy 02:01, 6 March 2011 (UTC)
If we do end up with to horizontal boxes, the shorter (vertical height) of the two should go on top, for balance reasons. This means that FS should be on top of FP, but FP should be on top of FL. Because the code for that would be a royal pain, I'm pretty sure that's off the table. If I had to choose one then, I'd likely choose having FS and FL on top of FP, per that, as David said "readers familiar with the usual layout would be more likely to continue scrolling". Either way, this leads into my second point:
Do keep in mind in all of this that the FS and FL sections will share coding. Whatever we decide as placement for one will have to be the placement for both. Coding it any other way would be prohibitively difficult, if not impossible. If Featured Lists gets a spot on the main page every day, which would be the result of a second proposal made in several months/years, it would be coded into it's own spot separately, however right now it's only possible to do one rotating content spot, whatever the form. I should have made this clearer earlier. Sven Manguard Wha? 04:23, 6 March 2011 (UTC)
You're mistaken; no such limitation exists. The part-time sections will be inserted via conditional code that modifies content based on the day of the week. This is extremely easy and doesn't require the part-time sections to appear in the same location.
Heck, if we wanted to, we could automatically jumble around or replace every section on the main page based on the day, with seven different combinations in total. (Of course, we have no reason to do that.) —David Levy 05:01, 6 March 2011 (UTC)
I'm sorry, but no. While it might seem that what you're suggesting is correct, it really isn't. The main page is costructed of layers upon layers of spaghetti code, and each section has their own separate jumble of subpages and transclusions and cobbled together code. In fact, one of the coders I'm working with has said multiple times that the main page code is probably due for a complete rewrite. Several issues limit the implementation for FS and FL. For one, an immense amount of work goes into ensuring that everything comes out balanced (that the green and blue sections are of the same length) and that everything renders as is intended. There is a very small margin of error in this, which is part of the reason that the main page looks as clean and crisp as it does. Between the pre-decided size limits and the spaghetti code, it would be a colossal mess to try to do anything that alters the green and blue sections. That leaves the section below them, the purple section. Now I'm not entirely sure what the coders said about technical limitations, they seem to know what they're doing but to me it's a different language. What I do know, however, is that there are layers of rules and precautions built in to make sure everything works right, and that does necessitate them sharing the same space. You'll have to ask them for more details. Suffice to say, I didn't just make something up out of thin air and stick it in bold text for my amusement, this is what I've been told since the beginning. Sven Manguard Wha? 06:08, 6 March 2011 (UTC)
I suspect that you've misunderstood what someone wrote. It's true that all of the code has to co-exist, but not in the manner that you've been led to believe.
The main page's code (including that which is transcluded from other pages) is relatively complicated and spread out, but conditional code to enable the display of x under one definable circumstance and y under another definable circumstance is trivially easy to author. I can state with 100% certainty that it would be no harder to place the two part-time sections in different locations than it would be to place them in the same one. (For the record, I've been involved in the main page's design for years, personally added the aforementioned purple box during the last major redesign, and have contributed such conditional code to the main page and elsewhere.)
I'll try to explain in layperson's terms how this would work.
One piece of code would say: "If it's Saturday or Sunday, change the layout to include the featured sound (transcluded from another page). Otherwise, do nothing."
Another piece of code would say: "If it's Monday, change the layout to include the featured list (transcluded from another page). Otherwise, do nothing."
There is absolutely no need for these two pieces of code to specify the same location or style for the part-time content (unless other content is formatted based on the assumption that the relevant conditions will remain constant, which simply isn't so in the above proposal). All of the non-transcluded code will be present at all times, but the two pieces of part-time content code will never be switched on simultaneously. —David Levy 06:39, 6 March 2011 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────My coding ability is limited, but I'm reasonably confident that David is right. Regardless of whether they share a box or not, FP/FL/FS will effectively become one section, and a switch statement should be able to determine placement in the way that he has explained. —WFC— 14:53, 6 March 2011 (UTC) (actually, if/else would make more sense, as there would be two separate statements. Point is, I'm sure it's do-able) —WFC— 14:55, 6 March 2011 (UTC)

Yes, I asked again. David is indeed right. I was working from information given to me before the two FPs a day idea was scrapped. When that idea was scrapped, a whole lot more options became realistically available. Sorry for the confusion. Sven Manguard Wha? 06:01, 7 March 2011 (UTC)
No worries. That was the information you were given, and you were right to be cautious if there was so much as an outside chance that consensus was leaning in the direction of something that was impossible. —WFC— 09:56, 7 March 2011 (UTC)
Right, we should get back to design decisions now. I see two (three) options that are on the table right now. One is the 55/45 split. The other is the two horizontal bars option. If we do the horizontal bar option, I'd opt for a "biggest on the bottom" setup (FP above FL but FS above FP) for a more balanced look, or just have both of them be above the FP per David's observation that people are more likely to keep scrolling down since they know that there's something there, the FP. Does anyone have any other ideas or should we start whittling down from those two (three) options? Sven Manguard Wha? 01:25, 8 March 2011 (UTC)
I think that we should abandon the 55/45 split idea, which has several significant drawbacks (poor compatibility with low resolutions, unnecessary inconsistency, possible interference with the featured pictures' scheduling).
Regarding the proposed full-width options, I agree with Strange Passerby that the featured list should appear above the featured picture, thereby grouping together all of the text-based content (instead of tacking on the featured list as an apparent afterthought) and retaining the benefits of having the featured picture at the bottom (maximized content accessibility for blind people and users with slow connections).
I don't object to the idea of also placing the featured sound above the featured picture. In addition to encouraging scrolling, this would enhance the overall consistency. —David Levy 02:59, 8 March 2011 (UTC)
  • Support 100%-width, FS/FL followed by FP, as per StrPsby & DL. Careful With That Axe, Eugene Hello... 08:42, 8 March 2011 (UTC)
  • We should abandon the 55/45 split idea. I don't think it looks particularly good, and it would cause trouble for FP. In any case, it would be unworkable if sounds or lists ever expand to other four days, which is plausible in the longer term. I think the lists mock-up above is ideal, and the question is whether sounds should also be presented as above (featured media in one section), or if sounds should be presented identically to lists, for consistency. I'm leaning towards the examples above, but can see both sides of it. —WFC— 12:28, 8 March 2011 (UTC)
If we were to place the featured sound above the featured picture, it still could (and should, in my opinion) share the purple box. Only the lack of a thematic connection justifies using a separate box for the featured list. —David Levy 16:45, 8 March 2011 (UTC)
Here are four demos of how the main page could look with FL above/below FP and FS above/below FP:
The colours for FL are simply a cyclic permutation of those used in FP, but obviously could be any that are decided. Please check them in different browser widths to get an idea of how others may see them. I don't think there's a huge aesthetic difference between any of them, but I have a slight preference for the FP below the other content as the larger image tends to set it off from the rest (at least to my eye). --RexxS (talk) 18:23, 9 March 2011 (UTC)
Thanks RexxS. I think in both cases it looks best with the featured picture on the bottom. I would, however, break up the combined FS/FP box into two boxes. I think it would look better that way. Sven Manguard Wha? 20:27, 9 March 2011 (UTC)
Strange, they are showing in separate boxes on my PC using FF 3.6.15, Opera 11.01, and even IE8. There should be the same gap between them as between the current DYK and TFP boxes (about 4px). Do they seem combined even if you zoom the page? If so, let me know your browser version and I'll look for a fix. - P.S. my pages are editable (this is a wiki!), so we can mess about with them until we're happy. That ought to give Adam a headstart on his coding when the community decide on the final details of the implementation. --RexxS (talk) 02:16, 10 March 2011 (UTC)
I see separate boxes too. I would prefer a combined one for the featured sound and picture. —David Levy 03:18, 10 March 2011 (UTC)
They are separated, I just had things zoomed out and didn't see the break. I would go the opposite way of David though, and do a separate color entirely for the FS (whatever color is decided for the FL) as they are two totally different things for one, and because it just looks better that way. Sven Manguard Wha? 05:22, 10 March 2011 (UTC)
The logic of grouping them together is that they aren't two totally different things. Both are media files used to supplement articles' text (hence the shared "File" namespace). While each of the two columns' content is thematically connected (our most polished articles and newest articles on the left; recent events and past events on the right), there actually is more editorial similarity between the featured sound and featured picture. —David Levy 05:41, 10 March 2011 (UTC)
Giving prominence to a brand new section wouldn't be a completely outlandish reason for FS to have its own box and colour to start with. I do agree with David though. If we go down the separate box for FS route, I think that the main page re-jig which has been touted for some time this year would be a good opportunity to group pictures and sounds, as the argument that people might miss sounds would no longer apply (unless of course strong objections were raised sooner). —WFC— 10:51, 10 March 2011 (UTC)
Indeed, the "giving prominence to a brand new section" rationale is reasonable. But if we're placing the featured sound above the featured picture, that prominence should come naturally. ("Hmm, there's a featured sound where the featured picture usually is. Oh, the box been expanded to include both.")
From past experience, I'll note that once something has been added to the main page, it can be extremely difficult to remove it. If we include a separate box for the featured sound now, an eventual attempt to combine the two boxes might meet resistance (because it would be perceived as an attempt to downgrade both sections' prominence). —David Levy 18:32, 10 March 2011 (UTC)

Make a damn decision so I can code it

Please stop changing the parameters every two days. Choose something. Stick with it. I can't make a new version of the main page when not only are new layouts being constantly proposed, in direct violation of the previous layouts, but noone is bothering to even tell me about the new proposals, which override previous, agreed consensusses, and seem to be made for no othr reason than someone gets another big idea, and decides to push it forwards.

The backend for FS is coded, the backend for FL just needs it copied oever. But all this constant inability to make a decision and stick with it makes things IMPOSSIBLE. Adam Cuerden (talk) 21:01, 10 March 2011 (UTC)

(e/c) Seems like a reasonable (if large) request. Can we focus rather than ramble here? Adam's been generous enough to give his time and support to all of this, but we really need to just say "is it (a) or (b) or (c)... etc?", get a consensus and let Adam do his best to knock something up. Throughout all of the FS proposal and some of the FL proposal we had suggestions on the table. Now it appears we're tossing all that out of the window (despite both proposals having substantial support from the community) and free-styling. Let's do us, and Adam, a favour, and re-focus... The Rambling Man (talk) 21:07, 10 March 2011 (UTC)
(edit conflict) Well there is that. Also, and a little less large, Saying FS and FP are the same thing is not only incorrect but also something I find grossly insulting. It would be like saying FA and FL are the same thing. In the strongest possible manner, I'm vouching for two horizontal sections, with FS and FL above FP, and with FS and FL having a distinct color from FP. Sven Manguard Wha? 21:13, 10 March 2011 (UTC)
I'm not sure I even know what proposal Adam is working off of is, and at this point, I don't care. I spend weeks trying to hear everyone's opinions and make everyone happy, and in return Adam throws a tantrum on my talk page. Do whatever you all want. It'll work, or it won't. I've learned a valuable lesson today about how much consensus actually matters. Depressing really. Sven Manguard Wha? 22:23, 10 March 2011 (UTC)

This is what's happening with FS and FL

This needs to start afresh
The following discussion has been closed. Please do not modify it.

I'm sorry,. I'm the one coding this, a certain person has a habit of going off half-cocked and writing new proposals every three days which ignore any and all previous consensus.

So here's what I intend to code, and if you have any objections to this, you can bring them up during the discussion after everything's ready to launch, and, if a majority of people agree with you, then changes can be made at that time.

  • On Mondays, Tuesdays, Wednesdays, and Thursdays, the main page will look as it does now.
  • On Fridays, the FP box will be split to allow Featured Lists taking up 55%% of the left of the FP box.
  • On Saturdays and Sundays, the FP box will be split to put FS on the right side of the FP box , 45%.

This was the proposal that was voted on, modified by such things as appear to have gotten majority consensus to date.

No other changes will be considered until a working prototype is completely ready to launch. I absolutely refuse to attempt to code for something that keeps having radical modifications proposed that undo all the planning work I've done to date.

I'm sorry, but at some point, the proposal has to become fixed. that point was several days ago, now. Once we have a working prototype, then, and only then, will any changes be considered, but we need that working prototype first, and then changes can be proposed, voted on, and implemented if, and only if, they achieve consensus.

Freeform proposals that throw out all previous discussion are over. They're basically stopping all possibility of work, by making me have to throw out all my planning sheets and start over. Adam Cuerden (talk) 21:24, 10 March 2011 (UTC)

When the proposals to add the featured list and featured sound were made, it was explicitly stated that the 55/45 split was merely an example and that we were not committing to any particular layout; that was to be discussed and decided upon later (after deciding whether to add one or both of the part-time sections). That's what we're doing now. Why on Earth are you already working on a prototype, and why do you believe that it makes sense to do so before a layout has been selected? —David Levy 21:45, 10 March 2011 (UTC)
Correction: That's what we were doing before you unilaterally closed an ongoing discussion. —David Levy 21:49, 10 March 2011 (UTC)
It would be useful if we could spend a second to actually appreciate the fact that Adam is doing all this background work, rather than hit him with "Why on Earth"s... If someone has a suggestion for the layout beyond those discussed during the FS/FL proposals, then fine, but as the FS proposal got community backing, including a consensus for the detailed technical solution proposed by Adam, it now seems a shame to start giving him a hard time when many people seem content to pull the rug from under him. If this is fallout from failure from some to adequately comprehend the initial FS proposal, then more's the pity. The Rambling Man (talk) 21:55, 10 March 2011 (UTC)
I do appreciate the work that Adam's doing, but there appears to have been a major misunderstanding. It was explicitly stated that we were strictly determining whether or not to add featured lists and featured sounds to the main page (with the 55/45 mock-up serving only as an example of a possible implementation), with layouts to be discussed later. Adam, apparently under the impression that a design was settled upon, just unilaterally closed that discussion and declared it moot.
I had a full-width layout in mind while the featured sound proposal was ongoing, but I refrained from suggesting it because such discussion was deemed premature. So frankly, I feel as though I've had the rug pulled out from under me too.
I don't blame Adam (or anyone else) for this misunderstanding. I merely want to resolve it. —David Levy 22:08, 10 March 2011 (UTC)
Reminds me of my own workplace, misplacing the blame for those misunderstanding those who are misunderstanding. Anyway, no need for the "why on Earth" kind of response to one of the only people who is bothering to improve our out-dated, stale main page. Let's make the most of the resources we have to actively seek a decent solution to all this. It's odd to me that Adam proposed a highly comprehensive technical solution which was almost unilaterally accepted, but now every "expert in main page design" (my phrase) has appeared out of the woodwork to say they "don't like it". The Rambling Man (talk) 22:17, 10 March 2011 (UTC)


Okay, let me explain.

The FS proposal very explicitly included both layout, and the technical proposal. It did note the mockup might vary slightly from the final implementation - but the technical notes made it very clear that the 55/45 split was part of the proposal. But the mockup wasn't of any actual code, so it was marked as a mockup.

During the FS proposal, some discussion of FLs happened. While finalising the FS plans, I realised I could probably adapt things to include FL fairly easily, and offered this solution to FL, but, while the FS proposal mentioned FL as a possibility, Sven went off half-cocked and started the voting early for some reason. There wasn't time to work out an FL inclusion, because Sven had decided to ignore the one-week explicitly given for discussion, and start voting.

Sven did not talk to me about making the vote live, and I was forced to spend a couple hours polishing up my long-form draft of the technical proposal, and posting it.

Following FS passing, FL ran, based on my proposal for a minimal-extra-coding FL. Half way through, with a vast majority in support, one person - Raul I believe - opposed it, saying he had misread the FS proposal.

Sven, without talking to anyone, immediately proposed that all layout for FL's should be ignored. Howcheng said that FPs could be removed from it, and Sven said "Oh, yes, we'll do that!"

This meant that I had to replan everything, and am now coding FL and FS separately. Luckily, I came up with a plan to do so, over the course of the next week, and after following discussion. I also go the rough prototype FS code done.

On the 5th, without telling anyone involved with the proposals, Sven decides that FL and FS should be broken off from the FP section.

I'm, sorry, but Sven isn't talking to me about this. I can't be bound by what he decides to do, when I've repeatedly asked him to talk to me before making new proposals, and yet, every time the diust settles down and there seems to be consensus, he makes changes without talking to anyone.

Sven has this habit of immediately acting unilaterally and throwing out all previous discussion the moment someone says anything negative about something. I've repeatedly had to replan everything from scratch as a result of his actions.

Sven means well, and is a passionate and valued member of the FS community, but he seems so worried about getting FS and FL onto the mainpage, that he's willing to override all previous discussion in order to satisfy a single upset person, instead of even waiting to see if the concern is generally held, and will make promises - effectively on my behalf, since I'm doing all the coding - to such people in order to satisfy them. If people have legitimate concerns, the FS proposal has an obligatory period after the coding is done where it's to be reviewed and tweaked. Things can be dealt with then, but I cannot work if people are going to promise changes, and not even tell me they've promised changes. Sven didn't tell me about his proposal of March 5th, I don't even think that a lot of people who supported my proposal WOULD support his newest proposal, because having a large box that extended the page's length, and which appeared and disappeared, was something a lot of people praised the original proposal for avoiding. Adam Cuerden (talk) 22:27, 10 March 2011 (UTC)

So, long story short, let me get the coding in place, then I will open the floor to any proposals for changes to layout. But I need a fixed point so I can get the coding done, and which won't cause everyone who voted on the original proposals to say "That's not what I voted on".
After it's done, we can do support/oppose voting on any proposed changes, during the review stage. But if we do it Sven's way, I end up in the situation where I either code something based on a discussion with 5-6 people that he may well change completely again in 3 days, causing everyone supported originally to yell at me for coding something they didn't vote on, when they're invited back for the review phase, OR I try to keep up, and likely end up with a finished product that's obsolete before I even finish because another radical change to the proposal happens when I'm in the middle of coding. Adam Cuerden (talk) 22:55, 10 March 2011 (UTC)
Me: "Am I correct that this is merely a non-binding example (and we'll have an opportunity to propose/discuss alternative implementations later)? That was my impression during the previous discussion."
Sven: "the proposal above states 'If this proposal passes, coding of the FL main-page inclusion will be put up for review, including a mock-up of it in action, and a rubber-stamping vote at simple majority to confirm its use.' so yes, the mockups are precisely that, mockups, with scope to be modified."
Evidently, Sven and you weren't on the same page, which is unfortunate. But it's clear from the discussions that many respondents were under the same impression that Sven and I were. Talk of a full-width layout even arose, but it was deemed premature (because that discussion was to be held later).
As noted above, I sincerely appreciate your work and don't blame you for this misunderstanding. But I hope that you can understand why your response came as a bit of a shock. Likewise, I understand your frustration.
Obviously, some people believed that they were commenting on both the sections' inclusion and the specific layout, while others believed that they were commenting strictly on the former (with the latter to be determined later). So I respectfully request that you please allow the community to resume discussing the layout and arrive at an unambiguous decision, and then finish coding the prototype. That should satisfy everyone and avoid wasting any more of your time and effort. —David Levy 23:07, 10 March 2011 (UTC)
I'm sorry, I did the FS proposal. Sven has constantly sabotaged the project by making promises he intended other people to keep on his behalf. Adam Cuerden (talk) 23:09, 10 March 2011 (UTC)
Again, I'm not blaming you (or anyone else). I'm just explaining that there's been a major misunderstanding (which I now seek to resolve). —David Levy 23:27, 10 March 2011 (UTC)

(edit conflict)x3 Adam can preface his complaints however he wants to, but he didn't follow the discussion, and didn't step in when he needed to. Now, because he's the coder, he's ignoring what other people have said. He had every reason to suspect that conversation would continue, and the fact that he didn't follow this page is no excuse for his surprise that things changed while he wasn't watching. I really don't even see the rush, as unlike FL, FS is weeks, maybe months, away from being ready to put anything on the main page. We still have to reassess all but a half dozen of the existing featured sounds to make sure that they are worthy of the main page, and there is a strong disagreement between several FS voters over where those standards should be. On top of that, we've actually seen a decrease in participation since the FS proposal was approved, and while I will not share the details here, our house is very much not in order. Between preexisting conflicts and the events of today, the most active members are barely talking to each other, and one of the most experienced nomination closers has been gone from the area for weeks. Quite simply, FS is not ready to do much anything, and this urgency on Adam's part certainly isn't going to solve any of those problems. Sven Manguard Wha? 23:14, 10 March 2011 (UTC)

That is a lie. However, you know what, fuck it, you've lost yourself a coder. Go find someoen else who's willing to deal with Sven. Adam Cuerden (talk) 23:17, 10 March 2011 (UTC)
That's not at all a lie, and you're ignoring just about anything that's inconvenient to you while plowing ahead your own way, something you seem to make a habit of doing. Sven Manguard Wha? 23:21, 10 March 2011 (UTC)
While your frustration is understandable, your response is unfortunate (and frankly, personal attacks such as this and this are unacceptable).
I sincerely hope that you'll take a well-needed break and reconsider. —David Levy 23:27, 10 March 2011 (UTC)
It won't help for anyone to blame anyone. Everyone acted in good faith, and an honest misunderstanding arose.
The only clear consensus is that featured lists and sounds should appear on the main page with the frequency discussed. As you noted, there is no rush for this to occur.
So can we please simply continue discussing the layout (as some of us were led to believe would occur as part of the process) and reach unambiguous consensus before we proceed with anything else? —David Levy 23:27, 10 March 2011 (UTC)

"<Sven_Manguard> I'm about to sabotoge FS's chances of getting on the main page. Congradulations." - PM on IRc. Sven's statement is very explictitly him trolling, and if he's such an immature little prick that telling him I'm upset with him means that he'll kill two featured process's chances of being on the main page, I'll rot in hell before ever working with him again. Adam Cuerden (talk) 23:29, 10 March 2011 (UTC)

Well now, that's a nice thing to see again. It's taken out of context, the proceeding conversation was all about how we screwed ourselves over by not communicating, and the statement immediately after that, the last one I sent before closing the window, was "I'm tired of lying about how sorry a shape FS is in. I'm going to tell everyone everything and let them decide if FS really deserves everytihng I've fought for"
If telling people the truth about a badly damaged featured process before it goes on the main page is "trolling" then I suppose the problem runs very, very deep. Sven Manguard Wha? 23:36, 10 March 2011 (UTC)
Both of you need to stop attacking each other, take a break and calm down. PLEASE. There was an honest misunderstanding. We all want the same thing (to improve the main page). —David Levy 23:36, 10 March 2011 (UTC)
Find a new coder. If nothing else, that he'd screw his best friend, La_Pianista, out of a chance to be on the main page due to him being too much of a prick to care bout nything but intentionally hurting me has meant I can't work with him, and I hand FS over to him, which he'll probably run into the ground. I'm off. Don't expect me back. Adam Cuerden (talk) 23:39, 10 March 2011 (UTC)
(edit conflict) I wanted to have a break from him. I told him that on the same IRC conversation that I didn't want to deal with any of this until Monday. Under the circumstances I certainly showed a great deal more restraint than I had hoped I'd ever have to muster. Adam's issue in this affair is that he assumed that everyone would keep him in the loop on everything. My issue was that I didn't think I had to; that I thought he was watching the main page talk. The fact that he then publicly chewed me out for trying to move forward without checking in with him every step of the way was another part of the problem. Going in, we knew that FS had it's share of issues, but they were minor (i.e. we knew everything had to be rechecked, we knew that closing nominations was a mess) but since they were internal working issues, we never brought them up here. Once he decided to open the door and start airing failings, I felt no compulsion to keep secret the issues plaguing FS. I told him as much. Perhaps "sabotage" was a poor choice of words, but that's what it felt like, and telling the truth should never feel like that.
The truth is that FS has numerous strong personalities. Adam is a process oriented person, he wants a clear objective and clear processes, and dosen't respond well to changes midway through a process. I am an appeaser. I want everyone to be as happy as possible, even if that reduces efficiency and isn't the most straightforward path. The only way we'd work together effectively is through communication. He never said he wanted more of it and I never thought I needed to give more of it. That's what caused today's spat. As to the other issues I addressed, FS currently has over 20 open nominations, many of which don't have more than two people's comments. Tony1 and X! have been sparse, Adam has been focusing on nominations, and I've been holding back to do the closings, meaning that four of the eight or so regulars were not commenting. There's a roll call for reassessing works promoted several years ago, but it's made little process, less than 5% of them have had decisions made on them. So yes, participation is low and tension is high. I thought that that would sort itself out, but with FS losing one of the two of Adam or I over this, I now doubt it will.
The truth hurts, but it needed to be said. I'm sorry for my part in this, the damage done to FS hurts me more than most. I really thought it had a bright future and was a place that I could do good. Now, I don't. Sven Manguard Wha? 00:00, 11 March 2011 (UTC)
There's no reason to bring other people into this mess Adam. FS will eventually go on the main page, my point was that it wasn't ready now, and that there were major issues that needed to be addressed. That a) I'd ever even try to hurt a friend (La Pianista) like that, or that b) that I was doing this in a deliberate attempt to hurt you, are absurd. I wanted the best for FS, I wanted that and only that from the beginning. Forcing an unpopular layout through isn't what's best for FS, and putting up FS before everything could be vetted isn't what's best for FS. That's why I said what I said, not to hurt you, but to help featured sounds. Sven Manguard Wha? 00:07, 11 March 2011 (UTC)
I'm hatting this. Relevant discussion will need to take place on these issues, but I think it's important to start afresh in a new section. —WFC— 00:28, 11 March 2011 (UTC)

We now need to be pragmatic, and figure out the way to move forward. I think it would be wrong to attempt to progress that discussion until Adam has the opportunity to participate, should he wish. In the meantime I would suggest that we reflect on the way forward individually, but put the discussion on hold until some time after 12:00 UTC. —WFC— 00:33, 11 March 2011 (UTC)

Please correct this error (third time of asking)

In OTD, as reported above - 'license' in the Raymonde de Laroche entry in OTD should read 'licence'. Am posting here as no-one seems to be taking any notice of where I posted above in the OTD section, and the error has been up for 13 hours now. Thanks 86.142.104.120 (talk) 15:11, 8 March 2011 (UTC)

Is there a particular reason why an article about a French woman should be written in British English? The Rambling Man (talk) 15:15, 8 March 2011 (UTC)
Is there a particular reason why it shouldn't be? 87.115.50.126 (talk) 19:21, 8 March 2011 (UTC)
I think that's the start of a boring, pointless non-argument. Happy pancake day. The Rambling Man (talk) 19:36, 8 March 2011 (UTC)
It is a silly issue, but fwiw, the article itself uses the British spelling of licence. Resolute 15:35, 8 March 2011 (UTC)
Yes, it makes no difference to me particularly, the hook being used links to an article with USEng spelling... Damned if you do, .... The Rambling Man (talk) 15:40, 8 March 2011 (UTC)
It's even funnier than that. From Raymonde de Laroche: "... an airplane pilot's licence." and "... the first woman in the world to receive a pilot licence when the Aero-Club of France issued her license #36 ...". No doubt someone will grasp the nettle and regularise the transatlantic spellings. --RexxS (talk) 02:31, 9 March 2011 (UTC)
Funny? --118.208.182.238 (talk) 06:26, 9 March 2011 (UTC)
Yes, I found it incongruous (hence mildly amusing) that someone objected to the use of en-us in the hook which has a lifetime of less than a day, when the article itself uses a random mixture of en-gb and en-us and has been that way for months, if not years, without anyone mentioning it. --RexxS (talk) 15:25, 9 March 2011 (UTC)
Raymonde de Laroche has been regularized to en-gb. Someone may want to check it since I'm American. howcheng {chat} 23:15, 9 March 2011 (UTC)
Damn, we'd better fix that to fixed-wing aircraft (there was a conflict war over this on Steve Fossett, where one argued that he was American and the other argued that we were an international encyclopedia. hbdragon88 (talk) 05:53, 10 March 2011 (UTC)

When we reach the WP equivalent of 'the least interesting day of the 20th century' we can have a main page devoted to 'all the usual problems' - multiple-English-spelling-systems, excess of US-sport-animal and plant-(continue according to taste) pages over previous week. misalignment of ITN articles and images, articles deemed inappropriate by Disgusted of Tunbridge Wells and so on. Jackiespeel (talk) 17:01, 10 March 2011 (UTC)

You are rather fond of banging on about Disgusted of Tunbridge Wells, aren't you? [7] [8] [9] [10] [11] [12] It's a very convenient way to belittle the opinions of anyone who you disagree with. Give it a rest. 87.115.50.126 (talk) 13:58, 11 March 2011 (UTC)

Where are we with FL and FS?

To move on.
The following discussion has been closed. Please do not modify it.

Okay. I'm not going to naively suggest that all the dust has cleared from yesterday. However, this is a new day, and we've all had a little time to reflect. Clearly there are some unresolved issues, but I would hope that those can be dealt with away from this page. This discussion should now be solely about where we go from the position we are in today.

For now, I think there are one, possibly two, key questions that we need to clear up.

  1. Will Adam reconsider his decision to step down from the coding?
  2. If Adam is no longer doing the coding, do we discuss the design first and code later, or code along the lines of the original mock-ups first, and discuss changes later?

My personal opinion is:

1. I very much hope that Adam will reconsider. If he is willing, I think we should respect his wishes to stop discussing changes until the working design is completed, bearing in mind that he has already done the majority of that work. Once that is complete, we can then discuss whether anything needs tweaking.
2. This comment is only relevant if Adam's decision to step down from coding is final. In this instance, the new coder would presumably be starting from scratch, and in light of that, it might be preferable to have an RfC on the new main page design before they get to work. I would suggest that in light of what has happened, we do not begin that RfC until it has been drafted and scrutinised for a couple of days to ensure that it is well stuctured, and tailored towards producing a concrete result from which the coder can confidently work from.

WFC— 13:36, 11 March 2011 (UTC)

I'll give you my decision in one week. At this time, I'm far too upset about everything that happened to make any decision other than "unlikely". Adam Cuerden (talk) 13:45, 11 March 2011 (UTC)
Regardless of Adam's decision, the only way to proceed that makes sense is (speaking as someone who has built countless web sites) design first, code second. There's nothing more infuriating as a coder to be halfway done with a page than when the design team comes back with changes that force you to redo the whole thing. howcheng {chat} 16:50, 11 March 2011 (UTC)
I edit conflicted with you saying the same thing. As someone who currently manages a development team, the thing that seems to drive them maddest is where people keep changing their minds while they are trying to finish the thing. Try to specify by outcome - what do you want to achieve - then let the coder decide how he can get you there. Elen of the Roads (talk) 16:54, 11 March 2011 (UTC)
This is why I was surprised and bewildered by the revelation that coding was underway. During the two proposals, there was much discussion of focusing strictly on whether to add featured sounds and lists to the main page on a part-time basis, with the layout to be discussed and determined later. It's unfortunate that Adam was unaware of this (and his frustration is understandable), but there simply is no sensible course of action other than determining the consensus implementation and then coding it. —David Levy 17:27, 11 March 2011 (UTC)
To be fair to Adam, he provided a comprehensive technical solution during the FS proposal which received near-unanimous support. Anyway, there were many misunderstandings there, so let's move on and hope that Adam will still be willing to help improve and modernise our main page. The Rambling Man (talk) 18:09, 11 March 2011 (UTC)
To be fair to Adam, he provided a comprehensive technical solution during the FS proposal which received near-unanimous support.
Some of the support was based upon the impression (which eventually was explicitly confirmed) that we were committing to the concept of including featured sounds and/or lists on the main page, not to the specific implementation illustrated in the mock-up. The layout, we understood, was to be discussed and determined later. Such a division was logical, as the alternative would have forced us to oppose the entire idea if we merely disliked the example design.
Anyway, there were many misunderstandings there, so let's move on and hope that Adam will still be willing to help improve and modernise our main page.
Agreed. I don't blame Adam (or anyone else) for the misunderstandings that occurred. I hope that Adam is able to come to terms with the situation and continue participating in the endeavor. —David Levy 18:46, 11 March 2011 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── I didn't refer to the mockup. I referred to the substantial "technical solution" section Adam provided, at the same time as the whole proposal. The Rambling Man (talk) 18:56, 11 March 2011 (UTC)

Oh, okay. The section actually was labeled "Technical details," and I don't think that anyone (including Sven) seeks to diminish the time and effort that Adam has invested in this and other elements of the endeavor. His work is sincerely appreciated, and I hope that he realizes that. —David Levy 19:15, 11 March 2011 (UTC)
Obviously, I want to continue to work with FS, and I really do, it's current hurdles aside, want it to hit the main page. However at the same time, I readily admit that Adam has done so very much more work for FS than I have. He's been in and out of that area for years and by his own estimation, is responsible for about 40% of the nominations over the full history of FS. If Adam is willing to go back to working with FS but does not want to go back to working with me, a decision I would understand completely, I'd be willing to essentially leave FS, or drastically curb participation there to a level that will make him more comfortable. Ultimately Adam has already done, and hopefully will continue to do, more good for FS than I probably ever will. I do not believe in putting what is best for one user (me) in front of what is best for the project, so I would bite the bullet to make sure that FS turns out a success. I don't relish making the offer, but it's there now, and I can't take it back. Sven Manguard Wha? 19:32, 11 March 2011 (UTC)

...I may as well bite the bullet - I misread a date, so my yelling at Sven yesterday over him having done something again was actually him having done something I had already talked to him about. Had he really done it again, it'd be worth my reaction to him. I strill don't like how the proposal seems to be in constant flux, but I overreacted. Adam Cuerden (talk) 21:22, 11 March 2011 (UTC)

Joint apology
  • Okay, just to be clear, I've talked with Sven. I misread the timing of his actions, he didn't realise I was misreading them and got naturally upset, and we're both horribly embarassed as to what happened. We're going to take a couple days off the FS/FL proposal, then move forwards again, working together. we apologise to everyone for the disruption, and letting our spat get way out of hand. Adam Cuerden (talk) 22:29, 11 March 2011 (UTC)
  • I should have done more to keep Adam in the loop, I didn't realize where he was in the coding, and should have done more to make sure I was up to date on the technical aspects. I readily admit that I got swept up by the madness from yesterday, and said things that were better left unsaid. We both have things to be shameful of, and I too offer a joint apology to everyone. Sven Manguard Wha? 22:33, 11 March 2011 (UTC)