#508 was worked on 14 days ago by @resmo and @wilderrodrigues

@DaanHoogland That's true. Although @wilderrodrigues will take over the PR and needs to create a new one. But let's stick to the proposal indeed. I'll remove #508 from the list.

I did not send a 👎 to dev@. I did not omit that mail by mistake (sorry for the double negative). the proposal seems radical (17 july is phased out on 17 August) but house cleaning is needed. let's make a PR like this on a weekly basis.

@DaanHoogland Weekly basis is OK with me!

cloudstack-pull-rats #325 ABORTED

cloudstack-pull-requests #1021 ABORTED

cloudstack-pull-rats #329 ABORTED

cloudstack-pull-requests #1024 ABORTED

cloudstack-pull-analysis #257 UNSTABLE
Looks like there's a problem with this pull request

cloudstack-pull-analysis #261 ABORTED

cloudstack-pull-rats #334 ABORTED

cloudstack-pull-requests #1029 ABORTED

cloudstack-pull-analysis #266 ABORTED

All, let's not do this for multiple reasons;

• by closing a PR which has not got attention we risk forgetting about it and losing the contribution
• generally those of us who have worked for long in the community or have dayjob colleagues working in the community, have better chances in getting their PRs merged; for new contributors this pattern is not encouraging and certainly not welcoming if their PRs get closed just because it did not caught any attention in one month's time
• our community works on the premise that everyone is a contributor working as per their convenience, interest and time, on top of this the developer community is not very large to ensure that all PRs will get attention or review within a months time of its arrival
• the requirement of 2 LGTM on each review makes it too much process-oriented that costs time and efforts, sometimes fixes are small but getting them merged has taken more time

@bhaisaab OK, let's leave it for now and discuss later. I will close the PR.

@bhaisaab @remibergsma : Rohit has some good points there and some that can be avoided. Noticably a PR that hasn't gotten any attention from the community should not be closed. But when several people have given feedback and the author does not respond it is of a different case. Let's revisit if the present backlog groth continues.