• We have completed three more interviews this week, with another scheduled
• Two more interviews are being scheduled
• We are preparing to interview survey respondents who indicate interest in being contacted (T371135#10263674)

Weekly update:

Weekly update:

Recruitment efforts ongoing for the former admin segment.

Please add the following projects:

Thanks to Xiao for telling me about this!

Weekly updates:

Update:

• Reached out to Movement Comms to assist with recruitment
• Translations received for outreach messages, localization of outreach messages, scheduling tool, and privacy releases completed
• Recruitment has started for the enwiki former administrator segment
• Recruitment slated to begin for idwiki and frwiki former administrators

Update:

• Assisted with survey piloting efforts
• Consultations with staff members who work closely with ru, fr, id Wikipedia communities, to better prepare for interview recruitment and discussion plans
• Preparing recruitment for ex-administrator segment

• Discussion guide finalized (internal link)
• Outreach emails, scheduler tool, and adapted privacy release form ready for translation (thanks to Bethany!)

Belated weekly update: continued development of the discussion guide. The guide will essentially be split into a "current admin/survey participant" version, and a "non-participant/ex-admin" version, since those are our two key groups for recruitment. The aim is to have interview materials ready in parallel with the survey materials, so that feedback, privacy review, and other logistical tasks can be handled simultaneously with the survey logistical requirements.

Weekly update:

Weekly update:

• Worked on finalization of wiki selection
• Finished getting and cleaning RFA statistics for 11 wikis, working on finding where to publish/if it should be published
• Contributed to writing updates for the public Meta page for the project, around final wiki selection

Weekly update:

Weekly update:

• Contributed to survey development plan
• Wrote draft version of updates for the public project page on Meta (officewiki draft available here)
• Evaluated administrator candidacy advice across 21 wikis to help shape "potential administrator" population segment for survey development plan
• Conducted an examination of publicly available statistics around Requests for Administrator on English Wikipedia

The finalized report is now available at Commons, and I have gone through project close-out steps. Marking this task as resolved.

Weekly updates:

Weekly update:

• Added more works to Zotero library + annotated bibliography summaries
• Contributed to public project page, added prompts and a research sign-up to the talk page
• Continued work on key term definitions

Finalized report is ready for internal review, and a share-out has been scheduled for Aug 8. Our current plan after the share-out is to write a summary update for the project page, and to publish the results on Commons so that this research is publicly available.

Quick update: Version 2 is getting closer to completion. Sections from other contributors have been integrated, mostly waiting on one more section edit, and a final pass. I should still be able to make the end-of-July deadline for this project.

Preliminary analysis is complete: Internal-use slide deck.

Qualtrics survey is closed with a total of 82 completed responses, which exceeds our targeted minimum of 50. We're now beginning work on survey analysis.

Weekly update - we are currently monitoring responses to the survey. Total responses are low so far, with 33 qualified respondents. We have another week when the survey is open but we may need to discuss adjustments to recruitment in order to hit our 50 reply target minimum.

In T368027#9913044, @kamila wrote:

@cwylo Can you please confirm that you have read the Analytics Data Access User Responsibilities ? Thank you!

I will likely prioritize this task starting Jun 24, since I will also be away at a Trust & Safety offsite from Jun 17 - 21. A deadline for the second week of July is possible, but tight, especially given my other commitments (T362462, preparations for said offsite). @leila Could I propose that a first draft be done for the second week of June, rather than trying to finalize the work by then? This would also give time for Diego, Martin and Pablo's contributions given the constraints of the Wiki Workshop.

Weekly updates are on hold until the recruitment Quicksurvey is deployed (T362969).

One of the key difficulties I see here is that "editor groups" are totally arbitrary assignations, generally organized on top of however that specific wiki has configured their user rights, user groups, and intended roles. I believe there are two main approaches we could take in order to classify editor groups: classification by socially-defined roles and classification by permissions.

After further discussions about this draft KR, we determined that this would be best achieved by creating a standardized methodology for collecting information about product satisfaction, and user-level/community-level product adoption. This would provide an advantage in reducing the amount of repeated preparatory work (e.g. reusable versus bespoke privacy statements, transferrable localization) and allow us to better cross-compare adoption and satisfaction across different products. The current intent is to collect fairly high-level satisfaction/adoption metrics, and fine-tune these on a per-project basis.

Weekly update

• QuickSurvey text and response localization finished (T362969)
• Qualtrics survey has been opened for responses using an anonymous survey link

QuickSurvey text and response text are as shown in the table below:

Updates on survey preparation (with backdates):

• Survey question bank finalized (Apr 26)
• Localizations completed for fr/hi/id (privacy statement, QuickSurvey statements, survey question bank and descriptive text) (May 01)
• Survey framework completed and set up in Qualtrics (May 09)

First draft is ready for comment.

Timeline update (pinging @Katherine.gatewood). Preliminary draft should be ready for review at the end of March. Factoring in revisions, I believe a more accurate delivery date would be some time between the first to second week of April. Apologies for slippage!

A rough analysis of daily total edit counts for those wikis where we have qualitative data (Punjabi, Tamil, Ukrainian, Bengali) indicates that a key cut-off point is about 1000 daily total non-bot edits. On wikis with daily total edits above 1000, we find more evidence that patrollers need assistance in the form of tools, filters, watchlists or other ways to manage the flow of incoming edit. Under this number, and a wiki with the average number of monthly active admins (10) plus some number of active patrollers seem to generally be able to keep up with the flow of edits.

From previous work on patrollers, primarily through previous work for Moderator Tools in 2022 and Patrolling on Wikipedia, we know we have identified these broad types of content moderation queue:

New project for close-out.

Elaboration on the patrol permission (source) - this seems pretty tied to the concept of marking new pages as having undergone review, either via Special:RecentChanges or Special:NewPages. The permission allows a user to mark a page as "patrolled". (Contrast autopatrol, which automatically marks all edits made by that user as patrolled.)

In T297961#7578116, @Prtksxna wrote:

In T297961#7578029, @STran wrote:

I skimmed the csv and it can be a combination of many. One notably had four associated with it: is_anonymous,is_anonymous_vpn, is_hosting_provider, is_public_proxy

@cwylo @STran do these values logically make sense, as in can IPs be VPN, Hosting provider and a Public Proxy at the same time?

In T271671#6734980, @Prtksxna wrote:

@cwylo based on the interviews you conducted, do you think these value/color combinations make sense?

The completed public writeup can be found here: Patroller Use of IPs

To clarify, "checkuser requests" in this ticket refers to use of the CheckUser extension, not requests from administrators asking checkusers to use the extension.

In T251797#6106849, @jwang wrote:

@cwylo, can you clarify what are advanced permissions?

I'd suggest eswiki, potentially zhwiki as a known outlier that relies entirely on steward CU work (but is of a comparable size to wikis with medium-sized local CU groups).