Codebase as of https://github.com/openhab/openhab2-addons/tree/c53e4a…

…ed2627ec899c083170430399f8925e3345 as an initial commit for the shrunk repo Signed-off-by: Kai Kreuzer <kai@openhab.org>
cweitkamp · Sep 20, 2020 · bbf1a7f · bbf1a7f
commit bbf1a7f
Show file tree

Hide file tree

Showing 302 changed files with 29,726 additions and 0 deletions.
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,47 @@
+---
+name: "\U0001F41B Bug report"
+about: Something isn't working correctly with an add-on. This is the wrong place for user-interfaces or openHAB Core issues.
+labels: bug
+
+---
+
+<!-- Provide a general summary of the issue in the *Title* above -->
+<!-- If the issue is related to a binding, please include its short name in -->
+<!-- square brackets in the title - Example: "[astro] My issue..." -->
+
+<!-- Important: Please contact the openHAB community forum for questions or -->
+<!-- for configuration and usage guidance: https://community.openhab.org -->
+
+<!-- Feel free to delete any comment lines in the template (starting with "<!--") -->
+
+## Expected Behavior
+<!-- If you're describing a bug, tell us what should happen -->
+<!-- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!-- If describing a bug, tell us what happens instead of the expected behavior -->
+<!-- Include related log information (preferably debug level) and related configs -->
+<!-- Use a file attachment for log and config information longer than a few lines -->
+<!-- Enclose multi-line log/code snippets with ``` on new lines for proper formatting -->
+<!-- If suggesting a change/improvement, explain the difference from current behavior -->
+<!-- For improvements, discuss at community.openhab.org first and include link to topic -->
+
+## Possible Solution
+<!-- Not obligatory, but suggest a fix/reason for the bug, -->
+<!-- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for Bugs)
+<!-- Provide a link to a live example, or an unambiguous set of steps to -->
+<!-- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+
+## Context
+<!-- How has this issue affected you? What are you trying to accomplish? -->
+<!-- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!-- Include as many relevant details about the environment you experienced the bug in -->
+* Version used: (e.g., openHAB and add-on versions)
+* Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
+* Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):
diff --git a/.github/ISSUE_TEMPLATE/documentation_issue.md b/.github/ISSUE_TEMPLATE/documentation_issue.md
@@ -0,0 +1,17 @@
+---
+name: "Documentation issue"
+about: Some information within the add-on documentation is wrong or missing
+labels: documentation
+
+---
+<!-- Please report only add-on related documentation issues here -->
+<!-- Documentation issues within user interfaces or the core should be -->
+<!-- reported at https://github.com/openhab/openhab-docs/issues/new -->
+
+<!-- Provide a general summary of the documentation issue in the *Title* above -->
+<!-- If the documentation issue is related to a specific add-on, please include its short name in -->
+<!-- square brackets in the title - Example: "[astro] My documentation issue..." -->
+
+<!-- Important: Please contact the openHAB community forum for questions or -->
+<!-- for configuration and usage guidance: https://community.openhab.org -->
+
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,19 @@
+---
+name: "Feature request"
+about: You think that your favorite add-on should gain another feature
+labels: enhancement
+
+---
+
+<!-- Provide a general summary of the feature request in the *Title* above -->
+<!-- If the feature request is related to an add-on, please include its short name in -->
+<!-- square brackets in the title - Example: "[astro] My feature request..." -->
+
+<!-- Important: Please contact the openHAB community forum for questions or -->
+<!-- for configuration and usage guidance: https://community.openhab.org -->
+
+## Your Environment
+<!-- Include as many relevant details about the environment when applicable -->
+* Version used: (e.g., openHAB and add-on versions)
+* Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
+* Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):
diff --git a/.github/ISSUE_TEMPLATE/usage_question.md b/.github/ISSUE_TEMPLATE/usage_question.md
@@ -0,0 +1,10 @@
+---
+name: "\U0001F914 Support/Usage Question"
+about: For usage questions, please use the openHAB community board!
+labels: question
+
+---
+
+This is an issue tracker for reporting problems and requesting new features. For usage questions, please use the openHAB community board where there are a lot more people ready to help you out. Thanks!
+
+https://community.openhab.org/
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,62 @@
+<!--
+Thanks for contributing to the openHAB project!
+Please describe the goal and effect of your PR here.
+Pay attention to the below notes and to *the guidelines* for this repository.
+Feel free to delete any comment sections in the template (starting with "<!--").
+-->
+
+<!-- TITLE -->
+
+<!--
+Please provide a PR summary in the *Title* above, according to the following schema:
+- If related to one specific add-on: Mention the add-on shortname in square brackets
+  e.g. "[exec]", "[netatmo]" or "[tesla]"
+- If the PR is work in progress: Add "[WIP]"
+- Give a short meaningful description in imperative mood
+  e.g. "Add support for device XYZ" or "Fix wrongly handled exception"
+  for a new add-on/binding: "Initial contribution"
+Examples:
+- "[homematic] Improve communication with weak signal devices"
+- "[timemachine][WIP] Initial contribution"
+- "Update contribution guidelines on new signing rules"
+-->
+
+<!-- DESCRIPTION -->
+
+<!--
+Please give a few sentences describing the overall goals of the pull request.
+Give enough details to make the improvement and changes of the PR understandable
+to both developers and tech-savy users.
+
+Please keep the following in mind:
+- What is the classification of the PR, e.g. Bugfix, Improvement, Novel Addition, ... ?
+- Did you describe the PRs motivation and goal?
+- Did you provide a link to any prior discussion, e.g. an issue or community forum thread?
+- Did you describe new features for the end user?
+- Did you describe any noteworthy changes in usage for the end user?
+- Was the documentation updated accordingly, e.g. the add-on README?
+- Does your contribution follow the coding guidelines:
+  https://www.openhab.org/docs/developer/development/guidelines.html
+- Did you check for any (relevant) issues from the static code analysis:
+  https://www.openhab.org/docs/developer/development/bindings.html#static-code-analysis
+- Did you sign-off your work:
+  https://www.openhab.org/docs/developer/contributing/contributing.html#sign-your-work
+-->
+
+<!-- TESTING -->
+
+<!--
+Your Pull Request will automatically be built and available under the following folder:
+https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/
+
+It is a good practice to add a URL to your built JAR in this Pull Request description,
+so it is easier for the community to test your Add-on.
+If your Pull Request contains a new binding, it will likely take some time
+before it is reviewed and processed by maintainers.
+That said, consider submitting your Add-on in the Eclipse IoT Marketplace
+See this thread for more info:
+https://community.openhab.org/t/24491
+
+Don't forget to submit a thread about your Add-on in the openHAB community:
+https://community.openhab.org/c/add-ons 
+-->
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,23 @@
+.antlr*
+.idea
+.DS_Store
+*.iml
+npm-debug.log
+.build.log
+
+.metadata/
+bin/
+target/
+src-gen/
+xtend-gen/
+.history/
+
+*/plugin.xml_gen
+**/.settings/org.eclipse.*
+
+bundles/**/src/main/history
+features/**/src/main/history
+features/**/src/main/feature
+
+.vscode
+.factorypath
diff --git a/.travis.yml b/.travis.yml
@@ -0,0 +1,23 @@
+os: linux
+dist: focal
+
+language: java
+jdk: openjdk11
+
+cache:
+  directories:
+  - $HOME/.m2
+
+before_cache:
+  # remove resolver-status.properties, they change with each run and invalidate the cache
+  - find $HOME/.m2 -name resolver-status.properties -exec rm {} \;
+
+notifications:
+    webhooks: https://www.travisbuddy.com/
+
+travisBuddy:
+    insertMode: update
+    successBuildLog: true
+
+install: true
+script: ./buildci.sh "$TRAVIS_COMMIT_RANGE"