kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #03559
Re: Library work and project librarian?
-
To:
kicad-devel@xxxxxxxxxxxxxxx
-
From:
"phinitnan_c" <crackerizer@...>
-
Date:
Wed, 04 Nov 2009 07:31:26 -0000
-
In-reply-to:
<alpine.SOC.1.99.0909292154250.8788@...>
-
User-agent:
eGroups-EW/0.82
Hello Vesa and all developers,
I would like to invite you to share these ideas through my wiki page at http://kicad.sourceforge.net/wiki/index.php/User:Crackerizer
I would love to see these ideas are put in kicad, not just a discussion.
--- In kicad-devel@xxxxxxxxxxxxxxx, Vesa Solonen <vsolonen@...> wrote:
>
> Is there any willingness to discuss our release library structure and
> content? I'd like to reach some consensus how to improve current situation
> and I'm also eager to take 'project librarian' position on best effort
> basis. I'm not willing to do 3D-models, but vetting submitted stuff and
> doing some cosmetic modifications to current symbols. Naturally my own
> stuff will get merged in too, as soon as it gets up to publication
> quality.
>
> What I think is needed mostly:
>
> *Official symbol drawing guidelines with sizes and line widths.
>
> *Discussion how to organise the library tree and possible sub-branches.
>
> *Library and component naming policy
>
> *Library licenses allowed.
>
>
> The more flexible symbol system would include line width classes, that
> would get sized on load time to user specification. There has been some
> ideas before and they may be rehearsed here:
> http://tech.groups.yahoo.com/group/kicad-devel/message/2215
>
> Some nice libraries I found recently:
> http://smisioto.no-ip.org/elettronica/kicad/kicad.htm
>
> IMHO the library is the last annoyance to new user of Kicad. The
> functionality is mostly enough in current development versions.
>
> -Vesa
>
References