@kostajh it should be a "destructive" delete per Codex / DS guidelines which I agree with it's a major action that we want to effectively communicate to the user. This pop up only shows when the user has made it to the step with the form which auto-populates with information. Even if we're not saving anything in the back-end, this experience still gives the impression that we've saved some possibly sensitive information so, after back and forth with DS, we went with the copy "Delete".

Per Codex, there's no border below the title ("Report Incident") on the desktop dialog component. There is for mobile.

@kostajh just jumping in here hope that's alright!

@JSengupta-WMF Some ongoing conversations I want to point you to:

• The user flow diagram in Figma and Abigail's comment on how do we decide where to route reports.
• Also in the user flow diagram, another important discussion on routing
• In Slack we have a thread going regarding @dchen 's research report on Indonesian Wikipedia

thanks @kostajh I like your recommendation. Let's streamline the information on the page and go with what you've suggested. Meanwhile I'll update Figma and Gdrive.

hey @kostajh yup that's the correct drive! I actually wasn't sure when and in what capacity you're back and working so my bad for not communicating that to you sooner :)

thanks for explanation @Mooeypoo !!!

hi all, the page titled "Spec (08/23/23)" in this Figma file is the latest copy of the design yes.

Great QAing Derrick. Love how detailed you're being.

I don't fully understand what a user will see if we do a byte limit. Otherwise, Kosta's suggestions sound good to me.

I made this ticket T344639 yesterday on this very subject and assigned it to @eigyan

@STei-WMF @Madalina can we share the journey map with the Community on our project page and see if they have any feedback? I'm curious if I've gotten the assumptions right.

hey @ppelberg thanks for sharing the Figma file. I love seeing how your team works! for example, I've never seen this "spotlight" technique but it's definitely helpful!

Looking at this helpful resource on journey mapping: https://www.youtube.com/watch?v=xK-2IE93HgQ

Some thoughts from me and the design team:

@Madalina this ticket can be closed!

The research has concluded and we're waiting on an update from @dchen about the synthesis and the report.

I also updated the local reporting workflows and uploaded them to Commons. We're ready to go on my end!

I uploaded the designs to share on Meta, to Commons and here the links:

• https://commons.wikimedia.org/wiki/File:Mobile_Entry_point_(Comment).png
• https://commons.wikimedia.org/wiki/File:Mobile_IRS_Step_1_(Dialog).png
• https://commons.wikimedia.org/wiki/File:Mobile_IRS_Step_2_(Form).png
• https://commons.wikimedia.org/wiki/File:Mobile_Step_2_(Error_1).png
• https://commons.wikimedia.org/wiki/File:Mobile_Step_2_(Error_2).png
• https://commons.wikimedia.org/wiki/File:Mobile_Step_2_(Scroll).png
• https://commons.wikimedia.org/wiki/File:Mobile_Step_2_(Typing).png
• https://commons.wikimedia.org/wiki/File:Mobile_Step_2_(Word_count).png
• https://commons.wikimedia.org/wiki/File:Mobile_Step_3_(Success_message).png
• https://commons.wikimedia.org/wiki/File:Desktop_Entry_point_(Topic_header).png
• https://commons.wikimedia.org/wiki/File:Desktop_Step_1_(Dialog).png
• https://commons.wikimedia.org/wiki/File:Desktop_Entry_point_(Comment).png
• https://commons.wikimedia.org/wiki/File:Mobile_Entry_point_(Topic_header).png

@STei-WMF I've published both diagrams on Commons. Here they are:

Hi all, here is the spec for the first version of the Incident Report System. As you'll see, we use an ellipsis / action menu for reporting from a topic header (which reports the entire topic) or a specific comment on a User Talk page.

I'm meeting with T&S policy and operations specialists this week to review copy from the policy and ops angle. I've already shared the Figma file with them.

@STei-WMF the local reporting workflows are ready to publish on our project page. Here they are and here is the "intro" paragraph that I think can accompany them but please make edits as you see fit!

I've added some copy for the Design section in the shared doc and here is a link to the Figma file with the mockups I'd like to share.

I've updated the UX copy in the Figma file and we can discuss some items there or here, whatever folks prefer. There is some nitty gritty product implications to iron out with the copy, after which we can make sure it works for long-text languages and is internationalized.

Discussed process with @Madalina and next steps will be:

• @dchen is going to take over this effort moving forward
• we plan to wrap up this first round of research by end of June and publish an insights report

• Feedback from 8 community members (admins & editors) from ko.wiki on the local reporting workflows

• @RamzyM-WMF translated distribution message for id.wiki and @STei-WMF to distribute on the village up
• Got feedback on local reporting flows from ko.wiki ^ see Vivien's message above
• Will incorporate some of the feedback from ko.wiki into the flows

• Workflow explorations in Miro: https://miro.com/app/board/uXjVMNhgng4=/
• Design explorations deck has been updated: https://docs.google.com/presentation/d/1Iq3zaYCd1ZtykiBe3IZhcUnukiDPznEtIuDTnbc1dq4/edit#slide=id.g23b8d698c3e_0_157

@STei-WMF no deadline currently! I'll let you know if that changes.