Closed (won't fix)
Project:
Drupal.org CVS applications
Component:
co-maintainer application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 Jun 2010 at 19:43 UTC
Updated:
27 Nov 2018 at 13:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
xarbot commentedComment #2
avpadernoHello, and thanks for applying for a CVS account.
If you were asked to become the co-maintainer of a module, then the current maintainer should have created an issue where he reported he accepted you as co-maintainer, and you should have reported the link of that issue here.
I am also happy if the current maintainer adds a comment here; without an explicit declaration of the current maintainer (private emails are not considered), this application cannot be accepted.
Comment #3
avpadernoComment #4
avpadernoPlease 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: