Re: [Kicad-developers] KiCad Libraries (again)

Hi, I've just submitted a pull request ( https://github.com/KiCad/kicad-website/pull/236) trying to make a bit more clear when/why you need to update the libraries. Also adding links to github lib repos. Comments welcome :) Thanks, Diego On Sun, Nov 5, 2017 at 10:33 PM, Diego Herranz <

Re: [Kicad-developers] KiCad Libraries (again)

Thanks, Rene On 4 Nov 2017 4:06 pm, "Rene Pöschl" wrote: On 03/11/17 21:34, Diego Herranz wrote: > First of all, I think all the recent work around the libraries is great! > Thanks to everyone involved. I think sometimes libraries are underestimated > (not just in KiCad).

Re: [Kicad-developers] KiCad Libraries (again)

First of all, I think all the recent work around the libraries is great! Thanks to everyone involved. I think sometimes libraries are underestimated (not just in KiCad). If KiCad manages to have extensive, high-quality and clearly arranged libraries, many more users will end up using it. Having

Re: [Kicad-developers] KiCad Libraries (again)

Thanks Nick! Really happy to have this running on the website! I think a blog post would be a good idea, I'll see if I can make some words On Thu, Nov 2, 2017 at 8:14 AM, Nick Østergaard wrote: > Hello > > I will just announce that I merged the pull request. I hope this will

Re: [Kicad-developers] KiCad Libraries (again)

Hello I will just announce that I merged the pull request. I hope this will aid in getting the librarians to feel more part of the "official" KiCad, if they didn't before. I am glad that we have motivated librarians around. I will encourage Oliver and Co. to write an article to the "blog"

Re: [Kicad-developers] KiCad Libraries (again)

I have been working on this for a while, and have submitted the first version here - https://github.com/KiCad/kicad-website/pull/219 On Thu, Sep 14, 2017 at 10:01 PM, Oliver Walters < oliver.henry.walt...@gmail.com> wrote: > Hi everyone, > > The conversation of how best to manage and distribute

Re: [Kicad-developers] KiCad Libraries (again)

On 9/19/2017 10:35 AM, José Ignacio wrote: > > > On Mon, Sep 18, 2017 at 7:52 PM, Rene Pöschl > wrote: > > > > On 19 Sep 2017 2:05 am, "José Ignacio" > wrote: > > Probably,

Re: [Kicad-developers] KiCad Libraries (again)

