<?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"
	>
<channel>
	<title>Comments on: Not with a bang, but a whimper</title>
	<atom:link href="http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/</link>
	<description>A blog about open source and security and open source security</description>
	<pubDate>Sat, 05 Jul 2008 15:49:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: links for 2008-05-06 &#124; Paranoid</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3475</link>
		<dc:creator>links for 2008-05-06 &#124; Paranoid</dc:creator>
		<pubDate>Tue, 06 May 2008 12:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3475</guid>
		<description>[...] Open Source Security » Blog Archive » Not with a bang, but a whimper Linus gets more patches while he is brushing his teeth than OpenSolaris gets in a week.???? (tags: open-solaris linux) [...]</description>
		<content:encoded><![CDATA[<p>[...] Open Source Security » Blog Archive » Not with a bang, but a whimper Linus gets more patches while he is brushing his teeth than OpenSolaris gets in a week.???? (tags: open-solaris linux) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Have you ever kissed a girl? &#187; Snoopy&#8217;s Home</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3468</link>
		<dc:creator>Have you ever kissed a girl? &#187; Snoopy&#8217;s Home</dc:creator>
		<pubDate>Sun, 04 May 2008 01:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3468</guid>
		<description>[...] source camp, instead it&#8217;s more like they just want to take some advantage. OpenSolaris is slow in development progress, and there are complains. For MySQL, they announed some of the new features [...]</description>
		<content:encoded><![CDATA[<p>[...] source camp, instead it&#8217;s more like they just want to take some advantage. OpenSolaris is slow in development progress, and there are complains. For MySQL, they announed some of the new features [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thoughts by Ted &#187; Blog Archive &#187; What Sun was trying to do with Open Solaris</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3467</link>
		<dc:creator>Thoughts by Ted &#187; Blog Archive &#187; What Sun was trying to do with Open Solaris</dc:creator>
		<pubDate>Wed, 23 Apr 2008 14:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3467</guid>
		<description>[...] So that explains why it&#8217;s take three long years to try to get basic open source development tools (such as putting Open Solaris source code in a distributed SCM located outside of the Sun firewall) for Open Solaris. It was never was Sun&#8217;s intention to try to promote a kernel engineering community, or at least, it was certainly not a high priority for them to do so. This can be shown by the fact that as of this writing they still are using the incredibly clunky requestor/sponsor system for getting patches into Solaris; setting up a git or mercurial servier is not rocket science. This lack is why Linux gets more contributions while brushing his teeth than Open Solaris gets in a week. [...]</description>
		<content:encoded><![CDATA[<p>[...] So that explains why it&#8217;s take three long years to try to get basic open source development tools (such as putting Open Solaris source code in a distributed SCM located outside of the Sun firewall) for Open Solaris. It was never was Sun&#8217;s intention to try to promote a kernel engineering community, or at least, it was certainly not a high priority for them to do so. This can be shown by the fact that as of this writing they still are using the incredibly clunky requestor/sponsor system for getting patches into Solaris; setting up a git or mercurial servier is not rocket science. This lack is why Linux gets more contributions while brushing his teeth than Open Solaris gets in a week. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Phipps</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3273</link>
		<dc:creator>Simon Phipps</dc:creator>
		<pubDate>Thu, 28 Feb 2008 15:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3273</guid>
		<description>&#62; previous versions of documents (SCA and roadmap) just disappearing, 


Just so you know, I have now made sure that all previous versions of the SCA are available at http://www.sun.com/software/opensource/contributor_agreement.jsp</description>
		<content:encoded><![CDATA[<p>&gt; previous versions of documents (SCA and roadmap) just disappearing, </p>
<p>Just so you know, I have now made sure that all previous versions of the SCA are available at <a href="http://www.sun.com/software/opensource/contributor_agreement.jsp" rel="nofollow">http://www.sun.com/software/opensource/contributor_agreement.jsp</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Watching the ripples &#187; Untangled</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3258</link>
		<dc:creator>Watching the ripples &#187; Untangled</dc:creator>
		<pubDate>Thu, 21 Feb 2008 21:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3258</guid>
		<description>[...] sense that anything would change. There were a few blog mentions from people outside the community (Emily Ratliff on the 14th, rippling to Michael Dolan on the 15th, which in turn rippled to Jim Grisanzio on the [...]</description>
		<content:encoded><![CDATA[<p>[...] sense that anything would change. There were a few blog mentions from people outside the community (Emily Ratliff on the 14th, rippling to Michael Dolan on the 15th, which in turn rippled to Jim Grisanzio on the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Comay</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3243</link>
		<dc:creator>David Comay</dc:creator>
		<pubDate>Wed, 20 Feb 2008 06:35:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3243</guid>
		<description>Emily, as Simon says I believe it's up to each facility.  At the Silicon Valley OpenSolaris group meeting, which does meet at a Sun facility in Santa Clara, there is no NDA required to be signed.  In fact, the last couple times I attended there was no formal sign in at all.

I don't know how long the transition will take - I could make excuses as to why it's taken so long but I'm sure you don't want to hear those.  Instead, I believe that substantial progrss has been made on a number of fronts.  I believe the primary Merucurial repository will be out in the next several months along with at least one of the other consolidations.  All of the work for the Indiana project is already being done completely out in the open and there are a number of outside contributors integrating changes directly with any sponsor.  And there has finally been progress on a bug tracking system, something which has been tricky since Sun has its own internal bug system which is used for previous versions of Solaris and coordinating those will require an effort.

If you look at the mail archives for opensolaris-arc@opensolaris.org, you'll see the architectural review for almost all of the work being done for OpenSolaris is completely out in the open (yes, there are still an occasional closed case but those either are due to clerical mistake or for the rare but real proprietary case.)

Perhaps it's a difference in seeing things as being half-full versus half-empty.  I'm as frustrated as anyone that certain things have taken as long as they have but I believe strongly that there will be significant improvements seen on a number of fronts this year.</description>
		<content:encoded><![CDATA[<p>Emily, as Simon says I believe it&#8217;s up to each facility.  At the Silicon Valley OpenSolaris group meeting, which does meet at a Sun facility in Santa Clara, there is no NDA required to be signed.  In fact, the last couple times I attended there was no formal sign in at all.</p>
<p>I don&#8217;t know how long the transition will take - I could make excuses as to why it&#8217;s taken so long but I&#8217;m sure you don&#8217;t want to hear those.  Instead, I believe that substantial progrss has been made on a number of fronts.  I believe the primary Merucurial repository will be out in the next several months along with at least one of the other consolidations.  All of the work for the Indiana project is already being done completely out in the open and there are a number of outside contributors integrating changes directly with any sponsor.  And there has finally been progress on a bug tracking system, something which has been tricky since Sun has its own internal bug system which is used for previous versions of Solaris and coordinating those will require an effort.</p>
<p>If you look at the mail archives for <a href="mailto:opensolaris-arc@opensolaris.org">opensolaris-arc@opensolaris.org</a>, you&#8217;ll see the architectural review for almost all of the work being done for OpenSolaris is completely out in the open (yes, there are still an occasional closed case but those either are due to clerical mistake or for the rare but real proprietary case.)</p>
<p>Perhaps it&#8217;s a difference in seeing things as being half-full versus half-empty.  I&#8217;m as frustrated as anyone that certain things have taken as long as they have but I believe strongly that there will be significant improvements seen on a number of fronts this year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily Ratliff</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3217</link>
		<dc:creator>Emily Ratliff</dc:creator>
		<pubDate>Mon, 18 Feb 2008 05:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3217</guid>
		<description>&gt; all corporations attempt to make visitors sign-in like this by default

Just to be clear, I am not objecting to signing in. I'm objecting to signing an NDA as part of the sign in procedure. I don't mind letting the company know my identity, I do mind being compelled to sign a legal agreement that says that I won't share anything confidential that I learn while on site. As it was explained to me by the receptionist, they were worried that attendees would glean confidential information from print-outs that might have been left laying around and thus wouldn't waive the NDA built in to the visitor's access application.

Emily</description>
		<content:encoded><![CDATA[<p>> all corporations attempt to make visitors sign-in like this by default</p>
<p>Just to be clear, I am not objecting to signing in. I&#8217;m objecting to signing an NDA as part of the sign in procedure. I don&#8217;t mind letting the company know my identity, I do mind being compelled to sign a legal agreement that says that I won&#8217;t share anything confidential that I learn while on site. As it was explained to me by the receptionist, they were worried that attendees would glean confidential information from print-outs that might have been left laying around and thus wouldn&#8217;t waive the NDA built in to the visitor&#8217;s access application.</p>
<p>Emily</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Phipps</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3214</link>
		<dc:creator>Simon Phipps</dc:creator>
		<pubDate>Mon, 18 Feb 2008 03:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3214</guid>
		<description>&#62; Shame on Google

As I recall, even IBM used to have the same requirements when we held BCS meetings at Hursley Park. That was over 8 years ago, but you should expect to see all corporations attempt to make visitors sign-in like this by default. I now assume it will be the case (wherever I am holding meetings, Sun or elsewhere) and negotiate it away or pick another venue.

&#62; Best of luck

Thank-you. There are many different approaches to open source and I think OpenSolaris can devise a path of its own.</description>
		<content:encoded><![CDATA[<p>&gt; Shame on Google</p>
<p>As I recall, even IBM used to have the same requirements when we held BCS meetings at Hursley Park. That was over 8 years ago, but you should expect to see all corporations attempt to make visitors sign-in like this by default. I now assume it will be the case (wherever I am holding meetings, Sun or elsewhere) and negotiate it away or pick another venue.</p>
<p>&gt; Best of luck</p>
<p>Thank-you. There are many different approaches to open source and I think OpenSolaris can devise a path of its own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily Ratliff</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3213</link>
		<dc:creator>Emily Ratliff</dc:creator>
		<pubDate>Mon, 18 Feb 2008 02:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3213</guid>
		<description>Hi Shawn and Simon,

I do draw a distinct difference in assigning the rights to a non-profit foundation versus a for-profit company.

As for the comment about wreckage, I meant that as my own characterization not as an indicator that I polled the OpenSolaris community and speak for them. I speak merely as an observer.

I have not returned. Shame on Google.

What percentage of the voters were Sun employees vs. non-Sun employees?

Best of luck to you both, if the OpenSolaris community has any chance of survival it will be due to your efforts.

Emily</description>
		<content:encoded><![CDATA[<p>Hi Shawn and Simon,</p>
<p>I do draw a distinct difference in assigning the rights to a non-profit foundation versus a for-profit company.</p>
<p>As for the comment about wreckage, I meant that as my own characterization not as an indicator that I polled the OpenSolaris community and speak for them. I speak merely as an observer.</p>
<p>I have not returned. Shame on Google.</p>
<p>What percentage of the voters were Sun employees vs. non-Sun employees?</p>
<p>Best of luck to you both, if the OpenSolaris community has any chance of survival it will be due to your efforts.</p>
<p>Emily</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Phipps</title>
		<link>http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3211</link>
		<dc:creator>Simon Phipps</dc:creator>
		<pubDate>Mon, 18 Feb 2008 00:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ratliff.net/blog/index.php/2008/02/14/not-with-a-bang-but-a-whimper/#comment-3211</guid>
		<description>Preamble:  Yes, it's a mess. As you note [5] I am trying to work out what to do next. Not to defend the mess, but I've comments on some of your portents of doom.

NDA:  I'm not sure it's fair to blame the User Group for lousy policies by their host, unless it was still in place second time around - have you returned? You have been very lucky not to encounter this common problem before - for example, Google had exactly the same requirement at their London office in Victoria when I attended a community meeting there recently.  As it turns out, the requirement is easily set aside at Sun premises and the Sun folks offering the premises to the User Group ought to have known - did you summon one of them?

Contrib Agreement:  Actually, this is a best-practice recommended by the FSF(1) and used by Red Hat, Novell, MySQL and many many others (even Apache has one). Sun's is the best there is in my view. You may not like it generically, but I fail to see why it's a sure-fire indicator of failure in this case.

OGB composition: The interim OGB that Sun selected was dominated by non-employees. The current composition reflects the voting by the membership rather than Sun's preference.

(1) http://www.softwarefreedom.org/resources/2008/foss-primer.html#x1-110002.3</description>
		<content:encoded><![CDATA[<p>Preamble:  Yes, it&#8217;s a mess. As you note [5] I am trying to work out what to do next. Not to defend the mess, but I&#8217;ve comments on some of your portents of doom.</p>
<p>NDA:  I&#8217;m not sure it&#8217;s fair to blame the User Group for lousy policies by their host, unless it was still in place second time around - have you returned? You have been very lucky not to encounter this common problem before - for example, Google had exactly the same requirement at their London office in Victoria when I attended a community meeting there recently.  As it turns out, the requirement is easily set aside at Sun premises and the Sun folks offering the premises to the User Group ought to have known - did you summon one of them?</p>
<p>Contrib Agreement:  Actually, this is a best-practice recommended by the FSF(1) and used by Red Hat, Novell, MySQL and many many others (even Apache has one). Sun&#8217;s is the best there is in my view. You may not like it generically, but I fail to see why it&#8217;s a sure-fire indicator of failure in this case.</p>
<p>OGB composition: The interim OGB that Sun selected was dominated by non-employees. The current composition reflects the voting by the membership rather than Sun&#8217;s preference.</p>
<p>(1) <a href="http://www.softwarefreedom.org/resources/2008/foss-primer.html#x1-110002.3" rel="nofollow">http://www.softwarefreedom.org/resources/2008/foss-primer.html#x1-110002.3</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
