It would be nice to come to agreement about some simple conventions for naming schema, filing schema in subdirectories, and structuring the analytics schema repository in general. These conventions would hopefully allow us to move more quickly, be autonomous, and most importantly, not be talking about names so much (which is really boring for everybody).
I think it would be good to see what we can learn from the primary repository, which has a lot of schema, but still think about how schema are used for analytics, which is a different use-case. We should also take into account the engineering pros and cons associated with certain approaches, as well as factors like usability, self-documentation, discoverability, and complexity over time. I would personally also like to see us make choices that minimize the number of decisions that need to be made in order to produce a schema. These add up, and can be small things, for example "what do I name this", "where should this go", "should this be capitalized", etc.