<?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: Possible Open Innovation Projects at NASA</title>
	<atom:link href="http://www.schingler.com/possible-open-innovation-projects-at-nasa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/</link>
	<description>conscious innovation</description>
	<lastBuildDate>Sun, 09 Oct 2011 05:41:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Rolando Quintanilla</title>
		<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/comment-page-1/#comment-117</link>
		<dc:creator>Rolando Quintanilla</dc:creator>
		<pubDate>Tue, 05 May 2009 01:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/?p=713#comment-117</guid>
		<description>You have some really good ideas Robbie.

&quot;Broadly speaking, for the last three decades NASA has changed its R&amp;D strategy  every 18 months. &quot;

Is that really true?  I am assuming that is an exaggeration, but then again :).

It does appear that NASA follows a mixture of strategies that in and of themselves would be good but because they are mixed don&#039;t work in practice.

One of the biggest hurdle to &quot;open&quot; in NASA is a Top-Down philosophy to management and the desire to hoard information.  That being stated, in general, I am not against the top-down approach (it has its place).  However, it can&#039;t be used when working with outside individuals and organizations who &quot;chose&quot; to work with NASA.  You can&#039;t &quot;control&quot; volunteers, it just won&#039;t fly.

Thanks for the post.  Hopefully someone who can do something about them reads your post.

