1
edit
Changes
→Project News
= Project Name Bug Tracker for Pidora=<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
== Project Leader ==
[[User:Sung_Hwan_Kim | Sung Hwan Kim]]<!-- Name(s) of primary person working on the projectbr/>[http://professorplumpi. If there is more than one person working on related projects, they must have separate project pages, and the project title and description should identify who is doing whatwordpress. For example: Include links to personal pages within wiki and to com/ professorplumpi blog sites. -->]
== Project Contributor(s) ==
== 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. -->
=== 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. -->
<!-- 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 ==
== Project News ==
After much testing on virtual machines, I have successfully installed Bugzilla on the production server expected to host this service. I have tried to match the current bug tracking system on Trac, interface wise, so current users should not notice too much different in using it.
I will now be attempting to customize the site, and hopefully get the Pidora logo to show up on the front page. I am by no means a web developer, and my limited perl skills have been sitting on a shelf for well over a year. Wish me luck!
<!-- 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. -->