Having good documentation in the code at least in the critical section/methods/classes would ease anyone who would like to understand and contribute. Given there is going to be issues with availability of committers to help/mentor, adding "good" documentation can go a long way. Something to consider for everyone when a we work on a familiar code and see not much documentation there.
On Wed, Mar 20, 2019 at 3:42 PM Xu Cang <[email protected]> wrote: > The motivation for contributing opensource work sometimes affected by > projects' popularity. And open source as a whole is hugely impacted by > public cloud companies since their profit-driven mindset. One of the > biggest public cloud provider even discourages employees from contributing > to open source by asking them filling documents, going through reviews and > signing agreements before you can do that under their employment. Past > Redis license change story also reveals some difficulties that open source > community is facing. https://news.ycombinator.com/item?id=19221754 > > On Wed, Mar 20, 2019 at 12:03 PM Andrew Purtell <[email protected]> > wrote: > > > I don’t think it is realistic, unfortunately. If you remember our OWNERS > > initiative, which failed, the idea there was for various functional areas > > or components there would in effect be a mentor, someone you could > > at-mention for advice and review. This failed because if this isn’t your > > full time paid profession you can’t devote the necessary time. Life and > day > > job intervene. Furthermore the available volunteer bandwidth of this > > community is in long term decline. The pendulum can shift back (viz > > zookeeper) but the trend as of today is similar to tends in the ASF > > incubator: seems like in the past there were more people around with more > > available time. There might be good intentions but little is more > > demoralizing than being ignored by someone expected to be a mentor, only > > because that mentor has severe time constraints due to day job or > personal > > life. > > > > > > On Wed, Mar 20, 2019 at 10:48 AM Misty Linville <[email protected]> > wrote: > > > > > Another open source project I’m on is exploring the idea of a mentoring > > > rotation where each mentor serves for a week and especially looks out > for > > > and provides practical assistance and review to new contributors for > that > > > week, on an office-hours type of basis. Many hands make light work. > WDYT? > > > I’d say that this type of mentoring, if done well, would be another way > > to > > > put one on the road to recognition for leadership within the project. > > > > > > On Wed, Mar 20, 2019 at 9:45 AM Tak-Lon (Stephen) Wu < > [email protected] > > > > > > wrote: > > > > > > > +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? > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Best regards, > > Andrew > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > decrepit hands > > - A23, Crosstalk > > >
