This task (or a version of it to be updated later in Q2) is now a blocker for T371865 (work on "who are moderators" that we will need to do in January 2025 and afterwards). As a result, I moved it back from Research-Freezer to the Research board and for now will move it to the January-March quarterly lane until details of scope and who will do what is clearer.

context for the due date: Miriam will prepare the report by December 4th. There will likely be needs for iterations that @diego will pick up as Miriam's delegate at that point. Diego will bring the report to the finish line by the due date as relevant.

@KinneretG in the Research portion of that survey, I'll link to https://research.wikimedia.org/contact.html to encourage developers to get in touch with us if they have questions. That is why I made this task effectively a "dependency" for that task. (to be fair: only a portion of this task will be the dependency, but I didn't worry about that level of accuracy.;)

@diego Thank you for the update.

@KinneretG Research Report and Research Weekly meeting notes are the two places I recommend checking. At this moment the team is at capacity so my ask is that you work with the information you have for this page. It is okay to just have a plan for how you will handle it moving forward given that there is a 5-year laps in updating it.

@KinneretG the verdict ;) is: You will present in December's P&T Staff meeting. I added the task deadline. I will move your presentation to the team (originally scheduled for October 29th) to a bit later to give you some time and also to remove a conflict which is the result of Daylight saving next week and the calendar events having too many conflicts.

Thank you, @Sdrqaz.

Claudia and I talked. Given the AoIR conference being next week and then OoO schedule: Claudia will send the draft to me on November 1st. This will be an extended abstract. I'll have the review ready for when Claudia is back. The November 24th deadline remains.

@ppelberg we reviewed this task in Research's backlog refinement meeting today. Our understanding is that this testing will happen on your team's end. You may need support (consulting or otherwise) from research scientists or design researchers on our end. If that ends up being the case, please let Xiao or myself (accordingly) know and we will work on prioritization on our end. Otherwise, we look forward to learn from what you learn and support you with possible next steps.

We discussed this task in backlog refinement today. set the deadline and priority based on earlier conversations and agreements.

We discussed this task in today's backlog refinement meeting and set the deadline (based on the original time estimate given by the team). Moving to In progress as work is in progress.

@MRaishWMF thank you for the work and the update. When should we expect to see it out? : )

@Barkeep49 thank you for letting me know and your note. (And thank you for your work on U4C). I will remove you as an assignee and assign back to myself for now.

@Barkeep49 I have moved the task to our sign-off lane in preparation to the upcoming conversation with ArbCom. I have also assigned the task to you so it's clear on our end that we are requesting a sign-off from ArbCom. Please feel free to re-assign to someone else in the group. Also, if this doesn't sound right to you for some reason, please assign the task back to me and I'll be the bearer until we all connect. :) (context for sign-off at the start of the paper). Looking forward to the next steps. :)

Weekly update:

• Eli informally connected with some members of enwiki ArbCom during WikiCon NA and did a temperature check on our plans for next steps.
• Given that overall what we had in mind sounded good to folks who Eli talked with we spent the last two weeks finalizing the paper and devising a plan for next steps.
• The paper is now ready for enwiki ArbCom (original requester) to review and sign-off if they see fit. Copy of the paper in a google document along with our questions, discussion suggestions and draft next steps. We hope to discuss these in the upcoming ArbCom meeting in November (if possible for the group).

Bethany and I met with Rita today. We concluded that:

• This task was not scoped in detail for Bethany and it was not officially communicated to her in the past.
• Bethany has done some work that can be used as part of the developing of the material for this task.
• We will use the upcoming offsite and the session Bethany and Carolyn are organizing to learn more about the needs on the Design and Design Research end and we will set a deadline once we better understand the teams' needs and the opportunities we learn about from those conversations.

Until mid-November, this task will stay in Research's Backlog with not much/at-all updates. Bethany may work on the outline of the module itself in preparation for future work but she will not spend a lot of time on it as it's not staged, yet.

@CSciubba the (private) document is now in the final version. I'm going to resolve this task. Please re-open if you need help with something.

@MunizaA I'm moving this task to in-progress b/c I'm closing the first quarter's lane. Please take the appropriate next steps with it.

@Isaac I'm closing the quarterly lane. I'll move this task to in-progress. Please close it when ready. Thanks for the work. :)

@diego thank you to you and everyone in the team, as well as Marshall, Mikhail, Miriam, Rita and Xiao who worked behind the scenes to secure the resourcing for this hypothesis. I appreciate everyone's proactive approach in offering time and resources.

@bhuvana

• I'm going to remove this task from the Research Backlog as the high level goal described in the task description is outside of the scope of what we (Research team at WMF) supports.
• I have reached out to colleagues in the WMF and notified them about this task. They may reach out to collaborate with you on this task. However, please don't feel you're blocked or you have to wait for others. : )
• When I checked with others, folks mentioned that the task description is ambiguous. You may want to work on it and make it more specific or clear.
• A resource that may be helpful for you to look into, if you already have not is https://design.wikimedia.org/style-guide/resources.html .

We are doing two other roadmaps: knowledge integrity and research community at the moment. The team will not have energy for another full roadmap work. I'm moving the parent task to freezer. We are working on some subtasks or related tasks (AI strategy, data platform strategy) that will inform this work once we pick it up.

Xiao and I talked about this task separately. I'm going to resolve it b/c we have moved away (as an organization) from writing one big detailed annual plan for the whole year. Instead, we're doing planning as we go.

Bethany is finalizing the implementation steps after receiving team feedback on Tuesday. We're working on communicating the changes. I extended the deadline to allow for this last piece to be done.

@KinneretG How about the November Product and Technology Staff meeting? I can request a timeslot if that works for you.

@Miriam thanks for your work and the team's work on this hypothesis and congrats on concluding it. As I have mentioned to you separately, I'm really happy to see how much we have learned as a result of this work over a span of a few months.

Weekly update:

• Eli did a major push over the past two weeks. Michael helped and I helped off and on. The document is super close to be done.
• We got a couple of good real world examples to start testing the document with (researchers who reached out and had questions about how to handle specific privacy related topics).

@XiaoXiao-WMF more categories at the level of existing headers. The specific category I now have in mind is: offline ML tools and services Fabian and Muniza have built. See for example (private): https://office.wikimedia.org/wiki/Team_interfaces/SRE_-_Observability/Documentation

@KinneretG I had a quick look. I must say that the familiarity of the template is so comforting for my eyes. ;) A couple of notes:

• I'm in the department offsite in the coming week and have declined/cancelled all my usual meetings. If you're blocked, please ping in Slack and we can find a time. otherwise, proceed in the coming week without me.