initial commit

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/workflows/create-pr.yml

@@ -0,0 +1,21 @@
+name: RELEASE
+
+on:
+  push:
+    branches: [develop]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [15.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: 🔀
+        uses: BaharaJr/create-pr@0.0.1
+        with:
+          GITHUB_TOKEN: ${{secrets.TOKEN}}
+          DESTINATION_BRANCH: master
+          KEYWORD: release

.github/workflows/docker-image.yml

@@ -0,0 +1,32 @@
+name: Docker Image CI
+
+on:
+  pull_request:
+    branches: [master]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check Out Repo
+        uses: actions/checkout@v2
+
+      - name: Login to Docker Hub
+        uses: docker/login-action@v1
+        with:
+          username: ${{ secrets.DOCKER_HUB_USERNAME }}
+          password: ${{ secrets.DOCKER_HUB_ACCESS_TOKEN }}
+
+      - name: Set up Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        id: docker_build
+        run: sh docker/build.sh
+
+      - name: 🔀
+        uses: BaharaJr/merge-pr@0.0.1
+        with:
+          GITHUB_TOKEN: ${{ secrets.TOKEN }}

.gitignore

@@ -0,0 +1,95 @@
+*.iml
+*.class
+# Package Files #
+*.war
+*.ear
+*.iml
+.classpath
+.idea
+.project
+.settings/*
+# Ignore package-lock.json
+package-lock.json
+
+# Ignore package.json
+package.json
+
+omods/*/api/.classpath
+omods/*/api/.project
+omods/*/api/.settings/*
+omods/*/api/target/*
+omods/*/omod/.classpath
+omods/*/omod/.project
+omods/*/omod/.settings/*
+omods/*/omod/target/*
+/.settings
+.DS_Store
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+# compiled output
+ui/dist
+ui/tmp
+ui/out-tsc
+# Only exists if Bazel was run
+ui/bazel-out
+# dependencies
+ui/node_modules
+node_modules/canvas/build/Release/librsvg-2
+# profiling files
+ui/chrome-profiler-events*.json
+ui/speed-measure-plugin*.json
+# IDEs and editors
+ui/.idea
+ui/.project
+ui/.classpath
+ui/.c9/
+*.launch
+ui/.settings/
+ui/.angular
+*.sublime-workspace
+# IDE - VSCode
+ui/.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+.history/*
+# misc
+ui/.sass-cache
+ui/connect.lock
+ui/coverage
+ui/libpeerconnection.log
+ui/npm-debug.log
+ui/yarn-error.log
+ui/testem.log
+ui/typings
+# System Files
+.DS_Store
+ui/Thumbs.db
+ui/proxy-config.json
+ui/cypress/videos/*
+ui/cypress/screenshots/*
+ui/cypress/reports/*
+*/backup/
+docker-compose.yml
+# Messaging support
+messaging/functions/node_modules/
+messaging/firestore-debug.log
+messaging/firebase-debug.log
+messaging/database-debug.log
+messaging/ui-debug.log
+# Generated files
+docs/.docusaurus
+docs/.cache-loader
+# Misc
+docs/.DS_Store
+docs/.env.local
+docs/.env.development.local
+docs/.env.test.local
+docs/.env.production.local
+docs/npm-debug.log*
+docs/yarn-debug.log*
+docs/yarn-error.log*
+<<<<<<< HEAD
+node_modules/canvas/build/Release/librsvg-2.so.2
+=======
+>>>>>>> develop

.vscode/extensions.json

@@ -0,0 +1,13 @@
+{
+	// See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
+	// Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
+
+	// List of extensions which should be recommended for users of this workspace.
+	"recommendations": [
+
+	],
+	// List of extensions recommended by VS Code that should not be recommended for users of this workspace.
+	"unwantedRecommendations": [
+
+	]
+}

.vscode/settings.json

@@ -0,0 +1,7 @@
+{
+    "python.analysis.typeCheckingMode": "basic",
+    "angular.enable-strict-mode-prompt": false,
+    "java.debug.settings.onBuildFailureProceed": true,
+    "java.configuration.updateBuildConfiguration": "automatic",
+    "java.compile.nullAnalysis.mode": "automatic"
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,71 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering a safe and welcoming environment, we as
+the iCare team pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity, gender expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Use welcoming and inclusive language
+- Respect each other
+- Provide and gracefully accept constructive criticism
+- Show empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- 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
+- The use of sexualized language or imagery
+- Unwelcome sexual attention or advances
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+iCare team 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.
+
+iCare team 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 to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies to all iCare communication channels - online or in person,
+and it also applies when an individual is representing the project or its community in
+public spaces. 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 iCare team at conduct@icare.io. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The iCare team
+will maintain confidentiality with regard to the reporter of an incident.
+Enforcement may result in an indefinite ban from all official iCare communication
+channels, or other actions as deemed appropriate by the iCare team.
+
+iCare 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](https://www.contributor-covenant.org), version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html