menu/vendor/ramsey/uuid/CONTRIBUTING...

Contributing

Contributions are welcome. We accept pull requests on GitHub.

This project adheres to a Contributor Code of Conduct. By participating in this project and its community, you are expected to uphold this code.

Team members

• Ben Ramsey - original author and maintainer
• Marijn Huizendveld - contributor, author of UUID type definition for Doctrine DBAL
• Thibaud Fabre - contributor, lead developer for version 3.0.0 re-architecture

Communication Channels

You can find help and discussion in the following places:

• GitHub Issues: https://github.com/ramsey/uuid/issues
• Wiki: https://github.com/ramsey/uuid/wiki

Reporting Bugs

Bugs are tracked in our project's issue tracker.

When submitting a bug report, please include enough information for us to reproduce the bug. A good bug report includes the following sections:

• Expected outcome
• Actual outcome
• Steps to reproduce, including sample code
• Any other information that will help us debug and reproduce the issue, including stack traces, system/environment information, and screenshots

Please do not include passwords or any personally identifiable information in your bug report and sample code.

Fixing Bugs

We welcome pull requests to fix bugs!

If you see a bug report that you'd like to fix, please feel free to do so. Following the directions and guidelines described in the "Adding New Features" section below, you may create bugfix branches and send us pull requests.

Adding New Features

If you have an idea for a new feature, it's a good idea to check out our issues or active pull requests first to see if the feature is already being worked on. If not, feel free to submit an issue first, asking whether the feature is beneficial to the project. This will save you from doing a lot of development work only to have your feature rejected. We don't enjoy rejecting your hard work, but some features just don't fit with the goals of the project.

When you do begin working on your feature, here are some guidelines to consider:

• Your pull request description should clearly detail the changes you have made. We will use this description to add to our CHANGELOG. If there is no description or it does not adequately describe your feature, we will ask you to update the description.
• We following the PSR-2 coding standard. Please ensure your code does, too.
• Please write tests for any new features you add.
• Please ensure that tests pass before submitting your pull request. We have Travis CI automatically running tests for pull requests. However, running the tests locally will help save time.
• Use topic/feature branches. Please do not ask us to pull from your master branch.
• Submit one feature per pull request. If you have multiple features you wish to submit, please break them up into separate pull requests.
• Send coherent history. Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

Running Tests

The following tests must pass before we will accept a pull request. If any of these do not pass, it will result in a complete build failure. Before you can run these, be sure to composer install.

composer test

Locally Test With Emulated MIPS Architecture

The following commands use Vagrant to start an Ubuntu VM, install necessary dependencies, and then run the tools/run-tests.sh script that will download a Docker image emulating the MIPS architecture. This is especially helpful for testing UUID generation in a big-endian environment.

vagrant init ubuntu/trusty64
vagrant up
vagrant ssh
sudo apt-get install docker.io qemu-user-static php5-cli php5-curl
cd /vagrant
curl -sS https://getcomposer.org/installer | php
php composer.phar install --no-interaction --prefer-dist
mkdir -p build/logs
ARCH=mips PHP_VERSION=5.6.14 TRAVIS_BUILD_DIR=/vagrant ./tools/run-tests.sh