You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
I am working on another script which will look through all the symbol files and work out which footprint associations need fixing. I'll have a PR up for that one soon.
Both of these steps can be performed for individual libraries, to make it easier. I will make a TODO file in this repo.
This means that once a library is marked as "complete" we can not accept any changes to it on the kicad-library repo
The text was updated successfully, but these errors were encountered:
This means that once a library is marked as "complete" we can not accept any changes to it on the kicad-library repo
I would say once a library is in the process of being transferred. Or at the latest when to pull request is made. (Here it becomes a lot harder to tell people with open pull requests that their stuff will not be handled in the old repo.)
I would like to start the transfer of symbol libraries from kicad-library to here. There are two major tasks to achieve:
1. Library Reorganization
The new libs will be sorted by function. Outline of examples for new library names - KiCad/kicad-library#1402
This can be handled (mostly) by script. We just need to work out which symbols to transition.
My script for managing this can be found here - KiCad/kicad-library-utils#184
2. Footprint Association
I am working on another script which will look through all the symbol files and work out which footprint associations need fixing. I'll have a PR up for that one soon.
Both of these steps can be performed for individual libraries, to make it easier. I will make a TODO file in this repo.
This means that once a library is marked as "complete" we can not accept any changes to it on the kicad-library repo
The text was updated successfully, but these errors were encountered: