This is an automated email from the ASF dual-hosted git repository.

mfordjody pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-kubernetes.git


The following commit(s) were added to refs/heads/master by this push:
     new 5a002d0c Add a collaborative governance module (#962)
5a002d0c is described below

commit 5a002d0c04d65e39bda1ec23c336cd6b6e13c3d2
Author: mfordjody <[email protected]>
AuthorDate: Sat Jul 18 17:33:56 2026 +0800

    Add a collaborative governance module (#962)
---
 .github/ISSUE_TEMPLATE/bug_report.md      | 68 +++++++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml         | 20 +++++++++
 .github/ISSUE_TEMPLATE/feature_request.md | 54 ++++++++++++++++++++++++
 .github/pull_request_template.md          | 45 ++++++++++++++++++++
 CONTRIBUTING.md                           | 22 ++++++++++
 5 files changed, 209 insertions(+)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md 
b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 00000000..e5e41c1b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,68 @@
+---
+name: Bug report
+about: Report reproducible incorrect behavior
+title: ""
+labels: bug
+assignees: ""
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+## What happened?
+
+<!-- Describe the observed behavior and its impact. -->
+
+## What did you expect to happen?
+
+<!-- Describe the expected behavior. -->
+
+## How can we reproduce it?
+
+<!-- Provide the smallest reproducible sequence. Include sanitized manifests 
or configuration when relevant. -->
+
+1.
+2.
+3.
+
+## Environment
+
+- Dubbo Kubernetes version or commit:
+- Installation method (Helm, manifests, source, other):
+- Kubernetes version and distribution:
+- Container runtime:
+- Operating system and architecture:
+- Other relevant component versions:
+
+## Logs and diagnostics
+
+<!-- Paste the smallest relevant log/configuration excerpt in a code block. 
Remove tokens, credentials, private endpoints, and personal data. -->
+
+```text
+
+```
+
+## Additional context
+
+<!-- Add screenshots, related issues, frequency, or known workarounds. -->
+
+## Checklist
+
+- [ ] I searched existing issues and did not find a duplicate.
+- [ ] I provided reproducible steps or explained why reproduction is not 
currently possible.
+- [ ] I removed credentials, private data, and other sensitive information.
+- [ ] This is not a security vulnerability. Security reports must use the 
private ASF channel linked by the issue chooser.
diff --git a/.github/ISSUE_TEMPLATE/config.yml 
b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 00000000..665072bb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,20 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+blank_issues_enabled: true
+contact_links:
+  - name: Report a security vulnerability
+    url: https://www.apache.org/security/
+    about: Do not disclose vulnerabilities publicly; follow the ASF private 
reporting process.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md 
b/.github/ISSUE_TEMPLATE/feature_request.md
index e69de29b..caf8ded9 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,54 @@
+---
+name: Feature request
+about: Propose a user-facing capability or an improvement
+title: ""
+labels: feature
+assignees: ""
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+## Problem or use case
+
+<!-- What problem are you trying to solve? Who is affected, and why is the 
current behavior insufficient? -->
+
+## Proposed solution
+
+<!-- Describe the expected behavior and, when relevant, the proposed API, 
configuration, or command-line experience. -->
+
+## Alternatives considered
+
+<!-- Describe existing workarounds or alternative designs you considered. -->
+
+## Compatibility and scope
+
+<!-- Note upgrade, API, configuration, performance, security, or operational 
implications. Write "None" when not applicable. -->
+
+## Additional context
+
+<!-- Add diagrams, examples, related issues, or links that help explain the 
proposal. -->
+
+## Contribution
+
+- [ ] I am willing to help implement or test this feature.
+
+## Checklist
+
+- [ ] I searched existing issues and did not find a duplicate.
+- [ ] This request describes one concrete problem or capability.
+- [ ] I have not included credentials, private data, or other sensitive 
information.
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 00000000..4de780b5
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,45 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+## Summary
+
+<!-- Explain what changed and why. Keep the pull request focused on one 
problem. -->
+
+## Related issue
+
+<!-- Use "Fixes #123" or "Related to #123". Explain why no issue is needed 
when applicable. -->
+
+## Changes
+
+<!-- List the important behavioral, API, configuration, deployment, or 
documentation changes. -->
+
+## Verification
+
+<!-- List exact commands, environments, and results. Add screenshots or 
cluster evidence when behavior is user-visible. -->
+
+## Compatibility and rollout
+
+<!-- Describe upgrade, downgrade, API, configuration, performance, security, 
and rollback implications. Write "None" when not applicable. -->
+
+## Checklist
+
+- [ ] I read and followed `CONTRIBUTING.md`.
+- [ ] I ran the relevant tests and static checks, including `make verify` when 
applicable.
+- [ ] I added or updated tests for changed behavior, or explained why no test 
is needed.
+- [ ] I updated user-facing documentation and examples, or the change does not 
require them.
+- [ ] New source files include the Apache license header.
+- [ ] The change does not contain credentials, private data, generated build 
output, or unrelated edits.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 549d8877..5d097baf 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,6 +2,28 @@
 
 Dubbo Kubernetes is released under the non-restrictive Apache 2.0 license and 
follows a very standard GitHub development process, using GitHub tracker for 
issues and merging pull requests into master. Contributions of all forms to 
this repository are acceptable, as long as they follow the prescribed community 
guidelines enumerated below.
 
+## Before opening an issue
+
+- Search existing issues before filing a new one.
+- Use the bug report template for reproducible incorrect behavior and the
+  feature request template for a concrete new capability or improvement.
+- Include the smallest useful reproduction, version and environment details,
+  and sanitized logs. Never post credentials, private data, or security
+  vulnerabilities in a public issue.
+- Report suspected security vulnerabilities through the private process at
+  <https://www.apache.org/security/>.
+
+## Before opening a pull request
+
+- Keep each pull request focused on one problem and link the related issue.
+- Describe compatibility and rollout implications for API, configuration,
+  deployment, performance, or security changes.
+- Run the relevant tests and static checks. `make verify` runs the checks that
+  are fast enough for normal pre-push validation.
+- Add or update tests for changed behavior and update user-facing documentation
+  or examples when needed.
+- Complete the pull request checklist and include exact verification evidence.
+
 ## Bot commands
 
 Comment on an issue or pull request with one of the following commands (the 
command must start the comment):

Reply via email to