Jumpstart

Thanks for your contribution. I've done a quick look around at some other distributions I know are in a similar direction, but they don't include what I would call the same set of base modules. The jumpstart install profile works as advertised.

A few code stylistic things have been picked up by the automatic review bot:

It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:

• Remove the translations folder, translations are done on http://localize.drupal.org
• Remove "version" from the info file, it will be added by drupal.org packaging automatically.
• Drupal Code Sniffer has found some code style issues (please check the Drupal coding standards). See attachment.

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Go and review some other project applications, so we can get back to yours sooner.

Thanks I think you are there! A few final comments from my manual review:

• You should remove the commented lines in your info file. It is better for them not to be there
• I would suggest you consider changing the default name of the site from Development7 to Jumpstart Site or something similar

Other than that, I feel that these are minor issues and in my opinion shouldn't affect your profile from being made available, so I am going to mark this as RTBC. I believe other site builders will benefit from having this ready-to-go install profile. The only other comment I would have is it would possibly be good to also include a WYSIWYG editor in a future release (and provide default configuration for it). While this is not really a "developer" feature, many sites turn such functionality on for end users to edit content.

With regards to other project applications, certainly feel free to any applications and provide feedback. If you are confident the application meets the required standards, contains secure code, the project works, and demonstrates good API use then you can mark the project application RTBC. If not, provide advice to the applicants on how they can improve their code. They will be very happy for it :) I have personally found the feedback and hints I have received have been invaluable in improving my coding style, Drupal understanding and API awareness.

Review of the 7.x-1.x branch:

• Drupal Code Sniffer has found some code style issues (please check the Drupal coding standards).
  

  
  FILE: ...pace/drupal-7/sites/all/modules/pareview_temp/test_candidate/README.txt
  --------------------------------------------------------------------------------
  FOUND 0 ERROR(S) AND 1 WARNING(S) AFFECTING 1 LINE(S)
  --------------------------------------------------------------------------------
   58 | WARNING | Line exceeds 80 characters; contains 91 characters
  --------------------------------------------------------------------------------
  

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.

manual review:

• jumpstart_install(): what are the differences to the standard profile? You could add that in the function doc block.
• There is not really much self-written code here to review, so this project is too short to approve you as git vetted user. However, I have promoted this single project manually to a full project for you: http://drupal.org/project/jumpstart

Thanks for your contribution, bserem! Welcome to the community of project contributors on drupal.org.

Now that this experimental project has been promoted, you'll need to update the URL of your remote repository or reclone it.
http://drupal.org/project/jumpstart/git-instructions

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

As you continue to work on your module, keep in mind: Commit messages - providing history and credit and Release naming conventions.