✨ 📚 Setup initial structure

.editorconfig

@@ -0,0 +1,19 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+ident_size = 4
+
+[*.md]
+ident_size = 2
+trim_trailing_whitespace = false
+
+[*.json]
+ident_size = 2
+
+[{.gitignore,.gitkeep,.editorconfig}]
+ident_size = 2

.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# Require maintainer's :+1: for changes to the .github/ repo-config files
+# mainly due to https://github.com/probot/settings privilege escalation
+.github/* @frenck
+.gitlab-ci.yml @frenck

.github/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. 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/

.github/CONTRIBUTING.md

@@ -0,0 +1,17 @@
+# Contributing
+
+You are welcome to edit, fork and create pull requests as you like.
+
+- If you make a change, make sure to refer to any issues that it fixes.
+- Make sure you have used linters and tested what you have added/changed
+  works.
+- Any pull request will be verified by the bots, so make sure you fix any
+  issues the bots find.
+- I, and any other users I approve will be able to merge your changes so
+  be patient.
+
+## Docs
+
+Feel free to improve documentation as you like by making a pull request in
+ `/docs`. Once merged into the master branch, my ci server will update the
+ docs in the `gh-pages` branch.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,20 @@
+# Problem/Motivation
+
+> (Why the issue was filed)
+
+## Expected behavior
+
+> (What you expected to happen)
+
+## Actual behavior
+
+> (What actually happened)
+
+## Steps to reproduce
+
+> (How can someone else make/see it happen)
+
+## Proposed changes
+
+> (If you have a proposed change, workaround or fix,
+> describe the rationale behind it)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+# Proposed Changes
+
+> (Describe the changes and rationale behind them)
+
+## Related Issues
+
+> ([Github link][autolink-references] to related issues or pull requests)
+
+[autolink-references]: https://help.github.com/articles/autolinked-references-and-urls/

.github/autolabeler.yml

@@ -0,0 +1,2 @@
+---
+"Type: Documentation": ["*.md", "*.j2"]

.github/config.yml

@@ -0,0 +1,50 @@
+---
+# Configuration for request-info - https://github.com/behaviorbot/request-info
+
+# *OPTIONAL* Comment to reply with
+# Can be either a string :
+requestInfoReplyComment:
+  - "We would appreciate it if you could provide us with more info about this issue/pr!"
+  - "Hmmm... That issue/PR is kinda low on text. Could you please provide some more content?"
+
+# *OPTIONAL* default titles to check against for lack of descriptiveness
+# MUST BE ALL LOWERCASE
+requestInfoDefaultTitles: []
+
+# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
+requestInfoLabelToAdd: "Incomplete"
+
+# *OPTIONAL* Require Pull Requests to contain more information than what is provided in the PR template
+# Will fail if the pull request's body is equal to the provided template
+checkPullRequestTemplate: true
+
+# *OPTIONAL* Only warn about insufficient information on these events type
+# Keys must be lowercase. Valid values are 'issue' and 'pullRequest'
+requestInfoOn:
+  pullRequest: true
+  issue: true
+
+# *OPTIONAL* Add a list of people whose Issues/PRs will not be commented on
+# keys must be GitHub usernames
+requestInfoUserstoExclude: []
+
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  :wave: Thanks for opening your first issue here!
+  If you're reporting a :bug: bug, please make sure you include steps to reproduce it.
+  Also, logs, error messages and information about your hardware might be usefull.
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+   :sparkling_heart: Thanks for opening this pull request! :sparkling_heart:
+   If your PR gets accepted and merged in, we will invite you to the project :tada:
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  Congrats on merging your first pull request! :tada::tada::tada:

.github/invite-contributors.yml

@@ -0,0 +1,10 @@
+---
+# If true, this will add new contributors as outside collaborators
+# to the repo their PR was merged in. Team name is ignored if this
+# flag is set to true.
+isOutside: false
+
+# Specify team name to add new contributors to a specific team
+# within your organization.
+# Use team name or team-name-slug
+team: Contributors

.github/lock.yml

@@ -0,0 +1,20 @@
+---
+# Configuration for lock-threads - https://github.com/dessant/lock-threads
+# Number of days of inactivity before a closed issue or pull request is locked
+daysUntilLock: 30
+
+# Comment to post before locking. Set to `false` to disable
+lockComment: >
+  This thread has been automatically locked because it has not had recent
+  activity. Please open a new issue for related bugs and link to relevant
+  comments in this thread.
+
+# Issues or pull requests with these labels will not be locked
+# exemptLabels:
+#   - no-locking
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Add a label when locking. Set to `false` to disable
+lockLabel: false

.github/move.yml

@@ -0,0 +1,20 @@
+---
+# Delete the command comment when it contains no other content
+deleteCommand: true
+
+# Close the source issue after moving
+closeSourceIssue: true
+
+# Lock the source issue after moving
+lockSourceIssue: true
+
+# Mention issue and comment authors
+mentionAuthors: true
+
+# Preserve mentions in the issue content
+keepContentMentions: false
+
+# Set custom aliases for targets
+# aliases:
+#   r: repo
+#   or: owner/repo

.github/no-response.yml

@@ -0,0 +1,13 @@
+---
+# Configuration for probot-no-response - https://github.com/probot/no-response
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 14
+# Label requiring a response
+responseRequiredLabel: "Status: Awaiting response"
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+  This issue has been automatically closed because there has been no response
+  to our request for more information from the original author. With only the
+  information that is currently in the issue, we don't have enough information
+  to take action. Please reach out if you have or find the answers we need so
+  that we can investigate further.

.github/potential-duplicates.yml

@@ -0,0 +1,14 @@
+---
+# Label name and color to set, when potential duplicates are detected
+issueLabel: "Potential duplicate"
+labelColor: e6e6e6
+
+# If similarity is higher than this threshold, issue will be marked as duplicate
+threshold: 0.70
+
+# Comment to post when potential duplicates are detected
+referenceComment: >
+  Potential duplicates found:
+  {{#issues}}
+    - [#{{ number }}] {{ title }} ({{ accuracy }}%)
+  {{/issues}}

.github/settings.yml

@@ -0,0 +1,150 @@
+---
+repository:
+  description: "The Lounge - Community Hass.io Add-on for Home Assistant"
+  topics: thelounge, irc-client, irc, hassio, hassio-addons, hass, javascript
+  homepage: https://addons.community
+  private: false
+  has_issues: true
+  has_projects: false
+  has_wiki: false
+  has_downloads: false
+  default_branch: master
+  allow_squash_merge: true
+  allow_merge_commit: false
+  allow_rebase_merge: true
+labels:
+  # Priority labels
+  - name: "Priority: Critical"
+    color: ee0701
+    description: "This should be dealt with ASAP. Not fixing this issue would be a serious error."
+  - name: "Priority: High"
+    color: b60205
+    description: "After critical issues are fixed, these should be dealt with before any further issues."
+  - name: "Priority: Medium"
+    color: 0e8a16
+    description: "This issue may be useful, and needs some attention."
+  - name: "Priority: Low"
+    color: e4ea8a
+    description: "Nice addition, maybe... someday..."
+
+  # Type labels
+  - name: "Type: Bug"
+    color: ee0701
+    description: "Inconsistencies or issues which will cause a problem for users or implementors."
+  - name: "Type: Documentation"
+    color: 0052cc
+    description: "Solely about the documentation of the project."
+  - name: "Type: Enhancement"
+    color: 1d76db
+    description: "Enhancement of the code, not introducing new features."
+  - name: "Type: Feature"
+    color: 0e8a16
+    description: "New features or options."
+  - name: "Type: Support"
+    color: 5319e7
+    description: "Marks an issue as an support ticket."
+  - name: "Type: Discussion"
+    color: d4c5f9
+    description: "Marks an issue as an generic discussion ticket."
+  - name: "Type: Maintaince"
+    color: 2af79e
+    description: "Generic maintaince tasks, e.g., package updates."
+
+  # Additional markers
+  - name: "Security"
+    color: ee0701
+    description: "Marks an security issues that needs to be resolved asap."
+  - name: "Idea"
+    color: fef2c0
+    description: "Marks an idea, which might be excepted and implemented."
+  - name: "Incomplete"
+    color: fef2c0
+    description: "Marks an PR or issue that is missing information."
+  - name: "Pull request"
+    color: fbca04
+    description: "There is an PR opened for this issue."
+  - name: "Accepted"
+    color: c2e0c6
+    description: "This issue or PR has been accepted."
+  - name: "Declined"
+    color: f9d0c4
+    description: "This issue or PR has been declined."
+  - name: "Potential duplicate"
+    color: e6e6e6
+    description: "This issue has been automatically marked as a potential duplicate."
+
+  # Ongoing Status labels
+  - name: "Status: Triage"
+    color: fbca04
+    description: "This issue needs to be triaged."
+  - name: "Status: On hold"
+    color: cccccc
+    description: "Issue or PR that has been placed on hold for now."
+  - name: "Status: In progress"
+    color: fbca04
+    description: "Issue is currently being resolved by a developer."
+  - name: "Status: Stale"
+    color: fef2c0
+    description: "There has not been activity on this issue or PR for quite some time."
+  - name: "Status: Awaiting response"
+    color: fef2c0
+    description: "Issue or PR awaits response from the creator."
+  - name: "Status: Blocked"
+    color: fef2c0
+    description: "Progress on this issue is currently not possible."
+
+  # Closing status labels
+  - name: "Closed: Known limitation"
+    color: e6e6e6
+    description: "Issue is closed, it is a known limitation."
+  - name: "Closed: Expected behavior"
+    color: e6e6e6
+    description: "Issues is closed, it is expected behavior."
+  - name: "Closed: Duplicate"
+    color: e6e6e6
+    description: "Issue is closed, duplicate of an existing issue."
+  - name: "Closed: Invalid"
+    color: e6e6e6
+    description: "Issue is closed, marked as not a valid issue (e.g., an user error)."
+  - name: "Closed: Wrong repository"
+    color: e6e6e6
+    description: "Issue is closed, was created in the wrong repository."
+  - name: "Closed: Won't Fix"
+    color: e6e6e6
+    description: "Issue is closed, it won't be fixed."
+  - name: "Closed: Done"
+    color: c2e0c6
+    description: "Issue closed, work on this issue has been marked complete."
+
+  # Others
+  - name: "Beginner Friendly"
+    color: 0e8a16
+    description: "Good first issue for people wanting to contribute to the project."
+  - name: "Help wanted"
+    color: 0e8a16
+    description: "We need some extra helping hands or expertise in order to resolve this."
+  - name: "Hacktoberfest"
+    description: "Issues/PRs are participating in the Hacktoberfest"
+    color: fbca04
+
+branches:
+  - name: master
+    protection:
+      required_pull_request_reviews:
+        # required_approving_review_count: 1
+        dismiss_stale_reviews: true
+        require_code_owner_reviews: true
+        dismissal_restrictions:
+          users: []
+          teams:
+            - Admins
+            - Masters
+      required_status_checks:
+        strict: false
+        contexts: []
+      enforce_admins: false
+      restrictions:
+        users: []
+        teams:
+          - Admins
+          - Masters

.github/stale.yml

@@ -0,0 +1,61 @@
+---
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 60
+
+# Number of days of inactivity before a stale Issue or Pull Request is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: 7
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - "Status: On hold"
+  - "Status: In progress"
+  - "Status: Awaiting response"
+  - "Status: Blocked"
+  - "Idea"
+  - "Security"
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: false
+
+# Label to use when marking as stale
+staleLabel: "Status: Stale"
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+unmarkComment: false
+
+# Comment to post when closing a stale Issue or Pull Request.
+# closeComment: >
+#   Your comment here.
+closeComment: false
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+
+# Limit to only `issues` or `pulls`
+only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed

.github/support.yml

@@ -0,0 +1,22 @@
+---
+# Configuration for support-requests - https://github.com/dessant/support-requests
+
+# Label used to mark issues as support requests
+supportLabel: "Type: Support"
+
+# Comment to post on issues marked as support requests. Add a link
+# to a support page, or set to `false` to disable
+supportComment: >
+  :wave: We use the issue tracker exclusively for bug reports and feature requests.
+  However, this issue appears to be a support request. Please use our
+  support channels to get help with the project.
+
+  Head over to the
+  [Home Assistant community forum](https://community.home-assistant.io/?u=timmo001)
+  or join our [Discord](https://discord.me/hassioaddons) chat.
+
+# Close issues marked as support requests
+close: true
+
+# Lock issues marked as support requests
+lock: false

.mdlrc

@@ -0,0 +1 @@
+rules "~MD024"

.yamllint

@@ -0,0 +1,64 @@
+---
+rules:
+  braces:
+    level: error
+    min-spaces-inside: 0
+    max-spaces-inside: 1
+    min-spaces-inside-empty: -1
+    max-spaces-inside-empty: -1
+  brackets:
+    level: error
+    min-spaces-inside: 0
+    max-spaces-inside: 0
+    min-spaces-inside-empty: -1
+    max-spaces-inside-empty: -1
+  colons:
+    level: error
+    max-spaces-before: 0
+    max-spaces-after: 1
+  commas:
+    level: error
+    max-spaces-before: 0
+    min-spaces-after: 1
+    max-spaces-after: 1
+  comments:
+    level: error
+    require-starting-space: true
+    min-spaces-from-content: 2
+  comments-indentation:
+    level: error
+  document-end:
+    level: error
+    present: false
+  document-start:
+    level: error
+    present: true
+  empty-lines:
+    level: error
+    max: 1
+    max-start: 0
+    max-end: 1
+  hyphens:
+    level: error
+    max-spaces-after: 1
+  indentation:
+    level: error
+    spaces: 2
+    indent-sequences: true
+    check-multi-line-strings: false
+  key-duplicates:
+    level: error
+  line-length:
+    level: warning
+    max: 120
+    allow-non-breakable-words: true
+    allow-non-breakable-inline-mappings: true
+  new-line-at-end-of-file:
+    level: error
+  new-lines:
+    level: error
+    type: unix
+  trailing-spaces:
+    level: error
+  truthy:
+    level: error

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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 lead. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project lead 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,29 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish
+to make via issue, email, or any other method with the owners of this repository
+before making a change.
+
+Please note we have a code of conduct, please follow it in all your interactions
+with the project.
+
+## Issues and feature requests
+
+You've found a bug in the source code, a mistake in the documentation or maybe
+you'd like a new feature? You can help us by submitting an issue to our
+[GitHub Repository][github]. Before you create an issue, make sure you search
+the archive, maybe your question was already answered.
+
+Even better: You could submit a pull request with a fix / new feature!
+
+## Pull request process
+
+1. Search our repository for open or closed [pull requests][prs] that relates
+   to your submission. You don't want to duplicate effort.
+
+1. You may merge the pull request in once you have the sign-off of two other
+   developers, or if you do not have permission to do that, you may request
+   the second reviewer to merge it for you.
+
+[github]: https://github.com/timmo001/addon-thelounge/issues
+[prs]: https://github.com/timmo001/addon-thelounge/pulls

LICENSE.md

@@ -0,0 +1,21 @@
+# MIT License
+
+Copyright (c) 2019 Timmo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

renovate.json

@@ -0,0 +1,11 @@
+{
+  "extends": [
+    "config:base"
+  ],
+  "commitMessageAction": "Updates",
+  "commitMessageTopic": "{{depName}}",
+  "commitMessagePrefix": ":arrow_up:",
+  "labels": [
+    "Type: Maintaince"
+  ]
+}