kicad-developers team mailing list archive
Mailing list archive
Re: Library Repository
Vesa Solonen <vsolonen@...>
Sat, 20 Feb 2010 19:20:59 +0200
Thunderbird 220.127.116.11 (X11/20090817)
Dick Hollenbeck kirjoitti:
> phinitnan_c wrote:
>> I've created a set of library/package/3d and would like to share with
> the group. How can i do that? I also think that it would be good if
> there is a center repository for the library and make the lirary easier
> to share.
My guess is that we all like to get this sorted, but I'm going to try
persuade everyone to wait a bit. Why? Because the infrastructure is not
ready yet. Current library system is IMO too limited for multiple
reasons and I have to make a document similar to Dick's
notes_about_pcbnew_new_file_format.odt found in KiCad SVN root, but
regarding symbol-component library.
Most of all, we haven't yet agreed on symbol styling and naming rules.
I've done some proposals about the style and they were generally
accepted (no strong opposition, so I take them accepted...). Feel free
to correct. Footprint naming was discussed some time ago, but decisions
were left somewhat open.
> I'm sure you understand that we cannot allow just anyone to slam stuff
> into the master library repo. Such a thing does exist on SVN, and Vesa
> has been the maintainer of it. If you want stuff merged, send them to him.
The maintainer seems a bit too honorable to me as I haven't yet written
_anything_ to that repo :) JP did the last addition, but I'm willing to
take the library lead if we reach consensus that I have enough
credibility to be the benevolent dictator there. I think "newlib"
directory gets added for that.
> Vesa if you don't want this hat, maybe its time to start recruiting
> help. We're going to have to have more defined roles to grow this
> project without chaos. I like that you stepped up and volunteered to
> wear a specific hat.
I'm very happy to get a defined role as a project librarian, no doubts
about it. Something to consider before a real library rework includes at
* Implementing one symbol to multiple component mapping
* Implementing pin and gate swapping
* Logical to electrical to physical mapping
some components don't have logical or electrical polarity, but only
physical (variable capacitor)
* Everything must be abstracted as much as possible to get flexibilty
and ease of use and maintenance.
* Is my style proposal good enough
None of the above is not going to be fun or fast and I very probably end
up being quite punctual regarding "libarary standards" because someones
work depends on it (me included). That may also upset someone, but it
won't be my intention. Be assured that I'll do my best to sort those
So in the end phinitnan_c, I'm very willing to work with you on this.