feat: migrate project from GitHub Enterprise

.gitattributes

@@ -0,0 +1,12 @@
+#
+# https://help.github.com/articles/dealing-with-line-endings/
+#
+# Linux start script should use lf
+/gradlew        text eol=lf
+
+# These are Windows script files and should use crlf
+*.bat           text eol=crlf
+
+# Binary files should be left untouched
+*.jar           binary
+

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @robert-mitchell-iii @masato-noda @akira-kawakatsu

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+## Issue
+
+https://github.com/line/geojson-kt/issues
+
+## Summary
+
+- **What** does this PR do?
+- **Why** is it being opened?
+
+## Changes
+
+- **How** was this PR implemented?
+- Please list major changes/additions.
+
+## Notes / References
+
+- Any relevant notes, materials, etc. (optional)
+
+## Checklist
+
+- [ ] Link to issue specified
+- [ ] Implementation satisfies the stated objective(s)
+- [ ] Test(s) added as appropriate
+- [ ] Documentation created/updated

.github/workflows/main.yml

@@ -0,0 +1,56 @@
+name: Run tests and code checks
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+permissions:
+  # Required by mikepenz/action-junit-report
+  checks: write
+  # Required by actions/checkout
+  contents: read
+  # Required by mi-kas/kover-report
+  pull-requests: write
+
+jobs:
+  test:
+    name: Test
+    runs-on:
+      - ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - uses: actions/setup-java@v3
+        with:
+          distribution: "temurin"
+          java-version: "17"
+          cache: "gradle"
+
+      - name: Run test
+        run: ./gradlew check --no-daemon
+
+      - name: Publish test reports
+        uses: mikepenz/action-junit-report@v3
+        if: always()
+        with:
+          report_paths: |
+            **/build/test-results/test/TEST-*.xml
+
+      - name: Create coverage report
+        if: ${{ github.event.pull_request }}
+        run: ./gradlew koverXmlReport
+
+      - name: Post coverage report as comment
+        if: ${{ github.event.pull_request }}
+        uses: mi-kas/kover-report@v1
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          path: |
+            ${{ github.workspace }}/build/reports/kover/report.xml
+          title: Code Coverage
+          update-comment: true
+          min-coverage-overall: 80
+          min-coverage-changed-files: 80
+          coverage-counter-type: LINE

.gitignore

@@ -0,0 +1,32 @@
+# Ignore Gradle project-specific cache directory
+.gradle
+
+# Ignore Gradle build output directory
+build
+
+.DS_Store
+
+# IntelliJ
+## User-specific settings
+.idea/**/workspace.xml
+.idea/**/tasks.xml
+.idea/**/usage.statistics.xml
+.idea/**/dictionaries
+.idea/**/shelf
+
+## Sensitive or high-churn files
+.idea/**/dataSources/
+.idea/**/dataSources.ids
+.idea/**/dataSources.local.xml
+.idea/**/sqlDataSources.xml
+.idea/**/dynamic.xml
+.idea/**/uiDesigner.xml
+.idea/**/dbnavigator.xml
+.idea/misc.xml
+
+# Module information is generated from Gradle on import
+# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839-How-to-manage-projects-under-Version-Control-Systems
+
+.idea/modules.xml
+.idea/modules/
+.idea/libraries

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[[email protected]](mailto:[email protected]).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+# Contributing
+
+First of all, thank you for considering contributing to `geojson-kt`!
+
+Before contributing, please review and agree to our [code of conduct](./CODE_OF_CONDUCT.md), if you have not already done so.
+
+## How Can I Contribute?
+
+You can contribute in a number of ways, including:
+
+- Finding and reporting bugs
+- Implementing missing functionality
+- Improving the documentation
+- etc.
+
+Every little bit helps!
+
+## Coding Conventions
+
+As general rule, we try to adhere to [Kotlin's coding conventions](https://kotlinlang.org/docs/coding-conventions.html) 
+as much as possible.
+
+[Detekt](https://detekt.dev/) is used to enforce basic style rules and ensure that the code meets some basic criteria to
+keep it clean and easy-to-use.
+
+## Pull Requests
+
+Please use clear, concise titles for pull requests.
+
+PR titles and individual commit messages should adhere to the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
+
+- PRs will be squashed and merged, so it is important that PR titles and commit messages are in the same format.
+
+## Questions
+
+If you have any questions, please open an issue we will get back to you as quickly as possible.