The way I'm thinking about the recipes these days (and the responsibilities of the infra sub-teams), I don't think there is a "Chromium side" of the recipes per se that would be owned solely by chromium devs. I think the right place to draw the line is in the src-side interfaces (the *.json files, the Test step APIs, the MB configs, etc.). 

I mostly want infra folks (either foundation or crossover) to own all the recipe-side code.

I think this is consistent with what we've discussed recently. Agree?

I'm going to reassign this to me for now ...

why is this a postmortem-related thing?

Just flying by, but in light of the current team organization, I think the owners in  comment #0 would be "foundation" and "crossover", not "infra" and "chromium".

I think actually that the answer is "all crossover", but maybe there's some stuff that we can pull out of the chromium recipes and modules that we'd want to share for non-chromium teams, like a new steps api and logic to handle retrying w/o patches. I'm not sure ...

@dnj - let's talk about this when you have some time. I'd like to make sure my current thinking about this stuff lines up with yours.

We talked about this, but I didn't update the bug. Our conclusion was that this CL as it stands is a bit vague, and we don't really want to think of things as "crossover" or not.

However, we should clean up these recipes and see if we can make them as generic as possible, with clean declarative APIs for repo-side configuration.

I'm closing this bug; we'll work on that cleanup elsewhere in other tasks.