-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit fdf60e9
Showing
98 changed files
with
17,115 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
.vagrant/ | ||
vendor/ | ||
config/development.config.php | ||
data/cache/* | ||
!data/cache/.gitkeep | ||
phpunit.xml | ||
/vendor | ||
/.vagrant | ||
phpunit.xml | ||
/Homestead.yaml | ||
/Homestead.json | ||
/after.sh | ||
/aliases |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
language: php | ||
|
||
php: | ||
- 7.0 | ||
- 7.1 | ||
- 7.2 | ||
|
||
before_script: | ||
- phpenv config-rm xdebug.ini | ||
- composer install --no-interaction | ||
|
||
script: | ||
- vendor/bin/phpunit | ||
|
||
matrix: | ||
include: | ||
- php: 5.6 | ||
env: dependencies=lowest | ||
allow_failures: | ||
- php: 5.6 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Contributor Code of Conduct | ||
|
||
The Zend Framework project adheres to [The Code Manifesto](http://codemanifesto.com) | ||
as its guidelines for contributor interactions. | ||
|
||
## The Code Manifesto | ||
|
||
We want to work in an ecosystem that empowers developers to reach their | ||
potential — one that encourages growth and effective collaboration. A space that | ||
is safe for all. | ||
|
||
A space such as this benefits everyone that participates in it. It encourages | ||
new developers to enter our field. It is through discussion and collaboration | ||
that we grow, and through growth that we improve. | ||
|
||
In the effort to create such a place, we hold to these values: | ||
|
||
1. **Discrimination limits us.** This includes discrimination on the basis of | ||
race, gender, sexual orientation, gender identity, age, nationality, technology | ||
and any other arbitrary exclusion of a group of people. | ||
2. **Boundaries honor us.** Your comfort levels are not everyone’s comfort | ||
levels. Remember that, and if brought to your attention, heed it. | ||
3. **We are our biggest assets.** None of us were born masters of our trade. | ||
Each of us has been helped along the way. Return that favor, when and where | ||
you can. | ||
4. **We are resources for the future.** As an extension of #3, share what you | ||
know. Make yourself a resource to help those that come after you. | ||
5. **Respect defines us.** Treat others as you wish to be treated. Make your | ||
discussions, criticisms and debates from a position of respectfulness. Ask | ||
yourself, is it true? Is it necessary? Is it constructive? Anything less is | ||
unacceptable. | ||
6. **Reactions require grace.** Angry responses are valid, but abusive language | ||
and vindictive actions are toxic. When something happens that offends you, | ||
handle it assertively, but be respectful. Escalate reasonably, and try to | ||
allow the offender an opportunity to explain themselves, and possibly correct | ||
the issue. | ||
7. **Opinions are just that: opinions.** Each and every one of us, due to our | ||
background and upbringing, have varying opinions. The fact of the matter, is | ||
that is perfectly acceptable. Remember this: if you respect your own | ||
opinions, you should respect the opinions of others. | ||
8. **To err is human.** You might not intend it, but mistakes do happen and | ||
contribute to build experience. Tolerate honest mistakes, and don't hesitate | ||
to apologize if you make one yourself. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,220 @@ | ||
# CONTRIBUTING | ||
|
||
## RESOURCES | ||
|
||
If you wish to contribute to Zend Framework, please be sure to | ||
read/subscribe to the following resources: | ||
|
||
- [Coding Standards](https://github.com/zendframework/zf2/wiki/Coding-Standards) | ||
- [Contributor's Guide](http://framework.zend.com/participate/contributor-guide) | ||
- ZF Contributor's mailing list: | ||
Archives: http://zend-framework-community.634137.n4.nabble.com/ZF-Contributor-f680267.html | ||
Subscribe: [email protected] | ||
- ZF Contributor's IRC channel: | ||
#zftalk.dev on Freenode.net | ||
|
||
If you are working on new features or refactoring [create a proposal](https://github.com/zendframework/ZendSkeletonApplication/issues/new). | ||
|
||
## Reporting Potential Security Issues | ||
|
||
If you have encountered a potential security vulnerability, please **DO NOT** report it on the public | ||
issue tracker: send it to us at [[email protected]](mailto:[email protected]) instead. | ||
We will work with you to verify the vulnerability and patch it as soon as possible. | ||
|
||
When reporting issues, please provide the following information: | ||
|
||
- Component(s) affected | ||
- A description indicating how to reproduce the issue | ||
- A summary of the security vulnerability and impact | ||
|
||
We request that you contact us via the email address above and give the project | ||
contributors a chance to resolve the vulnerability and issue a new release prior | ||
to any public exposure; this helps protect users and provides them with a chance | ||
to upgrade and/or update in order to protect their applications. | ||
|
||
For sensitive email communications, please use [our PGP key](http://framework.zend.com/zf-security-pgp-key.asc). | ||
|
||
## RUNNING TESTS | ||
|
||
First, use [Composer](https://getcomposer.org) to install all dependencies: | ||
|
||
```bash | ||
$ composer install | ||
``` | ||
|
||
Make sure that `zendframework/zend-test` is installed: | ||
|
||
```bash | ||
$ composer require --dev zendframework/zend-test | ||
``` | ||
|
||
To run tests: | ||
|
||
```bash | ||
$ composer test | ||
``` | ||
|
||
You can turn on conditional tests with the `phpunit.xml` file. | ||
To do so: | ||
|
||
- Copy `phpunit.xml.dist` file to `phpunit.xml` | ||
- Edit `phpunit.xml` to enable any specific functionality you | ||
want to test, as well as to provide test values to utilize. | ||
|
||
## Running Coding Standards Checks | ||
|
||
First, ensure you've installed dependencies via composer: | ||
|
||
```bash | ||
$ composer require --dev squizlabs/php_codesniffer | ||
``` | ||
|
||
To run CS checks only: | ||
|
||
```console | ||
$ composer cs-check | ||
``` | ||
|
||
To attempt to automatically fix common CS issues: | ||
|
||
```console | ||
$ composer cs-fix | ||
``` | ||
|
||
If the above fixes any CS issues, please re-run the tests to ensure | ||
they pass, and make sure you add and commit the changes after verification. | ||
|
||
## Recommended Workflow for Contributions | ||
|
||
Your first step is to establish a public repository from which we can | ||
pull your work into the master repository. We recommend using | ||
[GitHub](https://github.com), as that is where the component is already hosted. | ||
|
||
1. Setup a [GitHub account](http://github.com/), if you haven't yet | ||
2. Fork the repository (http://github.com/zendframework/ZendSkeletonApplication) | ||
3. Clone the canonical repository locally and enter it. | ||
|
||
```bash | ||
$ git clone https://github.com/zendframework/ZendSkeletonApplication.git | ||
$ cd ZendSkeletonApplication | ||
``` | ||
|
||
4. Add a remote to your fork; substitute your GitHub username in the command | ||
below. | ||
|
||
```bash | ||
$ git remote add {username} [email protected]:{username}/ZendSkeletonApplication.git | ||
$ git fetch {username} | ||
``` | ||
|
||
### Keeping Up-to-Date | ||
|
||
Periodically, you should update your fork or personal repository to | ||
match the canonical ZF repository. Assuming you have setup your local repository | ||
per the instructions above, you can do the following: | ||
|
||
|
||
```bash | ||
$ git checkout master | ||
$ git fetch origin | ||
$ git rebase origin/master | ||
# OPTIONALLY, to keep your remote up-to-date - | ||
$ git push {username} master:master | ||
``` | ||
|
||
If you're tracking other branches -- for example, the "develop" branch, where | ||
new feature development occurs -- you'll want to do the same operations for that | ||
branch; simply substitute "develop" for "master". | ||
|
||
### Working on a patch | ||
|
||
We recommend you do each new feature or bugfix in a new branch. This simplifies | ||
the task of code review as well as the task of merging your changes into the | ||
canonical repository. | ||
|
||
A typical workflow will then consist of the following: | ||
|
||
1. Create a new local branch based off either your master or develop branch. | ||
2. Switch to your new local branch. (This step can be combined with the | ||
previous step with the use of `git checkout -b`.) | ||
3. Do some work, commit, repeat as necessary. | ||
4. Push the local branch to your remote repository. | ||
5. Send a pull request. | ||
|
||
The mechanics of this process are actually quite trivial. Below, we will | ||
create a branch for fixing an issue in the tracker. | ||
|
||
```bash | ||
$ git checkout -b hotfix/9295 | ||
Switched to a new branch 'hotfix/9295' | ||
``` | ||
|
||
... do some work ... | ||
|
||
|
||
```bash | ||
$ git commit | ||
``` | ||
|
||
... write your log message ... | ||
|
||
|
||
```bash | ||
$ git push {username} hotfix/9295:hotfix/9295 | ||
Counting objects: 38, done. | ||
Delta compression using up to 2 threads. | ||
Compression objects: 100% (18/18), done. | ||
Writing objects: 100% (20/20), 8.19KiB, done. | ||
Total 20 (delta 12), reused 0 (delta 0) | ||
To ssh://[email protected]/{username}/ZendSkeletonApplication.git | ||
b5583aa..4f51698 HEAD -> master | ||
``` | ||
|
||
To send a pull request, you have two options. | ||
|
||
If using GitHub, you can do the pull request from there. Navigate to | ||
your repository, select the branch you just created, and then select the | ||
"Pull Request" button in the upper right. Select the user/organization | ||
"zendframework" as the recipient. | ||
|
||
If using your own repository - or even if using GitHub - you can use `git | ||
format-patch` to create a patchset for us to apply; in fact, this is | ||
**recommended** for security-related patches. If you use `format-patch`, please | ||
send the patches as attachments to: | ||
|
||
- [email protected] for patches without security implications | ||
- [email protected] for security patches | ||
|
||
#### What branch to issue the pull request against? | ||
|
||
Which branch should you issue a pull request against? | ||
|
||
- For fixes against the stable release, issue the pull request against the | ||
"master" branch. | ||
- For new features, or fixes that introduce new elements to the public API (such | ||
as new public methods or properties), issue the pull request against the | ||
"develop" branch. | ||
|
||
### Branch Cleanup | ||
|
||
As you might imagine, if you are a frequent contributor, you'll start to | ||
get a ton of branches both locally and on your remote. | ||
|
||
Once you know that your changes have been accepted to the master | ||
repository, we suggest doing some cleanup of these branches. | ||
|
||
- Local branch cleanup | ||
|
||
```bash | ||
$ git branch -d <branchname> | ||
``` | ||
|
||
- Remote branch removal | ||
|
||
```bash | ||
$ git push {username} :<branchname> | ||
``` | ||
|
||
## Conduct | ||
|
||
Please see our [CONDUCT.md](CONDUCT.md) to understand expected behavior when interacting with others in the project. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
FROM php:7.0-apache | ||
|
||
RUN apt-get update \ | ||
&& apt-get install -y git zlib1g-dev \ | ||
&& docker-php-ext-install zip \ | ||
&& a2enmod rewrite \ | ||
&& sed -i 's!/var/www/html!/var/www/public!g' /etc/apache2/sites-available/000-default.conf \ | ||
&& mv /var/www/html /var/www/public \ | ||
&& curl -sS https://getcomposer.org/installer \ | ||
| php -- --install-dir=/usr/local/bin --filename=composer | ||
|
||
WORKDIR /var/www |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
Copyright (c) 2005-2016, Zend Technologies USA, Inc. | ||
|
||
All rights reserved. | ||
|
||
Redistribution and use in source and binary forms, with or without modification, | ||
are permitted provided that the following conditions are met: | ||
|
||
- Redistributions of source code must retain the above copyright notice, | ||
this list of conditions and the following disclaimer. | ||
|
||
- Redistributions in binary form must reproduce the above copyright notice, | ||
this list of conditions and the following disclaimer in the documentation | ||
and/or other materials provided with the distribution. | ||
|
||
- Neither the name of Zend Technologies USA, Inc. nor the names of its | ||
contributors may be used to endorse or promote products derived from this | ||
software without specific prior written permission. | ||
|
||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND | ||
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED | ||
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE | ||
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR | ||
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES | ||
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; | ||
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON | ||
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT | ||
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS | ||
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
Oops, something went wrong.