From 7fea761af91bc87e35b78a6d26f977d9c46c5bbd Mon Sep 17 00:00:00 2001
From: laixingyou <laixy7@gmail.com>
Date: Tue, 12 Mar 2024 16:26:28 +0800
Subject: [PATCH] feat : add issue template

Signed-off-by: laixingyou <laixy7@gmail.com>
---
 .../ISSUE_TEMPLATE/new-metrics-model-idea.md  | 37 ++++++++++++++++
 .github/ISSUE_TEMPLATE/saas-bug-report.md     | 42 +++++++++++++++++++
 modules/community                             |  2 +-
 modules/docs                                  |  2 +-
 modules_i18n/community-zh                     |  2 +-
 modules_i18n/docs-zh                          |  2 +-
 6 files changed, 83 insertions(+), 4 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/new-metrics-model-idea.md
 create mode 100644 .github/ISSUE_TEMPLATE/saas-bug-report.md

diff --git a/.github/ISSUE_TEMPLATE/new-metrics-model-idea.md b/.github/ISSUE_TEMPLATE/new-metrics-model-idea.md
new file mode 100644
index 0000000..843acdc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/new-metrics-model-idea.md
@@ -0,0 +1,37 @@
+---
+name: New Metrics Model Idea
+about: Suggesting a new metrics models idea.
+title: "[Metrics Medel Lab]"
+labels: Metrics Model Lab
+assignees: eyehwan, normal-coder, wangliang-cs
+
+---
+
+<!-- Thank you for sharing your metric model idea with the Metrics Model Working Group! -->
+
+<!-- If it is an idea coming from CHAOSS metrics-model working group(https://github.com/chaoss/wg-metrics-models), you can attach metrics-model definition link here directly. Because we two communities have already setup a soomth collaboration process together. ! -->
+
+# Metric Model Title
+<!-- Title of the Metric Model -->
+
+# Why it Matters
+<!-- Provide text to explain to a reader why they should care about the metrics model. This description should be 1-2 sentences. -->
+
+# User Stories
+<!-- Provide text to the different types of users of this metrics model. This could include various roles including OSPO members, community managers, open source software users, and volunteer contributors. This should be in the form of a bulleted list for each of the provided user stories. -->
+
+# Metics in the Model
+<!--
+* Metric 1 (Link to metric on the CHAOSS website if applicable, brief description of the metric, and the suggested timeframe associated with data collection if applicable)
+* Metric 2 (Link to metric on the CHAOSS website if applicable, brief description of the metric, and the suggested timeframe associated with data collection if applicable)
+* And so on
+-->
+
+# References
+
+<!-- if this model has some references, like papers, articles etc, you can add links here.  
+-->
+
+# Projects to verify this model
+<!-- we have a list of open source projects classified by multiple technical fieds used to verify a new metrics-model, you can select a group of projects here(link would be coming soon). If projects we provided can not meet model's verify requirement, e.g. model is specific for a technical field, you can pop your requirement here also. 
+-->
diff --git a/.github/ISSUE_TEMPLATE/saas-bug-report.md b/.github/ISSUE_TEMPLATE/saas-bug-report.md
new file mode 100644
index 0000000..04c8b4e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/saas-bug-report.md
@@ -0,0 +1,42 @@
+---
+name: Saas Bug Report
+about: Creat a report to help us improve.
+title: '[Saas Bug Report]'
+labels: Saas Bug Report
+assignees: eyehwan, normal-coder, coder-sett
+---
+
+Issue tracker is **ONLY** used for reporting bugs. New features should be discussed on our slack channel. Please join our chat group on [Slack](https://join.slack.com/t/oss-compass/shared_invite/zt-1ttt9sv5h-8E~oPP6VJqm8ero5qH9LlA) for supporting issues.
+
+## Expected Behavior
+
+<!--- Tell us what should happen -->
+
+## Current Behavior
+
+<!--- Tell us what happens instead of the expected behavior -->
+
+## Possible Solution
+
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+
+## Steps to Reproduce
+
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+
+1.
+2.
+3.
+
+## Context (Environment)
+
+<!--- 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 -->
+
+## Detailed Description
+
+<!--- Provide a detailed description of the change or addition you are proposing -->
+
+## Possible Implementation
+
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->
diff --git a/modules/community b/modules/community
index 73d53e3..4baa276 160000
--- a/modules/community
+++ b/modules/community
@@ -1 +1 @@
-Subproject commit 73d53e31941c54caa18867b94f3b440a41af1fcb
+Subproject commit 4baa276f719ee85dde7c0c2a67bb6c86f54c6847
diff --git a/modules/docs b/modules/docs
index eb19d9b..ded8d37 160000
--- a/modules/docs
+++ b/modules/docs
@@ -1 +1 @@
-Subproject commit eb19d9be443533b75843727bd19f56e716b83d4f
+Subproject commit ded8d378a393c421252a65dbacd56e75e2c9324e
diff --git a/modules_i18n/community-zh b/modules_i18n/community-zh
index cf51cc2..4cb67de 160000
--- a/modules_i18n/community-zh
+++ b/modules_i18n/community-zh
@@ -1 +1 @@
-Subproject commit cf51cc2c0a0b58a9719705f81360ef8fe63420b6
+Subproject commit 4cb67deaa1d845e6f58d2b2b711e0eae8a2ea99b
diff --git a/modules_i18n/docs-zh b/modules_i18n/docs-zh
index fc90db5..97adac3 160000
--- a/modules_i18n/docs-zh
+++ b/modules_i18n/docs-zh
@@ -1 +1 @@
-Subproject commit fc90db54637b95149eca6f3fb7160b08e04234bd
+Subproject commit 97adac3d9f69c08143b0b87970d858cf01d32566