RQ</description>
		<content:encoded><![CDATA[<p>You have some really good ideas Robbie.</p>
<p>&#8220;Broadly speaking, for the last three decades NASA has changed its R&#038;D strategy  every 18 months. &#8221;</p>
<p>Is that really true?  I am assuming that is an exaggeration, but then again <img src='http://www.schingler.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p>It does appear that NASA follows a mixture of strategies that in and of themselves would be good but because they are mixed don&#8217;t work in practice.</p>
<p>One of the biggest hurdle to &#8220;open&#8221; in NASA is a Top-Down philosophy to management and the desire to hoard information.  That being stated, in general, I am not against the top-down approach (it has its place).  However, it can&#8217;t be used when working with outside individuals and organizations who &#8220;chose&#8221; to work with NASA.  You can&#8217;t &#8220;control&#8221; volunteers, it just won&#8217;t fly.</p>
<p>Thanks for the post.  Hopefully someone who can do something about them reads your post.</p>
<p>RQ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Krage</title>
		<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/comment-page-1/#comment-119</link>
		<dc:creator>Joshua Krage</dc:creator>
		<pubDate>Fri, 01 May 2009 00:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/?p=713#comment-119</guid>
		<description>directory.nasa.gov is the web interface.  The other names are the LDAP interfaces.</description>
		<content:encoded><![CDATA[<p>directory.nasa.gov is the web interface.  The other names are the LDAP interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Krage</title>
		<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/comment-page-1/#comment-122</link>
		<dc:creator>Joshua Krage</dc:creator>
		<pubDate>Thu, 30 Apr 2009 05:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/?p=713#comment-122</guid>
		<description>pubdir isn&#039;t yet web-accessible.  LDAP queries (dc=nasa,dc=gov) work for the exposed fields.

Some of the insights from the CTO sesssion:
http://search.twitter.com/search?q=%23nasacto

If Spacebook is considered a success, and I have every expectation it will, then it is easy to scale up to Agency support (was a design consideration).  It uses eAuth authentication, which is spreading through most web applications.</description>
		<content:encoded><![CDATA[<p>pubdir isn&#8217;t yet web-accessible.  LDAP queries (dc=nasa,dc=gov) work for the exposed fields.</p>
<p>Some of the insights from the CTO sesssion:<br />
<a href="http://search.twitter.com/search?q=%23nasacto" rel="nofollow">http://search.twitter.com/search?q=%23nasacto</a></p>
<p>If Spacebook is considered a success, and I have every expectation it will, then it is easy to scale up to Agency support (was a design consideration).  It uses eAuth authentication, which is spreading through most web applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robbie Schingler</title>
		<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/comment-page-1/#comment-118</link>
		<dc:creator>Robbie Schingler</dc:creator>
		<pubDate>Thu, 30 Apr 2009 02:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/?p=713#comment-118</guid>
		<description>Hi BD - I have updated the post to include more links and spelling out the acronyms.  Please let me know which ones need further explanation; I look forward to your comments!

Joshua - I couldn&#039;t find the pub.nasa.gov websites you are referring to.  I have seen some SpaceBook wireframes and look forward to its success!  Do you know the future plans for SpaceBook to be Agency wide (or replicated for other Centers?).  Also, what is it written in, and is it forward compliant to active directory (for Single Sign On)?

In general, with any software project, I firmly believe to start small and see if people bite, then let your users tell you what they really want.  It would be great to see a group formed which incubates a series of small applications, but for now, I guess they are side projects.  The main point of the interactive x500 + side project app is to share my side projects with people, see others, find collaborators, and shelve some projects that are being duplicated elsewhere!

Also, I would love to see what the CTOs came up with.  Please pass along the information, or if you want to ask one of them to guest blog on opennasa.com, that would be even better!

--Robbie</description>
		<content:encoded><![CDATA[<p>Hi BD &#8211; I have updated the post to include more links and spelling out the acronyms.  Please let me know which ones need further explanation; I look forward to your comments!</p>
<p>Joshua &#8211; I couldn&#8217;t find the pub.nasa.gov websites you are referring to.  I have seen some SpaceBook wireframes and look forward to its success!  Do you know the future plans for SpaceBook to be Agency wide (or replicated for other Centers?).  Also, what is it written in, and is it forward compliant to active directory (for Single Sign On)?</p>
<p>In general, with any software project, I firmly believe to start small and see if people bite, then let your users tell you what they really want.  It would be great to see a group formed which incubates a series of small applications, but for now, I guess they are side projects.  The main point of the interactive x500 + side project app is to share my side projects with people, see others, find collaborators, and shelve some projects that are being duplicated elsewhere!</p>
<p>Also, I would love to see what the CTOs came up with.  Please pass along the information, or if you want to ask one of them to guest blog on opennasa.com, that would be even better!</p>
<p>&#8211;Robbie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Krage</title>
		<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/comment-page-1/#comment-120</link>
		<dc:creator>Joshua Krage</dc:creator>
		<pubDate>Wed, 29 Apr 2009 23:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/?p=713#comment-120</guid>
		<description>Center CTOs and other technology leaders met last week to discuss improving the innovation processes across NASA.  Interesting parallels in the discussion.

A partial answer to the X.500 item... dir.nasa.giv (internal) and pubdir.nasa.giv (public) provide much of the directory information you seek.  A couple of groups are experimenting with mobile apps to query the directory.  A project called Spacebook is being piloted at GSFC (just entered Beta) which probably covers the rest of the bullet.</description>
		<content:encoded><![CDATA[<p>Center CTOs and other technology leaders met last week to discuss improving the innovation processes across NASA.  Interesting parallels in the discussion.</p>
<p>A partial answer to the X.500 item&#8230; dir.nasa.giv (internal) and pubdir.nasa.giv (public) provide much of the directory information you seek.  A couple of groups are experimenting with mobile apps to query the directory.  A project called Spacebook is being piloted at GSFC (just entered Beta) which probably covers the rest of the bullet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BD</title>
		<link>http://www.schingler.com/possible-open-innovation-projects-at-nasa/comment-page-1/#comment-121</link>
		<dc:creator>BD</dc:creator>
		<pubDate>Wed, 29 Apr 2009 17:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.opennasa.com/?p=713#comment-121</guid>
		<description>For future reference and non-NASA readers (and even some NASA folks), you might want to consider spelling out or hyperlinking all acronyms the first time you use them. I&#039;ll give the rest of the substance consideration in due course.

/b</description>
		<content:encoded><![CDATA[<p>For future reference and non-NASA readers (and even some NASA folks), you might want to consider spelling out or hyperlinking all acronyms the first time you use them. I&#8217;ll give the rest of the substance consideration in due course.</p>
<p>/b</p>
]]></content:encoded>
	</item>
</channel>
</rss>

