<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Introducing  Nordic’s new software licensing schemes</title><link>/nordic/nordic-blog/b/blog/posts/introducing-nordics-new-software-licensing-schemes</link><description>We are very excited to inform you that we have introduced our new software licenses with the release of SDK v13.0. The new licenses are based on the well-known BSD license class and give more flexibility and freedom to customers while still protectin</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: Introducing  Nordic’s new software licensing schemes</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/introducing-nordics-new-software-licensing-schemes</link><pubDate>Mon, 27 Aug 2018 21:09:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d97f03bc-9905-41c2-961c-3f1a9b9ccce6</guid><dc:creator>MichaelDennis</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Which license applies to which software?&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1021&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Introducing  Nordic’s new software licensing schemes</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/introducing-nordics-new-software-licensing-schemes</link><pubDate>Sun, 06 Aug 2017 11:07:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d97f03bc-9905-41c2-961c-3f1a9b9ccce6</guid><dc:creator>Roger Clark</dc:creator><slash:comments>0</slash:comments><description>&lt;blockquote&gt;
&lt;p&gt;This seems like the perfect opportunity to express my hope that you will consider moving SDK development to github as well&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I also think this would be an excellent idea.&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1021&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Introducing  Nordic’s new software licensing schemes</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/introducing-nordics-new-software-licensing-schemes</link><pubDate>Wed, 21 Jun 2017 04:37:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d97f03bc-9905-41c2-961c-3f1a9b9ccce6</guid><dc:creator>Janek Mann</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Really happy to see this change, and congratulations to the teams at Nordic for making this jump (clearly it must have taken someone a lot of convincing since it took this long).&lt;/p&gt;
&lt;p&gt;This seems like the perfect opportunity to express my hope that you will consider moving SDK development to github as well. The current model is frankly embarrassing... You release new SDKs with no clear changesets, and frequently code that was working before stops working on new SDKs, with no clear insight for your customers as to what changed. Even your own examples frequently stop working on new SDKs, and frankly I have a hard time understanding why you don&amp;#39;t seem to have a test plan before releasing new versions of the SDKs to ensure that all the examples compile and produce correct output, under all supported compilers!&lt;/p&gt;
&lt;p&gt;Moving to github would give you a central place to collect issues with the SDK, and give your customers clear understanding about when these issues have been fixed. Currently it feels like a &amp;quot;black box&amp;quot; to be frank.&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1021&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>