﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Matt Ellis commented on Releasing Open Source</title><description>And you wonder why Microsoft doesn't use/support/release OSS? Why corporations don't want to use OSS?
  
  
Shipping is a feature.
  
</description><link>http://ayende.com/2991/releasing-open-source#comment10</link><guid>http://ayende.com/2991/releasing-open-source#comment10</guid><pubDate>Mon, 03 Dec 2007 09:42:47 GMT</pubDate></item><item><title>Steve commented on Releasing Open Source</title><description>Ok, I posted while you posted above.
  
  
Thanks - I will go read what Apache says about those guarantees
</description><link>http://ayende.com/2991/releasing-open-source#comment9</link><guid>http://ayende.com/2991/releasing-open-source#comment9</guid><pubDate>Sun, 02 Dec 2007 23:27:52 GMT</pubDate></item><item><title>Steve commented on Releasing Open Source</title><description>For me it means:  it's stable enough to be used in production.  A release candidate to me means it is not suitable for a production environment and you are at your own risk.
  
  
I see one as saying 'we are confident this is production ready software'.
  
  
As long as Castle remains in 'RC' mode, it isn't suitable for use in a production, enterprise environment.  Others might differ in this opinion, but I will say, it makes it hard to justify using the software 
  
  
</description><link>http://ayende.com/2991/releasing-open-source#comment8</link><guid>http://ayende.com/2991/releasing-open-source#comment8</guid><pubDate>Sun, 02 Dec 2007 23:26:33 GMT</pubDate></item><item><title>Ayende Rahien commented on Releasing Open Source</title><description>Steve,
  
The Castle project follows the Apache principals, which means that 1.0 meas that we are making certain guarantees to the communities.
</description><link>http://ayende.com/2991/releasing-open-source#comment7</link><guid>http://ayende.com/2991/releasing-open-source#comment7</guid><pubDate>Sun, 02 Dec 2007 23:25:34 GMT</pubDate></item><item><title>Steve commented on Releasing Open Source</title><description>What is the difference in open source software of 'Release Candidate' and 'Version 1'
  
  
?
  
  
</description><link>http://ayende.com/2991/releasing-open-source#comment6</link><guid>http://ayende.com/2991/releasing-open-source#comment6</guid><pubDate>Sun, 02 Dec 2007 23:23:26 GMT</pubDate></item><item><title>Chad Myers commented on Releasing Open Source</title><description>@Ayende: But why is the release of known-good code hinged upon the documentation?  documentation should not be among release criteria, that's what I'm saying. Documentation can happen along the way, during, and after the release.
  
  
Some people need it, some people don't but all who use the code need the code. Let the people who need the docs build the docs. Get corporate sponsorship to help with the docs, etc.
  
  
Right now, no corp entity wants to touch it because it's not 'released'. Once you release the code, people will adopt it, even without documentation. Some PHB might demand docs, but that's when you can suggest sponsoring the docs.
  
  
I just don't see why you can't have one without the other. It's holding back Castle, IMHO.
</description><link>http://ayende.com/2991/releasing-open-source#comment5</link><guid>http://ayende.com/2991/releasing-open-source#comment5</guid><pubDate>Sun, 02 Dec 2007 20:27:17 GMT</pubDate></item><item><title>Ayende Rahien commented on Releasing Open Source</title><description>Chad,
  
We do.
  
The documentation for Castle &amp; NHibernate is check into the source files, and we accept documentation patches.
  
  
The main issue is that documentation is _not_ a popular topic. And as such, it is not making a lot of friends.
  
</description><link>http://ayende.com/2991/releasing-open-source#comment4</link><guid>http://ayende.com/2991/releasing-open-source#comment4</guid><pubDate>Sun, 02 Dec 2007 19:23:51 GMT</pubDate></item><item><title>Anonymous Coward commented on Releasing Open Source</title><description>http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html
</description><link>http://ayende.com/2991/releasing-open-source#comment3</link><guid>http://ayende.com/2991/releasing-open-source#comment3</guid><pubDate>Sun, 02 Dec 2007 15:40:58 GMT</pubDate></item><item><title>Chad Myers commented on Releasing Open Source</title><description>But what I don't get is that this is OPEN SOURCE... the code is open for anyone to contribute, but for some reason and release and documentation and package preparation is still done like a corporation.
  
  
Why can't they say, "This code is a release-worthy build. We're going to move onto the next version. We're not calling it an 'Official Release' yet because there is no/little documentation. If you want us to call it an 'Official Release', here is a Wiki page of topics that need documentation. Please get started right away!"
  
  
Why not treat the documentation as an open source project itself?
</description><link>http://ayende.com/2991/releasing-open-source#comment2</link><guid>http://ayende.com/2991/releasing-open-source#comment2</guid><pubDate>Sun, 02 Dec 2007 14:36:47 GMT</pubDate></item><item><title>Jim Bolla commented on Releasing Open Source</title><description>Exactly. OSS works because developers like solving interesting problems. Writing documentation is the opposite of an interesting problem. :-)
</description><link>http://ayende.com/2991/releasing-open-source#comment1</link><guid>http://ayende.com/2991/releasing-open-source#comment1</guid><pubDate>Sun, 02 Dec 2007 13:30:47 GMT</pubDate></item></channel></rss>