IssueTracker

Slipped Oct iteration. We... don't really have a plan here yet, but this is P1 to stop the bleeding.

libraries where all resources are currently considered public but have never been tracked

Safest route for external developers is to make all existing resources officially public. That's going to be more work since we can't just copy the public.txt file. It also means that internal developers are locked into their existing resources, which is... safer, but not good for evolution of libraries.

Easiest route for internal developers (and our team) is to make all existing resources officially private. That will potentially break g3 drops and third-party libraries; however, it's an easy workaround given that we don't do resource namespacing yet. Developers can just define the resource that they (or their dependency) needs. Anyone using a dependency's R class directly is already hosed, anyway, so we'll ignore that.