Page MenuHomePhabricator

Create API Policy Project Plan
Closed, InvalidPublic

Description

INVALID TASK, HUMAN ERROR

Background

The legal team is updating the general terms of service to include APIs. They need to point to a stable URL that describes an API Policy or at a minimum the emergence of an API Policy. Given that there is no pre-existing API policy or API governance in place, a project plan needs to be created to address how we will advance discovery of these topics.

Acceptance Criteria

  • Business/organization justification & stakeholder needs
  • List of requirements & project objectives
  • Project definition
    • Scope:
      • What is in and out of scope
      • Deliverable items
    • Time:
      • Timeline
      • Work processes
      • Known milestones
    • Budget: What resources are required for this work?
    • People & Roles: project stakeholders and DACI
    • Risks & Assumptions:
      • Risk assessment
      • Technical feasibility assessment
      • List of assumptions
    • Community consultation & communication plan
  • Reviewed by key stakeholders
  • Published on a stable on wiki URL where the project plan is made public
    • preferably on api.wikimedia.org

Event Timeline

Given that there is no pre-existing API policy or API governance in place

This doesn't seem accurate to me, we do have API policies and API governance, including https://www.mediawiki.org/wiki/API:Etiquette, https://meta.wikimedia.org/wiki/Special:MyLanguage/User-Agent_policy, https://www.mediawiki.org/wiki/API_versioning and https://www.mediawiki.org/wiki/API/Architecture_work/Planning#Deprecation_process and probably more scattered across the wikis. Certainly collecting/reconciling all of these would be nice.

This doesn't seem accurate to me, we do have API policies and API governance

Shaun from Wikimedia Legal here. You are correct that the original post is not accurately worded. There are various policies and governance documents, some of which you linked to in your comment.

Also, to clarify the terms of service already includes the API. The currently proposed TOU changes that are described have simply make it more transparent that the APIs are covered by the terms and explicit as to which kinds of policies govern the APIs.

My personal human error and misunderstanding. Apologies to all. Marking this task invalid.