Abandoned applications are now closed after 4 weeks instead of 10 weeks

Events happening in the community are now at Drupal community events on www.drupal.org.
Posted by klausi on January 2, 2016 at 11:36am

I updated PA Robot to close inactive project applications (in the "needs work" status) after 4 weeks instead of 10 weeks. That way applicants get feedback earlier that the application is blocked on their part in case they forgot to update the status.

Let me know if that causes any issues I have not thought of.

Comments

Great Idea +1 from my

Posted by pushpinderchauhan on January 2, 2016 at 1:07pm

Great Idea +1 from my side.

Will help to reduce the backlog in terms of active applications :)

Pushpinder Rana

Good point !! Contributors

Posted by manjit.singh on January 2, 2016 at 11:52pm

Good point !! Contributors would become more active for their application. And peer review will boost this up.

But Would it be applicable for "need work" status.

+1 supported, It will

Posted by rashid_786 on January 3, 2016 at 5:05am

+1 supported, It will encourage new contributors to participate actively and there should be some notification and intimation before updating the status as closed.

Rashid

+1

Posted by naveenvalecha on January 3, 2016 at 5:33pm

Good point, to close the inactive issues soon, it would help contributors to become more active for their application.
Needs work list https://www.drupal.org/project/issues/projectapplications?status=13&text...
I have seen that there are no issues in the queue more than 4 weeks and I think 2 weeks is more than enough time to close the inactive issues.
I would recommend to close the inactive issues after 2 weeks. What do you reckon here ?

Let's keep it at 4 weeks for

Posted by klausi on January 3, 2016 at 7:34pm

Let's keep it at 4 weeks for now and if that works we can always reduce it to 2 weeks later.

okay

Posted by naveenvalecha on January 4, 2016 at 6:26am

okay,we can wait for few more weeks. yes it would work and making it 2 weeks will helps applicants & reviewers to be active more in queues.

Four weeks instead of ten is

Posted by markconroy on January 3, 2016 at 5:49pm

Four weeks instead of ten is a sixty per cent reduction.

I'd say leave it at that and see if it makes a difference before we start dropping it to two weeks.

yes, 4 weeks will be best

Posted by rrfegade on January 14, 2016 at 9:24am

This will improve the response time from the developer and keep them active on their thread

Great one +1

Posted by fusionx1 on January 15, 2016 at 2:45am

Will encourage more developers, i have a lots of friends would be glad if they know that it will only take 4 weeks for them to get approved.

This 4 weeks is not about

Posted by pingwin4eg on January 15, 2016 at 7:43am

This 4 weeks is not about approving time, but about the time of idleness of developer response from 'Needs work' status of application to status 'Closed'.

Code review for security advisory coverage applications

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

AltStyle によって変換されたページ (->オリジナル) /