Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Apparently terrible things will happen if somehow someone gets a CVS account that isn't deemed worthy of one. We can't give people new cvs accounts or they will run amok and create modules and themes that aren't up to standards. That's clearly a privilege reserved for people that already have CVS accounts.
In this case, annlewis is taking over maintenance of this module. Please grant her a cvs account so she can do so.
Comments
Comment #1
AjK commentedThe review process came into being simple because you are right. Without the basics of writing secure code more and more people were getting CVS accounts and then committing awfully insecure code (note the difference, I don't care about awful code which I see a lot of, I mean insecure code). In these circumstances it's the already overburdened Drupal Security Team that has to pick up the mess and fix it.
So the review process was instigated to try and help new applicants become security aware. Yes, security mistakes will still be made, we are human after all, but lets not try to allow them from ignorance.
The CVS application review process can however be avoided by, yes, sponsorship from existing maintainers, just like this one. If only people would read the instructions comments like this wouldn't be needed at all. It took 3 attempts to get you guys just to read the guidelines page (and then I still had to spell this out). Thanks for wasting my time explaining this to you when it's clearly already explained on the guidelines page (and there's a link on the application page to the guidelines and the two decline emails to Ann gave a direct link to that page).
Ann now has her account, have fun.
Comment #2
akalsey commented