<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<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>LeafLabs Garden &#187; Topic: new/old bugtracker up on google code</title>
		<link>http://forums.leaflabs.com/topic.php?id=511</link>
		<description>A place to share, learn, and grow...</description>
		<language>en-US</language>
		<pubDate>Fri, 22 Jan 2016 00:06:13 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://forums.leaflabs.com/search.php</link>
		</textInput>
		<atom:link href="http://forums.leaflabs.com/rss.php?topic=511" rel="self" type="application/rss+xml" />

		<item>
			<title>gauteh on "new/old bugtracker up on google code"</title>
			<link>http://forums.leaflabs.com/topic.php?id=511#post-10888</link>
			<pubDate>Sat, 26 May 2012 05:47:30 +0000</pubDate>
			<dc:creator>gauteh</dc:creator>
			<guid isPermaLink="false">10888@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Agreed, github issues work great for other projects.&#60;/p&#62;
&#60;p&#62;I think a working/active issues-system would save a fair bit of frustration, especially since this forum has a tendency, in my opinion, to be rather volatile - topics and posts gets stuffed away fairly quick, only a few threads stay active for a long time.&#60;/p&#62;
&#60;p&#62;Also community topics, like SD card storage which I guess you are not interested in supporting officially in the near future lacks any structure. With the discussion spread out over various, flat (its boring to browse 20+ pages to get up-to-date), forum threads and a mostly lagging wiki things get messy ;) I would really welcome a more structured forum solution with a better connection to the wiki and issues-tracker (which only works if they are actively used!).&#60;/p&#62;
&#60;p&#62;The bottom line: I don't think the forum scales and I don't think the forum is very good at being an issue tracker.&#60;/p&#62;
&#60;p&#62;For forum features a good start would the common features of e.g. phpbb:&#60;br /&#62;
- easy to see new post / read threads&#60;br /&#62;
- better stats&#60;br /&#62;
- more structure (sub-forums / threads)&#60;br /&#62;
- use more of the space available&#60;br /&#62;
- more moderator features, duplicates, moving, merging.. &#60;/p&#62;
&#60;p&#62;- gaute
&#60;/p&#62;</description>
		</item>
		<item>
			<title>bnewbold on "new/old bugtracker up on google code"</title>
			<link>http://forums.leaflabs.com/topic.php?id=511#post-10809</link>
			<pubDate>Tue, 22 May 2012 09:41:57 +0000</pubDate>
			<dc:creator>bnewbold</dc:creator>
			<guid isPermaLink="false">10809@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;also, I don't know what features github issues were missing before, but they have milestones, assignment, and tags now. IIRC you can also view all issues for an organization or user across all repositories, though it's tricky to find that page.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gauteh on "new/old bugtracker up on google code"</title>
			<link>http://forums.leaflabs.com/topic.php?id=511#post-10804</link>
			<pubDate>Tue, 22 May 2012 04:13:33 +0000</pubDate>
			<dc:creator>gauteh</dc:creator>
			<guid isPermaLink="false">10804@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;I think it would be a good idea to make this information more accessible, its sort of hard to figure out where all of leaflabs have been laid out. Especially since you recommend posting a forum topic or pull request if there is a problem.&#60;/p&#62;
&#60;p&#62;What about a development/community page along the top links, whether it directs to a wiki page or something else doesn't matter.&#60;/p&#62;
&#60;p&#62;The current state should then be:&#60;br /&#62;
code: github&#60;br /&#62;
bugtracker: google&#60;br /&#62;
community: #leaflabs, freenode / forum&#60;/p&#62;
&#60;p&#62;- gaute
&#60;/p&#62;</description>
		</item>
		<item>
			<title>mbolivar on "new/old bugtracker up on google code"</title>
			<link>http://forums.leaflabs.com/topic.php?id=511#post-2612</link>
			<pubDate>Tue, 16 Nov 2010 05:38:34 +0000</pubDate>
			<dc:creator>mbolivar</dc:creator>
			<guid isPermaLink="false">2612@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;just as a side note: if you're frustrated that the code is on github, but the bug tracker is on google code, you're not alone.  we looked into github issues, but it's just lacking in too many features at this point. &#60;/p&#62;
&#60;p&#62;if github issues approaches feature parity with google code, we'll likely switch.  however, we won't lose history if that happens, since the github API permits us an automated migration mechanism:&#60;br /&#62;
&#60;a href=&#34;http://develop.github.com/p/issues.html&#34; rel=&#34;nofollow&#34;&#62;http://develop.github.com/p/issues.html&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>mbolivar on "new/old bugtracker up on google code"</title>
			<link>http://forums.leaflabs.com/topic.php?id=511#post-2609</link>
			<pubDate>Tue, 16 Nov 2010 04:58:27 +0000</pubDate>
			<dc:creator>mbolivar</dc:creator>
			<guid isPermaLink="false">2609@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;sorry about the long delay on fixing the bugtracker.  we looked into a lot of alternatives, and ended up just deciding to use our old google code page as a bugtracker.  the existing open bugs from redmine have been moved over:&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://code.google.com/p/leaflabs/issues&#34; rel=&#34;nofollow&#34;&#62;http://code.google.com/p/leaflabs/issues&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;closed bugs were too numerous to move over by hand, and it's against google's terms of service to play any bot-style tricks, so we're going to break history here (but hopefully, never again).&#60;/p&#62;
&#60;p&#62;after considering the issue at length, we decided that hosting our own tracker would take too much coder time away from maple and its related software, which, at the end of the day, is what you guys want.&#60;/p&#62;
&#60;p&#62;you currently need a google account to add new issues. if you have one and would like to do that, that's fine. but feel free to just report bugs on the forums, and we'll take care of maintaining the bugtracker.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
