search

joe-scotto / scottokeebs

A collection of free-to-build handwired keyboard and macropad projects.
https://scottokeebs.com
Other
916 stars 190 forks source link

KiCad files in their own repo #13

Closed rsescu closed 2 weeks ago

rsescu commented 8 months ago

Hi. Nice project, love your vids! Just a question, have you considered splitting Extras/ScottoKicad/ into it's own repository. Might be a cool idea to try and get it published as a plugin?

joe-scotto commented 8 months ago

I thought about it when I put everything together but I instead decided to keep it here as it makes it easier to just link one thing with everything.

Maybe one day I'll look into making it a plugin but no plans currently.

marcuswu commented 4 months ago

I came here to make the same suggestion as @rsescu. Perhaps use a git submodule to link the KiCad files back into this project so you can still pull it and use it as one?

joe-scotto commented 4 months ago

Submodules might actually be the solution I look into soon as the repo is starting to approach the 2gb limit. The problem and reason I haven't done anything is that my videos, specifically for Kicad, all show downloading the project and that wouldn't work with submodules on one repo. Might be just as simple as linking the new submodule underneath the video.

The other issue with this method is that it starts making it more complex for me to manage. The way I work now is that I just push everything to ScottoKeebs because it makes my life easier. In the next few months I'll take a deeper look at this because I am very close to hitting the repo size limit.

marcuswu commented 3 months ago

I was thinking about it more, and if you wanted the Kicad components under a separate license, it would be nicer under a separate repo. For instance, in order to clear the legality of utilizing these components within a commercial keyboard. It's clear you don't want the keyboards you've designed sold commercially without making a deal with you. However, is it ok to use the Kicad schematic and footprint libraries to design a unique design and sell that commercially? If that is the intent, a separate license file within a directory can work, but a separate repository with a different license is clearer.