Organized Component Library

[mmb186]

No description provided.

[EdHurtig]

Friendly DevOps Note: Upon Merge Pls Select "Squash & Merge" for this Pull Request.

[jmassucco17]

Organization is welcome. Please address the following:
-The .pretty files should only have .kicad_mod files inside. No sub-folders and no libs. See https://github.com/KiCad/kicad-footprints for reference
-We did not understand libs when we made all those libraries each with a single symbol. Libraries can contain many symbols - you should consolidate related components into libraries, either grouped by manufacturer or function (see https://github.com/KiCad/kicad-library/tree/master/library for reference)

[lukemerkl]

Pretty much everything James said. We discussed the incorrect use of the .lib files the other day. Maybe you or Colin missed a commit?

[lukemerkl]

This is not the same as the screenshot from earlier, which was correct. :(

Controllers, Texas Instruments, etc should not be folders containing .lib files. They should be .lib files with multiple components called out in the text. so, if you were to create Texas Instruments.lib it would contain the definitions for the lm321_5pin, the lmR16030s, the lmx93, and so on. Right now you are designating the LM321_5pin, for example, as a Library.