Comments on: Best Practices for Creating an Open Source Policy http://olex.openlogic.com/wazi/2009/create-open-source-policy/ Thinking OPEN Wed, 11 Nov 2009 19:16:14 -0700 http://wordpress.org/?v=2.8.5 hourly 1 By: Wazi » Articles » The Six Elements of Open Source Governance http://olex.openlogic.com/wazi/2009/create-open-source-policy/comment-page-1/#comment-3144 Wazi » Articles » The Six Elements of Open Source Governance Wed, 15 Jul 2009 21:46:52 +0000 http://olex.openlogic.com/wazi/?p=2288#comment-3144 [...] answer that question, you need to know some stuff, and then you need to create an open source policy. The questions below include the basic questions you and your organization need to be able to [...] [...] answer that question, you need to know some stuff, and then you need to create an open source policy. The questions below include the basic questions you and your organization need to be able to [...]

]]> By: Stormy http://olex.openlogic.com/wazi/2009/create-open-source-policy/comment-page-1/#comment-473 Stormy Mon, 02 Mar 2009 15:58:47 +0000 http://olex.openlogic.com/wazi/?p=2288#comment-473 Thanks, Gilles. I agree that here are a lot of tools that can help implement the policy. I mentioned FOSSology and OSS Discovery briefly. I saw this article as a how to get your policy up and running - I think there could be a whole part two article on best practices for implementing your open source software policy effectively! Thanks, Gilles. I agree that here are a lot of tools that can help implement the policy.

I mentioned FOSSology and OSS Discovery briefly. I saw this article as a how to get your policy up and running – I think there could be a whole part two article on best practices for implementing your open source software policy effectively!

]]> By: Neolex AB http://olex.openlogic.com/wazi/2009/create-open-source-policy/comment-page-1/#comment-445 Neolex AB Fri, 27 Feb 2009 12:35:27 +0000 http://olex.openlogic.com/wazi/?p=2288#comment-445 Indeed, a very good read for all us working with open source issues. We would also echo Gilles' comments regarding the use of automated tools for license audits. Indeed, a very good read for all us working with open source issues. We would also echo Gilles’ comments regarding the use of automated tools for license audits.

]]> By: Samuel http://olex.openlogic.com/wazi/2009/create-open-source-policy/comment-page-1/#comment-441 Samuel Thu, 26 Feb 2009 22:16:19 +0000 http://olex.openlogic.com/wazi/?p=2288#comment-441 Cher M. Broussard, I am entirely in agreement with you. Could you, please let me know what does EA stand for? Merci, Samuel Cher M. Broussard,
I am entirely in agreement with you.
Could you, please let me know what does EA stand for?

Merci,
Samuel

]]> By: Gilles Broussard http://olex.openlogic.com/wazi/2009/create-open-source-policy/comment-page-1/#comment-439 Gilles Broussard Thu, 26 Feb 2009 20:53:26 +0000 http://olex.openlogic.com/wazi/?p=2288#comment-439 Probably one of the best articles I have read on this subject. I am surprised you did not talk about automated tools (FOSSology, Protecode IP Analyzer and IP Assistant, Black Duck ProtexIP) that can help accelerate the process. In my company, we have found that defining the policy is important. Electronically capturing the policy and checking the licensing and copyright obligations against this policy thru an automated tool - we use EA - is essential to effectively deploy Open Source without increasing the development overhead. Probably one of the best articles I have read on this subject. I am surprised you did not talk about automated tools (FOSSology, Protecode IP Analyzer and IP Assistant, Black Duck ProtexIP) that can help accelerate the process. In my company, we have found that defining the policy is important. Electronically capturing the policy and checking the licensing and copyright obligations against this policy thru an automated tool – we use EA – is essential to effectively deploy Open Source without increasing the development overhead.

]]>