<?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: KDE Brainstorm Monthly Digest &#8211; issue 1</title>
	<atom:link href="http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/feed" rel="self" type="application/rss+xml" />
	<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1</link>
	<description>On the web since 1999</description>
	<lastBuildDate>Tue, 27 Jul 2010 23:23:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Alessandro Rossini</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11154</link>
		<dc:creator>Alessandro Rossini</dc:creator>
		<pubDate>Tue, 05 May 2009 14:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11154</guid>
		<description>Just a quick comment regarding the &quot;Payment/donation to get bugs fixed&quot; post. My name is Alessandro, not Alberto. :)

Best regards.</description>
		<content:encoded><![CDATA[<p>Just a quick comment regarding the &#8220;Payment/donation to get bugs fixed&#8221; post. My name is Alessandro, not Alberto. :)</p>
<p>Best regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheBlackCat</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11081</link>
		<dc:creator>TheBlackCat</dc:creator>
		<pubDate>Sun, 26 Apr 2009 16:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11081</guid>
		<description>I have a few suggestions for statistics.  

First, I would definitely not use a bar plot for the time series.  With a line it is much easier to see the connection between days than with a bar plot.  A stem/leaf plot might work, though, so I would try that out.  It is like a bar plot, but instead of wide bars it uses thin lines with a circle (or other shape) at the peak.  It is fairly easy for the eye to connect the dots into a curve but it does not look quite as jaggy as the line does.  I would also experiment with different time periods (6 hours, 12, hours, 1 day, 2 days, etc).  Perhaps post different combinations next month (or this month even) and let there be some discussion about what seems useful and what doesn&#039;t.  You can then narrow it down for future issues.

First, I think doing a 3 and/or 5-day sliding moving average would help smooth at some of those bumps (so that each day is actually the average of that day and the 1 or 2 days before or after).  This would not replace the time series, only complement it.

Second, I would have a histogram for the number of ideas for each user.  So for instance the number of users with 1 idea, the number of users with 2 ideas, the number of users with 3 ideas, etc.  That will tell us whether are dealing with a few users posting a lot of ideas or a lot of users posting a few ideas.

I would also post the number of ideas with each tag, at least for the top 10-20 most popular tags.

Posting a time series for comments on ideas would also be useful, to see how active discussion is and how it is changing over time.  Perhaps overlay it on the same plot as the time series for ideas, making comparison between the two.  You can have plots with two y-axes, one on the left and one on the right.  This would allow you to scale the two time series plots so they are similar in height even though their true range is very different.

Another interesting thing would be a plot with the number of comments on one axis and the number of positive votes on the other (a vote vs. comment count plot).  This would allow us to see whether commenting and voting are related, and if so in what way.  Perhaps with a correlation coefficient.  Same with comments vs. controversy.  

Having a histogram for the number of comments per idea (number of ideas with 0-5 comments, number of ideas with 5-10 comments, etc.) would be interesting.  So would a histogram for the votes and a histogram for the controversy.  Since there are far more votes and comments than there are ideas those would probably have to be broken into bins (number of ideas with 0-5 votes, 5-10 votes, etc).  

A pie chart representation of the ideas in each category, pending, implemented, done, etc., would be a good visual representation of that data.

The count of ideas for each of the top 5-20 most prolific forum members, the count of votes for the top 5-20 highest-rated ideas, and the controversy level for the top 5-20 most controversial ideas would also be interesting, along with links to those ideas.  You could also post the text of those 15-60 ideas at the end, like how the commit digest posts the labels for commits at the end.

Those are all the potentially interesting ideas I can come up with right now.  I will post more if they come to me.</description>
		<content:encoded><![CDATA[<p>I have a few suggestions for statistics.  </p>
<p>First, I would definitely not use a bar plot for the time series.  With a line it is much easier to see the connection between days than with a bar plot.  A stem/leaf plot might work, though, so I would try that out.  It is like a bar plot, but instead of wide bars it uses thin lines with a circle (or other shape) at the peak.  It is fairly easy for the eye to connect the dots into a curve but it does not look quite as jaggy as the line does.  I would also experiment with different time periods (6 hours, 12, hours, 1 day, 2 days, etc).  Perhaps post different combinations next month (or this month even) and let there be some discussion about what seems useful and what doesn&#8217;t.  You can then narrow it down for future issues.</p>
<p>First, I think doing a 3 and/or 5-day sliding moving average would help smooth at some of those bumps (so that each day is actually the average of that day and the 1 or 2 days before or after).  This would not replace the time series, only complement it.</p>
<p>Second, I would have a histogram for the number of ideas for each user.  So for instance the number of users with 1 idea, the number of users with 2 ideas, the number of users with 3 ideas, etc.  That will tell us whether are dealing with a few users posting a lot of ideas or a lot of users posting a few ideas.</p>
<p>I would also post the number of ideas with each tag, at least for the top 10-20 most popular tags.</p>
<p>Posting a time series for comments on ideas would also be useful, to see how active discussion is and how it is changing over time.  Perhaps overlay it on the same plot as the time series for ideas, making comparison between the two.  You can have plots with two y-axes, one on the left and one on the right.  This would allow you to scale the two time series plots so they are similar in height even though their true range is very different.</p>
<p>Another interesting thing would be a plot with the number of comments on one axis and the number of positive votes on the other (a vote vs. comment count plot).  This would allow us to see whether commenting and voting are related, and if so in what way.  Perhaps with a correlation coefficient.  Same with comments vs. controversy.  </p>
<p>Having a histogram for the number of comments per idea (number of ideas with 0-5 comments, number of ideas with 5-10 comments, etc.) would be interesting.  So would a histogram for the votes and a histogram for the controversy.  Since there are far more votes and comments than there are ideas those would probably have to be broken into bins (number of ideas with 0-5 votes, 5-10 votes, etc).  </p>
<p>A pie chart representation of the ideas in each category, pending, implemented, done, etc., would be a good visual representation of that data.</p>
<p>The count of ideas for each of the top 5-20 most prolific forum members, the count of votes for the top 5-20 highest-rated ideas, and the controversy level for the top 5-20 most controversial ideas would also be interesting, along with links to those ideas.  You could also post the text of those 15-60 ideas at the end, like how the commit digest posts the labels for commits at the end.</p>
<p>Those are all the potentially interesting ideas I can come up with right now.  I will post more if they come to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Einar</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11080</link>
		<dc:creator>Einar</dc:creator>
		<pubDate>Sun, 26 Apr 2009 07:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11080</guid>
		<description>@Grósz Dániel : Brainstorm is meant to be a &quot;filter&quot; for BKO with regards to wishlists items (that&#039;s why reporting in both places at once is not a good idea), because there can be user partecipation (voting) and even discussion to improve a particular idea. 
After discussion and voting, the requests are forwarded to BKO. The advantage is that by voting we group similar requests to a single one (= less duplication) and overall good quality requests are submitted. So I would not submit to Brainstorm and BKO together at the same time.</description>
		<content:encoded><![CDATA[<p>@Grósz Dániel : Brainstorm is meant to be a &#8220;filter&#8221; for BKO with regards to wishlists items (that&#8217;s why reporting in both places at once is not a good idea), because there can be user partecipation (voting) and even discussion to improve a particular idea.<br />
After discussion and voting, the requests are forwarded to BKO. The advantage is that by voting we group similar requests to a single one (= less duplication) and overall good quality requests are submitted. So I would not submit to Brainstorm and BKO together at the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grósz Dániel</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11079</link>
		<dc:creator>Grósz Dániel</dc:creator>
		<pubDate>Sun, 26 Apr 2009 00:08:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11079</guid>
		<description>What is the relation of KDE brainstorm and bugs.kde.org wishes? If I have an idea/proposal, where should I report it (or in both places)?</description>
		<content:encoded><![CDATA[<p>What is the relation of KDE brainstorm and bugs.kde.org wishes? If I have an idea/proposal, where should I report it (or in both places)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans (aka Mogger ;)</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11076</link>
		<dc:creator>Hans (aka Mogger ;)</dc:creator>
		<pubDate>Sat, 25 Apr 2009 19:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11076</guid>
		<description>This rocks! And it&#039;s only going to get better as we get more statistic to play with.

Regarding the graph, I like the line graph - it shows a trend, the relationship between time and number of ideas. I don&#039;t know which type is the &quot;right&quot; one, but that&#039;s what I personally think.</description>
		<content:encoded><![CDATA[<p>This rocks! And it&#8217;s only going to get better as we get more statistic to play with.</p>
<p>Regarding the graph, I like the line graph &#8211; it shows a trend, the relationship between time and number of ideas. I don&#8217;t know which type is the &#8220;right&#8221; one, but that&#8217;s what I personally think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Einar</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11075</link>
		<dc:creator>Einar</dc:creator>
		<pubDate>Sat, 25 Apr 2009 19:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11075</guid>
		<description>@dim: I tried a couple different solutions, then I stumbled upon a SciPy toolkit for time series, which is what I used to plot this figure. I&#039;ll investigate whether I can use other means to plot those (probably yes).</description>
		<content:encoded><![CDATA[<p>@dim: I tried a couple different solutions, then I stumbled upon a SciPy toolkit for time series, which is what I used to plot this figure. I&#8217;ll investigate whether I can use other means to plot those (probably yes).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dim</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11074</link>
		<dc:creator>dim</dc:creator>
		<pubDate>Sat, 25 Apr 2009 18:23:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11074</guid>
		<description>Really great idea! I like it :)

There is one proposal for presenting number of votes per day - because they are discrete numbers spread over discrete timeline, you should display votes through histogram with constant bar width with no space beetwen them. One such chart can be found on 2nd page of document at:

http://www.cdc.gov/healthyyouth/evaluation/pdf/brief12.pdf

Keep on rocking with KDE ;)</description>
		<content:encoded><![CDATA[<p>Really great idea! I like it :)</p>
<p>There is one proposal for presenting number of votes per day &#8211; because they are discrete numbers spread over discrete timeline, you should display votes through histogram with constant bar width with no space beetwen them. One such chart can be found on 2nd page of document at:</p>
<p><a href="http://www.cdc.gov/healthyyouth/evaluation/pdf/brief12.pdf" rel="nofollow">http://www.cdc.gov/healthyyouth/evaluation/pdf/brief12.pdf</a></p>
<p>Keep on rocking with KDE ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mannequinZOD</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11073</link>
		<dc:creator>mannequinZOD</dc:creator>
		<pubDate>Sat, 25 Apr 2009 15:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11073</guid>
		<description>Please post it on the dot, it is dot worthy material and of interest to the community</description>
		<content:encoded><![CDATA[<p>Please post it on the dot, it is dot worthy material and of interest to the community</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Konstantinos Smanis</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11072</link>
		<dc:creator>Konstantinos Smanis</dc:creator>
		<pubDate>Sat, 25 Apr 2009 12:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11072</guid>
		<description>+1 for the monthly digests of KDE Brainstorm.

Thumbs up!</description>
		<content:encoded><![CDATA[<p>+1 for the monthly digests of KDE Brainstorm.</p>
<p>Thumbs up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Einar</title>
		<link>http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1/comment-page-1#comment-11071</link>
		<dc:creator>Einar</dc:creator>
		<pubDate>Sat, 25 Apr 2009 11:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennogumi.org/2009/04/kde-brainstorm-monthly-digest-issue-1#comment-11071</guid>
		<description>@Ivan: perhaps next month, as I said it&#039;s a work in progress. But putting up a mockup or the text of the most voted idea is definitely a plus. I may try to edit the digest later on if I get time.

@aki For now I&#039;d like to see the reactions first. I&#039;m still not sure it&#039;s Dot-worthy material.

@all: thanks a lot!</description>
		<content:encoded><![CDATA[<p>@Ivan: perhaps next month, as I said it&#8217;s a work in progress. But putting up a mockup or the text of the most voted idea is definitely a plus. I may try to edit the digest later on if I get time.</p>
<p>@aki For now I&#8217;d like to see the reactions first. I&#8217;m still not sure it&#8217;s Dot-worthy material.</p>
<p>@all: thanks a lot!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
