Re: TONYC Grant Report February 2026
[email protected] ("Core Grant Manager") Tue, 17 Mar 2026 06:57:41 -0400
| Newsgroups | perl.perl5.porters |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Mar 5, 2026, at 6:28 PM, Tony Cook wrote: > [Hours] [Activity] > 2026/02/02 Monday > 0.08 #24122 review updates and comment > 0.17 #24063 review updates and apply to blead > 0.28 #24062 approve with comment and bonus comment > 0.92 #24071 review updates and approve > 0.40 #24080 review updates, research and comment > 0.18 #24122 review updates and approve > 0.27 #24157 look into it and original ticket, comment on > original ticket > 0.58 #24134 review and comments > 0.27 #24144 review and approve with comment > 0.18 #24155 review and comment > 0.48 #16865 debugging > 0.90 #16865 debugging, start a bisect with a better test case > ===== > 4.71 > > 2026/02/03 Tuesday > 0.17 review steve’s suggested maint-votes and vote > 0.17 #24155 review updates and approve > 1.30 #24073 recheck, comments and apply to blead > 0.87 #24082 more review, follow-ups > 0.83 #24105 work on threads support > 0.65 #24105 more work on threads, hash randomization support > ===== > 3.99 > > 2026/02/04 Wednesday > 0.13 github notifications > 1.92 #24163 review, comments > 0.48 #24105 rebase some more, fix tests, do a commit and push > for CI (needs more work) > 1.70 #24105 more cleanup and push for CI > ===== > 4.23 > > 2026/02/05 Thursday > 0.20 github notifications > 0.38 #24105 review CI results and fix some issues > 1.75 #24082 research and comments > 0.63 #24105 more CI results, update the various generated > config files and push for CI > 0.17 #23561 review updates and comment > 0.40 #24163 research and follow-up > 0.58 #24098 review updates and comments > ===== > 4.11 > > 2026/02/09 Monday > 0.15 #24082 comment > 0.20 #22040 comment > 0.30 #24005 research, comment > 0.33 #4106 rebase again and apply to blead > 0.35 #24133 comment > 0.35 #24168 review CI results and comment > 0.25 #24098 comment > 0.18 #24129 review updates and comment > 0.92 #24160 review, comment, approve > 0.17 #24136 review and briefly comment > 0.78 #24179 review, comments > 0.48 #16865 comment, try an approach > ===== > 4.46 > > 2026/02/10 Tuesday > 0.62 #24163 comment > 0.23 #24082 research > 0.20 #24082 more research > ===== > 1.05 > > 2026/02/11 Wednesday > 0.48 #24163 review updates and approve > 0.73 #24129 review updates > 0.45 #24098 research and follow-up comment > 0.32 #24134 review updates and approve > 0.17 #24080 review updates and approve > 1.18 #22132 setup, testing and comments on ticket and upstream > llvm ticket > 0.32 #23561 review update and approve > 0.42 #24179 review some more and make a suggestion > 1.03 #24187 review and comments > ===== > 5.10 > > 2026/02/12 Thursday > 0.43 #24136 research and comment > 0.17 #24190 review and approve > 0.90 #24182 review discussion and the change and approve > 0.08 #24178 review and briefly comment > 0.33 #24177 review, research and comment > 0.08 #24187 brief follow-up > 0.43 #24176 research, review and approve > 0.27 #24191 research, testing > 0.20 #24192 review and approve > 0.38 #24056 debugging > 0.58 #24056 debugging, something in find_lexical_cv()? > ===== > 3.85 > > 2026/02/16 Monday > 0.52 github notifications > 0.08 #24178 review updates and approve > 2.20 #24098 review and comments > 0.88 #24056 more debugging, find at least one bug > 0.92 #24056 work up tests, testing, commit message and push for > CI, perldelta and re-push > ===== > 4.60 > > 2026/02/17 Tuesday > 0.18 #24056 check CI results, rebase in case and re-push, open > PR 24205 > 2.88 #24187 review, comments > 0.47 #24187 more comments > 0.23 reply email from Jim Keenan re git handling for testing PR > tests without the fixes > ===== > 3.76 > > 2026/02/18 Wednesday > 3.02 #24187 review comments, work on fix for assertion, > testing, push for CI > 0.25 #24187 check CI, make perldelta and make PR 24211 > 0.35 #24098 review updates and approve > ===== > 3.62 > > 2026/02/19 Thursday > 0.30 #24200 research and comment > 0.47 #24215 review, wonder why cmp_version didn’t complain, > find out and approve > 0.08 #24208 review and comment > 0.73 #24213 review, everything that needs saying had been said > 0.22 #24206 review and comments > 0.53 #24203 review, comment and approve > 0.33 #24210 review, research and approve with comment > 0.37 #24200 review, research and approve > ===== > 3.03 > > 2026/02/23 Monday > 0.35 #24212 testing add #24213 to 5.42 votes > 2.42 #24159 review and benchmarking, comment > 0.73 #24187 try to break it > ===== > 3.50 > > 2026/02/24 Tuesday > 0.35 github notifications > 1.13 #24187 update PR 24211 commit message, rechecks > 0.43 #24001 re-work tests on PR 24060 > 0.30 #24001 more re-work > ===== > 2.21 > > 2026/02/25 Wednesday > 1.02 #24180 research, comments > 0.22 #24206 review update and comment > 0.28 #24208 review updates and comment > 0.57 #24060 more tests > 0.88 #24060 more tests, testing, debugging > ===== > 2.97 > > 2026/02/26 Thursday > 0.47 #24211 minor fixes per comments > 0.23 #24206 review updates and approve > 0.22 #24180 review updates and approve > 0.98 #24236 review and comments > 1.30 #24228 review, testing and comments > 0.08 #24236 research and comment > 0.78 #24159 review updates, testing, comments > ===== > 4.06 > > Which I calculate is 59.25 hours. > > Approximately 50 tickets were reviewed or worked on, and 3 patches > were applied. Thanks Tony, +1 from me! https://news.perlfoundation.org/post/maintaining_perl_tonyc_february_2026 -- Matthew Horsfall (alh)