Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2014 at 16:15 UTC
Updated:
11 Jul 2014 at 16:26 UTC
Jump to comment: Most recent
Comments
Comment #1
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
fabianderijkI've checked the code and added some small todo's. This is mostly comment stuff. The actual programmatic code looks good and is ready for production sites.
Comment #3
mehul.shah commentedThere are some errors & warnings reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxtomvv2183537git
Comment #4
gobinathmThere are issue reported by pareview.sh, please have these fixed.
Comment #5
fabianderijkThe code has been fixed.
Comment #6
fabianderijkComment #7
gobinathmJust checked preview & the issues are still present. Those needs to be resolved before moving this to RTBC
Comment #8
fabianderijkNow preview.sh does't show any errors anymore: http://pareview.sh/pareview/httpgitdrupalorgsandboxtomvv2183537git
Comment #9
gobinathmfabianderijk thanks for updating the issue. This application is still not ready for RTBC, as GIT brach naming starndards are not followed.
Follow the guide @ Release naming conventions and create appropriate name for your branches as per standard.
Follow the guide @ Setting a default branch and set appropriate default branch
Once the branch names are fixed you can change the STATUS of this issue to NEEDS REVIEW so that someone from the community will review & make it RTBC
Comment #10
tomvv commented7.x-1.x is now set as the main development branch. I changed this task status to Needs review.
Comment #11
fabianderijkI've just merged the develop & 7.x-1.x branch.
Comment #12
robin.ingelbrecht commentedThere is still a master branch, you have to delete it:
http://pareview.sh/pareview/httpgitdrupalorgsandboxtomvv2183537git
Comment #13
robin.ingelbrecht commentedComment #14
klausiThat is not an application blocker, please do a real manual review.
Comment #15
robin.ingelbrecht commentedKlausi,
i know, that is why I didn't put it in my own issue as a review.
Comment #16
gobinathmPlease delete branches other than 7.x-1.x (not a blocker thou)
Application Blocker
existing google_analytics - module already supports universal analytics. I don't understand the clear reason behind a new module to do the same task ? As you are aware our Drupal community strongly believe Collaboration rather than competition
Per the application description existing google analytics module is heavy !! can we quantify what does that mean ? how is it stated that existing module heavy ?
Ref :
https://drupal.org/contribute/development
https://drupal.org/node/23789
Comment #17
tomvv commentedThanks for your feedback. I am fully aware of collaboration importance. I cannot see why offering a module to the community can ever be seen as competition. I do agree that 'heavy' is perhaps not the right description for existing modules. The aim for this project is to have a module that focuses solely on Universal Analytics, especially with the use of dimensions, a specific Universal Analytics feature which cannot be found in the Google Analytics module at this moment. Furthermore, the Universal Analytics integration is still in dev state in the main Google Analytics module. Integration and cooperation with this module will be considered though. Still I believe at this point, other developers are looking for the features in this module as hard as I did before. This is why I think this module makes sense.
Comment #18
tomvv commentedI changed the description of the module in the project page, https://drupal.org/sandbox/tomvv/2183537. Also all branches other than 7.x-1.x were removed.
Comment #19
tomvv commentedComment #20
perignon commentedFrom a developer, site builder, and maintainers perspective I would rather see the cooperation happen now than creating yet another module for Google Analytics.
We already have problems on Drupal.org of modules that support the same services on the web but implement them in different ways. Case in point is the "Search API Solr" and "Apachesolr" modules. Luckily the two maintainers of those modules are starting to get together and hash a way forward.
So I would, as a developer, plead the case that this project here be put toward updating the existing Google Analytics module and not creating another module.
Comment #21
heddnIf that fails for whatever reason please get back to us and set this back to "needs review".
Comment #22
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.