scottbez1 / scottbez1/splitflap
KiCad 6 migration
Open
Nobody has claimed this yet.
area: electronics
area: tooling
priority: high
- Dominant language
- JavaScript
- Stars
- 4.1k
- Forks
- 344
- PR merge metrics
- No merged PRs in 30d
Description
KiCad 6 is out! All electronics projects should be updated and verified under KiCad 6.
A few areas of concern that come to mind:
- KiKit (currently using a custom fork to add V-Cut support https://github.com/scottbez1/KiKit/tree/vcutlayer which should be possible with the new CLI options in KiKit v1)
- KiBot - need to make sure everything works as expected under 6
- Checking, updating, or deprecating other KiCad automation scripts, like PCB SVG export and 3d rendering (maybe possible to switch to KiBot for these now?)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the electronics projects and automation scripts covered by the migration, then check the KiKit custom V-Cut fork and KiBot workflows under KiCad 6. Review the PCB SVG export and 3D rendering scripts, and determine whether KiBot can replace them. Done means every project and listed automation path is verified, updated, or explicitly deprecated.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100