Page MenuHomePhabricator

Code Stewardship Review for
Open, Needs TriagePublic


The following bullet points are optional - please fill them out if feasible, but this is not a hard requirement:

  • Current entry in mw:Developers/Maintainers:
    • Listed Code Steward: it's not listed
    • Listed Maintainer:
    • Listed In-training:
  • Number, severity, and age of known and confirmed security issues:
    • none
  • Was it a cause of production outages or incidents? List them:
  • Does it have sufficient hardware resources for now and the near future (to take into account expected usage growth)?
    • yes
  • Is it a frequent cause of monitoring alerts that need action, and are they addressed timely and appropriately?
    • no
  • When it was first deployed to Wikimedia production:
    • ~2007
  • Usage statistics based on audience(s) served:
    • In the 1/128 sampled web request logs, (in August 20201) this service has 1.7k entries over 30 days, so theoretically ~217,600 reqs/month, or ~5reqs/min. For reference in 2013, we were getting 11 reqs/second (per T81982).
  • Code changes committed in last 1, 3, 6, and 12 months:
    • 0
  • Reliance on outdated platforms (e.g. operating systems):
    • not really.
  • Number of developers who committed code in the last 1, 3, 6, and 12 months:
    • 0
  • Number and age of open patches:
    • 0
  • Number and age of open bugs:
    • 1 (migration to k8s)
  • Number of known dependencies:
    • It depends on PHP/curl and the MediaWiki prefixsearch API
  • Is there a replacement/alternative for the feature? Is there a plan for a replacement?
    • supposedly this functionality is no longer used in modern Apple devices/operating systems.
  • Submitter's recommendation (what do you propose be done?):