Ethan Jucovy wrote: > Does t.e.o have a keyword for these kinds of tickets?
For tickets where the ratio "value over work" is too low, no. > As a > non-core-developer I'd like to help out and also get more familiar with > the core codebase, and little bugs that aren't worth a core dev's time > to fix sound like they might be good tickets to start on. That's not the same thing. "Entry-level" tickets are marked with the keyword "bitesized". Their value can be anything, but the work needed is small. Whereas in the other category, the value is generally limited, but the work is large. > Along the same lines, does t.e.o have any way for a non core developer > to mark a ticket "has a patch, which works, [ideally has tests,] and > "just" needs a core developer to review the patch? Yes, we mark such tickets with the keyword "patch". For more keywords (and general guidelines about triaging tickets), see [1]. -- Remy [1] http://trac.edgewall.org/wiki/TracTicketTriage#Keywords
signature.asc
Description: OpenPGP digital signature
