[GHC] #15640: Add "difficulty" field to tickets

[GHC]

#15640: Add "difficulty" field to tickets
-------------------------------------+-----------------------------
        Reporter:  flip101           |                Owner:  hvr
            Type:  feature request   |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Trac & Git        |              Version:
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:  Other
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-----------------------------

Comment (by osa1):

 I 100% support this. I'm currently trying to contribute to another
 compiler (just to get a taste of it after about 4 years of GHC work) and
 one of the things I do is to filter "easy" tickets and pick one from
 there. Most of them are actually almost objectively easy, so while the
 "subjectivity" is a problem I think that's not a too serious one. I think
 most of the time an experienced GHC hacker could guess difficulty of a
 ticket quite accurately.

 > Can be welcoming to newcomers who want to contribute to GHC to start
 with tickets with low priority. The new field should be searchable so they
 can get a list of all tickets with low difficulty

 One of the things we should stop doing is fixing easy problems ourselves
 instead of marking tickets as "easy" (and "newcomers"). I know I sometimes
 do this and looking at the tickets I see a lot of other cases too. We
 should let the new contributors do these tickets. Simply enabling the
 field won't be enough for new contributors if we don't have any such
 tickets (because they're all fixed by experienced contributors).

 OTOH some of the simple issues are also quite annoying to the person who
 discovered it (e.g. a problem in a debug output or an incorrect assertion)
 so sometimes it's hard to resist the temptation to fix it ourselves. This
 is especially a problem if it turns out we don't have enough contributors
 and simple tickets stay unfixed for weeks/months.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/15640#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler