Page MenuHomePhabricator

Preference persistence, TDMP Phase 3: Gather, Summarize, and Create Tickets for Technical Decision Forum Feedback
Closed, ResolvedPublic5 Estimated Story Points

Description

Phase 1/2 << • Phase 3 • >> Phase 4

Background

As part of the Technical Decision Making Process, phase 3 is defined as "Get feedback from the Decision Forum". Specifically:

Once the problem statement is finalized, the Technical Decision Forum Representatives will review the problem statement and provides feedback to the decision team. Forum Representatives are expected to share their feedback within one week. The feedback answers these questions:

Is the problem statement correct?
Is it clear how solving this problem supports Wikimedia goals (movement strategy, medium term plan, annual plan, etc.)?
Are these the right stakeholders?
Is the needed subject matter expertise to make a decision reflected accurately? Are the right groups outlined in the problem statement?
The Forum project manager is responsible for requesting review from Forum members and sharing Forum feedback with the project owner.

Description

This ticket will cover gathering this feedback, summarizing it and creating relevant tickets in preparation for the prototype phase.

Acceptance Criteria

  • Work with the Technical Decision Forum Project Manager to distribute the survey to all relevant participants
  • Collect all survey responses and summarize themes in this ticket. Specifically:
    • Determine which responses are in and out of scope, and respond back with reasoning here
    • What solutions have been proposed that we should prototype?
    • What questions have been raised that need answering?
  • Write a decision record that summarizes these conversations -- examples here AIUI, writing a decision record will be part of T333882
  • For those proposals which are in scope, create Phabricator tickets for prototypes to create, and create spikes for open questions that need answering. Make these subtasks of https://phabricator.wikimedia.org/T333878

Details

Other Assignee
Mabualruz

Event Timeline

NBaca-WMF renamed this task from TDMP Phase3: Gather, Summarize, and Create Tickets for Technical Decision Forum Feedback to TDMP Phase 3: Gather, Summarize, and Create Tickets for Technical Decision Forum Feedback.Apr 3 2023, 8:22 PM
NBaca-WMF updated the task description. (Show Details)
ovasileva set the point value for this task to 5.Apr 20 2023, 5:23 PM
ovasileva renamed this task from TDMP Phase 3: Gather, Summarize, and Create Tickets for Technical Decision Forum Feedback to Preference persistence, TDMP Phase 3: Gather, Summarize, and Create Tickets for Technical Decision Forum Feedback.May 4 2023, 5:47 PM
nray changed the subtype of this task from "Task" to "Spike".May 11 2023, 8:38 PM
nray changed the subtype of this task from "Spike" to "Task".

@Mabualruz and I met today to discuss remaining work on this and decided that @Mabualruz will lead the remaining work on this ticket with me transitioning to more of a support role :

The TDF spreadsheet, Miro board, and notes can be used to complete the following:

  • Collect all survey responses and summarize themes in this ticket. Specifically:
    • Determine which responses are in and out of scope, and respond back with reasoning here
    • What solutions have been proposed that we should prototype?
    • What questions have been raised that need answering?

Collection of survey responses has already been done and responses can be seen on the TDF spreadsheet. If it's helpful, my work to cluster/respond to the responses can be seen on the Concerns tab of the spreadsheet . Everything else from the above blockquote still needs to be completed.

For those proposals which are in scope, create Phabricator tickets for prototypes to create, and create spikes for open questions that need answering. Make these subtasks of https://phabricator.wikimedia.org/T333878

In addition to the links mentioned above, the POC patch that @Jdlrobson and I have been working on may be useful (at least as a reference) for the above blockquote. It contains a number of ideas from the ideas/concerns I've heard from the TDMP meetings such as having an allow list (like the BetaFeatures extension) and restricting the number of features allowed. Both of these can be used to mitigate the performance impact of the render-blocking inline script.

I've reassigned this to Mo to reflect our above discussion ^^. Unfortunately, it doesn't appear that I have the ability to add myself as the "Other assignee":

Screenshot 2023-05-19 at 5.39.39 PM.png (1×1 px, 332 KB)

Signing off on this phase!

Jdlrobson updated the task description. (Show Details)