What kind of help is needed for SHA-256 work in the next ~year?

brian has been working on the SHA-256 implementation and now on the interop, pretty much solo, for quite some time. I realize that it's a bit late in the party to ask, but as we're talking about switching the default for new repositories in Git 3.0, I think it is past time for the rest of the project to pitch in if we can.

What kind of help would be useful to you at this point, brian? How much of the work is planned and ready for you to delegate to someone else (and what's the timeline like, if you have one)? Do you need help with testing any parts of the existing code in scaled scenarios? My understanding is that you have a roadmap to guide your own work, but if it's not shareable, is that something you could use some program management help with? Anything like that?

I can't guarantee that Google will be able to jump on and help right away, but at least understanding what needs doing is a good start for me to be able to ask around - especially if we're looking ahead to 2026, that gives me more room to try and get help. I thought to ask on the list instead of mailing brian directly because I assume that's the case for the other corporate contributors to the project, too ;)

 - Emily