🗒 Agendas, minutes and other meeting material
active 2024-04-18 → 2026-07-01 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 805 days from 2024-04-18 to 2026-07-01. Pushes: 36 total, peak 2 in a day. Pull requests: 4 total, peak 2 in a day. Issues: 10 total, peak 2 in a day. Comments: 13 total, peak 1 in a day. Stars: 5 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| anssiko | 56 | 36 | 4 | 8 |
| inexorabletash | 3 | 0 | 0 | 3 |
| domenic | 2 | 0 | 0 | 2 |
| reillyeon | 1 | 0 | 0 | 0 |
| Harmonyblue | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#38anssiko2025-12-05 09:25
- Pull request#38anssiko2025-12-05 08:58
- Issue comment#35anssiko2025-10-16 13:10WebML WG/CG F2F Agenda - TPAC 2025 (Kobe, Japan)
- Issue comment#35anssiko2025-10-06 07:37WebML WG/CG F2F Agenda - TPAC 2025 (Kobe, Japan)
- Issue comment#32anssiko2025-10-03 15:33WebML WG/CG scheduling poll for TPAC 2025 (Kobe, Japan)
- Issue#32anssiko2025-10-03 15:33WebML WG/CG scheduling poll for TPAC 2025 (Kobe, Japan)
- Issue#31anssiko2025-09-30 14:26WebML CG Teleconference - March 12 2025 - Agenda Topics Proposal
- Issue#25anssiko2025-09-30 13:53WebML WG - TPAC 2024 agenda
- Pull request#33anssiko2025-09-30 13:53
- Issue#32anssiko2025-06-13 13:43WebML WG/CG scheduling poll for TPAC 2025 (Kobe, Japan)
- Issue#30anssiko2024-12-15 10:15Some offline discussed suggested we should do this censoring, but we should be sure that the values are granular enough that developers still see progress every 50 ms in the typical case. That is, if we just used the integers 1-100, it's possible that for large models it'd take longer than 50 ms to move from 1 to 2.
- Issue comment#30anssiko2024-12-15 10:14Some offline discussed suggested we should do this censoring, but we should be sure that the values are granular enough that developers still see progress every 50 ms in the typical case. That is, if we just used the integers 1-100, it's possible that for large models it'd take longer than 50 ms to move from 1 to 2.
- Issue#30Harmonyblue2024-12-15 00:42Some offline discussed suggested we should do this censoring, but we should be sure that the values are granular enough that developers still see progress every 50 ms in the typical case. That is, if we just used the integers 1-100, it's possible that for large models it'd take longer than 50 ms to move from 1 to 2.
- Issue comment#25anssiko2024-08-16 07:33WebML WG - TPAC 2024 agenda
- Issue#27anssiko2024-08-15 09:34WebML WG Teleconference – 22 August 2024 - Open issues and PRs
- Issue comment#25domenic2024-08-09 06:24WebML WG - TPAC 2024 agenda
- Issue comment#25inexorabletash2024-07-30 22:31WebML WG - TPAC 2024 agenda
- Issue comment#25inexorabletash2024-07-12 22:38WebML WG - TPAC 2024 agenda
- Issue comment#25domenic2024-07-08 04:20WebML WG - TPAC 2024 agenda
- Issue comment#23anssiko2024-06-28 06:40WebML WG Hybrid Meeting at TPAC 2024
- Issue#23anssiko2024-06-28 06:40WebML WG Hybrid Meeting at TPAC 2024
- Issue#25anssiko2024-06-28 06:36WebML WG - TPAC 2024 agenda
- Issue comment#24inexorabletash2024-06-26 20:34WebML WG Teleconference – 27 June 2024 - Open issues and PRs
- Issue comment#23anssiko2024-05-24 10:26WebML WG Hybrid Meeting at TPAC 2024
- Issue#23reillyeon2024-05-15 23:51WebML WG Hybrid Meeting at TPAC 2024
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 5 stars here means stars gained during the window, not the repo's star count.