Closed (duplicate)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Jul 2010 at 10:05 UTC
Updated:
31 Mar 2019 at 08:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
promesI attached my plugin.
Comment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.
The archive doesn't contain a .info file, nor a .module file. As such, it cannot be considered a module.
Comment #3
promesThe uploaded plugin indeed is not a module but a plugin for module wysisyg, with all needed files. Since the maintainer of module wysisyg TwoD asked me to maintain this plugin and apply for a CVS account this is the only way to publish a plugin.
I understand this is the first application for a plugin. I hope the rules can be changed to become a maintainer of a plugin as well.
Comment #4
avpadernoYou can apply for a CVS if you have a module, or a theme, or an installation profile to commit; those are the only types of projects you can create on Drupal.org, and for which you can get a CVS account.
Comment #5
avpadernoComment #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