Display the project statistics in a Web page
Overview
This module can be used to count the number of lines and characters contained in the files of a project.
It can traverse a given project directory recursively and process files that match a given file name pattern.
The module counts the number of lines of the matched files and the total number characters excluding white space or just considering alphabetic characters.
The module can also display the statistics in a Web page.
Sandbox project page:
You can find the module in my sandbox at http://drupal.org/sandbox/ankitchauhan/1536580
You can clone the repository with the following command:
git clone --branch 6.x-1.x ankitchauhan@git.drupal.org:sandbox/ankitchauhan/1536580.git project_estimator
cd project_estimatorDrupal core version 6.x
Other project reviewed
http://drupal.org/node/1434388#comment-5954324
http://drupal.org/node/1434388#comment-5963546
http://drupal.org/node/1563728#comment-5964682
Comments
Comment #1
patrickd commentedwelcome,
As installation and usage instructions are quite important for us to review, please take a moment to make your project page follow tips for a great project page. Also create a README.txt that follows the guidelines for in-project documentation.
Major things you should fix:
while waiting for an in-depht review of your module you can start out fixing some coding style issues detected by automated tools:
http://ventral.org/pareview/httpgitdrupalorgsandboxankitchauhan1536580git
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
ankitchauhan commented@patrickd
Thanks for your quick response.
I am updating my application after fixing some coding style issue. But some of them are remaining, i am not able to fix them.
Please guide me
Thanks again,
ankit
Comment #3
patrickd commentedstr_replace('\\', '/', $dir_name);withdrupal_str_replace('\\', '/', $dir_name);trigger_error(filter_xss('Cannot find ' . $dir_name . ' directory.'), E_USER_ERROR);- why not using t() in these cases? ->trigger_error(t('Cannot find @directory directory.', array('@directory' => $dir_name)), E_USER_ERROR);Rest of the errors are only minor and can be ignored, you don't have to satisfy the nitpicking automated review by 100%, just make sure major issues are cleared.
Comment #4
ankitchauhan commentedthankx patrickd
I update this ASAP.
Comment #5
ankitchauhan commentedapplying for PAReview
Comment #6
ankitchauhan commentedapplying for PAReview bonus
Comment #6.0
ankitchauhan commentedreviewing module
Comment #6.1
ankitchauhan commentedupdating project summery
Comment #7
ankitchauhan commentedhi guys
I have fixed all the coding style issue generated by Code Sniffer and emptied the master branch.
Comment #8
ankitchauhan commentedComment #9
chertzogJust reading the code (i didnt install), here are a couple of small things.
Line 77: variables should be prefixed with your module name. So, something like "project_estimator_file_extension" instead of a very generic "file_extension".
Also, you use "administer site configuration" for your access checks in project_estimator_menu(). A better practice would be to implement hook_perm(), and define your own permissions.
Comment #10
klausiThank you for your reviews. When finishing your review comments also set the issue status either to "needs work" (you found some problems with the project) or "reviewed & tested by the community" (you found no flaws).
manual revew:
require_once dirname(__FILE__) . '/mymodule.inc';.Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #11
ankitchauhan commentedhi guys
I have fixed all the points that is suggested in #9 and #10 except one....
"print $fname['file_name'];": file names should be considered user provided input and therefore need to be sanitized before printing.
@klausi can you please guide me what to do here.
Comment #12
klausiProject 1: http://drupal.org/node/1556812
Project 2: http://drupal.org/node/1539536
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
Comment #13
ankitchauhan commentedComment #13.0
ankitchauhan commentedproject description updated
Comment #14
avpaderno