Wikipedia:Featured list candidates/Philadelphia Phillies all-time roster (E–F)/archive1
- The following is an archived discussion of a featured list nomination. Please do not modify it. Subsequent comments should be made on the article's talk page or in Wikipedia talk:Featured list candidates. No further edits should be made to this page.
The list was promoted by Dabomb87 21:15, 23 March 2011 [1].
Philadelphia Phillies all-time roster (E–F) (edit | talk | history | protect | delete | links | watch | logs | views)
Toolbox |
---|
- Nominator(s): — KV5 • Talk • 21:14, 5 February 2011 (UTC)[reply]
My current open nomination has four supports and no open complaints, so I'm nominating the fifth list in the series for featured status. All comments to be expediently addressed. Many thanks for your interest. — KV5 • Talk • 21:14, 5 February 2011 (UTC)[reply]
Resolved comments from The Rambling Man (talk) 17:08, 10 February 2011 (UTC)[reply] |
---|
Comments
The Rambling Man (talk) 18:18, 9 February 2011 (UTC)[reply]
|
- Support The Rambling Man (talk) 16:30, 27 February 2011 (UTC)[reply]
- Support – Don't see any problems here. Giants2008 (27 and counting) 00:28, 17 February 2011 (UTC)[reply]
I was asked to return by the nominator after the merge, and spotted only one new issue: the note above the table needs to be updated by mentioning the letter F (only E is mentioned now).Other than that, the merge has been done effectively and I feel comfortable retaining my support. Giants2008 (27 and counting) 01:05, 21 March 2011 (UTC)[reply]- There are two tables; each has its own caption. — KV5 • Talk • 01:33, 21 March 2011 (UTC)[reply]
Resolved comments from Courcelles 22:46, 21 February 2011 (UTC)[reply] |
---|
*One niggle, in the seasons column, why is Ennis's 2007 sorting between Eaton and Eyre? Courcelles 05:38, 19 February 2011 (UTC)[reply]
|
- Support Hacks are sometimes required to make sorting function, good work. Courcelles 22:46, 21 February 2011 (UTC)[reply]
- I think I preferred these separate, as it allowed a more focused lede to each group, but, so be it. Courcelles 23:28, 20 March 2011 (UTC)[reply]
- I agreed. — KV5 • Talk • 23:39, 20 March 2011 (UTC)[reply]
- I think I preferred these separate, as it allowed a more focused lede to each group, but, so be it. Courcelles 23:28, 20 March 2011 (UTC)[reply]
- Support, I see no issues beyond what was already addressed. Wizardman Operation Big Bear 17:28, 24 February 2011 (UTC)[reply]
- Reiterating support after reading through post-merge article. Wizardman Operation Big Bear 14:23, 22 March 2011 (UTC)[reply]
OpposeI think I am going to be labelled as the CFORKing guy, but why is this list separate from the "F" one? It has only 32 entries and with the F one would barely pass 100. There are a few well beyond 150 entries so I don't think it would be too much. Splitting under 1900 players in something like 20 FLs is too much. I think the aim should be closer to 10. Nergaal (talk) 20:27, 25 February 2011 (UTC)[reply]
- The goal was for lists with 10 or fewer players to be subsumed into others. 32 entries is more than enough to constitute a stand-alone list. — KV5 • Talk • 00:07, 26 February 2011 (UTC)[reply]
- Agreed with KV5, this passes 3b. Courcelles 03:50, 26 February 2011 (UTC)[reply]
- Agreed. When did 32 become too few elements to have a stand-alone list? The Rambling Man (talk) 16:30, 27 February 2011 (UTC)[reply]
- It is not that it is too few, but that the 1.9k players are split over too many lists. Nergaal (talk) 17:42, 28 February 2011 (UTC)[reply]
- You're objecting on the grounds of forking. This doesn't cover "too many lists" as far as I've ever read. Can you clarify your position with respect to WP:WIAFL? The Rambling Man (talk) 22:01, 28 February 2011 (UTC)[reply]
- Agree with TRM. The scopes of these particular lists are very clear, and each fully meets the requirements for stand-alone lists as set out in WP:SAL. We have featured lists of all sizes, and there's no criterion in WP:FL? that states a list may only be split when it reaches a certain size. In addition, you must view the split itself as a whole. This is not the "E" sublist split from the "F" sublist; rather, it is the "E" list split from the original list, and viewed in that sense, it truly does not violate 3b, because it could not reasonably be included as part of the main article. — KV5 • Talk • 00:54, 1 March 2011 (UTC)[reply]
- Take the following alternative scenario: if the original editor who split the main list into 10 distinct lists (instead of 20) and would have nominated the one named "E-F" I am sure nobody would have complained in that nomination about splitting E and F into separate articles because 111 is too much for a FL. FLs with more than 100 entires are passed on a regular basis these days, so I don't see how 111 would be a problem. The (original) intentn of CFORK (to my understanding) is to not split content more than it is necessary just to bump up the featured content count. Nergaal (talk) 05:04, 4 March 2011 (UTC)[reply]
- You're objecting on the grounds of forking. This doesn't cover "too many lists" as far as I've ever read. Can you clarify your position with respect to WP:WIAFL? The Rambling Man (talk) 22:01, 28 February 2011 (UTC)[reply]
- It is not that it is too few, but that the 1.9k players are split over too many lists. Nergaal (talk) 17:42, 28 February 2011 (UTC)[reply]
- Agreed. When did 32 become too few elements to have a stand-alone list? The Rambling Man (talk) 16:30, 27 February 2011 (UTC)[reply]
- Agree with the above objection; Policy clearly states that articles should be kept together. This translates into merging as many of the lists, as size and sorting permits. Precedence can be seen in the lists of gay/bi-sexual people. Sandman888 (talk) 16:16, 2 March 2011 (UTC)[reply]
- WP:AVOIDSPLIT is part of a guideline, not a policy, does clearly not say "articles should be kept together" but is all about ensuring articles meet notability criteria when split off, to whit: "Editors are cautioned not to immediately split articles if the new article would meet neither the general notability criterion nor the specific notability criteria for their topic." This article clearly meets the notability criteria, so no problem. And yes, other stuff exists. The Rambling Man (talk) 16:58, 2 March 2011 (UTC)[reply]
- "could not reasonably be included as part of a related article" is an FL criteria, which parallels the logic in avoiding small splits. The reference to wp:otherstuff is quite hollow; it is common to refer to other FL list to determine application of policy, but you already knew that. Sandman888 (talk) 09:04, 7 March 2011 (UTC)[reply]
- WP:AVOIDSPLIT is part of a guideline, not a policy, does clearly not say "articles should be kept together" but is all about ensuring articles meet notability criteria when split off, to whit: "Editors are cautioned not to immediately split articles if the new article would meet neither the general notability criterion nor the specific notability criteria for their topic." This article clearly meets the notability criteria, so no problem. And yes, other stuff exists. The Rambling Man (talk) 16:58, 2 March 2011 (UTC)[reply]
(→)TRM, splitting "per the alphabet" is your preference, isn't it? Show me a rule where I could see the "split lists per alphabet" line. There's none! I see no guideline supporting your position, either. Greatorangepumpkin, "E-F" will have less players than "C" and "B"(which are alread at WP:FL). If you're worried about lagging, you can submit "B" and "C" at WP:FLRC.Cheetah (talk) 21:29, 3 March 2011 (UTC)[reply]
Comment To get this out of the way at the start rather than the end of the post, I have grumbled about these lists, a lot. Possibly too much. Grumble though I may, it's beyond dispute there is consensus for the format. That said, the end of 3b ("could not reasonably be included as part of a related article") would seem to support Cheetah's specific suggestion of merging E and F. —WFC— 10:28, 4 March 2011 (UTC)[reply] |
- Support Thank you KV5 for your patience. I just went over all Phillies lists and the only lists that can still be merged are T-Z. Right now it's split into 4 lists, I think it can be 2 at the most. That's a comment for the future.--Cheetah (talk) 01:22, 21 March 2011 (UTC)[reply]
- Thanks, Cheetah; to address your final concern, if you look at the very bottom of the nom section, I have proposed merging T-V and W-Z to complete the series. Those merges will be done when (if) this passes and before I nominate G. One project at a time. — KV5 • Talk • 21:31, 21 March 2011 (UTC)[reply]
- Then I support your proposal.--Cheetah (talk) 02:32, 22 March 2011 (UTC)[reply]
- Thanks, Cheetah; to address your final concern, if you look at the very bottom of the nom section, I have proposed merging T-V and W-Z to complete the series. Those merges will be done when (if) this passes and before I nominate G. One project at a time. — KV5 • Talk • 21:31, 21 March 2011 (UTC)[reply]
Oppose on 3b, per my rationale below; E and F could reasonably be merged. —WFC— 01:29, 16 March 2011 (UTC)[reply]
Neutal Based on the discussion that has taken place here, and the merge, I have agreed not to oppose this on 3b. I trust the judgement of The Rambling Man, Giants2008, Courcelles and Wizardman as far as the quality of this list goes. —WFC— 23:16, 20 March 2011 (UTC)[reply]
- If E and F were merged (or even if not), could we at least get consensus that all the other current and future ones are acceptable so we don't have to go through this again? Wizardman Operation Big Bear 16:08, 15 March 2011 (UTC)[reply]
- Since all these articles are technically cforks, I think if they are split in a reasonable manner everybody will be happy. I am of the opinion that if the total is around 100 entries then that is an acceptable split. If Y+Z has 8+7=15 entries in total, that does not mean it is an acceptable split. U-Z has about 100 so I think that is an acceptable one, instead of slicing each possible letter that has 10 entries. Nergaal (talk) 16:20, 15 March 2011 (UTC)[reply]
Resolved discussion on 3(b). Capped by WFC |
---|
**I'm near enough with Nergaal. There is unquestionably consensus for an alphabetical split of sorts. The question now is just ensuring that the individual splits are reasonable. —WFC— 17:43, 15 March 2011 (UTC)[reply]
|
- Separate suggestion I intend to continue the above discussion, whether that takes place here or elsewhere (for instance an RfC). But I do feel that we should do what we can to ensure that the Phillies lists are promoted as quickly as is possible. And that, as far as we can in the circumstances, minimise the drama. I would therefore propose that another Phillies list be granted an exception to the usual convention of only one list at a time. There is no issue with the overall quality of these lists, save for whether some individual ones meet 3b. To assist with the reduced drama aspect, I would suggest that the list nominated should be the longest remaining list, as that can reasonably be assumed to be the one least likely to be affected by a merge proposal. It takes an average of three to four weeks to promote an FL: even if were to take us a couple of months to work this out, there should be 3-4 relatively uncontroversial ones which can be promoted in the meantime. —WFC— 00:33, 16 March 2011 (UTC)[reply]
- How short of a nomination period are we talking about? I don't feel comfortable with making the period too short for any list, even if it's in a series that is typically trustworthy quality-wise. For example, TRM continues to find issues to report in the MLB first-round draft picks series of lists, which are all of high quality. It's also possible that a reviewer who hasn't read lists in the series will spot problems that us regulars are missing. Then again, I also feel that this list should be promoted, and that the opposers are taking 3b beyond what it was intended to do (ensure that forky lists that shouldn't exist at all don't become featured, not determine how large a particular list should be), so what do I know? Giants2008 (27 and counting) 23:10, 16 March 2011 (UTC)[reply]
- BTW, I didn't mean a quick pass procedure. I just meant an exemption from the usual rule of not being allowed to nominate a second list where the first has opposition, as the nature of the opposition here would have no effect on the longer lists (safer bets include H, M and S). —WFC— 02:03, 17 March 2011 (UTC)[reply]
- I would have no problem with that as long as we don't go overboard. We don't need six of these lists up at once, but if a list other than this one was nommed now I wouldn't object. Giants2008 (27 and counting) 21:05, 17 March 2011 (UTC)[reply]
- BTW, I didn't mean a quick pass procedure. I just meant an exemption from the usual rule of not being allowed to nominate a second list where the first has opposition, as the nature of the opposition here would have no effect on the longer lists (safer bets include H, M and S). —WFC— 02:03, 17 March 2011 (UTC)[reply]
- Support Some level of merging, as has occurred, was probably a good thing. The list was always of high quality, this seemed like a pretty odd thing to hang up the nomination over (as it could be easily remedied if a different standard was decided on. Staxringold talkcontribs 23:15, 20 March 2011 (UTC)[reply]
- Given the respective positions of those in favour of and opposed to a merge, thrashing out a merge at this FLC was undoubtedly the least-worst option. If it didn't come here, it would only have happened in future at FLRC, or through an RFC which ultimately would have been focussed on these lists anyway. As a result of this discussion, the lists from G-S can now go through FLC uncontroversially, an RFC will only happen if others mimic the approach taken here.
and I'm sure that KV and Cheetah will find a solution by the time T-Z become an issue.just realised that T-Z have already been dealt with. The compromises that came as a direct result of the deadlock here have produced a stable situation. —WFC— 19:13, 21 March 2011 (UTC)[reply]
- Given the respective positions of those in favour of and opposed to a merge, thrashing out a merge at this FLC was undoubtedly the least-worst option. If it didn't come here, it would only have happened in future at FLRC, or through an RFC which ultimately would have been focussed on these lists anyway. As a result of this discussion, the lists from G-S can now go through FLC uncontroversially, an RFC will only happen if others mimic the approach taken here.
- I stroked out my oppose vote since my major concern was solved. I think though the two tables should be fully merged - you could leave a separator in the middle by selecting that row to be unsortable. Nergaal (talk) 01:22, 21 March 2011 (UTC)[reply]
- On that, I heartily disagree, because these are two separate lists contained in the same article, similar to the split lists of the Rawlings Gold Glove Award series (example: List of Gold Glove Award winners at catcher). — KV5 • Talk • 01:30, 21 March 2011 (UTC)[reply]
Comment glad that we're slowly reaching a consensus. I'm not saying it's right, but if we can move on from this, so much the better. My primary concern, perhaps my only concern is the subjective merging of lists. This is now setting the precedent that editors can hand-pick the "best" merges. I guess, as we have consensus, that's the way forward. However, I don't want to see people, in the future, arguing over whether L and M should be merged with N etc... Remember WP:SAL etc. The Rambling Man (talk) 18:53, 21 March 2011 (UTC)[reply]
- I disagree with this, but as my disagreement has nothing to do with this FLC, I've responded on The Rambling Man's talk page. —WFC— 19:41, 21 March 2011 (UTC)[reply]
- And I disagree, in part, with WFC's disagreement, but this disagreement over a disagreement has nothing to do with this FLC. I've replied at my talk page. The Rambling Man (talk) 19:44, 21 March 2011 (UTC)[reply]
Support I bought a new computer yesterday and I have no lags now. I red this list weeks ago and I saw no issues. I make a second run and still no issues. A great list even if I haven't seen any baseball games :P.--♫Greatorangepumpkin♫T 19:26, 21 March 2011 (UTC)[reply]
- The above discussion is preserved as an archive. Please do not modify it. No further edits should be made to this page.