Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Oct 2011 at 17:08 UTC
Updated:
16 Apr 2023 at 18:46 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
gargsuchi commentedVery nice module.
I have tried and tested the module - and works perfectly for me.
Few comments:
Once these issues are fixed, I will gladly mark the module as "Reviewed and tested by community"
Comment #2
steve.colson commentedRequested changes have been made. Ready to re-review!
Comment #3
webrmedia commentedReview of the 6.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
Definitely is an interesting module! :) Please note that I haven't actually run/tested the code. Thanks.
Comment #4
webrmedia commentedWhups, forgot to change the status! ;)
Comment #5
steve.colson commentedI am definitely not seeing those coder errors. I've run it through the 6.x-2.0-rc1 version of coder a few times now (selecting minor and critical to make sure it was catching everything as intended) and I've attached the screenshot of my most recent run through with settings and my results. What is incorrect in the settings? As near as I can tell the code seems to pass.
Comment #6
natemow commentedStephen -- check out klausi's PAReview.sh script at http://drupal.org/sandbox/klausi/1320008
All of the "needs review" feedback you're seeing in your project application is coming from the script's output.
Comment #7
steve.colson commentedI have made the changes as best as I can track. I do not have drush on this computer, so I cannot run pareview to double-check. Please re-review.
On a side note, asking people to use pareview implies that they should be on *nix computers, which is a huge problem. Testing systems should be able to easily run on any system that Drupal indicates it is supported. For that matter, it has far more setup requirements than coder--as coder is the Drupal standard review module, efforts should be put in to coder to make it "code standards current" for the 6.x version if there are discrepancies. Otherwise, code that passes review with the most recent stable version of the coder module *should* be considered complete in my opinion.
Comment #8
natemow commentedAgree that having all possible checks present in coder would be ideal, and I think there's been quite a bit of discussion around that already. There's also been talk of completely automating/integrating some of the coding standards reviews upon project application. The process is obviously not perfect yet, but it's a step in the right direction.
Review of the 6.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
Comment #9
steve.colson commentedJust to provide an update--My harddrive crashed and apparently I need a new logic board as well, that occured during the holidays and I am waiting to get my computer back from the manufacturer before I can complete this.
Comment #10
patrickd commentedSwitched back to needs review, so in-depth reviews won't be blocked by coding standart issues.
Comment #11
natemow commentedAutomated review attached -- This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Go and review some other project applications, so we can get back to yours sooner.
Comment #12
steve.colson commentedOk, #8 and #11 should be corrected.
Comment #13
klausiReview of the 6.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.
manual review:
I know, getting feedback on your application took long, you can speed up the process with #1410826: [META] Review bonus.
Comment #14
steve.colson commentedRe #13:
Automated review passes: http://ventral.org/pareview/httpgitdrupalorgsandboxstephencolson1322504git
manual review:
1. In this case, I disagree. In the event that someone disables/re-enables a module multiple times, the expected behavior should be that the settings stay consistent until they use the uninstall function.
2. Same
3. Updated for placeholders.
4. Updated for use of t().
Comment #15
jthorson commentedNo reviewer feedback for over 7 weeks ... I'm going to mark this RTBC due to the process stalling out, and the 7 week wait for reviewer feedback with no response.
Apologies for the delay, thank you for your patience, and let's get this pushed through!
Comment #16
ceardach commentedThanks a lot for this really cool module! And holy moly, am I impressed that you were able to have zero code standard warnings -- that takes total dedication, and we want that sort of dedication and collaboration in the community!
I agree with both you and klausi about the hook_install() and hook_uninstall() tasks -- although I lean more with klausi with the tasks modifying user profiles (what about new users since the disabling?). I think it is something that you'll need to sit back and think through. Absolutely not an application blocker, though!
Your code is gorgeous. My only suggestion is to add a blank line to the end of your files -- it minimizes conflicts in version control, so I'm sure you'll grow to love it.
I am recommending that your application be approved. Now make more really cool modules like this one ;)
Comment #17
mlncn commentedCongratulations, Stephen! You are now a "vetted" git user and can promote experimental sandboxes to full projects. Very excited to see this and other contributions from you!
Thank you gargsuchi, natemow, et al for your reviews, and thank you jthorson, ceardach for bringing this back up.
Comment #18
patrickd commentedComment #20
avpadernoComment #21
avpadernoComment #23
avpaderno