Changes

Jump to: navigation, search

Bug Tracker for Pidora

764 bytes added, 19:28, 7 October 2013
no edit summary
= Project Name Bug Tracker for Pidora=<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
 <!-- Description should be no longer than a paragraphTrac is an open source Project management and bug tracking system. Include links It is the system currently employed to any relevant keep track of bugs for Pidora. As with everything on-line resources. For examplethe internet, [http://fedoraprojectthere 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.org/wiki] or [http://developer There are many available modules to help control the incoming spam.mozilla.org MDC] 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 ==
<!-- Name(s) of primary person working on the project[[User:Sung_Hwan_Kim | Sung Hwan Kim]][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 ==
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. -->
=== Tracking ===
Trac to track Trac? =)
<!-- 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
**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 ==
Shkim33
1
edit
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/wiki/Special:MobileDiff/99991"

Navigation menu