Retire the "Typelevel Ecosystem" page

[armanbilge]

https://typelevel.org/cats/typelevelEcosystem.html

cats/docs/typelevelEcosystem.md

Line 1 in 0f18d6f

# Typelevel Ecosystem #

This page is not specific to Cats and it duplicates the listing at https://typelevel.org/projects/. So I think we should move these projects there, and the Cats page can simply redirect to it.

The tricky bit with this migration is that currently the way to get listed on that page is to submit a project as an affiliate. So what to do about all the non-affiliate projects on this list?

cc @typelevel/steering

[jducoeur]

Hmm -- I agree in principle, although I'm a bit concerned about losing interested projects in the shuffle. I would recommend a deprecation period where this page points people over to the main TL page and encourages them to apply there, before deleting this page.

The issue of intentionally non-affiliate projects is an interesting one, although I think there's an important question of how many projects intentionally don't want to be affiliated, vs the ones that it just never occurred to. I have no clue what those numbers might be.

[armanbilge]

I would recommend a deprecation period where this page points people over to the main TL page and encourages them to apply there, before deleting this page.

To be clear, I don't think we should ever delete this page. But it should be replaced by a page that points to the new page, and otherwise does not list any projects.

The issue of intentionally non-affiliate projects is an interesting one, although I think there's an important question of how many projects intentionally don't want to be affiliated, vs the ones that it just never occurred to.

The Typelevel projects page currently puts either an "organization" or "affiliate" badge on each project. So could we just list these un-affiliated projects without a badge?

[jducoeur]

The question is, what does un-affiliated mean?

I suspect that we aren't willing to uncritically just list everybody that applies -- listing a project is going to perceived as an endorsement to at least some degree, badge or not. There are certainly software projects with deeply toxic communities; I think it's unlikely that we want to list those in any form, even if they use our tech. (Hopefully not many such, but I don't think we can ignore the issue.)

We have clear standards for Organization and Affiliated projects. I could believe there might be a level below "Affiliated", with looser standards, but we have to figure out how that's defined -- basically, what are the minimum requirements for a project to show up on the TL site at all? Does it need a CoC? Does it need a minimum level of activity? Do we think it's appropriate to list non-affiliated projects at all on the main site? I can identify some questions, but I'm not at all sure of the answers.

(Would be great to get viewpoints from other members of @typelevel/steering here, especially folks who have been through this sort of discussion before. This is all off the top of my head, when I'm rather exhausted.)

[armanbilge]

I suspect that we aren't willing to uncritically just list everybody that applies -- listing a project is going to perceived as an endorsement to at least some degree, badge or not.

💯 very much agree with that, and that deserves a bigger discussion, probably on the governance repo?

Focusing back on Cats:

Basically, we have a list of projects here :) if they are not sufficiently "vetted" to be listed on the typelevel.org page, should we even really be listing them here? In that case, maybe we should clear out the list, and either (1) open issues on their repos asking them to apply to be listed or (2) re-vet them ourselves, to put on the typelevel.org page. I can help with (1).

Otherwise, I think we are stuck with this list, and the best we can do is put a heading on it "this is legacy, we have not (re-)vetted these projects, but we are too polite to remove them :) all new projects should apply to be listed on this new page instead."