kicad-developers team mailing list archive
Mailing list archive
Re: Oscad an EDA tool
On 07/01/2013 01:25 PM, Oscad Team wrote:
> Hello Dick, Martijn, Edwin
> We have not modified/bug-fixed/enhanced the KiCad source code. We have only used the
> binary version (installable through Ubuntu package manager for Ubuntu and the .exe file
> for Windows available on the KiCad webpg). We are using KiCad as the schematic editor and
> layout editor tool in Oscad. We mention that in our documents as well. In fact, in our
> tutorial series, we have made 4 tutorials on KiCad. We refer to them in our Oscad tutorial
> for the users to know more about schematic creation and PCB design. We have 3 tutorials on
> Oscad. All these tutorials are available on our webpage oscad.in <http://oscad.in> .
Awesome, sounds like a good way for me to finally learn how to use KiCad (better).
My "number of boards produced to lines of code contributed ratio" is embarrassing.
> We only call eeschema, pcbnew and cvpcb using a script and launch them. All our scripts
> are available on the webpage. Requesting you to kindly check the same.
Read section 3. of the GPLv2. This only applies if you are *distributing* binaries of
unmodified source or binaries of modified source. If you are pointing folks to a separate
resource from which users will obtain their own binaries, then there is no concern. In at
least the linux installer, I don't see where you are *distributing* KiCad binaries at all.
I don't know about the Windows installer.
The GPLv2 is present in file COPYRIGHT.txt in the KiCad source distribution if you do not
have prior familiarity.
> Kindly let us know of any issues/concerns/feedback.
I do like the conceptual approach that you have taken. It sounds like you have displaced
the kicad project manager with python code? (I don't know when I will find time to look
at it in detail.)
But using python to glue solution spaces together seems like a very sensible idea. That
top level code is not performance critical, so using the highest level language to do it
in makes perfect sense to me. Why program on your hands and knees when you can get up and
> Thanks and regards
> Oscad Team
> On Mon, Jul 1, 2013 at 8:31 PM, Dick Hollenbeck <dick@xxxxxxxxxxx
> <mailto:dick@xxxxxxxxxxx>> wrote:
> On 07/01/2013 07:31 AM, Edwin van den Oetelaar wrote:
> > On Mon, Jul 1, 2013 at 10:00 AM, Martijn Kuipers <martijn.kuipers@xxxxxxxxx
> > <mailto:martijn.kuipers@xxxxxxxxx <mailto:martijn.kuipers@xxxxxxxxx>>> wrote:
> > Just wondering if you (the OSCAD team) made any changes to KiCAD. I went to your
> > but was unable to find any source code to do a comparison.
> > So, my question is: did you do any enhancement/bug-fixing/changed to KiCAD code ?
> > Were any of "our" main debs aware of OSCAD launching? It seemed to me to come out of
> > the blue...
> > Kind regards,
> > Martijn
> > I have never heard of this.
> > Furthermore, no source code, not even a link to the KiCAD sources on the website.
> > Looks like somebody made a closed binary installer/distribution and forgot who is doing
> > most of the work.
> > I think this is a bad development, not the way to help the project or the users of
> > Greetings,
> > Edwin van den Oetelaar
> Thanks Edwin, let's all keep an eye on this relative to the GPLv2 licensing requirements.
> if( distribute_code )
> // read the damn license, do what it says
> Their stated intentions seem to comply, while their actions are not in obvious compliance.
> Help monitoring this is appreciated.
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp