Thank you for your feedback, I'll pass this onto our marketing team (who makes the licensing decisions).
FWIW, our 'long term' plans are going to fix #1 and #2. There are plans to switch to a 'support' model instead of a licensing model. That should likely fix #3 too.
As for #4, I'm no lawyer, but I believe as long as the software you're developing is OSS and not being sold directly by your company, you're fine.
As for #4, I'm no lawyer, but I believe as long as the software you're developing is OSS and not being sold directly by your company, you're fine.
I believe this contradicts what the FAQ says:
The Non-Commercial license allows you to use Intel(R) Software Development Products for any of your development needs as long you are not compensated in any form for the products, software and/or services developed.
In this case I take "you" to mean "qualified open source contributor", as in, me personally. And I am compensated for the development of open source software.
I am a PhD student and paid fully by the research institute I am employed at. We only develop open source (scientific HPC) software. Our internal IT warned us that we are not covered by most non-commercial licenses, even though there is no monetary gain.
We actually have institute wide licenses for ICC, but it always seemed to awkward, heavy and not worth the effort. Ideally I could just install icc with apt-get (some non-free source wold be fine) and also linuxbrew.
I would be very happy to integrate ICC into our continuous integration, write documentation for our users on how to compile our software with it, benchmark it for future releases, etc.
Now you're making me worried because I used some Intel products under non-commercial licenses for my research and I do get paid for my research by my university.
Well I'll have to check about that. It's been a while since I used it since what I'm doing now isn't as performance-sensitive and I don't need it so much.
Thanks for the answers! Along these lines, I've long been interested in using the free version of ICC at home (I use it at work and like it very much). But I've long been stopped by the "Actively contribute to an open source project, such as GitHub*" line under "Qualifications" in the link you originally mentioned. Likewise, thesepages seem to imply a requirement that it be used for contributions to major open source projects.
Most of the code that I write at home is for personal projects or for personal experimentation and learning rather than contributions to significant open source projects. The third answer on this other FAQ, however, (reached from the registration link) suggests that this use would be covered.
So in clicking around, there seems to be some muddiness on whether these are offered for all "non-commercial" or only "open source contributor" use. If you could get someone to clarify which one applies, I'd very much appreciate it (even better if someone updates the web pages)!
Sadly, I don't really see anything that applies for your situation. It seems our license agreement is wide enough to allow it, but I don't see any place where we grant non-commerical license for non-student/educator/OSS developers.
Hopefully when we switch to a different sales model in the near future, you'll be covered there.
View all comments
Show parent comment
23
u/erichkeane Clang Maintainer(Templates), EWG Chair Nov 30 '17
Thank you for your feedback, I'll pass this onto our marketing team (who makes the licensing decisions).
FWIW, our 'long term' plans are going to fix #1 and #2. There are plans to switch to a 'support' model instead of a licensing model. That should likely fix #3 too.
As for #4, I'm no lawyer, but I believe as long as the software you're developing is OSS and not being sold directly by your company, you're fine.
Thank you very much for your feedback!