evanshultz

@heitorPB Can you give us an update on this? It is ready for review? Also, please fix the branch conflicts and, if this is ready, bump the version at https://github.com/KiCad/kicad-website/pull/419/files#diff-87d0795c9f659b7ebd57e1b84e1c2435...

@heitorPB Sure. I'll try take a look later. Just trying to triage and marshal KLC changes to implementation. Edit: Note that I would now anticipate this revision being 3.0.22 at...

@heitorPB Above I understood there was a lot of work to be done before this PR would be ready. Can you please let us know if you believe this is...

I think that's a generally good way to abstract pin types instead of listing pin types bus-by-bus or case-by-case, but there are a few thoughts: 1. Of the two philosophies...

I started asking contributors to un-rotate pads if I had other comments about footprints. Only because it made the file size smaller to no effect on the footprint and, frankly,...

@poeschlr has, if I was properly in his mind, in the past avoided adding many clauses which were likely to give bogus results or constrain submission without reason. As I...

Sure. It seems to fit into KLC clauses S3.7 and F2.4, and should work with all other text since I've included a note about the pin 1 equivalent for footprints...

Here is a version of the image with the signals changed from numbers to letters. I believe it should be OK for us to use this in KLC but we...

We made the EP size a user choice. By default, a symbol is assigned the footprint with a thermal pad size that we believe is correct. But the user may...

Thanks for starting this, @antoniovazquezblanco ! I believe the root question was regarding footprints, so I'll add in my thoughts just for footprints below. --- In my experience the `XFormY`...