typelevel / typelevel/tsc

Talk about whether to (partially) unify the namespace

Open
#51 4 comments 0 reactions 1 assignee View on GitHub

@jducoeur is already working on this.

Since Jul 18, 2022.

marketing
Dominant language
No language data
Stars
11
Forks
4
Avg merge
1h 49m
Merged PRs (30d)
2

Description

In a recent Discord conversation, the point came up that we look fragmented in part because our projects are under many different namespaces.

This is a placeholder ticket to hold the conversation: do we care, and if so, how much? Unifying projects under, eg, a common typelevel namespace would make it a little more obvious that these projects are "official" -- that's nice, but is it worth the disruption? Also, given that many of the projects live under their own "brand" (eg, Davenverse), we aren't likely to want to try to shoehorn everything into a common namespace; is it worth doing so for some of them?

My current gut instinct is to not do this -- I'd prefer to just publicly own that TL is a community and ecosystem of cooperative systems that work together, and not try to claim that there is some sort of master plan or grand ruling body here. But we should talk about it, and consciously decide one way or another.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.