Come up with a "roadmap" to the Typelevel ecosystem

(This is a prerequisite to many other tasks; it isn't clear what its own final artifact is beyond a shared internal document.)

We have many, many, many projects. If we're going to talk about them publicly in a coherent way, we need to organize our thoughts about how they all work together. This involves several aspects:

• Categorizing them, so that we can talk about them coherently.
• Getting clear what each is good for. What use cases is each one strongest for?
• Seriously talking about the Typelevel "platform". For different sorts of application, what libraries should you be considering?

The last point is probably most crucial. We need to understand, very clearly, how the pieces work together, so that we can talk about this intelligently and make recommendations to folks who want to build serious software with TL libraries as the base.

没有确定文件、测试或入口点。首先审查 Typelevel 项目，并按类别和最适用的用例对它们进行整理，然后确定共享内部文档应针对不同应用类型提出哪些建议。完成的标准是形成一份连贯的路线图，说明这些项目如何协同工作，以及应如何在它们之间进行选择。