Difference between revisions of "Bug Tracker for Pidora"
(→Project Details) |
(→Project Plan) |
||
| Line 23: | Line 23: | ||
=== Tracking === | === Tracking === | ||
| − | + | While there isn't much version control needed, I may use github to keep changes to configuration files as I work on them. | |
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) --> | <!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) --> | ||
| Line 35: | Line 35: | ||
<!-- 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. --> | <!-- 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 | * 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 | * 0.2 | ||
| − | **Implement | + | **Implement application (and modules) on Production environment. |
* 0.3 | * 0.3 | ||
| − | ** | + | **Make any necessary changes to enhance performance. |
| + | |||
== Communication == | == Communication == | ||
Revision as of 22:53, 9 October 2013
Contents
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
While there isn't much version control needed, I may use github to keep changes to configuration files as I work on them.
Key contacts
Andrew Oatly-Willis
Goals by Release
Goals for each release and plans for reaching those goals:
- 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.
