Hello Marco,
thanks for migrating this to the google document. I guess for some high level topics the mailing list still is better.
1) I am not really convinced that the current layout is that flawed to justify a full re-structuring, restructuring effectively means loosing the history on GitHub.
2) I couldn't find any explanation of my previous point #2 in the introduction, maybe you I overlooked it and you can point me towards it. Because from what I understood the grouping will be based on the deployment bundles (microservices) and that may change in the future.
3) Looking at "Service Directory Proposed Layout" and "Example Service Directory Proposed Layout" it looks to me as if the proposed layout doesn't really work. At least in the example there are more exceptions than standard cases.
I would suggest to do a full breakdown (mapping table), from old to new, so that we can understand what the proposal actually is. Because right now I don't see how modules (like broker-core, dev-tools, sso, transport, …) would be match the proposed ruleset. I guess actually doing this in a spreadsheet might clear up a few questions.