Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 May 2012 at 23:32 UTC
Updated:
28 May 2012 at 16:00 UTC
Description: Improves Drupal core basic behavior by notifying all users that have the administer users permission when a new user registers with pending approval.
Users get a setting to disable these notifications in their user profile form.
See _user_mail_notify()
Version: Drupal 7
Sandbox: http://drupal.org/sandbox/sebcorbin/1574742
Repository: git clone --recursive --branch master http://git.drupal.org/sandbox/sebcorbin/1574742.git
Comments
Comment #0.0
SebCorbin commentedUpdated issue summary.
Comment #1
patrickd commentedwelcome,
Nice to see you've already fixed all coding standard issues.
Please have a look at the project application workflow.
Actually this project is too short to approve you as git vetted user. We are currently discussing how much code we need, but everything with less than 120 lines of code or less than 5 functions cannot be seriously reviewed (regarding security and correct api usage). However, it seems to me that you're already a quite active maintainer of other modules, therefore I'd look over this fact.
As installation and usage instructions are quite important for us to review, please take a moment to make your project page follow the tips for a great project page.
We do really need more hands in the application queue and highly recommend to get a review bonus so we can come back to your application sooner.
regards
Comment #2
SebCorbin commentedI see your point, but this is a very basic and plug-and-play module that just extends a "too simple" behavior in Drupal core.
I intended to keep this module's code very simple using all APIs/hooks that Drupal offers but I can understand if that is not enough.
I updated the project description in the sandbox as you said, even though the goal of this module is pretty straightforward :)
I will also make a D6 backport, if that can help on deciding the issue of this application.
I'll also look into some other project applications because you guys do a great job maintaining this constant queue.
Comment #2.0
SebCorbin commentedUpdated issue summary.
Comment #3
SebCorbin commentedComment #4
klausimanual review:
Although this project on its own is too short to approve you as git vetted user, there are several other projects that you are involved in and that show your skills. So the git vetted user role should be fine.
Otherwise looks RTBC to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #5
SebCorbin commentedWow I feel dumb for user_access(), thanks!
And I thought that empty() would fire a notice, I get less and less dumb :)
Comment #6
patrickd commentedThanks for your contribution and welcome to the community of project contributors on drupal.org!
I've granted you the git vetted user role which will let you promote this to a full project and also create new projects as either sandbox or "full" projects depending on which you feel is best.
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
As you continue to work on your module, keep in mind: Commit messages - providing history and credit and Release naming conventions.
Thanks to the dedicated reviewer(s) as well.
Comment #7.0
(not verified) commentedReviewed some applications