Comments on: GPLv2 and GPLv3 licensing dynasty or end of the road? http://www.visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/?utm_source=rss&utm_medium=rss&utm_campaign=gplv2-and-gplv3-%25e2%2580%2593-licensing-dynasty-or-end-of-the-road Distilling market noise into market sense. Mon, 06 Sep 2010 09:00:45 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Andreas Constantinou http://www.visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/comment-page-1/#comment-17530 Andreas Constantinou Mon, 08 Oct 2007 05:59:02 +0000 http://visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/#comment-17530 Hi Keith, You 're right, finding such an obvious mistake in a article makes you wonder about the quality of the overall paper. But the structure, the attention to detail in the later part of the paper and the depth of analysis I would hope point to a high-quality paper. Unfortunately the typo did crop in, and we 're improving our peer review process to make sure such typos don't slip in again. We are also in the process of including a client testimonials page to reinforce the continued quality of our work - in the meantime you can look us up at LinkedIn. Keep the comments coming! Andreas VisionMobile Hi Keith,

You ‘re right, finding such an obvious mistake in a article makes you wonder about the quality of the overall paper. But the structure, the attention to detail in the later part of the paper and the depth of analysis I would hope point to a high-quality paper. Unfortunately the typo did crop in, and we ‘re improving our peer review process to make sure such typos don’t slip in again.

We are also in the process of including a client testimonials page to reinforce the continued quality of our work – in the meantime you can look us up at LinkedIn.

Keep the comments coming!

Andreas
VisionMobile

]]> By: Keith http://www.visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/comment-page-1/#comment-17406 Keith Sat, 06 Oct 2007 13:56:32 +0000 http://visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/#comment-17406 Liz, The change you made does make the statement correct. I see my wording was unclear, in that I didn't mean that you wrote anything wrong about dynamic linking, but that you got the statement about static linking backwards. Sorry for the confusion due to that. I'll probably take time to read the rest of the paper, but given that this is the first thing I've seen by you or VisionMobile, I'm wary of putting very much reliance on what you wrote. When I find mistakes about facts I know in an article, it undermines my confidence in statements about things with which I'm not familiar. That's a normal response, I would think. Liz,

The change you made does make the statement correct. I see my wording was unclear, in that I didn’t mean that you wrote anything wrong about dynamic linking, but that you got the statement about static linking backwards. Sorry for the confusion due to that.

I’ll probably take time to read the rest of the paper, but given that this is the first thing I’ve seen by you or VisionMobile, I’m wary of putting very much reliance on what you wrote. When I find mistakes about facts I know in an article, it undermines my confidence in statements about things with which I’m not familiar. That’s a normal response, I would think.

]]> By: Keith http://www.visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/comment-page-1/#comment-17267 Keith Thu, 04 Oct 2007 19:49:16 +0000 http://visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/#comment-17267 Has anyone yet told you that you got the static/dynamic linking explanation on pages 5/6 backwards? It is generally accepted that static linking with GPL code creates a derivative work and so requires that the combined program be licensed as GPL, while there is disagreement about dymanic linking. You wrote it the other way around. I don't intend to be mean or overly-critical, but a mixup of that kind in the first few pages makes me wonder whether it is worth reading further. How well do you know your stuff? Hi Keith Firstly thank you for your comments. There is an error in the paper in that there should not be the word 'not' in the paragraph where we discuss static linking and we have now amended this in the paper. However we clearly state that there is no clear agreement (and so in your wording 'disagreement') within the FOSS community regarding dynamic linking. Finally we hope that you will read the complete paper before being overly-critical and we are always keen to discuss these issues further with all interested parties. Liz Has anyone yet told you that you got the static/dynamic linking explanation on pages 5/6 backwards? It is generally accepted that static linking with GPL code creates a derivative work and so requires that the combined program be licensed as GPL, while there is disagreement about dymanic linking. You wrote it the other way around.

I don’t intend to be mean or overly-critical, but a mixup of that kind in the first few pages makes me wonder whether it is worth reading further. How well do you know your stuff?

Hi Keith
Firstly thank you for your comments. There is an error in the paper in that there should not be the word ‘not’ in the paragraph where we discuss static linking and we have now amended this in the paper. However we clearly state that there is no clear agreement (and so in your wording ‘disagreement’) within the FOSS community regarding dynamic linking. Finally we hope that you will read the complete paper before being overly-critical and we are always keen to discuss these issues further with all interested parties.
Liz

]]> By: Melisa Bleasdale http://www.visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/comment-page-1/#comment-14043 Melisa Bleasdale Mon, 17 Sep 2007 23:12:59 +0000 http://visionmobile.com/blog/2007/09/gplv2-and-gplv3-%e2%80%93-licensing-dynasty-or-end-of-the-road/#comment-14043 You bring up an excellent point, that the end of the road for GPL3 adoptions seems unlikely. The open source community must take into account that many more projects will migrate with subsequent and upcoming releases. Many projects chose to hold off until their next revision, meaning that while we haven't seen a tidal wave of activity in terms of adoption, we have seen a steady rate of conversion. While tracking GPLv3 conversion rates is important for organizations looking for the risks and benefits of sticking with GPLv2 (or not), understanding what open source you're currently using in your code base is critical to successful risk mitigation. If you don't know what you have, where it's located, how you're using it and whether or not it carries license or vulnerability risks with it, how can you rectify the issues? When it comes to GPLv2 and v3, organizations must stay on top of possible forking issues and how to determine which parts of their applications fall under which license terms and whether both are present at once. It stands to get very complex, especially as you note, in the embedded market -- a market ripe for open source licensing challenges. --Melisa LaBancz-Bleasdale, Palamida You bring up an excellent point, that the end of the road for GPL3 adoptions seems unlikely. The open source community must take into account that many more projects will migrate with subsequent and upcoming releases. Many projects chose to hold off until their next revision, meaning that while we haven’t seen a tidal wave of activity in terms of adoption, we have seen a steady rate of conversion.

While tracking GPLv3 conversion rates is important for organizations looking for the risks and benefits of sticking with GPLv2 (or not), understanding what open source you’re currently using in your code base is critical to successful risk mitigation. If you don’t know what you have, where it’s located, how you’re using it and whether or not it carries license or vulnerability risks with it, how can you rectify the issues? When it comes to GPLv2 and v3, organizations must stay on top of possible forking issues and how to determine which parts of their applications fall under which license terms and whether both are present at once. It stands to get very complex, especially as you note, in the embedded market — a market ripe for open source licensing challenges.

–Melisa LaBancz-Bleasdale, Palamida

]]>