Hi, This time from my computer ... mobile phone emailing sort of sucks ;-)
But there's a big number of low-hanging-fruit there ... you don't have to have written the code in order to fix problems in it. It's the ideal place for new people to start contributing or to get re-started. Or get started with FlexJS. A lot of these you can actually fix in your lunch break. I already fixed about 20 blocker issues in there, but I haven't written a line of code in the compiler. I know that most code isn't written by anyone in our project. A git blame would make some of us look bad, but I know that most issues have the exact same timestamp in the Git blame so we all know where stuff came from. So let me be clear. I'm not saying that we are writing bad code, but I am making all aware that it is there. The sooner we clean it up, the better. Chris -----Ursprüngliche Nachricht----- Von: Josh Tynjala [mailto:joshtynj...@gmail.com] Gesendet: Donnerstag, 14. Juli 2016 22:33 An: dev@flex.apache.org Betreff: Re: Flash Builder borked Additionally, a decent number of those issues are attributed to people who are not actively working on Apache FlexJS these days. - Josh On Thu, Jul 14, 2016 at 1:25 PM, Harbs <harbs.li...@gmail.com> wrote: > It’s more likely that it’s more laziness or lack of familiarity with > the tools than anything else. > > On Jul 14, 2016, at 11:14 PM, Christofer Dutz > <christofer.d...@c-ware.de> > wrote: > > > But I have the impression that no-one is actually looking at the > > reports > cause everyone thinks his a real badass programmer. I regularly look > at findings in my code in order to improve my coding skills, but guess > I'm one of the few that think that way. > >
