rsuplido [rsuplido]

Hello, and thanks for applying for a CVS account.

In this case, you need to get the approval of the current maintainer of the module. If you didn't create a support request in the module queue, then create it; if you already created such report (and the maintainer accepted your offer), then report here the link to the support request.

Hm. Not sure whether I missed or forgot something, but, yes, there have been contributions to DrupalvB recently, but they were not sufficiently separated, documented, and polished to be directly committable without further adjustments. I'd be happy to add co-maintainers for DrupalvB, but we need to follow the best practices described in http://drupal.org/node/363367

There have not been replies in more than a week.

Please read the following links as this is very important information about CVS applications.

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for these applications. Please read Migrating from CVS Applications to (Git) Full Project Applications and Applying for permission to opt into security advisory coverage on how this affects and benefits you and the application process. In short, every user has now the permissions necessary to create new projects, but they need to apply for opt into security advisory coverage. Without applying, the projects will have a warning on projects that says:

This project is not covered by Drupal’s security advisory policy.