Is there some wishlist for future KiCad library components?

So I am fine with creating my own KiCad Symbol and Footprint libraries. And I am fully aware of the limited time of KiCad´s librarian team and highly appreciate the hard work of the team.

I am also aware that a handful of people cannot provide all possible user wishes. Still I wonder If there is somewhere a kind of wishlist or maybe just some kind of “rough roadmap” of future KiCad library additions where maybe user can vote for some specific component “families”?

E.g. at the moment I am about integrating a new STM32 µC into a design and while I am capable of creating “basic” parts I am not sure how to create Symbols of a whole family of µCs in the most “generic” way.

To be more concrete I would wish for the STM32WL31x Series of µCs - has anyone tips about what to take care of in creating symbols with best reuse and how to best deal with differences in alternate pin functions? I think about creating STM32WL3x by deriving from STM32WLE series that already is part of the official KiCad Libs but and not sure about the best practises in doing so.

KiCad does have a team of volunteers who do library maintenance. Acceptance as official KiCad parts (symbols and footprints) is quite strict, and there is a significant backlog with merge requests on gitlab.

KiCad’s STM32 libraries are already quite extensive. They also have (all?) the “alternative pin” assignments populated, so you can rename an ADC input or timer PWM output directly in the schematic. STM32 libraries are script generated. KiCad has STM32WL**, but indeed the WL3 series is not (yet) among it.

So, for an “official” / efficient addition of the whole STM32WL3x range, you should look into the scripts (which you can find on gitlab) or make a request for this on gitlab. If you just want to get your own project going, then making a copy of a similar STM32 IC and modifying it in the symbol editor is a much easier option.

https://componentsearchengine.com/search?term=STM32WL31

unlinked as the forum was doing something weird to it. I suggest not bikeshedding too much over alternate pin definitions and just using what you need for your project at hand.