[D7] DrupalVagrant

Vagrant Setup process information will be better to read and understand if given in Step wise format.

Git clone failed for http://git.drupal.org/sandbox/ssdas/2551571.git while invoking http://pareview.sh/pareview/httpgitdrupalorgsandboxssdas2551571git

Git clone failed. Aborting.

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

I have tried clone repo...it gave.
$ git clone --branch 7.x-1.x http://git.drupal.org/sandbox/ssdas/2551571.git
Cloning into '2551571'...
fatal: repository 'http://git.drupal.org/sandbox/ssdas/2551571.git/' not found

Fixed the git clone URL in the issue summary for non-maintainer users.

I'm a robot and this is an automated message from Project Applications Scraper.

Vagrant Box Setup Successfully with
Services and Packages installed and running.

• Samba
• Apache
• MySql
• Mongo DB
• Elastic Search
• PHP
• Drush Utility
• Composer
• Jenkins

@SoumyaDas: Thanks for adding me as contributor.

Great work !!!

Its very useful contribution and all is working as per requirement , very easy to setup compare to VDD and I would be suggest to add MemCache and other debugging tools.

It's working fine for me.

@deepakjoshi You are correct it is very easy to setup as compare to VDD and We can also provision our own setup through vagrantfile. It will very useful if we add Drupal build script along with the setup.

Change the name to [D7] Vagrant Shell Provisioned

@rakesh.gectcr: Anyone can change the issue title, this is surely not an application blocker. Please do a manual review of the code.

Doing a manual code review; I got a big question:

II line 51: you're syncing a Windows folder. Why is it hardcoded? I mean, I use Linux, other devs use mac; but this is only taking in account Windows users. It's just a question; I really want to know.

Nice work, thanks for your contribution.

This isn't a Drupal module or theme, but a setup script for Vagrant Box. I am not even sure that this sort of thing belongs in the Drupal.org repo. The CLI tool drush (a fairly important tool for the Drupal community) is hosted on Github: https://github.com/drush-ops/drush

But I leave it to the git admin who does the final review to make that call.

You should not push to the repo with .gitignore included (make it ignore itself).

The bash script is mostly sudo commands to install stuff it pulls from the net. I am a Drupal developer, not a CentOS system manager, so I may have overlooked something, but didn't see any red flags.

There isn't a single line of code that interacts with Drupal in the repo (it consists of a bash script + a configuration file) - so I am adding the Single project promote-tag - as there is 0 lines of PHP code and 0 Drupal functions in the application - but I don't see what more there is to review, so I am setting its status to RTBC.

Before this is promoted, it should also be checked by a git admin that is also a CentOS system manager and knows about security in CentOS on the CLI-level.

PS: I deliberately haven't added the [D7] to the issue summary, as the virtual machine it creates should be capable of running any version of Drupal.

@Yogesh Pawar,
this project is not Drupal 7. his isn't even a Drupal module or theme, but a setup script for Vagrant Box.

It makes no sense to have a Drupal version indicator in the title.

I agree with gisle.
The project application is done to see if the user understood how to write a module or theme, but this application is done with a Bash script, so we cannot say the OP knows how to write a module or a theme. There is no way for saying the OP shows to know how to use the Drupal API, what the Drupal coding standards are, or how to implement a hook.

We do a single project promotion in this case.

I have promoted the project to full project (https://www.drupal.org/project/vagrant_for_drupal).

Here are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thank you, 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.

Thanks go the dedicated reviewer(s) as well.