Get CIQ onto the embargoed security lists, Linux first - treat the absence as our failing; give upstream hours from the Stratum engineers to wherever Tim directs, and let Tim move without waiting on Peter

Situation

In the 10/21 Tim Pepper 1:1 Peter set three things. CIQ getting onto embargoed security lists is a goal - Linux matters more to him than Kubernetes - and he views not being admitted as a failing on CIQ side to be fixed by building community trust; Tim brokers the conversations. Weekly hours from both Stratum/Kubernetes engineers (one hired, one req open) go to upstream work wherever Tim directs. And Tim moves things forward without waiting on Peter: invite him to meetings rather than reschedule around him, and Peter will tell his team and Marketing to jump when Tim asks. The upstream/downstream development training Tim plans will include the Linux org.

Reasoning

Embargo-list membership is reputational and earned by visibly operating as a normal, professional upstream player; CIQ heritage makes that trust gap real, so the fix is behavior over time rather than a request. Peter travel would otherwise make him the bottleneck on the advisor he hired to close his own knowledge gaps.

Additional Context

Builds on 10/1 (six-month push to be a better open-source steward, Tim advises) and 9/23 (upstream contribution is the entry ticket). Peter expects to have to align Greg on sending engineers to community conferences such as FOSDEM. Tim comments on the Stratum launch messaging go directly to Lindsay with Peter on CC.

Observed Evidence

I am happy dedicating a number of hours a week of both of their time to wherever you think it would be best spent. When you are ready for that talk, I do want the Linux side of the house there.

Confidence Breakdown

Reasoning Depth Analysis