<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: NASA :  Innovation and Collaboration</title>
	<atom:link href="http://www.opennasa.com/2008/09/29/nasa-innovation-and-collaboration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.opennasa.com/2008/09/29/nasa-innovation-and-collaboration/</link>
	<description>Your NASA, My NASA, OUR NASA</description>
	<lastBuildDate>Thu, 23 Jun 2011 16:14:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Courtney Graham/ HQ OGC</title>
		<link>http://www.opennasa.com/2008/09/29/nasa-innovation-and-collaboration/comment-page-1/#comment-7484</link>
		<dc:creator>Courtney Graham/ HQ OGC</dc:creator>
		<pubDate>Mon, 06 Oct 2008 16:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/2008/09/29/nasa-innovation-and-collaboration/#comment-7484</guid>
		<description>Try and make use of your local legal/patent counsel or CIO office for questions like this.  It doesn&#039;t appear that the people commenting on this site realize that there is a right answer and a lot of the legwork has already been done. Your patent counsel can usually point you in the right direction for questions like this (and your earlier question regarding distributing information about your program).

For example, NASA was one of the first government agencies to develop an OSI-approved open source license.  http://www.opensource.org/licenses/nasa1.3.php   

We are also wrapping up an agreement with SourceForge to facilitate deposit of source code by NASA engineers and our contractors for use by the open source community.  However, release of software to the community does require review prior to the release to ensure that NASA protects the intellectual property of its contractors and complies with ITAR and other regulations.  You can check with your  local IPP office - they are the software release authority for the agency.

If you want to publicly release NASA scientific and technical information, that may also need to be reviewed for intellectual property and ITAR issues before you release it - putting it into the STI database is a great way to ensure you have a static address if you want to post information on how to access it elsewhere.

Your local legal office should also be able to help you determine whether there are restrictions on what you would like to post - the current administration has placed a lot of limits on information that would have been fine to distribute just a few years ago.

Obviously, you personally are free to comment, post and share your personal view on your own time - all of my comments above apply when you are speaking for the agency or want to distribute information/software for NASA.  

If you have trouble finding this information, feel free to contact me directly - Courtney B. Graham in the HQ Office of General Counsel and I will help you find the right person.  I&#039;m in .X500.  

&quot;Follow me on Twitter: netlawyer&quot;

Courtney</description>
		<content:encoded><![CDATA[<p>Try and make use of your local legal/patent counsel or CIO office for questions like this.  It doesn&#8217;t appear that the people commenting on this site realize that there is a right answer and a lot of the legwork has already been done. Your patent counsel can usually point you in the right direction for questions like this (and your earlier question regarding distributing information about your program).</p>
<p>For example, NASA was one of the first government agencies to develop an OSI-approved open source license.  <a href="http://www.opensource.org/licenses/nasa1.3.php" rel="nofollow">http://www.opensource.org/licenses/nasa1.3.php</a>   </p>
<p>We are also wrapping up an agreement with SourceForge to facilitate deposit of source code by NASA engineers and our contractors for use by the open source community.  However, release of software to the community does require review prior to the release to ensure that NASA protects the intellectual property of its contractors and complies with ITAR and other regulations.  You can check with your  local IPP office &#8211; they are the software release authority for the agency.</p>
<p>If you want to publicly release NASA scientific and technical information, that may also need to be reviewed for intellectual property and ITAR issues before you release it &#8211; putting it into the STI database is a great way to ensure you have a static address if you want to post information on how to access it elsewhere.</p>
<p>Your local legal office should also be able to help you determine whether there are restrictions on what you would like to post &#8211; the current administration has placed a lot of limits on information that would have been fine to distribute just a few years ago.</p>
<p>Obviously, you personally are free to comment, post and share your personal view on your own time &#8211; all of my comments above apply when you are speaking for the agency or want to distribute information/software for NASA.  </p>
<p>If you have trouble finding this information, feel free to contact me directly &#8211; Courtney B. Graham in the HQ Office of General Counsel and I will help you find the right person.  I&#8217;m in .X500.  </p>
<p>&#8220;Follow me on Twitter: netlawyer&#8221;</p>
<p>Courtney</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander M Orlando</title>
		<link>http://www.opennasa.com/2008/09/29/nasa-innovation-and-collaboration/comment-page-1/#comment-7146</link>
		<dc:creator>Alexander M Orlando</dc:creator>
		<pubDate>Mon, 29 Sep 2008 10:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/2008/09/29/nasa-innovation-and-collaboration/#comment-7146</guid>
		<description>Hi Rolando

just got to your blog and it would be great to continue this conversation. Contact me so we can discuss.</description>
		<content:encoded><![CDATA[<p>Hi Rolando</p>
<p>just got to your blog and it would be great to continue this conversation. Contact me so we can discuss.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

