develooper Front page | perl.perl5.porters | Postings from March 2023

Re: TONYC Grant Report January 2023

Thread Previous
From:
Ricardo Signes
Date:
March 3, 2023 16:46
Subject:
Re: TONYC Grant Report January 2023
Message ID:
c0da4df4-b945-4ef7-a9df-f6ee1fc43c47@betaapp.fastmail.com
👍🏽 Thanks, Tony.

On Wed, Mar 1, 2023, at 06:48, Tony Cook wrote:
> [Hours]         [Activity]
> 2023/01/03      Tuesday
> 0.08           github notifications
> 1.40           #20599 review, comments
> 1.02           #20637 review and comments
> 0.07           #20621 review and approve
> 0.40           #20647 review discussion, start to look over code
> =====
> 2.97
> 
> 2023/01/04      Wednesday
> 0.30           #20599 follow-up
> 0.07           #20637 look over discussion
> 0.47           rfc #32 review and review discussion
> 0.15           #20667 review and approve
> 1.35           #20647 more look over code, find a crash, comments
> 1.25           #20647 more look over code, comment on some other issues
> 0.73           #20668 review and approve
> =====
> 4.32
> 
> 2023/01/05      Thursday
> 0.42           #20676 review, comment
> 1.77           #20506 rebase, retest
> 0.33           #20506 minor change, retest
> 0.08           #20671 review and comment
> 0.42           #20593 rebase, testing, push for CI
> 0.70           #20500 rebase. re-test
> =====
> 3.72
> 
> 2023/01/09      Monday
> 0.32           #20647 review discussion, briefly comment
> 0.57           github notifications, some comments
> 0.60           #20647 look at embed messages for macros
> 1.15           #20677 review, comments
> 0.95           #20678 review, testing
> =====
> 3.59
> 
> 2023/01/10      Tuesday
> 0.60           #20678 start gcc build
> 0.68           #20500 apply to blead, perldelta
> 0.37           #20539 apply to blead, perldelta
> 0.67           rfc 19
> 1.23           #20678 reproduce, debugging, comment
> =====
> 3.55
> 
> 2023/01/12      Thursday
> 1.42           #20678 work up a possible fix, testing, make PR 20687
> 0.37           #17154 look for similar problems at khw’s suggestion, #p5p
>                 discussion
> 0.68           rfc 23 read discussion, comment
> 0.75           rfc 15 read discussion, comment
> 0.82           #20355 work on adapting Errno for CPAN, make IO depend on
>                 it, push for CI (especially dist-modules)
> =====
> 4.04
> 
> 2023/01/13      Friday
> 0.52           #20647 feature-class get_av, testing and comment
> =====
> 0.52
> 
> 2023/01/16      Monday
> 1.32           #20355 address test-dist-modules failures, push for more
>                 CI
> 0.62           github notifications
> 0.65           #20711 review, comment
> 0.28           #20637 further review, approve
> =====
> 2.87
> 
> 2023/01/17      Tuesday
> 0.27           #20689 review and approve
> 0.30           #20712 look for a remembered similar issue
> 1.08           #20712 try to reproduce (clang issues) - turned out to be
>                 https://github.com/llvm/llvm-project/issues/59903
> =====
> 1.65
> 
> 2023/01/18      Wednesday
> 0.05           github notifications
> 0.43           #20487 review and review discussion, approve
> 0.80           #20712 reproduce and make PR #20719
> 0.88           #20709 try to reproduce on various freebsd, look over the
>                 probe code, comment with steps to get more info
> 0.53           #20692 research and comment
> 1.50           feature bundle re-work
> =====
> 4.19
> 
> 2023/01/19      Thursday
> 0.98           review list discussion, comment on dzil thread
> 0.72           #20692 comment
> 0.03           #20719 apply to blead
> 0.90           #20207 look into file-replace-inplace, debugging
> 0.60           #20207 more debugging, find apparent issue and comment
> 0.52           #20711 review and approve
> 0.33           #20709 review response and suggest some further things to
>                 try
> =====
> 4.08
> 
> 2023/01/20      Friday
> 0.43           #20692 further comment
> =====
> 0.43
> 
> 2023/01/23      Monday
> 0.48           #20709 research and comment
> 0.50           github notifications
> 0.17           #20732 review and approve
> 0.32           #20709 follow-up
> 0.90           #20733 diagnose, start work on a fix
> 1.15           #20733 finish, testing, push for CI
> 0.83           feature bundle re-work: look into deparse failures, looks
>                 like the hints magic isn’t working as I expected
> =====
> 4.35
> 
> 2023/01/24      Tuesday
> 0.22           #20709 comment
> 0.20           #20733 review CI results and make PR 20736
> 1.57           feature bundle re-work, debug missing expected magic
> 1.45           feature bundle re-work, more debug missing expected magic
> =====
> 3.44
> 
> 2023/01/25      Wednesday
> 0.32           #20736 apply to blead and perldelta
> 1.13           #20739 review discussion, some research
> 1.17           feature bundle re-work, read code to try to find missing
>                 magic
> 1.85           feature bundle re-work
> =====
> 4.47
> 
> 2023/01/27      Friday
> 0.65           #20741 review and comments
> 0.25           #20741 follow-up review, comments and approve
> =====
> 0.90
> 
> 2023/01/30      Monday
> 0.22           github notifications
> 0.08           #20751 review and approve
> 1.10           #20747 review and comments
> 0.53           feature bundle re-work: know why magic isn’t as expected,
>                 re-work
> 0.32           #20747 follow-up
> 0.47           feature bundle re-work
> 0.70           #20747 look into threaded build crash, discussion with dmq
> =====
> 3.42
> 
> 2023/01/31      Tuesday
> 0.05           github notifications
> 0.18           review list discussion
> 0.35           #20753 review and approve
> 0.12           #20752 review and apply to blead (has another approval)
> 0.58           #20742 review, debugging
> 1.37           #20742 more debugging, try some fixes
> =====
> 2.65
> 
> Which I calculate is 55.16 hours.
> 
> Approximately 35 tickets were reviewed or worked on, and 5 patches
> were applied.
> 
Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About