New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CSD criterion A11: Obviously made up #184

Merged
merged 1 commit into from Oct 24, 2013

Conversation

Projects
None yet
6 participants
@jackmcbarn
Contributor

jackmcbarn commented Oct 24, 2013

No description provided.

@Technical-13

This comment has been minimized.

Contributor

Technical-13 commented Oct 24, 2013

Be advised that this new criterion is contested as harmful to Wikipedia and there has been no RfC consensus to enact or create it. See discussion: http://en.wikipedia.org/wiki/Wikipedia_talk:Criteria_for_speedy_deletion#Going_forward

@jackmcbarn

This comment has been minimized.

Contributor

jackmcbarn commented Oct 24, 2013

Technical 13 seems to be the only one who believes that, if you look at the discussion he linked to (and the one on WT:TW).

@theopolisme

This comment has been minimized.

Contributor

theopolisme commented Oct 24, 2013

I do not have enough time to weigh in at the discussion on-wiki, but, tl;dr, I think that the A11 criterion is [[WP:CREEP|quite creepy]] and should not have been added without significantly more discussion. Some famous last words:

Or should we stick an RFC on top to seek wider opinion? --Fuhghettaboutit

Yeah, when you're making a new method for pages to be deleted, that's probably a good idea.

@theopolisme

This comment has been minimized.

Contributor

theopolisme commented Oct 24, 2013

So, whilst I do not necessarily believe it to be "harmful", I do believe it should have been better advertised and discussed by more folks that just the [[WP:CSD]] regulars.

@mc10

This comment has been minimized.

Collaborator

mc10 commented Oct 24, 2013

I'm going to wait on this one for now, at least until some more support is shown. As a technical note, if A11 is approved, the deletion reason must be added to MediaWiki:Deletereason-dropdown so that admins can choose A11 as an appropriate deletion reason.

@Technical-13

This comment has been minimized.

Contributor

Technical-13 commented Oct 24, 2013

Hopefully the new RfC: http://en.wikipedia.org/wiki/Wikipedia_talk:Criteria_for_speedy_deletion#RfC:_Does_Wikipedia_need_three_different_CSD_criterion_for_.22No_indication_of_importance.22_or_should_they_all_be_merged_into_one.3F will offer some final consensus on this. I invite everyone to participate, whether or not you agree with the proposal or not. Thanks.

@atlight

This comment has been minimized.

atlight commented on 88bc530 Oct 24, 2013

You should read the comment at the top of twinklespeedy.js. (read "twinkle.js" for "twinkle.header.js")

@Amalthea

This comment has been minimized.

Collaborator

Amalthea commented Oct 24, 2013

While I'm personally not convinced that we needed that criterion, the discussion was closed by Beeblebrox saying "Consensus seems pretty clearly in favor of the addition of this criterion", it's currently on the policy page, and despite an ongoing RfC it is not currently apparent that consensus has changed.
For now, it seems to be community policy, and Twinkle should reflect that, no matter our personal opinions.

I've added it to to MediaWiki:Deletereason-dropdown, thanks for the note mc10

@atlight

This comment has been minimized.

Collaborator

atlight commented Oct 24, 2013

Yes, per my comment at WT:TW we can merge this once the comment on the pull request patch is dealt with. (or possibly in a separate commit, but I don't have time right now...)

@Amalthea Amalthea merged commit 88bc530 into azatoth:master Oct 24, 2013

@Amalthea

This comment has been minimized.

Collaborator

Amalthea commented Oct 24, 2013

Ah, I didn't read WT:TW, just got a lot of mails. :)
I've made the changes you mentioned in a separate commit and merged/deployed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment