<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Community inertia in Debian and Ubuntu</title>
	<atom:link href="http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/</link>
	<description>a potpourri of mirth and madness</description>
	<lastBuildDate>Mon, 23 Jan 2012 03:06:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: nona</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1407</link>
		<dc:creator><![CDATA[nona]]></dc:creator>
		<pubDate>Fri, 31 Jul 2009 03:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1407</guid>
		<description><![CDATA[While I love Debian and apt/dpkg, it would be nice if apt/dpkg was turned into something of a git/conary/zeroinstall-like thing (for source and binaries), so that (temporarily) forking, merging and maintaining &quot;partially overlapping&quot; distros would be easier. I suspect it would allow for a lot more experimentation and faster integration.

I&#039;ve been quite happy with my Debian setups, but I&#039;ve found myself lusting after some of the concepts in Foresight (Conary), NixOS, ZeroInstall etc.]]></description>
		<content:encoded><![CDATA[<p>While I love Debian and apt/dpkg, it would be nice if apt/dpkg was turned into something of a git/conary/zeroinstall-like thing (for source and binaries), so that (temporarily) forking, merging and maintaining &#8220;partially overlapping&#8221; distros would be easier. I suspect it would allow for a lot more experimentation and faster integration.</p>
<p>I&#8217;ve been quite happy with my Debian setups, but I&#8217;ve found myself lusting after some of the concepts in Foresight (Conary), NixOS, ZeroInstall etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yannick</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1406</link>
		<dc:creator><![CDATA[Yannick]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 22:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1406</guid>
		<description><![CDATA[You can&#039;t say that experimental is rarely used.

  $ apt-show-versions &#124; grep experimental &#124; wc -l
  429

It&#039;s the KDE 4.3RC effect. ;-)

Furthermore, experimental is not a distribution, it&#039;s only an additional repository. What I meant was more (in the Ubuntu style):

Alice and her friends want to work on multiarch. They create an unstable-multiarch branch were they implement it and can see what it breaks in the distribution.

Frank and his friends want to work on KMS and create and unstable-kms branch.

Frank&#039;s branch and Alice&#039;s one are distinct so the work of each team does not bother the other (and users can participate using the branched distributions).]]></description>
		<content:encoded><![CDATA[<p>You can&#8217;t say that experimental is rarely used.</p>
<p>  $ apt-show-versions | grep experimental | wc -l<br />
  429</p>
<p>It&#8217;s the KDE 4.3RC effect. ;-)</p>
<p>Furthermore, experimental is not a distribution, it&#8217;s only an additional repository. What I meant was more (in the Ubuntu style):</p>
<p>Alice and her friends want to work on multiarch. They create an unstable-multiarch branch were they implement it and can see what it breaks in the distribution.</p>
<p>Frank and his friends want to work on KMS and create and unstable-kms branch.</p>
<p>Frank&#8217;s branch and Alice&#8217;s one are distinct so the work of each team does not bother the other (and users can participate using the branched distributions).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mdz</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1396</link>
		<dc:creator><![CDATA[mdz]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 13:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1396</guid>
		<description><![CDATA[You make a very good point.  Most Debian developers use sid/unstable as their daily working environment, and this means that they value its stability very highly.  This contributes to the inertia which needs to be overcome in order to make a major change.

If a Debian developer breaks something in unstable, this can make their fellow developers unproductive and slow down the whole project.

Debian has an &quot;experimental&quot; repository which is similar to what you describe, but it is rarely utilized, often misunderstood and has some technical shortcomings.]]></description>
		<content:encoded><![CDATA[<p>You make a very good point.  Most Debian developers use sid/unstable as their daily working environment, and this means that they value its stability very highly.  This contributes to the inertia which needs to be overcome in order to make a major change.</p>
<p>If a Debian developer breaks something in unstable, this can make their fellow developers unproductive and slow down the whole project.</p>
<p>Debian has an &#8220;experimental&#8221; repository which is similar to what you describe, but it is rarely utilized, often misunderstood and has some technical shortcomings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yannick</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1394</link>
		<dc:creator><![CDATA[Yannick]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 12:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1394</guid>
		<description><![CDATA[Matt, there&#039;s one point you missed, or at least it&#039;s not explicit enough.

One big strength of Debian, IMHO, is the rolling release aspect of Sid. I&#039;ve been using Sid for nearly ten year with only one major glitch (as far as I can remember).

The &quot;resistance to change&quot; you describe and the careful, painful (for DD) and long transitions are what make Unstable so… stable.

At the opposite, development version of Ubuntu (that I test regularly) is often broken. It&#039;s not a critic per se, it&#039;s what permits big changes.

The idea of distribution branches (no ig, Unstable, Testing and Stable are not branches in the sense of source branches) is very interesting.

It would be cool if developers could make a branch of Unstable to test new features. A bit like Ubuntu&#039;s PPA but at the distribution level. This would lead to a &quot;broken branch&quot; were fix could be done before new feature would merge back to unstable.

The problem is that it would ask time and effort from developers and, more important I think, infrastructure for the Debian project.

Yannick]]></description>
		<content:encoded><![CDATA[<p>Matt, there&#8217;s one point you missed, or at least it&#8217;s not explicit enough.</p>
<p>One big strength of Debian, IMHO, is the rolling release aspect of Sid. I&#8217;ve been using Sid for nearly ten year with only one major glitch (as far as I can remember).</p>
<p>The &#8220;resistance to change&#8221; you describe and the careful, painful (for DD) and long transitions are what make Unstable so… stable.</p>
<p>At the opposite, development version of Ubuntu (that I test regularly) is often broken. It&#8217;s not a critic per se, it&#8217;s what permits big changes.</p>
<p>The idea of distribution branches (no ig, Unstable, Testing and Stable are not branches in the sense of source branches) is very interesting.</p>
<p>It would be cool if developers could make a branch of Unstable to test new features. A bit like Ubuntu&#8217;s PPA but at the distribution level. This would lead to a &#8220;broken branch&#8221; were fix could be done before new feature would merge back to unstable.</p>
<p>The problem is that it would ask time and effort from developers and, more important I think, infrastructure for the Debian project.</p>
<p>Yannick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jg</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1377</link>
		<dc:creator><![CDATA[jg]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 19:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1377</guid>
		<description><![CDATA[&quot;a troublesome pattern which was pointed out by Debian developers at DebConf&quot;

I don&#039;t know who these supposed Debian devs are (ie, whether they&#039;re really Ubuntu devs who consider themselves also debian devs simply because they&#039;re at DebConf, or whether they&#039;re officially maintaining any debian packages), nor what percentage of the debian dev community they comprise. Yes, I do know that there are a number of debian devs who would like to see some things change/improve in debian&#039;s infrastructure (but mostly in regards to faster approval for new dev assignments, less personal flame wars on the mailing list, or other such &quot;social&quot; things. I haven&#039;t heard many clamoring for adding additional &quot;branches&quot; to debian&#039;s existing 3 official branches. I&#039;m sure there are some folks doing that, but not enough to warrant consideration of the dangerously counterproductive suggestions you&#039;ve made).

But here&#039;s the bottom line: Debian&#039;s infrastructure is _already much better_ than Ubuntu&#039;s. The former produces more software, more upstream support, more kernel contributions, a distro with much wider platform support, a more stable, faster performing distro, a more customizable distro, a distro that is more trusted and utilized in businesses, etc. It&#039;s also a community that is much more transparent (to the point that it can&#039;t stifle dissenting viewpoints even if the &quot;big cheese&quot; wanted to). Contrast that with, as just one example, Ubuntu devs censorship of objections to Canonical&#039;s self-serving, hypocritical commercial use of the Ubuntu name in its commercial Ubuntu One service. There is no accountability nor transparency in the Ubuntu community. There are only people who have the power to stifle opposing viewpoints, and do so.

You need to stop talking about what Debian&#039;s community and infrastructure should be doing, because it&#039;s _already_ way better than Ubuntu&#039;s alternative, and instead spend your time fixing all of the much-worse-problems with Ubuntu&#039;s development and community.

And that&#039;s the bottom line.

&quot;attribute your comments to some meaningful identity, such as your real name&quot;

Why, so you can change the subject to talking about me instead of the merits (or rather, lack of merits) of what you say about Debian in your blogs?

That&#039;s the sort of stuff I&#039;ve come to expect from the Ubuntu community. Typical.

If you&#039;re &quot;at a disadvantage&quot;, why don&#039;t you just employ the usual Ubuntu way of handling that -- just censor my reply, pretend that the Ubuntu way is still the best, and continue to dole out &quot;helpful&quot; advice about how the other distro communities can learn something from Ubuntu (as if they should be using it as something other than an example of how _not_ to be as useful a distro to the Linux community as Debian is).]]></description>
		<content:encoded><![CDATA[<p>&#8220;a troublesome pattern which was pointed out by Debian developers at DebConf&#8221;</p>
<p>I don&#8217;t know who these supposed Debian devs are (ie, whether they&#8217;re really Ubuntu devs who consider themselves also debian devs simply because they&#8217;re at DebConf, or whether they&#8217;re officially maintaining any debian packages), nor what percentage of the debian dev community they comprise. Yes, I do know that there are a number of debian devs who would like to see some things change/improve in debian&#8217;s infrastructure (but mostly in regards to faster approval for new dev assignments, less personal flame wars on the mailing list, or other such &#8220;social&#8221; things. I haven&#8217;t heard many clamoring for adding additional &#8220;branches&#8221; to debian&#8217;s existing 3 official branches. I&#8217;m sure there are some folks doing that, but not enough to warrant consideration of the dangerously counterproductive suggestions you&#8217;ve made).</p>
<p>But here&#8217;s the bottom line: Debian&#8217;s infrastructure is _already much better_ than Ubuntu&#8217;s. The former produces more software, more upstream support, more kernel contributions, a distro with much wider platform support, a more stable, faster performing distro, a more customizable distro, a distro that is more trusted and utilized in businesses, etc. It&#8217;s also a community that is much more transparent (to the point that it can&#8217;t stifle dissenting viewpoints even if the &#8220;big cheese&#8221; wanted to). Contrast that with, as just one example, Ubuntu devs censorship of objections to Canonical&#8217;s self-serving, hypocritical commercial use of the Ubuntu name in its commercial Ubuntu One service. There is no accountability nor transparency in the Ubuntu community. There are only people who have the power to stifle opposing viewpoints, and do so.</p>
<p>You need to stop talking about what Debian&#8217;s community and infrastructure should be doing, because it&#8217;s _already_ way better than Ubuntu&#8217;s alternative, and instead spend your time fixing all of the much-worse-problems with Ubuntu&#8217;s development and community.</p>
<p>And that&#8217;s the bottom line.</p>
<p>&#8220;attribute your comments to some meaningful identity, such as your real name&#8221;</p>
<p>Why, so you can change the subject to talking about me instead of the merits (or rather, lack of merits) of what you say about Debian in your blogs?</p>
<p>That&#8217;s the sort of stuff I&#8217;ve come to expect from the Ubuntu community. Typical.</p>
<p>If you&#8217;re &#8220;at a disadvantage&#8221;, why don&#8217;t you just employ the usual Ubuntu way of handling that &#8212; just censor my reply, pretend that the Ubuntu way is still the best, and continue to dole out &#8220;helpful&#8221; advice about how the other distro communities can learn something from Ubuntu (as if they should be using it as something other than an example of how _not_ to be as useful a distro to the Linux community as Debian is).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Community inertia in Debian and Ubuntu &#124; Debian-News.net - Your one stop for news about Debian</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1376</link>
		<dc:creator><![CDATA[Community inertia in Debian and Ubuntu &#124; Debian-News.net - Your one stop for news about Debian]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 17:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1376</guid>
		<description><![CDATA[[...] had required about six years of “thinking” and two months of actual development&#8230; More here  Debian is a good example of a large open source project with well established patterns of work. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] had required about six years of “thinking” and two months of actual development&#8230; More here  Debian is a good example of a large open source project with well established patterns of work. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Community inertia in Debian and Ubuntu &#124; Ubuntu-News - Your one stop for news about Ubuntu</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1375</link>
		<dc:creator><![CDATA[Community inertia in Debian and Ubuntu &#124; Ubuntu-News - Your one stop for news about Ubuntu]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 17:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1375</guid>
		<description><![CDATA[[...] had required about six years of “thinking” and two months of actual development&#8230; More here  Debian is a good example of a large open source project with well established patterns of work. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] had required about six years of “thinking” and two months of actual development&#8230; More here  Debian is a good example of a large open source project with well established patterns of work. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: effiejayx</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1374</link>
		<dc:creator><![CDATA[effiejayx]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 15:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1374</guid>
		<description><![CDATA[I tend to agree with Matt the people on the sidelines are the ones making all the fuzz.

day to day we see colaboration happen and that&#039;s the ways it should be. we need more of that perhaps but let us keep on working on behalf of what these project stand for.

There will always be naysayers and what not but it is up to us to keep the work going regardless of all the adversities.]]></description>
		<content:encoded><![CDATA[<p>I tend to agree with Matt the people on the sidelines are the ones making all the fuzz.</p>
<p>day to day we see colaboration happen and that&#8217;s the ways it should be. we need more of that perhaps but let us keep on working on behalf of what these project stand for.</p>
<p>There will always be naysayers and what not but it is up to us to keep the work going regardless of all the adversities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Carter</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1372</link>
		<dc:creator><![CDATA[Jonathan Carter]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 14:20:48 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1372</guid>
		<description><![CDATA[How is it possibly more of a fork than a branch? I can&#039;t think of any other Debian derivative that works as much as a branch than Ubuntu does. The Ubuntu team has worked hard from early days to try to make sure that it doesn&#039;t become a fork and that it plays well within the Debian eco-system.]]></description>
		<content:encoded><![CDATA[<p>How is it possibly more of a fork than a branch? I can&#8217;t think of any other Debian derivative that works as much as a branch than Ubuntu does. The Ubuntu team has worked hard from early days to try to make sure that it doesn&#8217;t become a fork and that it plays well within the Debian eco-system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: foo</title>
		<link>http://mdzlog.alcor.net/2009/07/27/community-inertia-in-debian-and-ubuntu/#comment-1371</link>
		<dc:creator><![CDATA[foo]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 13:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.alcor.net/?p=542#comment-1371</guid>
		<description><![CDATA[Ubuntu is more of a fork than a branch. I don&#039;t see a plan for merging Ubuntu into Debian and then closing up shop.]]></description>
		<content:encoded><![CDATA[<p>Ubuntu is more of a fork than a branch. I don&#8217;t see a plan for merging Ubuntu into Debian and then closing up shop.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

