Closed (won't fix)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Mar 2010 at 19:01 UTC
Updated:
21 Oct 2018 at 17:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kpbowler commentedUploading the module.
Comment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review your code, pointing out what needs to be changed.
As per http://drupal.org/cvs-application/requirements, the motivation message should be expanded to contain more details about the features of the proposed module, and it should include also a comparison with the existing solutions.
Comment #3
kpbowler commentedThanks, I am currently reviewing several contrib modules to see how mine compares. I'll post again when I know more.
Comment #4
kpbowler commentedIt does seem that the ThemeKey module does all this and more...
I think I may have to concede and use that module instead. Would be silly to replicate the functionality of a very good module.
Comment #5
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: