Difference between revisions of "Bug Tracker for Pidora"
(Created page with '= Project Name = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == <!-- Description should be no longer than a pa…') |
|||
| Line 1: | Line 1: | ||
| − | = | + | = Bug Tracker for Pidora= |
| − | |||
== Project Description == | == 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 == | == Project Leader == | ||
| − | + | [[User:Sung_Hwan_Kim | Sung Hwan Kim]] | |
| − | + | [http://professorplumpi.wordpress.com/ professorplumpi blog] | |
| − | |||
| − | |||
| − | |||
== Project Contributor(s) == | == Project Contributor(s) == | ||
| Line 21: | 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. | ||
<!-- 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. --> | ||
| Line 27: | Line 23: | ||
=== Tracking === | === Tracking === | ||
| + | Trac to track Trac? =) | ||
<!-- 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, ...) --> | ||
=== Key contacts === | === Key contacts === | ||
| + | Andrew Oatly-Willis | ||
<!-- Add links to any mentors or key participants in the community. --> | <!-- Add links to any mentors or key participants in the community. --> | ||
| Line 37: | 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 | ||
| + | **Research and test each of the modules that look promising | ||
* 0.2 | * 0.2 | ||
| + | **Implement the modules that show significant decrease in spam | ||
* 0.3 | * 0.3 | ||
| − | + | **???Profit | |
== Communication == | == Communication == | ||
Revision as of 18:28, 7 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
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 here. I will update this section as I get a chance to test the different options available.
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
