Merge branch 'master' into master

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,32 +1,29 @@
 ---
-name: Bug/issue report
+name: 🐛 Bug Report
 about: Report an issue to help improve the project.
 title: ''
 labels: 'kind/bug'
 assignees: ''
 ---
-**Description**
+#### Description
 <!-- A brief description of the issue. -->
 
-**Expected Behavior**
+#### Expected Behavior
 <!-- A brief description of what you expected to happen. -->
 
-**Screenshots**
+#### Screenshots/Logs
 <!-- Add screenshots, if applicable, to help explain your problem. -->
 
-**Environment:**
- - OS: [e.g. Ubuntu]
- - Browser: [e.g. Chrome, Safari]
- - Version: [e.g. 22]
- - Device: [e.g. laptop, iPhone 8]
+#### Environment:
+- Host OS: 
+- Meshery Version: 
+- Kubernetes Version: 
+- Browser: 
 
----
-[Optional] **To Reproduce**
+<!-- Optional 
+#### To Reproduce
 Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
-
-[Optional] **Additional Context**
-<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/ci.md

@@ -0,0 +1,21 @@
+---
+name: 🛠 Continuous Integration / DevOps
+about: Improve or update workflows or other automation
+title: '[CI]'
+labels: 'area/ci'
+assignees: ''
+---
+#### Current Behavior
+<!-- A brief description of what the problem is. (e.g. I need to be able to...) -->
+
+#### Desired Behavior
+<!-- A brief description of what you expected to happen. -->
+
+#### Implementation
+<!-- Specifics on the approach to fulfilling the feature request. -->
+
+#### Acceptance Tests
+<!-- Stipulations of functional behavior or non-functional items that must be in-place in order for the issue to be closed. -->
+
+#### Reference:
+- [Meshery Build & Release Strategy](https://docs.google.com/document/d/11nAxYtz2SUusCYZ0JeNRrOLIxkgmmbUVWz63MBZV2oE/edit#)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+- name: 🙋🏾🙋🏼‍Question
+  url: https://github.com/layer5io/meshery/discussions/new
+  about: Submit your question using GitHub Discussions.

.github/ISSUE_TEMPLATE/documentation.md

@@ -1,18 +1,16 @@
 ---
-name: Documentation issue
+name: 📄 Documentation issue
 about: Issues related to documentation.
 title: '[Docs]'
 labels: 'area/docs'
 assignees: ''
 ---
 **Current State:**
 
-
 **Desired State:**
 
-
 ---
 **Contributor Resources**
-- [Meshery documentation site](https://meshery.layer5.io/docs/)
+- [Meshery documentation site](https://docs.meshery.io/)
 - [Meshery documentation source](https://github.com/layer5io/meshery/tree/master/docs)
 - [Instructions for contributing to documentation](https://github.com/layer5io/meshery/blob/master/CONTRIBUTING.md#documentation-contribution-flow)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,26 +1,24 @@
 ---
-name: Feature Request
-about: Suggest an enhancement to this project.
+name: 💡 Feature Request
+about: Suggest an enhancement to Meshery.
 title: ''
 labels: 'kind/enhancement'
 assignees: ''
 ---
-
-**Current Behavior**
+#### Current Behavior
 <!-- A brief description of what the problem is. (e.g. I need to be able to...) -->
 
-
-**Desired Behavior**
+#### Desired Behavior
 <!-- A brief description of the enhancement. -->
 
-
 ---
-**Implementation**
-<!-- Specifics on the approach to fulfilling the feature request. -->
+[Optional]
 
-**Mockups**
-<!-- Any visual diagrams of the desired user interface. -->
+#### Implementation
+<!-- Specifics on the approach to fulfilling the feature request. -->
 
-**Acceptance Tests**
+#### Acceptance Tests
 <!-- Stipulations of functional behavior or non-functional items that must be in-place in order for the issue to be closed. -->
 
+#### Mockups
+<!-- Any visual diagrams of the desired user interface. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,7 +5,7 @@ This PR fixes #
 **Notes for Reviewers**
 
 
-**[Signed commits](../CONTRIBUTING.md#signing-off-on-commits-developer-certificate-of-origin)**
+**[Signed commits](https://github.com/layer5io/meshery/blob/master/CONTRIBUTING.md#signing-off-on-commits-developer-certificate-of-origin)**
 - [ ] Yes, I signed my commits.
 
 

.github/config.yml

@@ -2,7 +2,12 @@
 # Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
  # Comment to be posted to on first time issues
 newIssueWelcomeComment: >
-   Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the [Layer5 Contributors' Welcome Guide](https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit?usp=sharing) and sure to join the [community Slack](http://slack.layer5.io/).
+   Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the [Layer5 Contributors' Welcome Guide](https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit?usp=sharing) and be sure to join the [community Slack](http://slack.layer5.io/).
+  \
+  \ Let us know how you would like to proceed:
+  \ 1. You would like an existing contributor in the community to address this issue.
+  \ 1. You would like to address (fix) this issue.
+
  # 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: >
@@ -15,10 +20,12 @@ newPRWelcomeComment: >
 # 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: >
-  Thanks for your contribution to the Layer5 community! :tada:
-
+     	   	    	    	 Thank you for contributing to the Layer5 community! :tada:
+  \
+  \
   ![Congrats!](https://raw.githubusercontent.com/layer5io/meshery/master/.github/welcome/Layer5-celebration.png)
-
+  \
+  \
     	   	    	    	 :star: Please leave a [star on the project](../stargazers). :smile:
 
 #-------------------------------------------------------------------------------

.github/dependabot.yml

@@ -0,0 +1,64 @@
+version: 2
+updates:
+- package-ecosystem: gomod
+  directory: "/"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10
+  labels:
+  - pr/dependencies
+  - kind/chore
+  ignore:
+  - dependency-name: github.com/prologic/bitcask
+    versions:
+    - "> 0.3.9"
+    - "< 0.4"
+  - dependency-name: k8s.io/api
+    versions:
+    - ">= 0.20.a"
+    - "< 0.21"
+  - dependency-name: k8s.io/apimachinery
+    versions:
+    - ">= 0.20.a"
+    - "< 0.21"
+  - dependency-name: k8s.io/client-go
+    versions:
+    - ">= 0.20.a"
+    - "< 0.21"
+- package-ecosystem: npm
+  directory: "/ui"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10
+  reviewers:
+  - dhruv0000
+  labels:
+  - kind/chore
+  - pr/dependencies
+  ignore:
+  - dependency-name: "@material-ui/core"
+    versions:
+    - "> 4.9.13"
+    - "< 5"
+  - dependency-name: next
+    versions:
+    - "> 10.0.1"
+    - "< 10.1"
+  - dependency-name: next-redux-wrapper
+    versions:
+    - ">= 6.a"
+    - "< 7"
+  - dependency-name: react-select
+    versions:
+    - ">= 3.1.a"
+    - "< 3.2"
+- package-ecosystem: npm
+  directory: "/provider-ui"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10
+  reviewers:
+  - ramrodo
+  labels:
+  - kind/chore
+  - pr/dependencies

.github/stale.yml

@@ -1,5 +1,5 @@
 # Number of days of inactivity before an issue becomes stale
-daysUntilStale: 45
+daysUntilStale: 40
 # Number of days of inactivity before a stale issue is closed
 daysUntilClose: 10
 # Issues with these labels will never be considered stale