Difference between revisions of "Bug Tracker for Pidora"

From CDOT Wiki
Jump to: navigation, search
(Project Leader)
(Project Details)
Line 16: Line 16:
  
 
== Project Details ==
 
== Project Details ==
While I have the option of continuing to use Trac or switching to BugZilla, I believe I will continue with Trac, as much of it is already implemented (however this does not mean I am closed to the idea of switching to BugZilla; should this avenue show more promise in the future)Trac has several internal and external filtering strategies, which can be found [http://trac.edgewall.org/wiki/SpamFilter here].  I will update this section as I get a chance to test the different options available.
+
Originally I had thought to keep Trac, and simply upgrade any necessary components to implement [http://trac.edgewall.org/wiki/SpamFilter Trac spam filtering modules].  However, after being informed of the current version of the system, it seems it would be equal effort begin from scratch.  In light of this BugZilla seems to be the better choice; having been originally developed and used by the Mozilla ProjectAlso, it is currently employed by " [http://en.wikipedia.org/wiki/Mozilla_Foundation Mozilla Foundation], [http://en.wikipedia.org/wiki/Wikimedia_Foundation Wikimedia Foundation], [http://en.wikipedia.org/wiki/WebKit WebKit], [http://en.wikipedia.org/wiki/NASA NASA], [http://en.wikipedia.org/wiki/Yahoo! Yahoo!], [http://en.wikipedia.org/wiki/GNOME GNOME], [http://en.wikipedia.org/wiki/KDE KDE], [http://en.wikipedia.org/wiki/Apache_Software_Foundation Apache], [http://en.wikipedia.org/wiki/Red_Hat Red Hat] and [http://en.wikipedia.org/wiki/Novell Novell]" (Wikipedia)This avenue may prove to be more robust in the future as it will lend to better performance and scalability.  Trac on the other hand is currently deploying version 1.0 as the stable release, the previous version (and installed currently as the bug tracker for Pidora) is version 0.12. 
  
 
<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->
 
<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->

Revision as of 22:44, 9 October 2013

Bug Tracker for Pidora

Project Description

Trac is an open source Project management and bug tracking system. It is the system currently employed to keep track of bugs for Pidora. As with everything on the internet, there are those that use it as it is intended; but you also have a group of people that derive pleasure by abusing it and spamming the system. There are many available modules to help control the incoming spam. While spam cannot be completely eliminated, it can be significantly reduced, and what is able to squeeze in through the automated controls, is easily dealt with by the administrator.

Project Leader

Sung Hwan Kim
professorplumpi blog

Project Contributor(s)

Project Details

Originally I had thought to keep Trac, and simply upgrade any necessary components to implement Trac spam filtering modules. However, after being informed of the current version of the system, it seems it would be equal effort begin from scratch. In light of this BugZilla seems to be the better choice; having been originally developed and used by the Mozilla Project. Also, it is currently employed by " Mozilla Foundation, Wikimedia Foundation, WebKit, NASA, Yahoo!, GNOME, KDE, Apache, Red Hat and Novell" (Wikipedia). This avenue may prove to be more robust in the future as it will lend to better performance and scalability. Trac on the other hand is currently deploying version 1.0 as the stable release, the previous version (and installed currently as the bug tracker for Pidora) is version 0.12.


Project Plan

Tracking

Trac to track Trac? =)

Key contacts

Andrew Oatly-Willis

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1
    • Research and test each of the modules that look promising
  • 0.2
    • Implement the modules that show significant decrease in spam
  • 0.3
    • ???Profit

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Non-Seneca Participants

Planets

Project News