Hi @Krinkle and everyone on this task,
We are looking at a 3 phases approach to deprecate Flow. This is only the first phase "make flow boards read only".

I approve this.
Thanks for the ping as I have been in and out a lot.

Let's not add it for now as this is only local wikiprojects. We can then iterate and add it after the fact. tagging @ifried so that she is aware of this.

As David's manager, I approve this request. Please contact me if you have any questions!

@ifried we estimated this task. Up to you to review the content to make sure it is general enough for all purpose.

I think it is useful to have as it removes ambiguity. Just share where you’d have it on the card as you’re going to go on parental leave. It’s better to get your thoughts. We can then decide to include it at a specific stage of the MVP.

@gonyeahialam I think we should also note on the "card" the wiki the wikiproject is on. On your designs, there are two cards/boxes for wikiproject women in red. The user would need to know which wiki it is on to be able to choose the one that interest them.

Good to know. We are about to start on a spike to Investigate Flow automatic migration approaches with T371738. I also tagged this task as subtask for the Epic T332022: Undeploying Flow.
Let us know what progress you make.

@gonyeahialam The high fidelity designs look great. This is totally a good starting point for the engineers.

Hi there, Is there someone in serviceops SRE who can help us with this?
Thank you in advance!

Let's take those decisions on the scenarios, Claudio mentions. He can then deliver this first version. We can then add take the time to think through changes to address the usability feedback and iterate on the first version.

It is valuable to understand how many times a user appears in various invitation lists.

As far as the label of the checkbox, could we do something like:

• Show events that already started and are ongoing

Looks good to me too.

@sbassett Do we actually need a security review for this?

It seems to me that we have spent enough time discussing the value of JSON vs SQL to take an informed decision. I would leave it to @cmelo to decide and proceed with his task as he owns it and has probably spent the most time thinking about this.

So to summarize: We agreed that Global was fine.