{"id":19474825,"url":"https://github.com/speced/spec-maintenance","last_synced_at":"2025-04-25T12:32:01.932Z","repository":{"id":191938340,"uuid":"685677279","full_name":"speced/spec-maintenance","owner":"speced","description":"Specs and tools to track browser spec maintenance","archived":false,"fork":false,"pushed_at":"2025-03-03T06:40:06.000Z","size":627,"stargazers_count":3,"open_issues_count":12,"forks_count":3,"subscribers_count":3,"default_branch":"main","last_synced_at":"2025-04-18T08:31:57.482Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://speced.github.io/spec-maintenance/","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/speced.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-08-31T18:57:06.000Z","updated_at":"2025-02-17T04:39:48.000Z","dependencies_parsed_at":"2023-10-17T05:27:42.670Z","dependency_job_id":"c92eb4a2-800b-4c4e-abc3-5c5d7b9feae8","html_url":"https://github.com/speced/spec-maintenance","commit_stats":null,"previous_names":["jyasskin/spec-maintenance","speced/spec-maintenance"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/speced%2Fspec-maintenance","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/speced%2Fspec-maintenance/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/speced%2Fspec-maintenance/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/speced%2Fspec-maintenance/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/speced","download_url":"https://codeload.github.com/speced/spec-maintenance/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":250817841,"owners_count":21492237,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-10T19:27:07.770Z","updated_at":"2025-04-25T12:32:01.412Z","avatar_url":"https://github.com/speced.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Web Specification Maintenance\n\n[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/speced/spec-maintenance?quickstart=1)\n\nThis repository holds a [tool](https://speced.github.io/spec-maintenance/) for tracking the maintenance of web specifications. To get started quickly:\n\n1. Click the Codespaces button above.\n1. Wait for the codespace to finish initializing.\n1. Run `pnpm dev` in the codespace's terminal.\n1. When VSCode reports that \"Your application running on port 4321 is available\", click the \"Open in\n   Browser\" button to see the server.\n\n## Research that motivated the design\n\nThe current tool behavior is documented in an [About\npage](https://speced.github.io/spec-maintenance/about).\n\n### Triage\n\nAll new issues (and PRs) need to get a priority assigned within a reasonable amount of time. To\ndetermine that amount of time, I looked at the distribution of the times it took issues to get their\nfirst comment or review from someone other than the issue's author.\n\n| | Issues that are\u003cbr\u003estill open | Issues that have\u003cbr\u003ebeen closed | Overall\n---: | --- | --- | ---\n10th percentile | 21 minutes | 7 minutes | 8 minutes\n25th percentile | 2 hours    | 43 minutes | 50 minutes\nmedian          | 16 hours   | 8 hours    | 9 hours\nmean            | 2.1 months | 3.3 weeks  | 1 month\n75th percentile | 1.3 weeks  | 3 days    | 3 days\n90th percentile | 4.3 months | 3.3 weeks | 1 month\n\nI propose we set an SLO of 1 week to triage issues. If all issues took as long to triage as they do\nto comment on, this would leave 26% of the 16731 open issues currently out of SLO. 20% of the 94591\nissues we've ever had have violated this SLO.\n\n### Priorities\n\nI propose we define 3 priority levels, with labels `Priority: Urgent`, `Priority: Soon`, and\n`Priority: Eventually`. `Priority: Eventually` issues won't have an SLO. For the others, we can look\nat the latency distribution for closing issues. Still-open issues tend to be much older than closed\nissues, and I assume they'd mostly be labeled with `Priority: Eventually`.\n\n| | Time to close\n---: | ---\n10th percentile | 1 hour\n25th percentile | 17 hours\nmedian          | 1.1 weeks\nmean            | 3.7 months\n75th percentile | 2.3 months\n90th percentile | 11.1 months\n\nWith half of all closed issues being closed in about a week, we can probably set a `Priority:\nUrgent` SLO of 1 week more than the triage SLO, so 2 weeks.\n\nIf we set a `Priority: Soon` SLO of 3 months, we'll catch over half of the remaining issues, so\nthat's what I suggest.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspeced%2Fspec-maintenance","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fspeced%2Fspec-maintenance","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspeced%2Fspec-maintenance/lists"}