View source for Bug Tracker for Pidora

= 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 (bunch of jerks!).  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 ==

[[User:Sung_Hwan_Kim | Sung Hwan Kim]]<br/>
[http://professorplumpi.wordpress.com/ professorplumpi blog]

== Project Contributor(s) ==

<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.

NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. -->

== Project Details ==
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 Project.  Also, 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. -->

== Project Plan ==

=== Tracking ===
While there isn't much version control needed, I may use git to keep changes to configuration files as I work on them.
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->

=== Key contacts ===
Andrew Oatly-Willis
<!-- Add links to any mentors or key participants in the community. -->

=== Goals by Release ===

Goals for each release and plans for reaching those goals:
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
* 0.1
**Decide between BugZilla(currently the leader), and Trac.
**Install chosen application and any necessary spam filtering modules on a local machine/drive.
**Test installation against spam (possibly use cases already in Pidora bug tracker).
* 0.2
**Implement application (and modules) on Production environment.
* 0.3
**Make any necessary changes to enhance performance.

== Communication ==

=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->

=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->

=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->

=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->

=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->

=== Non-Seneca Participants ===
<!-- Links to the blogs of any non-Seneca participants in this project -->

=== Planets ===
<!-- Links to any planets related to this project -->

== Project News ==

<!-- This is where a permanent record of your releases and updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->