Create a repository mapping with descriptions for the project

[TimMonko]

Description

It's important we have some kind of map and pulse on our repos. This both helps give us an overview of what is actually happening, and for contributors to know how to help -- especially as we plan to spin out more and more repos from napari (like new plugins and such). This is one of the ways that I struggled so much when contributing early to napari, especially with both the documentation system and the plugin system (and I still feel like I'm learning all the npe2 stuff!)

I did my very best to organize this as much as possible, but of course its quite opinionated and some may have a different idea about active/maintenance/early/backlog. I certainly think giving us an eye on backlog will help us triage even our own stuff.

I also note the following repos in the historical/archive section but they are not yet archived. I would recommend we archive these repos:
napari-scipy2025-workshop
surveys (this one could just be outright deleted)
napari-workshop-template
napari-plugin-engine
napari-language-packs

[psobolewskiPhD]

Sad to see napari-workshop-template go, it was such a huge help in setting up my own workshops.
😞

[TimMonko]

Sad to see napari-workshop-template go, it was such a huge help in setting up my own workshops. 😞

Totally fair! I'm pretty unsure about it, given that it is useful, but its been not maintained long enough that if anything its probably harmful to keep around.

Do you think we could reinvigorate with the new napari/workshops strategy? I think you are not the only person that made "community" workshops from the template. Let's definitely move this discussion somewhere else. .. Zulip? napari/napari-workshop-template? I'm not sure I'll let you decide since you have both the most context and experience with it