Re: [Kicad-developers] [RFC] 3D models repository

Wayne, others, A lot of input here, thanks everyone. Based on the suggestions above, my proposal is as follows: symbols licence file:

Re: [Kicad-developers] Hard-coded hotkeys in pcbnew/tools/selection_tool.cpp

In fact, this isn't the only GAL hotkey that is hard-coded right now. I noticed that the GAL tools that have editable hotkeys use the TOOL_ACTION::LegacyHotkey -- what should be done about GAL-only features that had hotkeys added? Should they be shown in the hotkey editing window with a note that

Re: [Kicad-developers] Pcbnew Python Interface breakage?

Thanks JP! This fixes the invocation error. It does behave differently to the previous version in that it doesn't throw parse errors if a library has invalid kicad_mod files in it. I have been using this function to make sure footprints are valid so it wouldn't work for that any more. Looking at

Re: [Kicad-developers] [RFC] 3D models repository

Hi, On 28.06.2017 19:40, Wayne Stambaugh wrote: > "KiCad Developers" should probably be changed to "KiCad" as in the > project. They have been used interchangeably in the past so my > motivation to change them would be low. That is still not a legal entity. > That is the point of the KiCad

Re: [Kicad-developers] fp_arc confusion

On 2017-06-27 06:18 PM, hauptmech wrote: I suspect it will come up about as often as it has (so once in 5 years?). Perhaps you could a couple lines of documentation for fp_arc in the file formats pdf so the next person that encounters this has a chance to recognize the error? It was

Re: [Kicad-developers] [RFC] 3D models repository

On 6/28/2017 12:18 M, Simon Richter wrote: > Hi, > > On 28.06.2017 16:48, Wayne Stambaugh wrote: > >> In source we typically do this: >> >> * Copyright (C) 2017 Leet Hacker , >> * Copyright (C) 2017 KiCad Developers. > >> The user copy right is followed by the

Re: [Kicad-developers] [RFC] 3D models repository

Hi, On 28.06.2017 16:48, Wayne Stambaugh wrote: > In source we typically do this: > > * Copyright (C) 2017 Leet Hacker , > * Copyright (C) 2017 KiCad Developers. > The user copy right is followed by the project copyright which is > updated as the file is modified

Re: [Kicad-developers] [RFC] 3D models repository

My two cents. All this copyleft licensing stuff for _libraries_ is over-complicating things, copyright on stuff like footprints and accurate 3d models is fairly tenuous as the representation of the work is very tightly constrained by engineering concerns and standardization, and a good chunk are

[Kicad-developers] Jenkins build is back to normal : kicad-qa #2676

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

Simon, I committed your patch to the master branch. I cleaned up the formatting, removed trailing whitespace, and added a table of contents. If I broke any formatting, please let me know. In the future, please limit you column width to 80 or 100 for markdown files. It's also a good idea to add

Re: [Kicad-developers] Differential pair suffix matcher

On 28.06.2017 15:23, hauptmech wrote: > I'm not sure what you mean by supporting busses. Aren't they already > supported with the current matching code? I mean recognizing net names such as BUS_LINE_P0/BUS_LINE_N0 (with the index as the last character). Differential bus routing might happen in

Re: [Kicad-developers] [RFC] 3D models repository

In source we typically do this: * Copyright (C) 2017 Leet Hacker , * Copyright (C) 2017 KiCad Developers. The user copy right is followed by the project copyright which is updated as the file is modified by other developers. It may also be a good idea to add the

Re: [Kicad-developers] [RFC] 3D models repository

Javier, Thank you for the clarification. Adding the license to each file as a comment is fine but there are some caveats. The current symbol library parser will choke on the license comment. I can change this fairly easily although that would break the no legacy file format change mandate that

Re: [Kicad-developers] [RFC] 3D models repository

Good-to-know knowledge. Thanks for the education, Javier. So if I do some minor changes to some file with "Copyright John Smith 2017" and since it is minor I don't even bother adding a second line there, does it imply "I'm passing my copyright ownership to John Smith" or actually the copyright

Re: [Kicad-developers] Differential pair suffix matcher

I'm not sure what you mean by supporting busses. Aren't they already supported with the current matching code? Or do you mean routing a bus of pairs in a single action? On 29/06/17 00:53, Tomasz Wlostowski wrote: On 28.06.2017 05:23, hauptmech wrote: Are there any issues with matching "P"

Re: [Kicad-developers] [RFC] 3D models repository

One more clarification: all files need a copyright notice which precedes the license notice. So something like "Copyright John Smith 2017" and then "This work is licensed under..." The reason is simple: copyrightable works start their life as "all rights reserved" by default. The only person who

Re: [Kicad-developers] [RFC] 3D models repository

Sorry, I forgot to answer this: On Wed, Jun 28, 2017 at 1:24 PM, Oliver Walters < oliver.henry.walt...@gmail.com> wrote: > Wayne, Maciej, et al, > > This has been sitting in my //todo for a while. Can I get some > clarification on the LICENSE issue and then I will ensure it is applied to > the

Re: [Kicad-developers] [RFC] 3D models repository

Hi, as a reminder, here are the texts we proposed: For schematics symbols and for complete symbol libraries: "This work is licensed under the Creative Commons CC-BY-SA 4.0 License. To the extent that circuit schematics that use Licensed Material can be considered to be ‘Adapted Material’, then

Re: [Kicad-developers] Differential pair suffix matcher

On 28.06.2017 05:23, hauptmech wrote: > Are there any issues with matching "P" and "N" instead of "_P" and "_N" > for the differential pair suffix matcher? I have an existing design with > the former convention. Matching the single letters will also correctly > match the "_P" style suffix. > > If

Re: [Kicad-developers] [RFC] 3D models repository

Oliver, I don't make any claims to be a legal expert but I believe that adding a LICENSE file to each repo should suffice. Perhaps our friends and CERN could comment on this if I am mistaken. Cheers, Wayne On 6/28/2017 7:24 AM, Oliver Walters wrote: > Wayne, Maciej, et al, > > This has been

Re: [Kicad-developers] [RFC] 3D models repository

Wayne, Maciej, et al, This has been sitting in my //todo for a while. Can I get some clarification on the LICENSE issue and then I will ensure it is applied to the repos: Am I correct in my understanding that the following text is ALL that is required (placed within a LICENSE file in each repo)?

Re: [Kicad-developers] fp_arc confusion

or use boost::variant and switch to std::variant in the future? On 28 June 2017 at 00:18, hauptmech wrote: > The tokens for circles are fine. > > I suspect it will come up about as often as it has (so once in 5 years?). > > Perhaps you could a couple lines of documentation

Re: [Kicad-developers] Pcbnew Python Interface breakage?

Le 27/06/2017 à 17:03, Kaspar Emanuel a écrit : > I am just looking at writing a fix at > https://github.com/KiCad/kicad-source-mirror/blob/37f8c83c5bc5e8a61cc25d69de569dee7eea0e9f/pcbnew/swig/module.i#L69 > > If you can see a quick fix you could probably save me a lot of time as I am > planning