Merge branch 'release/1.0.0'

Author: bbriatte

.gitattributes

@@ -0,0 +1,6 @@
+fastlane/* linguist-vendored
+*.rb linguist-vendored
+Podfile* linguist-vendored
+Gemfile* linguist-vendored
+Brewfile* linguist-vendored
+*.podspec linguist-vendored

.gitignore

@@ -43,7 +43,7 @@ playground.xcworkspace
 # you should judge for yourself, the pros and cons are mentioned at:
 # https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
 #
-# Pods/
+Pods/
 
 # Carthage
 #
@@ -63,3 +63,13 @@ fastlane/report.xml
 fastlane/Preview.html
 fastlane/screenshots
 fastlane/test_output
+fastlane/xcov_report
+
+## Ruby specific
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+Gemfile.lock
+
+# Environment normalization:
+/.bundle/
+/vendor/bundle

.swiftlint.yml

@@ -0,0 +1,2 @@
+line_length: 200
+file_length: 500

.travis.yml

@@ -0,0 +1,20 @@
+osx_image: xcode8.2
+language: objective-c
+cache:
+  - bundler
+  - cocoapods
+branches:
+  only:
+    - develop
+    - master
+notifications:
+  email: false
+before_install:
+  - gem install bundler
+  - bundle update && brew update
+  - bundle install && brew bundle
+  - bundle exec pod repo update --silent
+script:
+  - bundle exec fastlane run_tests
+after_success:
+  - bundle exec fastlane ci_framework_deploy

Brewfile

@@ -0,0 +1,2 @@
+brew 'swiftlint'
+brew 'git-flow'

CHANGELOG.md

@@ -0,0 +1,4 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+`parallax-view-controller-transition-swift` adheres to [Semantic Versioning](http://semver.org/).

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]](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and 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,94 @@
+# Contributing to parallax-view-controller-transition-swift
+
+First off, thanks for taking the time to contribute! :tada::+1:
+
+The following is a set of guidelines for contributing to Digipolitan and its packages, which are hosted in the [Digipolitan Organization](https://github.com/digipolitan) on GitHub.
+These are just guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+
+#### Table Of Contents
+
+[What should I know before I get started?](#what-should-i-know-before-i-get-started)
+  * [Code of Conduct](#code-of-conduct)
+
+[How Can I Contribute?](#how-can-i-contribute)
+  * [Reporting Bugs](#reporting-bugs)
+
+## What should I know before I get started?
+
+### Code of Conduct
+
+This project adheres to the Contributor Covenant [code of conduct](CODE_OF_CONDUCT.md).
+By participating, you are expected to uphold this code.
+Please report unacceptable behavior to [[email protected]](mailto:[email protected]).
+
+### Reporting Bugs
+
+This section guides you through submitting a bug report for Digipolitan. Following these guidelines helps maintainers and the community understand your report :pencil:, reproduce the behavior :computer: :computer:, and find related reports :mag_right:.
+
+Before creating bug reports, please check [this list](#before-submitting-a-bug-report) as you might find out that you don't need to create one. When you are creating a bug report, please [include as many details as possible](#how-do-i-submit-a-good-bug-report). If you'd like, you can use [this template](#template-for-submitting-bug-reports) to structure the information.
+
+#### Before Submitting A Bug Report
+
+* **Perform a [search](https://github.com/issues?q=+is%3Aissue+user%3Adigipolitan)** to see if the problem has already been reported. If it has, add a comment to the existing issue instead of opening a new one.
+
+#### How Do I Submit A (Good) Bug Report?
+
+Bugs are tracked as [GitHub issues](https://guides.github.com/features/issues/). After you've determined
+
+Explain the problem and include additional details to help maintainers reproduce the problem:
+
+* **Use a clear and descriptive title** for the issue to identify the problem.
+* **Describe the exact steps which reproduce the problem** in as many details as possible.
+* **Provide specific examples to demonstrate the steps**. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use [Markdown code blocks](https://help.github.com/articles/markdown-basics/#multiple-lines).
+* **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
+* **Explain which behavior you expected to see instead and why.**
+* **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem.
+* **If you're reporting that parallax-view-controller-transition-swift crashed**, include a crash report with a stack trace from the operating system. On iOS, the crash report is available in Xcode, on macOS, the crash report will be available in `Console.app` under "Diagnostic and usage information" > "User diagnostic reports". Include the crash report in the issue in a [code block](https://help.github.com/articles/markdown-basics/#multiple-lines), a [file attachment](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/), or put it in a [gist](https://gist.github.com/) and provide link to that gist.
+* **If the problem is related to performance**, include a CPU profile capture and a screenshot with your report.
+* **If the problem wasn't triggered by a specific action**, describe what you were doing before the problem happened and share more information using the guidelines below.
+
+Provide more context by answering these questions:
+
+* **Did the problem start happening recently** (e.g. after updating to a new version of parallax-view-controller-transition-swift) or was this always a problem?
+* If the problem started happening recently, **can you reproduce the problem in an older version of parallax-view-controller-transition-swift ?** What's the most recent version in which the problem doesn't happen? You can download older versions of parallax-view-controller-transition-swift from [the releases page](https://github.com/digipolitan/parallax-view-controller-transition-swift/releases).
+* **Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
+
+Include details about your configuration and environment:
+
+* **Which version of parallax-view-controller-transition-swift are you using?
+* **What's the name and version of the macOS or iOS you're using**?
+
+#### Template For Submitting Bug Reports
+
+    [Short description of problem here]
+
+    **Reproduction Steps:**
+
+    1. [First Step]
+    2. [Second Step]
+    3. [Other Steps...]
+
+    **Expected behavior:**
+
+    [Describe expected behavior here]
+
+    **Observed behavior:**
+
+    [Describe observed behavior here]
+
+    **Screenshots and GIFs**
+
+    ![Screenshots and GIFs which follow reproduction steps to demonstrate the problem](url)
+
+    **parallax-view-controller-transition-swift version:** [Enter parallax-view-controller-transition-swift version here]
+    **OS and version:** [Enter macOS / iOS / linux name and version here]
+
+    **Installed packages:**
+
+    [List of installed packages here]
+
+    **Additional information:**
+
+    * Problem started happening recently, didn't happen in an older version of parallax-view-controller-transition-swift: [Yes/No]
+    * Problem can be reliably reproduced, doesn't happen randomly: [Yes/No]
+    * Problem happens with all files and projects, not only some files or projects: [Yes/No]

DGParallaxViewControllerTransition.podspec

@@ -0,0 +1,13 @@
+Pod::Spec.new do |s|
+s.name = "DGParallaxViewControllerTransition"
+s.version = "1.0.0"
+s.summary = "Parallax interactive transition during UIViewController presentation"
+s.homepage = "https://github.com/Digipolitan/parallax-view-controller-transition-swift"
+s.authors = "Digipolitan"
+s.source = { :git => "https://github.com/Digipolitan/parallax-view-controller-transition-swift.git", :tag => "v#{s.version}" }
+s.license = { :type => "BSD", :file => "LICENSE" }
+s.source_files = 'Sources/**/*.{swift,h}'
+s.ios.deployment_target = '8.0'
+s.tvos.deployment_target = '9.0'
+s.requires_arc = true
+end