I'm working on integrating FindBugs static analysis into our build, which has uncovered a long list of outstanding issues. (JIRA <https://issues.apache.org/jira/browse/BEAM-176>, pull request <https://github.com/apache/incubator-beam/pull/357>). Once integrated, I'd like to triage the baseline issues which will be a great source of low-hanging-fruit bugs.
On Sun, May 22, 2016 at 3:07 AM Yash Sharma <[email protected]> wrote: > Great to know someone's on top of it already. > We should encourage creating /marking minor tasks which would give new > contributors opportunity to break the ice. > > Another place could be test cases for certain modules which will also > provide knowledge of code flow. > > -regards > On May 22, 2016 8:01 PM, "Jean-Baptiste Onofré" <[email protected]> wrote: > > > Hi Yash, > > > > During ApacheCon, I discussed with Davor to create a Jira tag: "low > > hanging fruit" ;) > > I did such tag in other Apache projects to encourage contribution. > > > > I see some potential Jira on this kind, especially documentation and > > examples. > > > > Regards > > JB > > > > On 05/22/2016 11:56 AM, Yash Sharma wrote: > > > >> Hi Experts, > >> I have just been checking the Beam issue tracker but could not find lot > of > >> minor/trivial tasks. Also many of the existing minor tasks are quite > old. > >> These tasks are very helpful for newbie contributions and it would be > >> great > >> to see some minor tasks (or a newbie label), and would serve as good > >> starting points for fresh contributors. > >> > >> Thoughts ? > >> > >> Best Regards, > >> Yash > >> > >> > > -- > > Jean-Baptiste Onofré > > [email protected] > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > >
