Also, my impression is the places where there are big potential gains are not so much in little things where the correct fix is obvious, but bigger-picture things that are potentially controversial.
Personally, I wouldn’t waste any time on a discussion of a potential big fix unless the instigating party had already shown the ability and willingness to hack on the codebase by, for example, fixing a number of ‘little things’. (Since usually such people never contribute anything and so discussing their proposals is a waste of time and energy.)
Great to hear you’re interested in contributing Chris. The LW codebase takes a bit to get your head around so I’d certainly suggest starting with smaller bugs or small features before diving into big new features. You should definitely get in touch with us (TrikeApps) and Luke to discuss what you want to work on to make sure it’s the best use of your time and your approach considers all angles.
For reference, Accepted issues are generally bugs. The Accepted status indicates they have been reviewed and acknowledged as a bug. Approved is used to indicate tickets that are approved for work (generally by Lucas). These are good candidates to work on but you should definitely coordinate with us to make sure they aren’t being worked on already.
https://code.google.com/p/support/issues/detail?id=1210 suggests sorting by stars should be possible.
Personally, I wouldn’t waste any time on a discussion of a potential big fix unless the instigating party had already shown the ability and willingness to hack on the codebase by, for example, fixing a number of ‘little things’. (Since usually such people never contribute anything and so discussing their proposals is a waste of time and energy.)
Fair enough, and I see the link for sorting by stars is here.
Should I literally just be going down the list top to bottom? Or limit myself to things that are accepted / authorized?
I don’t know what the accepted/authorized stuff means (if anything). Might as well start looking at the top ones and seeing what you can feasibly do.
Great to hear you’re interested in contributing Chris. The LW codebase takes a bit to get your head around so I’d certainly suggest starting with smaller bugs or small features before diving into big new features. You should definitely get in touch with us (TrikeApps) and Luke to discuss what you want to work on to make sure it’s the best use of your time and your approach considers all angles.
For reference, Accepted issues are generally bugs. The Accepted status indicates they have been reviewed and acknowledged as a bug. Approved is used to indicate tickets that are approved for work (generally by Lucas). These are good candidates to work on but you should definitely coordinate with us to make sure they aren’t being worked on already.