Initial commit

.github/workflows/maven.yml

@@ -0,0 +1,18 @@
+name: Orion Build
+
+on: [pull_request]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+    - name: Set up JDK 1.8
+      uses: actions/setup-java@v1
+      with:
+        java-version: 1.8
+    - name: Setup NPM
+      run: echo "deb https://deb.nodesource.com/node_12.x bionic main" > /etc/apt/sources.list.d/nodesource.list && curl -s -k https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add - && apt-get update && apt-get install -y nodejs && rm -rf /var/lib/apt/lists/*
+    - name: Build with Maven
+      run: mvn -B package --file pom.xml

.gitignore

@@ -0,0 +1,121 @@
+*.class
+
+.DS_Store*
+
+# Mobile Tools for Java (J2ME)
+.mtj.tmp/
+
+# Package Files #
+*.jar
+*.war
+*.ear
+
+node_modules/*
+node_modules
+yarn.lock
+package-lock.json
+
+dist/
+build/
+
+# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
+hs_err_pid*
+/target/
+
+.metadata
+bin/
+tmp/
+*.tmp
+*.bak
+*.swp
+*~.nib
+local.properties
+.settings/
+.loadpath
+.recommenders
+
+# Eclipse Core
+.project
+
+# External tool builders
+.externalToolBuilders/
+
+# Locally stored "Eclipse launch configurations"
+*.launch
+
+# PyDev specific (Python IDE for Eclipse)
+*.pydevproject
+
+# CDT-specific (C/C++ Development Tooling)
+.cproject
+
+# JDT-specific (Eclipse Java Development Tools)
+.classpath
+
+# Java annotation processor (APT)
+.factorypath
+
+# PDT-specific (PHP Development Tools)
+.buildpath
+
+# sbteclipse plugin
+.target
+
+# Tern plugin
+.tern-project
+
+# TeXlipse plugin
+.texlipse
+
+# STS (Spring Tool Suite)
+.springBeans
+
+# Code Recommenders
+.recommenders/
+
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and Webstorm
+# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
+
+# User-specific stuff:
+.idea/workspace.xml
+.idea/tasks.xml
+.idea/dictionaries
+.idea/vcs.xml
+.idea/jsLibraryMappings.xml
+
+# Sensitive or high-churn files:
+.idea/dataSources.ids
+.idea/dataSources.xml
+.idea/dataSources.local.xml
+.idea/sqlDataSources.xml
+.idea/dynamic.xml
+.idea/uiDesigner.xml
+
+# Gradle:
+.idea/gradle.xml
+.idea/libraries
+
+# Mongo Explorer plugin:
+.idea/mongoSettings.xml
+
+## File-based project format:
+*.iws
+
+## Plugin-specific files:
+
+# IntelliJ
+/out/
+.idea/
+*.iml
+
+# mpeltonen/sbt-idea plugin
+.idea_modules/
+
+# JIRA plugin
+atlassian-ide-plugin.xml
+
+# Crashlytics plugin (for Android Studio and IntelliJ)
+com_crashlytics_export_strings.xml
+crashlytics.properties
+crashlytics-build.properties
+fabric.properties

ADOPTERS.md

@@ -0,0 +1,7 @@
+# Adopters
+
+This is an alphabetical list of people and organizations who are using this
+project. If you'd like to be included here, please send a Pull Request that
+adds your information to this file.
+
+- [Pinterest](https://www.pinterest.com/)

CODE_OF_CONDUCT.md

@@ -0,0 +1,40 @@
+# Code of Conduct
+
+At Pinterest, we work hard to ensure that our work environment is welcoming
+and inclusive to as many people as possible. We are committed to creating this
+environment for everyone involved in our open source projects as well. We
+welcome all participants regardless of ability, age, ethnicity, identified
+gender, religion (or lack there of), sexual orientation and socioeconomic
+status.
+
+This code of conduct details our expectations for upholding these values.
+
+## Good behavior
+
+We expect members of our community to exhibit good behavior including (but of
+course not limited to):
+
+- Using intentional and empathetic language.
+- Focusing on resolving instead of escalating conflict.
+- Providing constructive feedback.
+
+## Unacceptable behavior
+
+Some examples of unacceptable behavior (again, this is not an exhaustive
+list):
+
+- Harassment, publicly or in private.
+- Trolling.
+- Sexual advances (this isn’t the place for it).
+- Publishing other’s personal information.
+- Any behavior which would be deemed unacceptable in a professional environment.
+
+## Recourse
+
+If you are witness to or the target of unacceptable behavior, it should be
+reported to Pinterest at [email protected]. All reporters will
+be kept confidential and an appropriate response for each incident will be
+evaluated.
+
+If the maintainers do not uphold and enforce this code of conduct in
+good faith, community leadership will hold them accountable.

CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing
+
+First off, thanks for taking the time to contribute! This guide will answer
+some common questions about how this project works.
+
+While this is a Pinterest open source project, we welcome contributions from
+everyone. Regular outside contributors can become project maintainers.
+
+## Help
+
+If you're having trouble using this project, please start by reading the [`README.md`](README.md)
+and searching for solutions in the existing open and closed issues.
+
+## Security
+
+If you've found a security issue in one of our open source projects,
+please report it at [Bugcrowd](https://bugcrowd.com/pinterest); you may even
+make some money!
+
+## Code of Conduct
+
+Please be sure to read and understand our [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md).
+We work hard to ensure that our projects are welcoming and inclusive to as many
+people as possible.
+
+## Reporting Issues
+
+If you have a bug report, please provide as much information as possible so that
+we can help you out:
+
+- Version of the project you're using.
+- Code (or even better whole projects) which reproduce the issue.
+- Steps which reproduce the issue.
+- Screenshots, GIFs or videos (if relevent).
+- Stack traces for crashes.
+- Any logs produced.
+
+## Making Changes
+
+1. Fork this repository to your own account
+2. Make your changes and verify that tests pass
+3. Commit your work and push to a new branch on your fork
+4. Submit a pull request
+5. Participate in the code review process by responding to feedback
+
+Once there is agreement that the code is in good shape, one of the project's
+maintainers will merge your contribution.
+
+To increase the chances that your pull request will be accepted:
+
+- Follow the coding style
+- Write tests for your changes
+- Write a good commit message
+
+## License
+
+By contributing to this project, you agree that your contributions will be
+licensed under its [license](LICENSE).