Come up with a "roadmap" to the Typelevel ecosystem
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
No files, tests, or entry points are identified. Start by reviewing the Typelevel projects and organizing them by category and strongest use cases, then define what the shared internal document should recommend for different application types. Done means there is a coherent roadmap explaining how the projects work together and how to choose among them.
Written by the indexing model from the issue text.
Description
(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.
- Dominant language
- HTML
- Stars
- 42
- Forks
- 115
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from typelevel/typelevel.github.com
-
Difficulty 3/5 Half a day Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
typelevel/typelevel.github.com#610 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
typelevel/typelevel.github.com#602 · 4 comments ·
-
typelevel/typelevel.github.com#590 · 3 comments · 2 reactions · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in typelevel/typelevel.github.com
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100