The submitter must acquire the skills to transmit reliable write-ups to draw the attention of consumers. On Nov 2, 2018 10:43 PM, "Dmitriy Pavlov" <dpavlov....@gmail.com> wrote:
> Hi Craig, > > Ignite dev list is now quite busy-list. GitHub comments are not forwarded > (for the main repository, it is only forwarded for an additional GitBox > repository, and probably we need to disable it as well or create > notifications list). Forwarding comments may create additional pressure to > contributors because they need to filter out emails from contributions > which are not interesting. > > Some Ignite developers use the list to find a reviewer, and reviewers reply > to dev list/to JIRA about results. The reviewer mentions where to find > comments. > > Community Developers, thank you for all your replies. > > I've forwarded the reference to this thread and to 'large code drops' > thread to Ignite dev list. I'm sure it will help the participants to > understand why it is an important thing to share their ideas/plans/results > using the list. > > Sincerely, > Dmitriy Pavlov > > > пт, 2 нояб. 2018 г. в 18:31, Craig Russell <apache....@gmail.com>: > > > +1 to what Myrle says. > > > > I especially like the idea of engaging the submitter to discuss a pull > > request. Even if it's to say "Thanks for this. It looks perfect as is". > But > > often, there will be a bit of back and forth. > > > > One potential problem is the work flow using the github tools, which can > > have the effect of dialog "off-list" between the submitter and the other > > devs. I don't know how to solve this issue except for one of the other > devs > > to initiate contact via the dev list in addition to the issue tools. > > > > Are the github tools for the project configured to copy the dev list on > > every interaction on a pull request? > > > > Craig > > > > > On Nov 2, 2018, at 8:23 AM, Myrle Krantz <my...@apache.org> wrote: > > > > > > If anyone on the PMC is uncomfortable with making someone a committer > > > because of their uncommunicativeness, I'd be inclined to give it a > little > > > more time. A "no" now, doesn't mean a "no" forever. Maybe ask that > > person > > > a few questions about their PR's on the list and see if they can be > > > encouraged to engage? Maybe let the PMC member who's advocating for a > > > particular contributor be the one to take point on that effort? > > > > > > Greets, > > > Myrle > > > > > > > Craig L Russell > > Secretary, Apache Software Foundation > > c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo < > > http://db.apache.org/jdo> > > >