Neat! Thank you! What do you think about having a separate repo for it? That will make it lighter weight to have as a submodule in another github repo.

I don't mind. I could host it if need be under my github repo. What naming would you suggest for such a version of the repo?

I've made: https://github.com/debug-edge/pcb-rnd Happy to have it under the debug-edge org.

Sounds perfect. Did you want to move them over or do you want me to fork it and do a pull request?

hmm, there's a problem with namespace collision of the proposed repo with pcb-rnd the layout editor. Would DebugEdge-for-pcb-rnd or something like that be better? It's a bit like setting up a repo named "KiCad". I have deleted my fork of https://github.com/debug-edge/pcb-rnd

I think you can rename your fork and it'll work ok. Let me know if you can't. Will it have a footprint and a component? Maybe pcb-rnd-lib would be ok.

this is a problem you will have to address for multiple layout editors.

specification, and then implementations in different formats

pcb-rnd supports parametric footprints too, so the repo could end up holding static versions of the footprints, a parametric version, and example layouts.

there is already a librnd that contains shared code for the EDA suite. The name should ideally be less generic and relate specifically to the DebugEdge connector.

Perhaps DebugEdge-pcb-rnd or DebugEdge-example-pcb-rnd or DebugEdge-4-pcb-rnd might be OK?

DebugEdge-example-pcb-rnd

would be the most extensible naming convention, allowing

DebugEdge-example-Eagle
DebugEdge-example-KiCad
etc..