Code review for security advisory coverage applications

klausi remembered me about the surveys we prepared for the talk at dc munich and yes, it's about time that I publish them as promised.

Also, as the "the process sucks"-discussions are on fire again some of these comments might be useful.

Here are the (anonymized) exports of webform.com:
(tried to import them on google docs it did a horrible job, I recommend you to use open/libre/whatever-office and set "tabs" as delimiter.)

Survey 1:
"Project application process"
30. Apr - 14. May
122 Submissions
http://groups.drupal.org/files/pasurvey1.csv

Survey 2:

We have currently 27 RTBC project applications that need a final check by a code review administrator. I am quite busy with the review bonus program so I don't have time to review/approve all of them.

You can help: if you are a code review administrator it would be cool if you could checkout at least one RTBC application per week (or more, or less - any help is appreciated).

I created the Twitter account @drupal_review that automtically aggregates some RSS feeds and to post news on the project application review process occasionally.

Currently the following feeds are forwarded with twitterfeed.com:

Fixed applications: http://drupal.org/project/issues/rss/projectapplications?status=2
Discussions in this group: http://groups.drupal.org/node/103499/feed

If you are a code review administrator and would like to help maintain this account just contact me.

Drupal core has Issue count thresholds to keep the number of outstanding bugs and tasks under control. It might be a good idea to introduce something similar for project applications. This would mean that we do not approve RTBC applications while a certain threshold is exceeded. We reach out to the other applicants and the rest of the community in such a situation to get back under the threshold(s). Getting back means reviewing applications.

I'm proposing two thresholds:

<

ul>

Me and patrickd are proposing a session about the project application review process at Drupalcon Munich. Feel free to provide us with feedback what else you would like to see in this session.

Currently we have the policy that applicants can raise their application priority after 2 weeks without a response (documented in How to review Full Project applications). A review bonus is now strongly recommended in the application documentation and I think we should also adapt our application priority guidelines.

There should still be some review process after one is given full git access, as there are many people who take it in wrong sense & put modules as which are not may be required.
Just some review process so that same quality which is checked while approving project applications during giving git access can also be maintained later.
Do we really require those projects which may not follow standards to be there ?
Like http://drupal.org/project/contact_profile
No offense, but is it fine to put a module with minimal code [e.g. drupal_alter just] as full project?

Dunno how usefull it is, but it gives a nice overview:

// edit: added a shortlink
http://ventral.org/paissues

It is based on the rocketship module of Gábor Hojtsy, modified to work on the project application queue.