This is an automated email from the ASF dual-hosted git repository.
djwang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudberry-pxf.git
The following commit(s) were added to refs/heads/main by this push:
new 9eb45ace ASF: update community files to follow ASF rules
9eb45ace is described below
commit 9eb45ace8a937bc642527b5da8d413e217ddacfa
Author: Dianjin Wang <[email protected]>
AuthorDate: Mon Jan 26 17:41:07 2026 +0800
ASF: update community files to follow ASF rules
This commit includes updates on these files:
.github/ISSUE_TEMPLATE/bug-report.yml
.github/ISSUE_TEMPLATE/config.yml
.github/pull_request_template.md
CODE-OF-CONDUCT.md
CONTRIBUTING.md
SECURITY.md
---
.github/ISSUE_TEMPLATE/bug-report.yml | 8 +-
.github/ISSUE_TEMPLATE/config.yml | 14 +--
.github/pull_request_template.md | 13 +--
CODE-OF-CONDUCT.md | 158 ++++++----------------------------
CONTRIBUTING.md | 8 +-
SECURITY.md | 99 +++++++++++----------
6 files changed, 97 insertions(+), 203 deletions(-)
diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml
b/.github/ISSUE_TEMPLATE/bug-report.yml
index ea736c32..90786500 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -1,14 +1,14 @@
name: "\U0001F41B Bug Report"
-description: Problems and issues with code in PXF for CloudberryDB.
+description: Problems and issues with code in PXF for Apache Cloudberry.
title: "[Bug] "
labels: ["type: Bug"]
body:
- type: markdown
attributes:
- value: "Thank you for reporting the problem! We really appreciate your
efforts to improve Cloudberry Database. Before reporting it, please (ideally)
test on the latest release or main to see if the issue is fixed."
+ value: "Thank you for reporting the problem! We really appreciate your
efforts to improve Apache Cloudberry. Before reporting it, please (ideally)
test on the latest release or main to see if the issue is fixed."
- type: textarea
attributes:
- label: Cloudberry Database and PXF version
+ label: Apache Cloudberry and PXF version
description: What version are you using?
- type: textarea
attributes:
@@ -56,7 +56,7 @@ body:
options:
- label: >
I agree to follow this project's
- [Code of Conduct](https://cloudberrydb.org/community/coc).
+ [Code of
Conduct](https://github.com/apache/cloudberry/blob/main/CODE_OF_CONDUCT.md).
required: true
- type: markdown
attributes:
diff --git a/.github/ISSUE_TEMPLATE/config.yml
b/.github/ISSUE_TEMPLATE/config.yml
index a3a57eb1..ea2b86e6 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,14 +1,14 @@
-blank_issues_enabled: false
+blank_issues_enabled: true
contact_links:
- name: 🙏🏻 Q&A
- url: https://github.com/orgs/cloudberrydb/discussions/categories/q-a
- about: Ask for help when running/developing Cloudberry Database.
+ url: https://github.com/apache/cloudberry/discussions/categories/q-a
+ about: Ask for help when running/developing Apache Cloudberry.
- name: 💡️ New Ideas / Feature Requests
- url:
https://github.com/orgs/cloudberrydb/discussions/categories/ideas-feature-requests
+ url:
https://github.com/apache/cloudberry/discussions/categories/ideas-feature-requests
about: Share ideas for new features.
- name: 🎙️ Submit Your Proposal
- url: https://github.com/orgs/cloudberrydb/discussions/categories/proposal
- about: As a developer, proposing any major change or enhancement to
Cloudberry Database.
+ url: https://github.com/apache/cloudberry/discussions/categories/proposal
+ about: As a developer, proposing any major change or enhancement to Apache
Cloudberry.
- name: 💬️ Join Slack for Real-time Chat
- url: https://communityinviter.com/apps/cloudberrydb/welcome
+ url: https://inviter.co/apache-cloudberry
about: Real-time chat including QA, Dev, Events and more.
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 0dfb7e84..3760148b 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,6 +1,7 @@
<!--Thank you for contributing! -->
+
<!--In case of an existing issue or discussions, please reference it-->
-fix #ISSUE_Number
+closes: #ISSUE_Number
<!--Remove this section if no corresponding issue.-->
---
@@ -13,8 +14,8 @@ fix #ISSUE_Number
Here are some reminders before you submit your pull request:
-* Make sure that your Pull Request has a clear title and commit message. You
can take the [Git commit
template](https://github.com/cloudberrydb/cloudberrydb/blob/main/.gitmessage)
as a reference.
-* Sign the Contributor License Agreement as prompted for your first-time
contribution (*One-time setup*).
-* Learn the [code contribution](https://cloudberrydb.org/contribute/code) and
[doc contribution](https://cloudberrydb.org/contribute/doc) guides for better
collaboration.
-* List your communications in the [GitHub
Issues](https://github.com/cloudberrydb/cloudberrydb-site/issues) or
[Discussions](https://github.com/orgs/cloudberrydb/discussions) (if has or
needed).
-* Feel free to ask for the cloudberrydb team to help review and approve.
+* Make sure that your Pull Request has a clear title and commit message. You
can take the [Git commit
template](https://github.com/apache/cloudberry/blob/main/.gitmessage) as a
reference.
+* Learn the [code contribution](https://cloudberry.apache.org/contribute/code)
and [doc contribution](https://cloudberry.apache.org/contribute/doc) guides for
better collaboration.
+* Make sure that CICD workflow is successful.
+* List your communications in the [GitHub
Issues](https://github.com/apache/cloudberry-pxf/issues) or
[Discussions](https://github.com/apache/cloudberry/discussions) (if has or
needed).
+* Feel free to ask for the [cloudberry
committers](https://github.com/orgs/apache/teams/cloudberry-committers) or
other people to help review and approve.
\ No newline at end of file
diff --git a/CODE-OF-CONDUCT.md b/CODE-OF-CONDUCT.md
index 922d7f50..aa80fc58 100644
--- a/CODE-OF-CONDUCT.md
+++ b/CODE-OF-CONDUCT.md
@@ -1,131 +1,27 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
- and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
- community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances
of
- any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
- without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders 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 will communicate reasons for
moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail
address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
[email protected].
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
+<!--
+ 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.
+-->
+
+# Code of Conduct
+
+Apache Cloudberry (Incubating) follows the ASF [Code of
+Conduct](https://www.apache.org/foundation/policies/conduct).
+
+If you observe behavior that violates those rules please follow the
+[ASF reporting
+guidelines](https://www.apache.org/foundation/policies/conduct#reporting-guidelines).
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 518942f4..6af259c5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,10 +1,10 @@
-Cloudberry Database community welcomes contributions from anyone, new and
+Apache Cloudberry community welcomes contributions from anyone, new and
experienced! We appreciate your interest in contributing. This guide will help
you get started with the contribution.
## Code of Conduct
-Everyone who participates in Cloudberry Database, either as a user or a
+Everyone who participates in Apache Cloudberry, either as a user or a
contributor, is obliged to follow our community [Code of
Conduct](./CODE_OF_CONDUCT.md). Every violation against it will be reviewed
and investigated and will result in a response that is deemed necessary and
@@ -25,13 +25,13 @@ Some behaviors that contribute to creating a positive
environment include:
2. Clone down the repo to your local system.
```
-git clone https://github.com/your-user-name/pxf.git
+git clone https://github.com/your-user-name/cloudberry-pxf.git
```
3. Add the upstream repo. (You only have to do this once, not every time.)
```
-git remote add upstream https://github.com/cloudberrydb/pxf.git
+git remote add upstream https://github.com/apache/cloudberry-pxf.git
```
4. Create a new branch to hold your work.
diff --git a/SECURITY.md b/SECURITY.md
index 36b48877..81c7936c 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -1,63 +1,60 @@
-Thanks for helping make Cloudberry Database safe!
+<!--
+ 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.
+-->
+
+# Security Policy
+
+The Apache Security Team handles all security issues across Apache projects and
+coordinates the response to vulnerabilities. For details on the vulnerability
+handling process, supported versions, and what is considered a security issue,
+visit: https://www.apache.org/security/.
----
-
-## Reporting Security Issues
-
-To report a security issue, please email
-[[email protected]](mailto:[email protected]). This
-project follows a 90-day disclosure timeline. We will publish the
-[security
-advisories](https://github.com/cloudberrydb/cloudberrydb/security/advisories)
-via GitHub.
-
-You should receive a response within 2 weeks. If for some reason you
-do not, please follow up via email to ensure we received your original
-message.
-
-Please include the requested information listed below (as much as you
-can provide) to help us better understand the nature and scope of the
-possible issue:
+## Do not
-* Type of issue (e.g. buffer overflow, SQL injection, cross-site
- scripting, etc.)
-* Full paths of source file(s) related to the manifestation of the
- issue
-* The location of the affected source code (tag/branch/commit or
- direct URL)
-* Any special configuration required to reproduce the issue
-* Step-by-step instructions to reproduce the issue
-* Proof-of-concept or exploit code (if possible)
-* Impact of the issue, including how an attacker might exploit the
- issue
+For better collaboration, we hope you:
-This information will help us triage your report more quickly.
+- DO NOT report non-security-impacting bugs through this channel. If you have
+ any questions on using, development, please use [GitHub
+ Issues](https://github.com/apache/cloudberry/issues),
+ [Discussions](https://github.com/apache/cloudberry/discussions), [Dev mailing
+ list](https://cloudberry.apache.org/community/mailing-lists) or
+ [Slack](https://inviter.co/apache-cloudberry) instead.
+- DO NOT report security issues on public GitHub Issues, Jira tickets, mailing
+ lists, or other public forums.
-## Do not
+## Reporting Security Issues
-For better collaboration, we hope you:
+Send your report to: [[email protected]](mailto:[email protected]).
-- Do not file public issues on GitHub for security vulnerabilities.
-- Do not report non-security-impacting bugs through this channel. If
- you have any questions on using, development, please use [GitHub
- Issues, Discussions or
- Slack](https://github.com/cloudberrydb/cloudberrydb/issues/new/choose)
- instead.
+Please send one plain-text email per vulnerability with the following and
+additional information as necessary (as much as you can provide):
-## Handling Process
+- Description of the vulnerability
+- Steps to reproduce
+- Affected versions
+- Potential impact
+- Any known mitigations
+- (Optional) Suggested fix
-Here's an overview of the security issues handling process:
+## Public Discussion
-* The reporter reports the security issues to the Cloudberry Database
- team.
-* The Cloudberry Database team investigates the report and decides to
- accept or reject the report. If our team rejects the report, the
- team will explain why to the reporter. If we accept the report, our
- team will work privately with the reporter to fix the security
- issues.
-* Release the new version of the Cloudberry Database that includes the
- fix.
-* Public the security issues.
+For general security questions or discussions, please use the development
+mailing list: [[email protected]](mailto:[email protected])
## Preferred Languages
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
