CVS edit link for PierreMunck

I am a drupal's developer, with 2 years of experience in drupal and 5 years in web developement.
I have got some modules who can made drupal's community stronger
like features_migrate to make feature for the migrate module and some otherelse
CommentFileSizeAuthor
#1 features_migrate.tar_.gz4.83 KBPierreMunck

Comments

PierreMunck’s picture

Issue tags: +features, +migrate
StatusFileSize
new4.83 KB

Description :

Export à Table Wizard and Migration to a feature.

depends

Table Wizard 6.x-1.3 http://drupal.org/project/tw
Migrate 6.x-1.1 http://drupal.org/project/migrate
Features 6.x-1.0 http://drupal.org/project/features
ctools 6.x-1.7 http://drupal.org/project/ctools

avpaderno’s picture

Component: Miscellaneous » new project application
Issue tags: -features, -migrate +Module review

Hello, and thank you for applying for a CVS account.

As per requirements, the motivation needs to include more than 2 sentences to describe the module features (the description should allow to understand the module features without to look at the code), and a comparison with the existing solutions.

I will report here a little checklist:

  • The code needs to follow the coding standards; check in particular the format used for the control structures, and the name given to PHP variables, Drupal persistent variables, functions defined from the module.
  • Files available from third-party sites should not be included within the module/theme. This is particularly true for files that are not licensed under GPL License v2, but it is also true for files that are licensed under the same license used by Drupal.
  • The license file should not be included as well; the packaging script already include that file. In any cases, the code for modules/themes committed in drupal.org repository needs to be released under the same license used by Drupal; any compatible license is not allowed.
  • Check the code passes the Coder validation.
zzolo’s picture

Status: Postponed (maintainer needs more info) » Postponed

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

  • The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
  • Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
avpaderno’s picture

Issue summary: View changes
Status: Postponed » Closed (won't fix)

As per previous comment, I am setting this issue as Won't fix.
Since new users can now create full projects, applications have a different purpose and they are handled on a different issue queue. See Apply for permission to opt into security advisory coverage for more information.