Removing the netlist scripts from that list would be a good start, but hopefully that goes without saying
Doing a quick sample of my projects going back to 4.x, it looks like “bom_csv_grouped_by_value” is the one I always use, but “bom_csv_grouped_by_value_with_fp” seems the same but better and I’ll use that one going forward. If you’re going to keep one, “bom_csv_grouped_by_value_with_fp” would seem to be the superset plugin and I don’t think the others would be missed (by me at least).
For my purposes the HTML ones are obsolete when you can use @qu1ck’s interactive html bom plugin instead, but maybe there’s still a usecase.
The power of the system is that you can customize plugins for your own use, though I don’t know how many people actually do that. But it’s a lot friendlier to customize them when there are a good variety of example plugins that can be used as a basis for a new one.
- Is there a way you can slim down the list while still shipping enough plugins to use as a basis for custom BOM plugins? (Nearly-identical plugins don’t provide any extra value as examples)
- If kicad ends up shipping plugins that aren’t included in the default plugin list, will the existence of the additional plugins be documented so that users are aware of them? Undiscoverable plugins are as good as nonexistent.