Wikipedia talk:Abuse response/Strategy

Latest comment: 14 years ago by Netalarm in topic Nomination process

Bots and automated functions

edit

(Moved from archive main talk page.)

  • Count and list blocks across an IP range
  • Count edits across an IP range
  • Count warnings across an IP range

Developing...   Thorncrag  00:20, 17 August 2010 (UTC)Reply

I just found a new way to do these lol, I still have to look into what is possible without killing the toolserver. Are we looking for these on IRC or onwiki? (Wiki is going to be a heck of a lot longer just because of BRFA and other programing delays. -- DQ (t) (e) 01:18, 5 September 2010 (UTC)Reply

Escalating forms of contact

edit

[Forthcoming]

Information packet for ROs

edit

[Forthcoming]

Regular meetings

edit

It has been proposed to set a regular scheduled meeting to take place on #wikipedia-en-abuse connect.

Nomination process

edit
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.
The original proposal for a nomination process where an existing project member was required to nominate a new member failed, resulting a an alternate proposal which succeeded with unanimous support. Modify the nomination instructions to request and strongly encourage the nominee to contact a current member for guidance on nominating themselves and remove the step-by-step instructions. This will allow the project person to help them through the process and also introduce to the other members and learn about the prospect and give advice on how to proceed. Netalarmtalk 05:19, 14 October 2010 (UTC)Reply

I propose changing from self-nomination to requiring an existing project member to nominate another. Reasons should be obvious. Please Support/Oppose/Discuss here. This will take effect immediately for any new nominations following any currently open.

  Support as proposer.    Thorncrag   00:45, 1 October 2010 (UTC)Reply
  Oppose Some of our best users are self nominated, but I see the ful reasoning behind it. Maybe we could say contact a project coord if your're interested. I think since we already go through the nom process, it's good enough. -- DQ (t) (e) 00:51, 1 October 2010 (UTC)Reply
  Oppose I just learned that the proposal the way it is now is against community principles, so have to oppose for now. Bobby122 Contact Me (C) 01:04, 1 October 2010 (UTC)Reply
  Oppose Self electing groups are not consistent with Wikipedia's community principles, particularly relating to the openness of the project. See Wikipedia:Requests_for_comment/Self_electing_groups for more information. Netalarmtalk 01:56, 1 October 2010 (UTC)Reply
  Oppose As per Netalarm. Phearson (talk) 04:00, 1 October 2010 (UTC)Reply
  Oppose While I can see benefits from introducing the proposal, Delta and Netalarm concerns are valid. Acather96 (talk) 12:55, 2 October 2010 (UTC)Reply
  Oppose Probably wouldn't work... There are often people who want to join but don't know anyone else in this project. Pilif12p :  Yo  19:10, 2 October 2010 (UTC)Reply
  Oppose - Supporting alternative proposal. Mlpearc powwow 15:24, 4 October 2010 (UTC)Reply
  Oppose - I oppose as well. Self nomination is essential with Wikipedia, if sysops can be self nominated, why shouldn't other projects? --WolfnixTalk17:21, 10 October 2010 (UTC)Reply

Initial Discussion

edit
  • Just to clarify, this is not changing self-election (which we technically already are) only nomination. Modeling OTRS, where the community does not approve members they are approved by the administrators. So we aren't as strict as OTRS. That all being said, I would not ignore votes from outside our group on nominations, either. So in that respect, we are not self-elected anyhow.    Thorncrag   02:04, 1 October 2010 (UTC)Reply
    • Amend proposal. I propose adding a very prominent notice on the nomination page to clarify that community votes and input is allowed and in fact very warmly welcomed. None of us would remove community votes or ignore them, so we are not self-elected.    Thorncrag  

Alternative Proposal

edit

Seeing that the previous proposal wasn't thoroughly thought through, I think a sufficient compromise would be to:

  • Modify the nomination instructions to request and strongly encourage the nominee to contact a current member for guidance on nominating themselves and remove the step-by-step instructions. This will allow the project person to help them through the process and also introduce to the other members and learn about the prospect and give advice on how to proceed.

  support as proposer.    Thorncrag   02:06, 3 October 2010 (UTC)Reply

  support - I think this is a good modification to our current system, and a good alternative to the other proposal Enti342 MEMO

  Support - This seems better. Mlpearc powwow 15:21, 4 October 2010 (UTC)Reply

  Support - This proposal is better. Bobby122 Contact Me (C) 22:58, 4 October 2010 (UTC)Reply

  Support - Looks better. Pilif12p :  Yo  21:45, 8 October 2010 (UTC)Reply

  Support Better. -- DQ (t) (e) 17:21, 10 October 2010 (UTC)Reply

  Support - I agree, this is quite like what happens. I believe that some sort of wikibased form/information should be done, but mainly person-to-person contact (Even if they don't have an IRC client, webchat is available.) --WolfnixTalk17:24, 10 October 2010 (UTC)Reply

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

Inactive and lapsing membership

edit
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.
Members that have not active participated (broadly construed) in the abuse response project will be delisted after a period of thirty days and will have to renominate themselves to resume membership. The opposes have not addressed the argument of the multiple supports with valid points, and further discussion regarding exceptions may be held, but the general idea has support.

We need a mechanism incorporated into the guidelines to remove inactive and lapsed members. I propose the following:

  • A member who has not actively participated (broadly construed) in project activities shall be considered inactive after a period of 30 days.
  • A member who has not actively participated (broadly construed) in project activities shall be de-listed as a project member and will be required to re-nominate thereafter to resume membership.
  • Where any disagreement exists consensus for the status change must be reached.
  support as proposer.    Thorncrag   01:21, 1 October 2010 (UTC)Reply
  Oppose Creates extra work. Phearson (talk) 04:04, 1 October 2010 (UTC)Reply
  Support. This will help maintain a list of users that are active so we can more easily gauge the state of the project. It'll also help us eliminate any user that's just here for "hats." (which is a significant problem in most counter-vandalism/abuse projects) Netalarmtalk 06:36, 1 October 2010 (UTC)Reply
  Support Per Netalarm. Acather96 (talk) 12:57, 2 October 2010 (UTC)Reply
  Support - Also per Netalarm. Mlpearc powwow 15:19, 4 October 2010 (UTC)Reply
  Support sounds fine. Pilif12p :  Yo  17:10, 10 October 2010 (UTC)Reply
  Support I agree, that inactive users should be moved to an inactive list. I believe after 60 days they should need to be renominated. --WolfnixTalk17:15, 10 October 2010 (UTC)Reply
  Oppose Just dimissing members because of inactivity is not what we should be doing, maybe in unexplained absense yes, but not if explained. -- DQ (t) (e) 17:20, 10 October 2010 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Community outreach and awareness

edit

[Forthcoming discussion on outreach to the Wikipedia community and raising awareness]