Closed (won't fix)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 May 2010 at 04:21 UTC
Updated:
2 Nov 2018 at 14:44 UTC
Jump to comment: Most recent
Comments
Comment #1
monan commentedI received email to upload a submission. I don't have a submission yet though as I'm applying for a co-maintainership...
Please see issue: http://drupal.org/node/803800
Thanks!
monan
Comment #2
avpadernoHello, and thanks for applying for a CVS account.
As the project has been marked as abandoned, I don't think the previous maintainer can approve you as co-maintainer. The module has a security issue; I think that in this case, the procedure to follow is slightly different.
Comment #3
monan commentedWe'd be glad to fix the module... It got marked as abandoned AFTER we applied for co-maintainership. As you can see here: http://drupal.org/node/803800, he is around and did approve.
Nothing to be done here?
Thanks...
Mike Monan
Comment #4
avpadernoThat's not correct. It has been marked as abandoned, and with a security issue, the day before you applied for a CVS account.
Anyway, as there is a report about a security issue, you needs to provide the code you want to commit in CVS, which will be reviewed from a member of the security team.
Comment #5
monan commentedOK... Maybe I didn't look at the project page directly ahead of applying for CVS. I guess we applied for co-maintainer in the issue queue the same day apparently, just after being marked as abandoned. I could have sworn that it was still good the day we put the CVS application in, but whatever.
We'll make the fix and send it to security@drupal.org.
After this is complete, will the project be marked as un-abandoned, and will we get CVS access at that point?
Thanks...
Mike Monan
Comment #6
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:
Comment #7
avpaderno