Transfer footprint generator to the KiCad community ?

[myfreescalewebpage]

Hello @pointhi

First of all just want to say that's a very nice job done here that help so much to create footprints :)

I was wondering why the repository was not part of the KiCad community ? I see several good reasons:

• better visibility for people submitting footprints, they often do not know the existence of this repository
• maintenance by all librarians, @poeschlr particularly is very good at this job. Today I realized that you were mandatory to merge the pull requests

However, maybe you have good reasons to not doing that ?

Cheers, Joel

Edit: this will also permit to expend the management of labels we have to this repo. See also my propositions on this subject at https://github.com/KiCad/kicad-symbols/issues/1368

[pointhi]

There was some plane someday, but it remained in my hand. Personally I would have control over KicadModTree to keep it clean. The scripts on the other hand are merged when the footprint is merged, no matter how the quality of the script is. Simply because those scripts are more for documentation and rare use.

Personally, I would like to make footprint generators a official project. But based on the official kicad project code and not a duplication of it. See here: https://github.com/pointhi/kicad-python

Some related issue: https://github.com/pointhi/kicad-footprint-generator/issues/55

The main idea is to have a unified scripting api, for plugins as well as footprints. And the footprint generator has a unified interface to work with command line as well as inside KiCad.