In other projects that I've worked on, bug trackers sometimes tag tickets based on various attributes. An example of this is the Servo project on github:
https://github.com/servo/servo/issues Tickets here are tagged by component, type of ticket (bug, refactoring, enhancement, ...), and difficulty. We've been getting some newer developers recently, both corporate and hobbyist, and I think some of this tagging could be useful to our workflow--specifically tagging tickets for difficulty. What this would require is the creation of projects like "Trivial", "Easy", "Hard", "Wizards Only", etc, and then adding these projects to tickets. In this way, someone with knowledge of the related area for a ticket could mark some tickets out which could then be handled by people with the related level of expertise/stubbornness. Ideally, this would somewhat reduce work for our more senior developers by making easier tasks more visible. It would also enable new developers to find tickets which they could make progress with while avoiding falling into evas_map and other bug abysses. If this goes well, it may be worthwhile to also start tagging/creating tickets for "todo" items using the same methods. ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
