+1 one for the mentoring if one existing member who knows the feature plan and is willing to create tasks for pickup.
my current barrier is to find a continuous topic/component and focus on it, but I'm a bit too random with my approach. Currently, not sure this is the right way, I lookup JIRAs by filtering tags (e.g. BUG) with priority and created dates to find newly reported issues and somehow didn't know which JIRA should be resolved next release. meanwhile, I may miss older JIRA which potentially is critical (probably the longer it has no one look at it, should it considered as less critical?). Thanks, Stephen On Wed, Mar 20, 2019 at 12:12 AM Artem Ervits <[email protected]> wrote: > Would be great to have mentors. Ted used to review my patches and provide > feedback on timely basis, understand everyone is busy but would be nice to > have a point person (per feature, bug, branch, module, etc). I have cycles > to burn but currently it feels a bit overwhelming as community may feel > there's a certain level of familiarity with the process necessary. > > On Wed, Mar 20, 2019, 4:59 AM Misty Linville <[email protected]> wrote: > > > #1 this is difficult code. That’s probably the one we can’t surmount but > I > > wanted to put it out there. > > > > On Tue, Mar 19, 2019 at 5:03 PM Sean Busbey <[email protected]> wrote: > > > > > I have my own opinions, obvs. But I'm curious what other folks think > are > > > the biggest impediments to new contributors? > > > > > >
