discourse/chef/cookbooks/apt/CONTRIBUTING

If you would like to contribute, please open a ticket in JIRA:

* http://tickets.opscode.com

Create the ticket in the COOK project and use the cookbook name as the
component.

For all code contributions, we ask that contributors sign a
contributor license agreement (CLA). Instructions may be found here:

* http://wiki.opscode.com/display/chef/How+to+Contribute

When contributing changes to individual cookbooks, please do not
modify the version number in the metadata.rb. Also please do not
update the CHANGELOG.md for a new version. Not all changes to a
cookbook may be merged and released in the same versions. Opscode will
handle the version updates during the release process. You are welcome
to correct typos or otherwise make updates to documentation in the
README.

If a contribution adds new platforms or platform versions, indicate
such in the body of the commit message(s), and update the relevant
COOK ticket. When writing commit messages, it is helpful for others if
you indicate the COOK ticket. For example:

    git commit -m '[COOK-1041] Updated pool resource to correctly delete.'

In the ticket itself, it is also helpful if you include log output of
a successful Chef run, but this is not absolutely required.
Use chef-solo to install phantomjs into Vagrant VM. This introduces two configuration management runs into the Vagrant provisioning phase. The first chef-solo run ensures that a current version of chef is installed using the omnibus updater. The second chef-solo run installs vim and phantomjs. Much more is possible, this is a proof of concept. Cookbooks are stored in the chef directory, and managed by librarian-chef, which is like a bundler for cookbooks. Chef is run when VM is first downloaded and booted, but not on subsequent halt/up cycles. To force chef to run again, use `vagrant provision`. 2013-02-07 14:09:57 -05:00			`If you would like to contribute, please open a ticket in JIRA:`

			`* http://tickets.opscode.com`

			`Create the ticket in the COOK project and use the cookbook name as the`
			`component.`

			`For all code contributions, we ask that contributors sign a`
			`contributor license agreement (CLA). Instructions may be found here:`

			`* http://wiki.opscode.com/display/chef/How+to+Contribute`

			`When contributing changes to individual cookbooks, please do not`
			`modify the version number in the metadata.rb. Also please do not`
			`update the CHANGELOG.md for a new version. Not all changes to a`
			`cookbook may be merged and released in the same versions. Opscode will`
			`handle the version updates during the release process. You are welcome`
			`to correct typos or otherwise make updates to documentation in the`
			`README.`

			`If a contribution adds new platforms or platform versions, indicate`
			`such in the body of the commit message(s), and update the relevant`
			`COOK ticket. When writing commit messages, it is helpful for others if`
			`you indicate the COOK ticket. For example:`

			`git commit -m '[COOK-1041] Updated pool resource to correctly delete.'`

			`In the ticket itself, it is also helpful if you include log output of`
			`a successful Chef run, but this is not absolutely required.`