After seeing quite a bit of confusion with Google's API Style Guide (https://cloud.google.com/apis/design/) we decided to copy Python's PEP system / IETF's RFC system and create a new way to track API design guidance and rules, called AIPs (not a typo, that's API Improvement Proposals). This system is sort of like the National Electric Code for building APIs, with specific, citable, open-source licensed guidance for API design topics, standard design patterns, and other API design building blocks. This talk would introduce the system, explain a bit of history, show how it works, and how it can be adopted by folks that don't work at Google (with a built-in mechanism to override guidance that might be great for Google but isn't great for a start-up or a bank). This is already in use today and lives at https://aip.dev.
