The main concern is related to chances that newcomer will have to obtain a review support from the community.
Actually, a lot of people doing their best to provide a feedback to newcomers, and count of issues still in PA state goes down (84 is a relatively small count of issues in PA state). But 1428 PRs may imply we don't review here, as we have tons of incomplete PRs. Actually, most of these PRs were merged (but not using ./apply-pull-request.sh script, but manually, without reference to PRs). Another benefit of revising this list, if there are any changes which were not accomplished with a proper ticket with PA status, we will identify a number of additional contributions to be applied to the codebase. пн, 10 дек. 2018 г. в 19:53, Nikolay Izhikov <nizhi...@apache.org>: > Hello, Dmitriy. > > What, exactly concerns newcomers? > What is wrong with opened PR? > How project will benefit from closed PR? > > > The same proposal is related to IEP statuses. If you were involved in an > IEP, please validate its status > > +1. We should maintain IEP description up to date. > > пн, 10 дек. 2018 г., 19:15 Dmitriy Pavlov dpav...@apache.org: > > > Hi Igniters, > > > > Newcomers to Apache Ignite sometimes became concerned about many open PRs > > in the project. Apache Ignite TC Bot also performs runs checks with a PR > > open. Apache Ignite pulls list https://github.com/apache/ignite/pulls > > contains > > 1442 PRs open while only 84 issues are waiting for review. > > > > Could you please verify the list of your PRs in Apache Ignite > > https://github.com/pulls and close every not needed/already merged > > change? > > > > The same proposal is related to IEP statuses. If you were involved in an > > IEP, please validate its status here > > https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals > > Please > > set a correct state for your IEP, as well. > > > > Should you have any questions, please don't hesitate to ask here. Thank > you > > in advance! > > > > Sincerely, > > Dmitriy Pavlov > > >
