Why not start an official KiCad Atomic library?

[Joan_Sparky]

@Sprig

If there were a place to upload the various Atomic Parts that KiCad users have in their own libraries, then maybe there could be a separate KiCad Atomic Parts Compliance (KAPC) rules to that separate library.

“Es gibt nichts Gutes, außer man tut es.”
Erich Kaestner

Go ahead, write up a KAPC 0.1 and stuff will develop from there.

Something to start with and base your efforts on (as a lot of grey-matter has mulled over this already, repeatedly):

Standard symbol field names initiative

Following discussions here on the forum, on the KiCAD libraries GitHub and the developers mailing list it seems there is no consensus on setting up default names in KiCAD or the standard symbol libraries as an acceptable solution to encouraging interoperability between third party tools. It is therefore up to the community of tool builders to decide on a standard to follow, to prepare a document that describes it and to put it up online somewhere and badger people when they don’t use it. …

Default manufacturer's part number field in KiCad libraries

A github issue requested that KiCost support a field called PartNumber (or something like that) that the KiCad libraries now had for each symbol. I’ve got a nightly Windows version of KiCad and I’ve examined and grepped the symbol libraries but can’t find any field like that. Does such a field exist? Is it in the standard libraries that are installed with the nightly builds, or is it somewhere else?