WIP - add testing capabilities

Author: mikebronner

.travis.yml

@@ -0,0 +1,17 @@
+language: php
+
+php:
+    - 7.0
+    - 7.1
+
+before_script:
+    - travis_retry composer self-update
+    - travis_retry composer install --no-interaction --prefer-source --dev
+
+script:
+  - ./vendor/bin/phpunit --coverage-text --coverage-clover ./build/logs/clover.xml
+
+after_script:
+  - php vendor/bin/coveralls
+  - wget https://scrutinizer-ci.com/ocular.phar
+  - php ocular.phar code-coverage:upload --format=php-clover ./build/logs/clover.xml

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# How to contribute
+We welcome everyone to submit pull requests with:
+- fixes for issues
+- change suggestions
+- updateing of documentation
+
+However, not every pull request will automatically be accepted. I will review each carefully to make sure it is in line with
+ the direction I want the package to continue in. This might mean that some pull requests are not accepted, or might stay
+ unmerged until a place for them can be determined.
+
+## Testing
+- [ ] After making your changes, make sure the tests still pass.
+- [ ] When adding new functionality, also add new tests.
+- [ ] Make sure there are no build errors on our CI server (https://ci.genealabs.com/build-status/view/7)
+- [ ] All code must past PHPCS and PHPMD PSR2 validation.
+
+## Submitting changes
+When submitting a pull request, it is important to make sure to complete the following:
+- [ ] Add a descriptive header that explains in a single scentence what problem the PR solves.
+- [ ] Add a detailed description with animated screengrab GIFs vidualizing how it works.
+- [ ] Explain why you think it should be implemented one way vs. another, highlight performance improvements, etc.
+
+## Coding conventions
+Start reading our code and you'll get the hang of it. We optimize for readability:
+- indent using four spaces (soft tabs)
+- use Blade for all views
+- avoid logic in views, put it in controllers or service classes
+- ALWAYS put spaces after list items and method parameters (`[1, 2, 3]`, not `[1,2,3]`), around operators (`x += 1`, not `x+=1`), and around hash arrows.
+- this is open source software. Consider the people who will read your code, and make it look nice for them. It's sort of like driving a car: Perhaps you love doing donuts when you're alone, but with passengers the goal is to make the ride as smooth as possible.
+- emphasis readability of code over patterns to reduce mental debt
+- always add an empty line around structures (if statements, loops, etc.)
+
+Thanks!
+Mike Bronner, GeneaLabs

ISSUE_TEMPLATE.md

@@ -0,0 +1,18 @@
+# Issue
+*summarize your issue here*
+
+## Environment
+Laravel Version: *x.y.z*
+Laravel Messenger Package Version: *x.y.z*
+PHP Version: *x.y.z*
+Homestead Version: *x.y*
+Operating System & Version: *name x.y.z*
+
+## Stack Trace
+- [ ] I have cleared my Laravel log file.
+- [ ] I have then reproduced my issue.
+- [ ] I have copied the __first__ listed stack trace from the fresh log file.
+
+```
+*paste the first stack trace here*
+```

README.md

@@ -1,6 +1,12 @@
 ** DO NOT INSTALL -- STILL IN EXPERIMENTAL STAGE**
 
-# Laravel-cached-models
+# Model Caching for Laravel
+[![Travis](https://img.shields.io/travis/GeneaLabs/laravel-model-caching.svg)](https://travis-ci.org/GeneaLabs/laravel-model-caching)
+[![SensioLabs Insight](https://img.shields.io/sensiolabs/i/fde269ac-c382-4d17-a647-c69ad6b9dd85.svg)](https://insight.sensiolabs.com/projects/fde269ac-c382-4d17-a647-c69ad6b9dd85)
+[![Scrutinizer](https://img.shields.io/scrutinizer/g/GeneaLabs/laravel-model-caching.svg)](https://scrutinizer-ci.com/g/GeneaLabs/laravel-model-caching)
+[![Coveralls](https://img.shields.io/coveralls/GeneaLabs/laravel-model-caching.svg)](https://coveralls.io/github/GeneaLabs/laravel-model-caching)
+[![GitHub (pre-)release](https://img.shields.io/github/release/GeneaLabs/laravel-model-caching/all.svg)](https://github.com/GeneaLabs/laravel-model-caching)
+[![Packagist](https://img.shields.io/packagist/dt/GeneaLabs/laravel-model-caching.svg)](https://packagist.org/packages/genealabs/laravel-model-caching)
 
 ## Features
 - automatic relationship caching.