Skip to content

Audit of TL Projects both organizational and affliates ensure adherance #191

Open

Description

@dhinojosa

We have projects on the https://typelevel.org/projects page that need follow-up to ensure they use open-source licenses, that use our code of conduct at a minimum

Some projects that are on our project page but don't adhere are the following, and please feel free to add to the list that require closer inspection:

On Edit: Added status to Droste, Scoverage, Scala-Steward, HTTP4s, Scodec, Argonaut-Shapeless, Banana-RDF, Calico, and finished the rest of our project page in regards to CoC

Activity

  1. jducoeur commented on Jun 29, 2026

    @jducoeur
    Member

    Refined may be worth a serious discussion at this point. While it is an official affiliate project, it's also kind of behind the times -- in practice, it feels like everyone is drifting towards Iron now. Not sure what we should do about that.

    Droste isn't ours, right? It's not on the project list, AFAIK it's not an affiliate project, and I think we have no say in it. Is there reason to believe we should even be talking about it?

  2. dhinojosa commented on Jun 29, 2026

    @dhinojosa
    MemberAuthor

    Droste isn't ours, right? It's not on the project list, AFAIK it's not an affiliate project, and I think we have no say in it. Is there reason to believe we should even be talking about it?

    No, it's only in our Discord as a project. But if there was an attempt, it would be nice to know about it, and maybe have a recursion scheme library in our bazaar? Maybe? But I do get everything you are saying, @jducoeur

  3. dhinojosa commented on Jun 30, 2026

    @dhinojosa
    MemberAuthor

    One possible and passive strategy is to submit a PR to all these projects to update the CoC to Typelevel.

  4. dhinojosa commented on Jun 30, 2026

    @dhinojosa
    MemberAuthor

    Worth noting, all the projects on the page are either Apache 2.0 or MIT. One was Mozilla, so I think licensing is good for all projects.

  5. dhinojosa commented on Oct 18, 2026

    @dhinojosa
    MemberAuthor

    3. Refined may be worth a serious discussion at this point. While it is an official affiliate project, it's also kind of behind the times -- in practice, it feels like everyone is drifting towards Iron now. Not sure what we should do about that.

    I was looking at Refined yesterday (fell into a rabbit hole more like it) and remembered this comment. I was just wondering what makes Refined seem behind the times, in your opinion, @jducoeur? Was it just leaner because it uses Scala 3 and things like inline?

    We are also continuing to support Scala 2.x in nearly everything; I suppose when 3.x becomes the prevalent option, then we can redo or upgrade Refined. Maybe even Refined can start to work on a Scala 3-exclusive option now using everything Refined has, since I think Refined has a syntax, or at least that's my initial reaction

  6. jducoeur commented on Oct 18, 2026

    @jducoeur
    Member

    My opinion wasn't based on much more than a gut-check: when I researched this at the beginning of the year (as part of standing up our new 3.x stack at work), my sense was that the Scala community as a whole was drifting towards Iron. (And I personally find Iron's syntax a little more appealing.)

    Taking a quick glance at the internals, it looks like Refined is properly opaque-based in the 3.x tree, which is the important part: that means that it's not technically falling behind. And once we (someday) leave 2.x behind, the codebase could be simplified significantly.

    So I think it's fine to keep it going so long as there is still active usage and people interested in maintaining it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions