On 04.05.2015 16:19, De Cesaris, Ivan wrote: > Hi All, > jumping on the topic of "the future of OpenOCD", one thing I'd like the core > group to consider is the license. > > Maybe this is not obvious to everyone but the code, being GPL, precludes some > usages. > I'm not a lawyer but I can't release internal developed code for new silicon > to any external customer (i.e. not in my company), because an NDAs can't > "override" GPL licensing. > Something like a BSD license would work great in this kind of scenario, > otherwise whatever external customer needs to wait for the debugging > capabilities to be publicly disclosed before we can ship any OpenOCD. I am not sure if this is a good idea. If the license was BSD, nothing stops a company from developing internal code based on OpenOCD, and only distributing it to their customers (maybe even under NDA), never giving back to the project.
cu Michael ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
