Last updated
This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.
Try to triage issues within .
| Issue | Title | Within SLO | On maintainers' plates for | Time left | Time past SLO |
|---|---|---|---|---|---|
| #27 | error codes should ideally link to definitions | ❌ | |||
| #32 | Investigate report-uri management workflows | ❌ | |||
| #84 | Make `report_to` field optional | ❌ | |||
| #107 | Disallow "hop-by-hop" headers in `request_headers` and `response_headers` | ❌ | |||
| #119 | Define HTTP/3 Error Type | ❌ | |||
| #120 | server_ip is likely not defined correctly. | ❌ | |||
| #156 | JSON validation schema | ❌ | |||
| #157 | Add note about transparent MitM proxies | ❌ | |||
| #166 | Rebase NEL on top of Fetch | ❌ | |||
| #171 | Replace manual list of dependencies by automatically generated index | ❌ |