State AI regulations are failing to distinguish between developers and deployers, potentially holding open source contributors liable for downstream uses they don't control. Katie Steen-James, OSI's first full-time US policy manager, explains how developers can engage with policy makers through Federal Register public comment periods, why the developer vs. deployer distinction matters, and how OSI's Open Policy Alliance tracks opportunities for participation. The core message: policy affects open source regardless of whether developers engage, so knowing how to participate makes the difference between supportive and burdensome regulation.
Table of contents
Why state AI regulations impact open source, and where to submit public comments that actually matter.Key takeawaysMore from We Love Open SourceAbout the AuthorSort: