On Sat, Mar 28, 2015 at 2:42 AM, Miguel Ángel Ajo <majopela@xxxxxxxxxx>
wrote:
I’m not sure it fits all use cases I could think of, for example,
let’s think you’re a board assembler/manufacturer, and you setup
a site that accepts KiCad designs, and processes the files
automatically via scripting to send you a cost estimation,
and other information.
Having SINTEF as AGPL could require them to publish their
website scripts?, or their processing scripts?, it would be nice
by the way, since other assemblers could have the chance to
start doing the same, but… it’s probably an entry barrier for
this ti happen.
opinions?,
Miguel Ángel Ajo
I don't think this is a problem; the IGES export code can always be
removed in such a case; after all why would you want to send
KiCad + IGES files to a board manufacturer? Anyway, these are
issues which people in some situations will need to deal with and
in the worst case they remove IGES support or get confirmation
from SINTEF about whether they require a licensing agreement or
not. I'd say the vast majority of our users (in fact all current users
as far as I know) will have no problems at all even using SISL in
their design environments.
- Cirilo
_______________________________________________
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
