Difference between revisions of "Licensing FAQ"
BenHilburn (Talk | contribs) |
(Minor fixes) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[UHD]] | + | [[UHD]] is publicly offered under the [https://www.gnu.org/licenses/gpl-3.0.en.html GNU General Public License version 3 (GPLv3)], and is also available under a less-restrictive Alternative License. For more details, please see the [https://www.ettus.com/sdr-software/detail/licenses Licenses page on ettus.com]. |
| + | |||
| + | [[RFNoC]] is publicly offered under the [https://www.gnu.org/licenses/lgpl-3.0.en.html GNU Lesser General Public License version 3 (LGPLv3)]. | ||
This page contains some Frequently Asked Questions about these licenses. Please note that while we can provide guidance about our licensing model, you should make license decisions based on your own legal counsel. | This page contains some Frequently Asked Questions about these licenses. Please note that while we can provide guidance about our licensing model, you should make license decisions based on your own legal counsel. | ||
| Line 7: | Line 9: | ||
=== "Does the GPLv3 license prohibit me from selling a product that uses your software?" === | === "Does the GPLv3 license prohibit me from selling a product that uses your software?" === | ||
| − | No | + | No! You can sell products & services with GPLv3 software. You must provide the source code for your product to anyone to whom you convey your product. See the question below. |
=== "Can I use the GPLv3-licensed version of UHD in my proprietary product?" === | === "Can I use the GPLv3-licensed version of UHD in my proprietary product?" === | ||
| − | If you use the GPLv3-licensed version of UHD in your application, your application must then also be licensed under the GPLv3. If you want to create a proprietary product with Ettus Research HW / SW, you need to use the Alternative License, which was created specifically for this purpose. | + | Yes! If you use the GPLv3-licensed version of UHD in your application, your application must then also be licensed under the GPLv3. If you want to create a proprietary product with Ettus Research HW / SW, you need to use the Alternative License, which was created specifically for this purpose. |
=== "We are using the GPLv3-licensed version of UHD internally, but do not want to release our source code." === | === "We are using the GPLv3-licensed version of UHD internally, but do not want to release our source code." === | ||
| Line 23: | Line 25: | ||
=== "We don't mind giving source code to our customers, but don't want to release it publicly. Do we need the Alternative License?" === | === "We don't mind giving source code to our customers, but don't want to release it publicly. Do we need the Alternative License?" === | ||
| − | It depends. The GPLv3 does not require you to release your source code publicly. It only requires you to provide your source code to anyone to whom you convey your application. Your application must be licensed under the GPLv3, though, so your customers would have the right to share the source code more broadly if they wished. | + | It depends, but if you want to ''guarantee'' that your source code does not become available publically then way to do this is via the Alternative License. The GPLv3 does not require you to release your source code publicly. It only requires you to provide your source code to anyone to whom you convey your application. Your application must be licensed under the GPLv3, though, so your customers would have the right to share the source code more broadly -- even publically -- if they wished. |
=== "We are using the GPLv3 version of your software. If we integrate your software into our product, does that mean we have to ship your source code along with our product?" === | === "We are using the GPLv3 version of your software. If we integrate your software into our product, does that mean we have to ship your source code along with our product?" === | ||
| − | If you have not made changes to our source code, then you can simply point your customers to our public software repositories. If you have made changes to our source code, you must either provide your "fork" of our software to your customers | + | If you have not made changes to our source code, then you can simply point your customers to our public software repositories. If you have made changes to our source code, you must either provide your "fork" of our software to your customers or contribute your changes back to us so that they are in the mainline version of the software. |
| − | + | ||
[[Category:Software Resources]] | [[Category:Software Resources]] | ||
Latest revision as of 12:13, 30 August 2022
UHD is publicly offered under the GNU General Public License version 3 (GPLv3), and is also available under a less-restrictive Alternative License. For more details, please see the Licenses page on ettus.com.
RFNoC is publicly offered under the GNU Lesser General Public License version 3 (LGPLv3).
This page contains some Frequently Asked Questions about these licenses. Please note that while we can provide guidance about our licensing model, you should make license decisions based on your own legal counsel.
Contents
- 1 Frequently Asked Questions
- 1.1 "Does the GPLv3 license prohibit me from selling a product that uses your software?"
- 1.2 "Can I use the GPLv3-licensed version of UHD in my proprietary product?"
- 1.3 "We are using the GPLv3-licensed version of UHD internally, but do not want to release our source code."
- 1.4 "We don't mind releasing our source code, but we need to make changes to UHD. Do we need the Alternative License?"
- 1.5 "We don't mind giving source code to our customers, but don't want to release it publicly. Do we need the Alternative License?"
- 1.6 "We are using the GPLv3 version of your software. If we integrate your software into our product, does that mean we have to ship your source code along with our product?"
Frequently Asked Questions
"Does the GPLv3 license prohibit me from selling a product that uses your software?"
No! You can sell products & services with GPLv3 software. You must provide the source code for your product to anyone to whom you convey your product. See the question below.
"Can I use the GPLv3-licensed version of UHD in my proprietary product?"
Yes! If you use the GPLv3-licensed version of UHD in your application, your application must then also be licensed under the GPLv3. If you want to create a proprietary product with Ettus Research HW / SW, you need to use the Alternative License, which was created specifically for this purpose.
"We are using the GPLv3-licensed version of UHD internally, but do not want to release our source code."
That's fine! The GPL only obligates sharing source code with an external party when they receive your application.
"We don't mind releasing our source code, but we need to make changes to UHD. Do we need the Alternative License?"
No, you do not need the Alternative License. The GPLv3-licensed version of UHD is perfect for this. It allows you to make changes to UHD as you wish, as long as you provide the source code for your "fork" of UHD to recipients of your application.
"We don't mind giving source code to our customers, but don't want to release it publicly. Do we need the Alternative License?"
It depends, but if you want to guarantee that your source code does not become available publically then way to do this is via the Alternative License. The GPLv3 does not require you to release your source code publicly. It only requires you to provide your source code to anyone to whom you convey your application. Your application must be licensed under the GPLv3, though, so your customers would have the right to share the source code more broadly -- even publically -- if they wished.
"We are using the GPLv3 version of your software. If we integrate your software into our product, does that mean we have to ship your source code along with our product?"
If you have not made changes to our source code, then you can simply point your customers to our public software repositories. If you have made changes to our source code, you must either provide your "fork" of our software to your customers or contribute your changes back to us so that they are in the mainline version of the software.
