The project application review process is done only once per applicant, so we need to make sure that they provide us with enough self-written code that we can review. Otherwise we cannot really judge their skills and understanding of Drupal.
This does not mean that short projects will never get approved, a git admin can promote a project on behalf of the user without giving the git vetted user role to them. We decided to do so also for simple Features only projects, so we could also do it in these cases. Applicants can come back to the review queue whenever they have something new they want to promote.
I propose two simple rules that can be used to deny the "create full projects" permission:
* The project has less than five function or class method definitions
* The PHP/Javscript source code is less than 120 lines long (including comments and whitespace).
This does not mean that projects that satisfy these rules will automatically result in the "create full projects" permission. We can always discuss if there are other reasons why a project in not enough for the "create full projects" permission.