Page MenuHomePhabricator

<Product Initiative> Structured talk APIs
Closed, DeclinedPublic

Description

Request Status: New Request
Request Type: research and project support
Related OKRs: Healthy Communications (S2S)

Request Title: Structured talk APIs

  • Request Description: Currently we have two production APIs which parse Talk pages and return a "structured" representation of the content as threads and other meta or derived data:

This request is to understand the need and potential support to a single API and maintaining and expanding functionality, particularly to ensure wide language support.

  • Indicate Priority Level:Medium
  • Main Requestors: Josh Minor, Matt Cleinman
  • Ideal Delivery Date: Q4
  • Stakeholders: Android, iOS, Editing, any external consumers of Talk pages (Enterprise?)

Request Documentation

Document TypeRequired?Document/Link
Related PHAB TicketsYes<add link here>
Product One PagerYes<add link here>
Product Requirements Document (PRD)Yes<add link here>
Product RoadmapNo<add link here>
Product Planning/Business CaseNo<add link here>
Product BriefNo<add link here>
Other LinksNo<add links here>

Event Timeline

@JMinor can you add the links to the api repos please and any other contextual/reference documentation?

@JMinor can you add the links to the api repos and any other reference documentation for this?

hi y'all – a drive-by comment to share, what seems to be, related work the Editing Team is doing to make it easier for the apps to offer in-line replying.

More context in: T285971: Update Talk API to support in-line replying on Android


Note: there's also T290186, a parent task the Editing Team is using to gather the work required to empower other teams and platforms to leverage the infrastructure we've developed as part of the Talk Pages Project.

@ppelberg thanks for links. I'd love your help to put more materials for the process together. Initiating this ticket is one of my todos from the communication summit.

to empower other teams and platforms to leverage the infrastructure we've developed

My goal is to bring that discussion and potential future into this new process that @DAbad is building to ensure key infrastructure like this has a clearer path to being a long term product we support rather than a team project.

@DAbad I added links to the entry point documentation for the two systems. I'm working on gathering the other supporting materials, and will try to get some more of the pieces in places before the Steering Committee meeting.

DAbad renamed this task from <> Structured talk APIs to <Product Initiative> Structured talk APIs.Feb 22 2022, 1:27 PM
DAbad moved this task from Backlog to Investigate on the Foundational Technology Requests board.
DAbad added a project: API Platform.

Planning to do initial investigation in upcoming API Platform Team sprint.

Per Peter above: iOS and Android teams are currently investigating switching to the new API for talk pages (https://phabricator.wikimedia.org/T285971). If that's successful, this ticket becomes irrelevant and we may be able to remove the /api/rest_v1/page/talk/ API entirely.

Removing inactive task assignee. (Please do so as part of offboarding - thanks.)

Krinkle subscribed.

Closing remaining non-software tasks relating to team process or planning for the "API Platform" team that existed from July 2023 - Jan 2024 (https://www.mediawiki.org/wiki/API_Platform_Team).