Post #1808948

Over the years I just assigned myself bug reports. And then never get around to fixing them. This year I have done the opposite and started to unassign myself and for some of them I also decided to put them in the easy to fix list and even put them in the newsletter. Guess what the bugs I had assigned to myself are now being fixed. The summary here is dont be greedy and instead spread the work around. And getting in new folks might be easier than we had thought. Provide them with guidance of what can be done and folks will come and fix it. The other thing I learned now is that unless there are provided steps on getting partial transitions finished nobody is going to fix them. So it is better to write them up for new comers to work on than just say it is partial transitioned. When I first started this newsletter I did it as I wanted to know what went in the last week but I now have turned it into gaining new contributors and hopefully folks will stay around. I am also learning so much about how to attract new people. And even learning about gcc missopportunities for the last 20 years here. And hope folks see this work and see that it is working and start doing similar stuff. On reviewing side of getting more reviewers, similar things need to happen. Provide an opportunity for someone nervous about reviewing to come in and review a patch. Even if it is a private review to a mentor. I suspect there are folks out there that want to review a patch or two but dont know how to start or even how to select a patch to review. Even though we old timers learned the hard way to review, it does not mean new folks have that same experience.