Thank you for the specific feedback and general. One thing I noticed is you do not include the framework in the folder name. I may have fallen out of favor, b

Thank you for the specific feedback and general. One thing I noticed is you do not include the framework in the folder name. I may have fallen out of favor, but a while back it seemed like repos would be named in part by their tech. I.e. product_name_django. A quick look at trending projects in python and swift on github seems to confirm that. [0] It seems like you give top level naming to services and to entire applications. Is there anything other than memory or doc with indicating meta to quickly discern what is what? db48x commented on a top-level doc like this, do you use something like that? Perhaps a readme provides this? Can you tell me anything about issues / tickets? For example, I commonly use github issues on a per-repo basis, on some projects that's a problem because they go together. However on a monorepo like you've described, perhaps a lot of tagging would be needed to classify what goes to what. I'm interested in how you issues up to commits, and have effective milestones filled with these issues. [0] https://github.com/trending/swift https://github.com/trending/swift, https://github.com/trending/python https://github.com/trending/python For example, you might see repos that