Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2011 at 02:33 UTC
Updated:
20 Jan 2012 at 14:40 UTC
Do a Barrel Roll is a Drupal 7 module that provides the same functionality you can find on Google if you search for 'do a barrel roll': the HTML body spins 360 degrees of CSS 3 awesomeness. It is a small module, depends on search and isn't very usfeul, it is just funny.
It is available at my sandbox: http://drupal.org/sandbox/barraponto/1336130
Comments
Comment #1
doitDave commentedHi barraponto,
coder results look good, there is one really small issue:
Two personal notes aside:
Good luck!
Comment #2
barrapontoOk, I've commited Doxygen documentation to the .module file.
As for CSS3, it is the *only* thing this module does. I believe it should be clearer in the module description, although it already states it relies on CSS 3 and won't work on IE.
Comment #3
doitDave commentedHi, looks fixed for me. Let's wait for more comments.
As for CSS3, this was really but a personal opinion aside reviewing. Decisions like this are of course up to a site admin and, even more, his intended audience ;)
Anyhow, keep in mind that "does not work on IE" is really not the only implication that may come up until the offiicial W3C release of CSS3.
Comment #4
nmudgal commentedIt appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Please report any bugs to klausi.
Comment #5
barrapontoUpdated, no more errors/warnings in Coder, moved code to 7.x-1.x branch, cleaned up master branch and added a README.txt file.
Comment #6
elc commentedAmusing as this is, is there any reason why you didn't throw one of your more worthwhile modules into the submission queue? There's not enough in this module to actually get a feel for your coding, project handling, git use or understanding of Drupal APIs and security issues.
For a reviewer to actually get an idea of those properties, they are going to have to go off to the other works you have and go from there.
A least I had some fun making google spin the page. Any change of a D6 port :P
Comment #7
klausiI agree with ELC - can't we review a bigger project of yours? Please close this issue if you agree and open a new one for that other project. Other input is welcome as well of course.
Comment #8
barrapontoOk, I will provide another project.
Comment #9
barrapontoSince wontfixing, I have added a settings form (using Forms API, Menu API) with custom permissions and wrote proper javascript using Drupal.behaviors and Drupal.settings.
So, do I need to provide another module? I am a regular at some issue queues like Zen, Tao, Views, Core and Display Suite. Does it help if I get someone to vouch for me?
Comment #10
jthorson commentedThough this is a rather small module, it's also very clean ... and barraponto's post/commit history speaks for itself - clean projects, proper use of javascript behaviours and other APIs, a custom theme, node form columns co-maintainer, and some cutting edge SASS stuff in the sandbox.
I also would have preferred to have seen a larger project submitted (such as the Compass plugin) ... but after attempting to actually look through the Compass sandbox, I realized that it probably would get caught up in this process for weeks as we waited for a front-end reviewer who is familiar with the techniques.
Based on this conclusion, the application code, community activity and post/commit history; combined with what I saw in barraponto's other sandbox projects, I wouldn't have any issues with marking this one as RTBC.
Comment #11
barraponto@jthorson I tried submitting Compass Drupal Plugin first, but it's not a module, it is more of a Theme helper just as Drush is a Drupal helper. Due to not being a theme, nor a module, nor anything in between, I had a bad time trying to get it approved (and of course there is a lack of SASS/Compass-savvy reviewers). See #969842
I'll find some time to review applications front end coding.
Comment #12
klausiAlthough this module on its own is a little small to approve you, I agree with jthorson that your other work is enough.
Thanks for your contribution, barraponto! 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.
Comment #13
barraponto@klausi thanks a lot, I have already started reviewing: #1291488: Spanish Installation Profile