On Mon, Sep 18, 2017 at 7:52 PM, Rene Pöschl wrote: > > > On 19 Sep 2017 2:05 am, "José Ignacio" wrote: > > Probably, contributors would need to agree to be attributed as a group > when the work is embedded in a design (When the library is distributed

Re: [Kicad-developers] KiCad Libraries (again)

Hi, Am 19.09.2017 um 01:44 schrieb Oliver Walters: > Thanks for the links Rene. > > Rene also found an older reference to a discussion between Wayne and > Torsten > -  > https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg16268.html > > This strongly suggests that the gEDA

Re: [Kicad-developers] KiCad Libraries (again)

IMO (engineer's point of view), the licensing for the 3D models is a good template for the schematic and footprint libraries. Regards, Ingo ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net

Re: [Kicad-developers] KiCad Libraries (again)

On 19 Sep 2017 2:05 am, "José Ignacio" wrote: Probably, contributors would need to agree to be attributed as a group when the work is embedded in a design (When the library is distributed in whole or part they should get attributed individually as the GPL requires).

Re: [Kicad-developers] KiCad Libraries (again)

Probably, contributors would need to agree to be attributed as a group when the work is embedded in a design (When the library is distributed in whole or part they should get attributed individually as the GPL requires). Ownership transfer shouldn't be necessary. a CLA is a good idea anyway to

Re: [Kicad-developers] KiCad Libraries (again)

Huh, this looks pretty cool - https://github.com/cla-assistant/cla-assistant On Tue, Sep 19, 2017 at 9:46 AM, Oliver Walters < oliver.henry.walt...@gmail.com> wrote: > PS: It would be nice to provide a simplified way for non-GPL users to >> provide attribution for the libraries without having to

Re: [Kicad-developers] KiCad Libraries (again)

> > PS: It would be nice to provide a simplified way for non-GPL users to > provide attribution for the libraries without having to name every single > john doe that made a symbol or footprint. If it's made simple people will > probably be more inclined to comply. What would such a thing look

Re: [Kicad-developers] KiCad Libraries (again)

Thanks for the links Rene. Rene also found an older reference to a discussion between Wayne and Torsten - https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg16268.html This strongly suggests that the gEDA license is the way to go. Unless I hear any very strong objections I

Re: [Kicad-developers] KiCad Libraries (again)

On 19/09/17 00:59, José Ignacio wrote: The GPL with font exception is probably the better of the two, as it is the least restrictive one contributors seem to agree on Well we use this already for the 3d model lib. https://github.com/KiCad/kicad-packages3D/wiki/Model-Licencing So it would

Re: [Kicad-developers] KiCad Libraries (again)

PS: It would be nice to provide a simplified way for non-GPL users to provide attribution for the libraries without having to name every single john doe that made a symbol or footprint. If it's made simple people will probably be more inclined to comply. On Mon, Sep 18, 2017 at 5:59 PM, José

Re: [Kicad-developers] KiCad Libraries (again)

The GPL with font exception is probably the better of the two, as it is the least restrictive one contributors seem to agree on. On Mon, Sep 18, 2017 at 5:47 PM, Oliver Walters < oliver.henry.walt...@gmail.com> wrote: > A further issue that has cropped up twice in the last hour: Library >

Re: [Kicad-developers] KiCad Libraries (again)

A further issue that has cropped up twice in the last hour: Library licensing https://github.com/KiCad/kicad-library/issues/1259#issuecomment-330374095 https://forum.kicad.info/t/default-libraries-gpl-licencing-vs-proprietary- designs/140/8 We have been discussing this for a while in this

Re: [Kicad-developers] KiCad Libraries (again)

Oliver, Great work! This is really shaping up nicely. Cheers, Wayne On 9/17/2017 12:13 AM, Oliver Walters wrote: > Hugo can use external JSON data during the build step, so I've worked > out how to list the GitHub library releases directly onto the downloads > page! > > Some progress images

Re: [Kicad-developers] KiCad Libraries (again)

Diego, This has already been done :) On Sun, Sep 17, 2017 at 6:51 PM, Diego Herranz wrote: > Hi, Oliver. > > Thanks a lot for your work on this. I think it's gonna be really useful, > especially for newbies, but also for experienced users. > > Regarding the new repo to

Re: [Kicad-developers] KiCad Libraries (again)

I have also created a FOOTPRINTS repository at - https://github.com/KiCad/footprints The intent is to have ALL the .pretty repos merged here, to combat the ever decreasing maintainability of the libraries. For now, it contains each .pretty repository as an individual submodule. On Sun, Sep 17,

Re: [Kicad-developers] KiCad Libraries (again)

Hugo can use external JSON data during the build step, so I've worked out how to list the GitHub library releases directly onto the downloads page! Some progress images here: https://imgur.com/a/2V6E3 Most of the framework is in place now. I need some assistance with wording for

Re: [Kicad-developers] KiCad Libraries (again)

Some more progress: https://github.com/KiCad/kicad-library/issues/1622 On Sat, Sep 16, 2017 at 12:53 PM, Oliver Walters < oliver.henry.walt...@gmail.com> wrote: > I have worked out how to transfer the KLC page to the Hugo templating > system (it is SO much harder to use than Jenkins :p) > >

Re: [Kicad-developers] KiCad Libraries (again)

I have worked out how to transfer the KLC page to the Hugo templating system (it is SO much harder to use than Jenkins :p) Example: https://i.imgur.com/4kZnvOA.png The libraries information is also moved across, but that's just static content so it's much simpler. I'll keep you posted. On

Re: [Kicad-developers] KiCad Libraries (again)

Hi, On 15.09.2017 04:14, Oliver Walters wrote: > Full description of library elements, including image previews / > metadata / etc. This will be searchable. I'd like to also get a culture going where the library is a huge commons, and it is acceptable and encouraged to improve existing parts:

Re: [Kicad-developers] KiCad Libraries (again)

Oliver, thanks for your efforts on this. I have been thinking for a while that the current way libraries are located and downloaded could benefit from improvement: - At present the symbol, footprint and 3d libs are/can be installed site-wide (e.g. Mac /Library/Application Support/kicad/

Re: [Kicad-developers] KiCad Libraries (again)

Oliver, Am 15.09.2017 um 00:27 schrieb Oliver Walters: A minor nitpick from personal preference: An always visible table of contents for easy jumping between pages and/or breadcrumb navigation would be great. Can you provide an example of what you mean? From the screenshots,

Re: [Kicad-developers] KiCad Libraries (again)

On 9/14/2017 8:54 PM, Oliver Walters wrote: > Ben, > > That's also an option, I hadn't considered that! Perhaps I was focused > on the GitHub-side solution too closely. > > Wayne, do you want to weigh in here before I spend too much further > effort developing this? Could the libraries page be

Re: [Kicad-developers] KiCad Libraries (again)

Hi, TL;DR yes, please place information about new libraries, their changes and plans on this to the KiCad website! But also keep information about changed documentation or localizations here. Am 15.09.2017 um 04:01 schrieb Adam Wolf: > I really, really like the idea of having the libraries page

Re: [Kicad-developers] KiCad Libraries (again)

This sounds awesome to me, and helps keep KiCad cohesive. I remember when basically every KiCad site was a fan site and it was pretty hard to find anything, and we have done a great job lately and this is going to help make it even better I think! I do not think that this even technically

Re: [Kicad-developers] KiCad Libraries (again)

Adam, Both are really good points. Here's what I propose: *Short Term:* Move the library information / license / KLC / contributing information to the website. This will also include links to download library releases (from github) *Medium Term:* Provide downloads of individual libraries,

Re: [Kicad-developers] KiCad Libraries (again)

I really, really like the idea of having the libraries page on the KiCad website itself. I have run into numerous people who do not understand that the github libraries are "official". Plus, this means that *for whatever reason* if the libraries move from github, the pages explaining the

Re: [Kicad-developers] KiCad Libraries (again)

Ben, That's also an option, I hadn't considered that! Perhaps I was focused on the GitHub-side solution too closely. Wayne, do you want to weigh in here before I spend too much further effort developing this? Could the libraries page be developed on the KiCad website itself? The structure could

Re: [Kicad-developers] KiCad Libraries (again)

On 15 Sep 2017 01:29, "Andrey Kuznetsov" wrote: If possible, would be good to have a single full KLC page with all the rules combined in addition to the individual chapter pages, hopefully using the same KLC source without having to maintain 2 version. This is useful when

Re: [Kicad-developers] KiCad Libraries (again)

Ingo, On 15 Sep 2017 03:51, "Ingo Kletti" wrote: Hi, will the framework allow to generate and present previews/artwork for the schematic symbols and footprints contained in the different libraries? This might be useful if in the future the libraries become really

Re: [Kicad-developers] KiCad Libraries (again)

Hi, will the framework allow to generate and present previews/artwork for the schematic symbols and footprints contained in the different libraries? This might be useful if in the future the libraries become really big (e.g. if there should be official atomic libraries). Think of a user

Re: [Kicad-developers] KiCad Libraries (again)

Hey Oliver, Nice work! Once this is ready to go, it is definitely something that should be added or linked to the KiCad website. Currently our users really don't have friendly resource for discovering what libraries are available for KiCad and how to get them. I consider this a big plus for

Re: [Kicad-developers] KiCad Libraries (again)

If possible, would be good to have a single full KLC page with all the rules combined in addition to the individual chapter pages, hopefully using the same KLC source without having to maintain 2 version. This is useful when you want to use the browser find functionality instead of clicking on

Re: [Kicad-developers] KiCad Libraries (again)

Does this method provide an advantage over doing a similar thing using Hugo and putting the docs on the kicad-pcb.org website? https://github.com/KiCad/kicad-website - Ben On Thu, Sep 14, 2017 at 7:01 AM, Oliver Walters < oliver.henry.walt...@gmail.com> wrote: > Hi everyone, > > The

[Kicad-developers] KiCad Libraries (again)

Hi everyone, The conversation of how best to manage and distribute KiCad libraries has been raging for a while now. Users looking to download or contribute to the libraries are currently presented with a github landing page and some bland wiki pages (e.g. for the KLC information). I have been