Hello @nbara :)
as mentioned in #103 (comment) I have now submitted quite a few PRs for ASR, based on a big Claude orchestrator that ran for a while, comparing the code here to published papers and other publicly available ASR code (never copying verbatim from licensed code).
I have instructed the coding agent to keep the diff minimal, and to open a dedicated PR for each issue.
I think a few PRs can be merged with clear benefits and with low-effort reviews:
☝️ should be merged first as it is needed for other tests to pass
☝️ easy to review /clear benefit
and then the remaining PRs may need some more review / discussion. I think that can come after merging the clear ones, to clean up a little first.
☝️ need some closer look / review
What do you think?
Hello @nbara :)
as mentioned in #103 (comment) I have now submitted quite a few PRs for ASR, based on a big Claude orchestrator that ran for a while, comparing the code here to published papers and other publicly available ASR code (never copying verbatim from licensed code).
I have instructed the coding agent to keep the diff minimal, and to open a dedicated PR for each issue.
I think a few PRs can be merged with clear benefits and with low-effort reviews:
☝️ should be merged first as it is needed for other tests to pass
☝️ easy to review /clear benefit
and then the remaining PRs may need some more review / discussion. I think that can come after merging the clear ones, to clean up a little first.
☝️ need some closer look / review
What do you think?