Reviews and mentoring of user gisle

I am using an abandoned module called Flexi Access on my site. My project is to turn this module into a user friendly and flexible client for the ACL module. The goal is to use this module to provide the site the administrator with a form interface that let him/her create and maintain named ACLs for the ACL module (the ACL module have all the functionality I need, but it comes without a user interface on its own).

Here is a pointer to the project: https://drupal.org/project/flexiaccess

I thought that the review process included leeway for review of projects that have been taken over - So long as a good representation of your own code is available for review. Also, this might be a little more difficult as most existing project don't pass the pareview script.

Thank you for your comments, jthorson and frob.

My main motivation for doing these reviews is not to gain the 'git vetted user' role. At the moment, I just want to get more involved with the community and learn how to make an acceptable Drupal project.

However, getting such a role will be a nice bonus, since the process for being granted maintainership of abandoned projects seems to be quite backlogged (there are some quite old applications in the webmasters queue flagged "needs review" without a single review or comment).

As for the state of the code in my project, it is true that it closely resembles the original project (a diff will show those interested what I've changed), since my contribution so far is only bug fixes. However, it passes the PAReview script and coder (and the original project didn't).

However, I haven't submitted this project as target for reviews for 'git vetted user role' promotion, and have no plans to do so in the near future. Currently, I'm only here to learn.

logicdesign,
thank you for your comments. I certainly see your point.

Unfortunately, at the moment, I don't have a good new project to submit into the "git vetted" process. I don't want to "make up" a project for this. If I am going to do it, it should be something I would really need and use for my sites (otherwise, I may not be motivated enough to maintain it properly).

I think the "submit a new project for review to become git vetted"-process set up by klausi is a great idea, but it has the unfortunate side-effect that it only motivates people interested in becoming "git vetted" to create new projects. With 19086 full projects already on http://drupal.org/project, I am not sure that what the Drupal community really needs is more new projects.

In my experience, there are too many poorly maintained (or not maintained at all) projects in the Drupal projects namespace. Most of those can of course be ignored. But some of those I use, and I really would see the maintenance status of those improve.

At the moment, I use most of the time I have available for Drupal work to try to "fix" the abandoned modules my sites depend on. But, as pointed out by jthorson, there is an alternative process for dealing with unsupported (abandoned) projects, outlined here: http://drupal.org/node/251466

However, I wonder if this process is working? Because these projects are abandoned, they're buggy and and they attract few users. As a result, almost nobody is interested in reviewing the patches submitted for them by the people who want get them maintained and functional again. Suggested patches remains in the "needs review" state without a single reply for very many weeks. Example: http://drupal.org/node/1405972

I now have a project that I want reviewed in order to become git vetted user. The name of the project is Anonymous publishing.

The application is in the issue queue for Drupal.org Project applications.

I understand that it is now possible to apply for git vetted access according to the procedures listed under the heading Abandoned Module Applications.