klausi is scaling back, your help needed!

Posted by klausi on February 8, 2014 at 7:51pm

As you might have noticed I have scaled back my efforts on the project applications issue queue a bit, meaning that I'm busy with other things and cannot review as many project applications as I did in the past. I won't stop reviewing applications completely, so don't worry: I'm not gone :-)

As a consequence the review bonus program will not work as good as it previously did and applicants will have to wait a couple of weeks before they get my attention.

There are a couple of things you can do to help me and the applicants:
1. Help me reviewing Review Bonus applications, so that we can continue with timely responses at least for those that are community-minded people that help each other (instructions for reviewing).
2. We still desperately need more active code review administrators that approve applicants. Just be an active reviewer for a month or two and we can make you to a code review administrator yourself!
3. Start implementing our process improvement plan to make the project application process more efficient.

Thanks for supporting me and all the new contributors!

Comments

Klausi, Thanks for all the

Posted by greggles on February 8, 2014 at 9:14pm

Klausi,

Thanks for all the work you've done. It's been an amazing few years of work in the queue, rallying people outside the queue, and on our processes!

Thanks also for stepping down gracefully and asking others to help out. That is a very responsible and respectful thing to do and helps to keep our project healthy.

knaddison blog | Morris Animal Foundation

Thanks for this

Posted by gobinathm on March 7, 2014 at 3:37am

Klausi,

Thanks for doing this activity for last few years. I'm very much interested to be part of this team & help clear out project review queue as a code review administrators.

Very good! I saw that you are

Posted by klausi on March 7, 2014 at 9:59am

Very good! I saw that you are not a git vetted user yourself yet, so the first step would be to approve you there. I'll look into your project application shortly.

The second step is to be active as a reviewer regularly and collect your reviews on a wiki page like https://groups.drupal.org/node/393378 . Extra bonus points for finding security issues in project applications. You can also help me by working through the review bonus list, so that we can approve those faster.

After one or two months building up trust we can make you a code review administrator.

Thanks for helping out!

thanks for encouraging reply

Posted by gobinathm on March 24, 2014 at 7:00am

klausi, thanks for an encouraging reply. I have created a Wiki page & will start adding all the review links as when its done.

Created wiki page

Posted by mpdonadio on March 14, 2014 at 7:43pm

I just created my wiki page. Will find my old reviews and add them, and see if I can start reviewing again.

Tagging to help the process

Posted by mpdonadio on May 17, 2014 at 1:45pm

klausi, I have been thinking a little about the review process, and had an idea. There are a few things going on.

One, is the lack of people doing reviews, or at least those by those not doing it as part of the review bonus program. Hopefully the call-to-action you made will improve things. I am going to do my best to do two a day (one morning and one evening). It looks like there may one or two other people who are doing the same.

Personally, I have been concentrating on the Needs Review projects, as I feel I have a better eye for these. This leads to the next thought, and is specific to the need for new admins, so I am commenting here and not on the process improvement post.

There are a lot of projects with RBTC+PAReviewBonus. If one of the potential new admins does a review and leaves it as RBTC, there is no other indication that this has been done. Would you object to us using the PAreview: admin mentoring tag to identify RBTC+PAReviewBonus that we think are ready for prime time?

One thing I also have trouble with is the need for second opinions, and especially surrounding whether a particular review item warrants a workflow state change. As part of this, I started to add some examples to https://drupal.org/node/532400, but was thinking that PAreview: second opinion tag could help matters here. And for anyone reading, you can hit me up for a second opinion either on Twitter or Drupal Answers chat.

Thoughts?

I agree with mpdonadio on

Posted by er.pushpinderrana on September 16, 2014 at 4:37am

I agree with mpdonadio on using the PAreview: admin mentoring tag to identify RTBC+PAReviewBonus that we think are ready for prime time.

I also face this problem sometime when I review any RTBC application, if anything seems blocker then its fine to switch status to Need Work but if everything is fine then there is no extra tag available there to post my reviews over there. I think it would be good if this extra layer added for new mentors. It would help new reviewers to reviews more RTBC applications plus becoming a good reviewer :).

So plus one from my side.

Pushpinder Rana