The tl;dr: Our new preferred method of contributing changes is via GitHub pull requests, and all Puppet Labs developers will be submitting their changes for inclusion into the repository via pull request.
We will still be accepting changes via `rake mail_patches`, git-format-patch(1) & git-send-email(1), and attaching diffs to Redmine tickets, though these are not the preferred method. As I'm sure most people reading this have noticed, we've already arranged for puppet-dev to receive mail notifications of opened and closed pull requests. We've also been putting together a CONTRIBUTING.md file to be included in the repositories, with the idea that this will make it much easier for new people to find out what the preferred method of submitting a contribution is. This will also mean that changes to the contribution process will need to go through, at minimum, the same review process as merged code, so it should be more stable than when it was a wiki page. Another motivating factor behind having this CONTRIBUTING.md file, is that we've been wanting to move towards using GitHub pull requests as the primary means of submitting contributions. By moving to using pull requests primarily, the barrier to entry should be much lower for new contributors, and those less than intimately familiar with the intricacies of getting git-send-email(1) working with their particular email provider, and with Google Groups. In addition to lowering the barrier to entry, it should make tracking the status of contributions much more reliable. The full CONTRIBUTING.md file can be found in the repository[1], and it will have gone out to puppet-dev as an emailed patch shortly before this message. [1] https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md -- Jacob Helwig ,---- | Join us for PuppetConf, September 22nd and 23rd in Portland, OR | http://bit.ly/puppetconfsig `----
signature.asc
Description: Digital signature
