<rss version="2.0">
  <channel>
    <title>Bugs Everywhere</title>
    <link>http://bugseverywhere.org/be/show/HomePage</link>
    <description>An Instiki wiki</description>
    <language>en-us</language>
    <ttl>40</ttl>
    <item>
      <title>Home Page</title>
      <description>&lt;h2&gt;What is Bugs Everywhere?&lt;/h2&gt;


	&lt;p&gt;Bugs Everywhere is a &amp;#8220;distributed bugtracker&amp;#8221;, designed to complement distributed revision control systems.  By using distributed revision control as a backend for bug state, we gain several convenient features:&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Bugs and code that live on branches are tracked together&amp;#8212;when a branch is merged, both the code changes and bug changes that the branch contains are merged alongside each other.  We no longer have to be confused about whether a fix that is applied to the development branch but not yet present in the production branch means that our bug is &amp;#8220;fixed&amp;#8221;.&lt;/li&gt;
		&lt;li&gt;Users can fully modify bug state while offline, unlike with many centralized bugtrackers.&lt;/li&gt;
		&lt;li&gt;When a user checks out your source code, she gets the current bug state for free.&lt;/li&gt;
		&lt;li&gt;We can still provide access to a friendly web interface for users&amp;#8212;in this model, a web interface becomes just another client that merges with the main repository.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Download&lt;/h2&gt;


	&lt;p&gt;Bugs Everywhere is written in &lt;a href="http://python.org"&gt;Python&lt;/a&gt; and available via &lt;a href="http://git-scm.com"&gt;Git&lt;/a&gt;.&lt;br /&gt;&lt;pre&gt;
  % git clone git://gitorious.org/be/be
&lt;/pre&gt;&lt;br /&gt;You can also &lt;a href="http://gitorious.org/be/be"&gt;browse the code online&lt;/a&gt;.&lt;/p&gt;


	&lt;p&gt;There is also a &lt;a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=bugs-everywhere"&gt;Debian package&lt;/a&gt; , but it may lag behind our git repository.&lt;/p&gt;


	&lt;h2&gt;Documentation&lt;/h2&gt;


	&lt;p&gt;Generated documentation is &lt;a href="http://docs.bugseverywhere.org/"&gt;available here&lt;/a&gt;.&lt;/p&gt;


	&lt;h2&gt;Current features&lt;/h2&gt;


	&lt;ul&gt;
	&lt;li&gt;Command-line (&amp;#8220;be&amp;#8221;) interface&lt;/li&gt;
		&lt;li&gt;Supported version control backends:  Arch, Bazaar, Darcs, Git, Mercurial, Monotone.&lt;/li&gt;
		&lt;li&gt;Static &lt;span class="caps"&gt;HTML&lt;/span&gt; bug repository dumps for online browsing.&lt;/li&gt;
		&lt;li&gt;Web interface, created by Steve Losh.&lt;/li&gt;
		&lt;li&gt;Interactive email interface via procmail.&lt;/li&gt;
		&lt;li&gt;Free software licensed under the &lt;span class="caps"&gt;GNU GP&lt;/span&gt;Lv2 or later&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Planned features&lt;/h2&gt;


	&lt;ul&gt;
	&lt;li&gt;&lt;span class="newWikiWord"&gt;Noah Kantrowitz&lt;a href="http://bugseverywhere.org/be/new/NoahKantrowitz"&gt;?&lt;/a&gt;&lt;/span&gt; is interested in &lt;a href="http://www.essaylib.com"&gt;writing&lt;/a&gt; a &lt;a href="http://trac.edgewall.org/"&gt;Trac&lt;/a&gt; backend, so that Trac&amp;#8217;s web interface can be used for BE bugs.&lt;/li&gt;
		&lt;li&gt;&lt;span class="newWikiWord"&gt;Adrian Wilkins&lt;a href="http://bugseverywhere.org/be/new/AdrianWilkins"&gt;?&lt;/a&gt;&lt;/span&gt; would like to see a Mylyn connector for &lt;span class="caps"&gt;BE &lt;/span&gt;(but appreciates that this is a lot of work)&lt;/li&gt;
		&lt;li&gt;Your name/ideas here!&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Submitting bug reports/feature requests&lt;/h2&gt;


	&lt;p&gt;To report a bug, you&amp;#8217;re welcome to either e-mail details to the mailing list, or do the following in your branch of the BE repository:&lt;/p&gt;


&lt;pre&gt;
 % be --repo http://bugs.bugseverywhere.org/ new "The demuxulizer is broken"           
 Created bug with ID bea/abc
 % be --repo http://bugs.bugseverywhere.org/ comment bea/abc
 &amp;lt;Describe bug&amp;gt;
 % be --repo http://bugs.bugseverywhere.org/ commit "Reported bug in demuxulizer" 
&lt;/pre&gt;

	&lt;p&gt;You may also send merge requests, or ask for write access to the repository.&lt;/p&gt;


	&lt;h2&gt;Mailing list&lt;/h2&gt;


	&lt;p&gt;There is a mailing list for developer discussion (and bug submission) at &amp;#8220;be-devel(ATSIGN)bugseverywhere.org&amp;#8221;.  To sign up for it, see its &lt;a href="http://void.printf.net/cgi-bin/mailman/listinfo/be-devel"&gt;listinfo page&lt;/a&gt;.&lt;/p&gt;


	&lt;h2&gt;History&lt;/h2&gt;


	&lt;p&gt;Bugs Everywhere was conceived and written by developers at &lt;a href="http://panoramicfeedback.com/"&gt;Panoramic Feedback&lt;/a&gt;, primarily.  Panoramic Feedback is no longer developing BE, and the current maintainer is &lt;a href="http://blog.printf.net/"&gt;Chris Ball&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>Mon, 06 Sep 2010 22:34:01 Z</pubDate>
      <guid>http://bugseverywhere.org/be/show/HomePage</guid>
      <link>http://bugseverywhere.org/be/show/HomePage</link>
    </item>
    <item>
      <title>Cherry Py</title>
      <description></description>
      <pubDate>Tue, 15 Jun 2010 17:27:16 Z</pubDate>
      <guid>http://bugseverywhere.org/be/show/CherryPy</guid>
      <link>http://bugseverywhere.org/be/show/CherryPy</link>
    </item>
    <item>
      <title>Chris Ball</title>
      <description>&lt;p&gt;Chris Ball&amp;#8217;s Contact Information:&lt;/p&gt;


	&lt;p&gt;&lt;a href="http://blog.printf.net/"&gt;http://blog.printf.net/&lt;/a&gt;&lt;br /&gt;&lt;a href="mailto:chris-nospam@printf.net"&gt;chris-nospam@printf.net&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 18 Nov 2009 02:08:09 Z</pubDate>
      <guid>http://bugseverywhere.org/be/show/ChrisBall</guid>
      <link>http://bugseverywhere.org/be/show/ChrisBall</link>
    </item>
  </channel>
</rss>
