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.git
The following commit(s) were added to refs/heads/main by this push:
new 11333c0b4d Doc: update basic community files for ASF
11333c0b4d is described below
commit 11333c0b4d3a4962b0a6610ceb5b6d7a12e45ec4
Author: Dianjin Wang <[email protected]>
AuthorDate: Fri Nov 1 15:23:26 2024 +0800
Doc: update basic community files for ASF
In this commit, basic community files are udpated to follow the Apache
rules and requests, including CoC, Security policy, and other places for
a good project name.
---
.asf.yaml | 4 +-
.github/DISCUSSION_TEMPLATE/proposal.yml | 4 +-
.github/ISSUE_TEMPLATE/bug-report.yml | 8 +-
.github/ISSUE_TEMPLATE/config.yml | 14 +--
.github/full_color_black.svg | 39 +++++++-
.github/full_color_white.svg | 39 +++++++-
.github/pull_request_template.md | 4 +-
.gitmessage | 4 +-
CODE_OF_CONDUCT.md | 135 ++------------------------
CONTRIBUTING.md | 102 ++++++++++----------
README.md | 156 +++++++++++++------------------
SECURITY.md | 68 ++------------
12 files changed, 223 insertions(+), 354 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 6054d1417b..04618bee51 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -129,7 +129,7 @@ notifications:
issues: [email protected]
# Route pull request notifications to commits mailing list
pullrequests: [email protected]
- # Route discussion notifications to commits mailing list
- discussions: [email protected]
+ # Route discussion notifications to dev mailing list
+ discussions: [email protected]
# Route dependabot pull request notifications to private mailing list
pullrequests_bot_dependabot: [email protected]
diff --git a/.github/DISCUSSION_TEMPLATE/proposal.yml
b/.github/DISCUSSION_TEMPLATE/proposal.yml
index bee7585e10..25cf78dbb0 100644
--- a/.github/DISCUSSION_TEMPLATE/proposal.yml
+++ b/.github/DISCUSSION_TEMPLATE/proposal.yml
@@ -5,11 +5,11 @@ body:
attributes:
value: "
- Thanks for proposing major changes to Cloudberry Database!
+ Thanks for proposing major changes to Apache Cloudberry!
When changes are just minor updates, general bug fixes, just Pull
Request directly!
- When you just have one idea or more `casual` feature request, consider
choosing [Ideas / Feature
Requests](https://github.com/apache/cloudberrydb/discussions/new?category=ideas-feature-requests).
+ When you just have one idea or more `casual` feature request, consider
choosing [Ideas / Feature
Requests](https://github.com/apache/cloudberry/discussions/new?category=ideas-feature-requests).
But any of the following can be considered a major change that needs to
have **Proposal**.
diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml
b/.github/ISSUE_TEMPLATE/bug-report.yml
index 732cc92a26..7b310ad360 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 Cloudberry Database core.
+description: Problems and issues with code in Apache Cloudberry core.
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 version
+ label: Apache Cloudberry version
description: What version are you using?
- type: textarea
attributes:
@@ -60,7 +60,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 7b889c42b7..26171e9e9b 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,17 +1,17 @@
blank_issues_enabled: false
contact_links:
- name: 🙏🏻 Q&A
- url: https://github.com/apache/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/apache/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/apache/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.
- name: 🪲 Issues for Website, Docs
- url: https://github.com/cloudberrydb/cloudberrydb-site/issues
+ url: https://github.com/apache/cloudberry-site/issues
about: Hey, we have one dedicated repo for the website and docs.
diff --git a/.github/full_color_black.svg b/.github/full_color_black.svg
index e0cec6febc..6fd299516f 100644
--- a/.github/full_color_black.svg
+++ b/.github/full_color_black.svg
@@ -1 +1,38 @@
-<svg xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink"; fill="none" version="1.1"
width="422" height="102" viewBox="0 0 422 102"><defs><clipPath
id="master_svg0_1_1088"><rect x="0" y="0" width="422" height="102"
rx="0"/></clipPath><clipPath id="master_svg1_1_1090"><rect x="0" y="-18"
width="140" height="140" rx="0"/></clipPath><linearGradient
x1="0.33318981528282166" y1="0.24062524735927582" x2="0.9564955234527588"
y2="1.1402971744537354" id="master_svg2_1_643" [...]
\ No newline at end of file
+<svg width="1200" height="199" viewBox="0 0 1200 199" fill="none"
xmlns="http://www.w3.org/2000/svg";>
+<g clip-path="url(#clip0_1_1126)">
+<path d="M369.423 171.976C361.81 171.976 354.768 170.723 348.295
168.218C341.823 165.712 336.207 162.163 331.449 157.572C326.691 152.98 322.982
147.579 320.322 141.368C317.662 135.156 316.333 128.343 316.333 120.931C316.333
113.519 317.662 106.708 320.322 100.497C322.982 94.2845 326.712 88.8824 331.511
84.2907C336.311 79.699 341.947 76.1503 348.419 73.6447C354.892 71.1391 361.934
69.8862 369.547 69.8862C377.64 69.8862 385.054 71.2794 391.788 74.0658C398.523
76.8521 404.185 80.9666 408.77 [...]
+<mask id="mask0_1_1126" style="mask-type:luminance" maskUnits="userSpaceOnUse"
x="1" y="-38" width="293" height="292">
+<path d="M293.435 -38H1.43542V254H293.435V-38Z" fill="white"/>
+</mask>
+<g mask="url(#mask0_1_1126)">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M77.4601 114.679L77.4559
114.674C71.5921 106.395 67.9804 97.4057 66.6208 87.7065C61.4427 90.0811 56.7974
93.4282 52.6849 97.748C45.1577 105.655 41.287 114.918 41.0727 125.538C40.8528
136.449 44.5235 146.044 52.0849 154.323C59.582 162.532 68.9692 167.388 80.2464
168.891L137.984 168.893L176.537 168.889L176.501 189.746L137.948 189.75L78.9126
189.747L78.2838 189.671C61.6364 187.64 47.7658 180.551 36.6719 168.404C25.3717
156.031 19.8876 141.615 [...]
+<path d="M203.201 185.17C236.686 185.17 263.831 159.071 263.831
126.876C263.831 94.6815 236.686 68.5825 203.201 68.5825C169.716 68.5825 142.571
94.6815 142.571 126.876C142.571 159.071 169.716 185.17 203.201 185.17Z"
stroke="url(#paint1_linear_1_1126)" stroke-width="21"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M265.145 17.4988C264.897
18.1989 264.632 18.8928 264.349 19.5805C264.066 20.2681 263.767 20.9488 263.45
21.6224C263.133 22.2961 262.8 22.9619 262.449 23.6199C262.099 24.2779 261.733
24.9273 261.35 25.5682C260.967 26.209 260.569 26.8405 260.155 27.4626C259.74
28.0847 259.311 28.6968 258.866 29.2989C258.421 29.9009 257.961 30.4922 257.486
31.0726C257.012 31.6531 256.523 32.2222 256.02 32.7797C255.517 33.3373 255
33.8827 254.469 34.416C253.93 [...]
+<path fill-rule="evenodd" clip-rule="evenodd" d="M182.692 129.148C183.154
131.246 184.006 133.23 185.247 135.101C186.561 137.08 188.216 138.783 190.211
140.209C190.434 140.368 190.648 140.537 190.853 140.717C191.059 140.897 191.256
141.087 191.443 141.286C191.63 141.485 191.807 141.693 191.973 141.91C192.14
142.126 192.296 142.35 192.44 142.582C192.585 142.814 192.718 143.053 192.839
143.298C192.961 143.543 193.07 143.793 193.167 144.049C193.263 144.304 193.347
144.564 193.418 144.828C19 [...]
+</g>
+<path d="M322.755 53.7713L340.102 15.8113H344.045L361.423
53.7713H357.195L341.234 18.1227H342.882L326.921 53.7713H322.755ZM329.572
43.65L330.759 40.3769H352.842L354.061 43.65H329.572ZM378.561
53.7713V15.8113H392.735C395.967 15.8113 398.74 16.3291 401.056 17.3645C403.372
18.3993 405.152 19.8847 406.396 21.8205C407.64 23.7563 408.262 26.0848 408.262
28.806C408.262 31.4914 407.64 33.806 406.396 35.7497C405.152 37.6935 403.372
39.183 401.056 40.2184C398.74 41.2533 395.967 41.7708 392.735 41. [...]
+<path d="M1167.95 90.4589V67.9541H1170.38L1181.45 85.1938H1180.19L1191.13
67.9541H1193.56L1193.59 90.4589H1190.75L1190.72 72.2H1191.33L1181.47
87.6756H1180.07L1170.02 72.2H1170.8V90.4589H1167.95ZM1153.08
90.4589V70.4359H1144.62V67.9541H1164.5V70.4359H1156.04V90.4589H1153.08Z"
fill="black"/>
+</g>
+<defs>
+<linearGradient id="paint0_linear_1_1126" x1="79.4053" y1="57.0286"
x2="190.152" y2="214.271" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FF5900"/>
+<stop offset="0.432306" stop-color="#FD9A2F"/>
+<stop offset="1" stop-color="#FFAA00"/>
+</linearGradient>
+<linearGradient id="paint1_linear_1_1126" x1="169.066" y1="78.4995"
x2="200.829" y2="185.872" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FE7C19"/>
+<stop offset="1" stop-color="#FEA315"/>
+</linearGradient>
+<linearGradient id="paint2_linear_1_1126" x1="229.445" y1="20.2011"
x2="240.964" y2="43.9007" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FF5900"/>
+<stop offset="1" stop-color="#FEA015"/>
+</linearGradient>
+<linearGradient id="paint3_linear_1_1126" x1="177.635" y1="125.346"
x2="184.697" y2="144.201" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FE7C19"/>
+<stop offset="1" stop-color="#FEA315"/>
+</linearGradient>
+<clipPath id="clip0_1_1126">
+<rect width="1200" height="199" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/.github/full_color_white.svg b/.github/full_color_white.svg
index 2f67b987d5..39d49edc6f 100644
--- a/.github/full_color_white.svg
+++ b/.github/full_color_white.svg
@@ -1 +1,38 @@
-<svg xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink"; fill="none" version="1.1"
width="422" height="102" viewBox="0 0 422 102"><defs><clipPath
id="master_svg0_97_1771"><rect x="0" y="0" width="422" height="102"
rx="0"/></clipPath><clipPath id="master_svg1_97_1783"><rect x="0" y="-18"
width="140" height="140" rx="0"/></clipPath><linearGradient
x1="0.33318981528282166" y1="0.24062524735927582" x2="0.9564955234527588"
y2="1.1402971744537354" id="master_svg2_1_64 [...]
\ No newline at end of file
+<svg width="1200" height="199" viewBox="0 0 1200 199" fill="none"
xmlns="http://www.w3.org/2000/svg";>
+<g clip-path="url(#clip0_92_311)">
+<path d="M369.423 171.976C361.81 171.976 354.768 170.723 348.295
168.218C341.823 165.712 336.207 162.163 331.449 157.572C326.692 152.98 322.983
147.579 320.322 141.368C317.663 135.156 316.333 128.343 316.333 120.931C316.333
113.519 317.663 106.708 320.322 100.497C322.983 94.2845 326.712 88.8824 331.511
84.2907C336.311 79.699 341.947 76.1503 348.419 73.6447C354.892 71.1391 361.935
69.8862 369.548 69.8862C377.641 69.8862 385.054 71.2794 391.788 74.0658C398.523
76.8521 404.185 80.9666 408.7 [...]
+<mask id="mask0_92_311" style="mask-type:luminance" maskUnits="userSpaceOnUse"
x="1" y="-38" width="293" height="292">
+<path d="M293.436 -38H1.43555V254H293.436V-38Z" fill="white"/>
+</mask>
+<g mask="url(#mask0_92_311)">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M77.4603 114.679L77.4562
114.674C71.5924 106.395 67.9807 97.4057 66.6211 87.7065C61.443 90.0811 56.7977
93.4282 52.6852 97.748C45.158 105.655 41.2872 114.918 41.073 125.538C40.853
136.449 44.5237 146.044 52.0851 154.323C59.5823 162.532 68.9695 167.388 80.2467
168.891L137.985 168.893L176.537 168.889L176.501 189.746L137.949 189.75L78.9128
189.747L78.284 189.671C61.6367 187.64 47.766 180.551 36.6722 168.404C25.372
156.031 19.8879 141.615 20.2 [...]
+<path d="M203.202 185.17C236.687 185.17 263.832 159.071 263.832
126.876C263.832 94.6815 236.687 68.5825 203.202 68.5825C169.717 68.5825 142.572
94.6815 142.572 126.876C142.572 159.071 169.717 185.17 203.202 185.17Z"
stroke="url(#paint1_linear_92_311)" stroke-width="21"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M265.145 17.4988C264.897
18.1989 264.632 18.8928 264.349 19.5805C264.066 20.2681 263.767 20.9488 263.45
21.6224C263.133 22.2961 262.8 22.9619 262.45 23.6199C262.099 24.2779 261.733
24.9273 261.35 25.5682C260.968 26.209 260.569 26.8405 260.155 27.4626C259.741
28.0847 259.311 28.6968 258.866 29.2989C258.421 29.9009 257.961 30.4922 257.486
31.0726C257.012 31.6531 256.523 32.2222 256.02 32.7797C255.517 33.3373 255
33.8827 254.469 34.416C253.93 [...]
+<path fill-rule="evenodd" clip-rule="evenodd" d="M182.692 129.148C183.154
131.246 184.006 133.23 185.247 135.101C186.561 137.08 188.216 138.783 190.211
140.209C190.434 140.368 190.648 140.537 190.853 140.717C191.059 140.897 191.256
141.087 191.443 141.286C191.63 141.485 191.807 141.693 191.973 141.91C192.14
142.126 192.296 142.35 192.44 142.582C192.585 142.814 192.718 143.053 192.839
143.298C192.961 143.543 193.07 143.793 193.167 144.049C193.263 144.304 193.347
144.564 193.418 144.828C19 [...]
+</g>
+<path d="M322.755 53.7713L340.102 15.8113H344.045L361.423
53.7713H357.195L341.234 18.1227H342.882L326.921 53.7713H322.755ZM329.572
43.65L330.759 40.3769H352.842L354.061 43.65H329.572ZM378.561
53.7713V15.8113H392.735C395.967 15.8113 398.74 16.3291 401.056 17.3645C403.372
18.3993 405.152 19.8847 406.396 21.8205C407.64 23.7563 408.262 26.0848 408.262
28.806C408.262 31.4914 407.64 33.806 406.396 35.7497C405.152 37.6935 403.372
39.183 401.056 40.2184C398.74 41.2533 395.967 41.7708 392.735 41. [...]
+<path d="M1167.95 90.4589V67.9541H1170.38L1181.45 85.1938H1180.19L1191.13
67.9541H1193.56L1193.59 90.4589H1190.75L1190.72 72.2H1191.33L1181.47
87.6756H1180.08L1170.02 72.2H1170.8V90.4589H1167.95ZM1153.08
90.4589V70.4359H1144.62V67.9541H1164.5V70.4359H1156.04V90.4589H1153.08Z"
fill="white"/>
+</g>
+<defs>
+<linearGradient id="paint0_linear_92_311" x1="79.4055" y1="57.0286"
x2="190.152" y2="214.271" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FF5900"/>
+<stop offset="0.432306" stop-color="#FD9A2F"/>
+<stop offset="1" stop-color="#FFAA00"/>
+</linearGradient>
+<linearGradient id="paint1_linear_92_311" x1="169.066" y1="78.4995"
x2="200.829" y2="185.872" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FE7C19"/>
+<stop offset="1" stop-color="#FEA315"/>
+</linearGradient>
+<linearGradient id="paint2_linear_92_311" x1="229.445" y1="20.2011"
x2="240.964" y2="43.9007" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FF5900"/>
+<stop offset="1" stop-color="#FEA015"/>
+</linearGradient>
+<linearGradient id="paint3_linear_92_311" x1="177.635" y1="125.346"
x2="184.697" y2="144.201" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FE7C19"/>
+<stop offset="1" stop-color="#FEA315"/>
+</linearGradient>
+<clipPath id="clip0_92_311">
+<rect width="1200" height="199" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index bfc25d0ffc..f8a0f84823 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,4 +1,4 @@
-<!-- Thank you for your contribution to Apache Cloudberry (incubating)! -->
+<!-- Thank you for your contribution to Apache Cloudberry (Incubating)! -->
Fixes #ISSUE_Number
@@ -46,4 +46,4 @@ Fixes #ISSUE_Number
---
<!-- Join our community:
- Mailing list:
[[email protected]](https://lists.apache.org/[email protected])
(subscribe: [email protected])
-- Discussions: https://github.com/apache/cloudberry/discussions -->
+- Discussions: https://github.com/apache/cloudberry/discussions -->
\ No newline at end of file
diff --git a/.gitmessage b/.gitmessage
index 93ab5e0714..9852789f9a 100644
--- a/.gitmessage
+++ b/.gitmessage
@@ -33,8 +33,8 @@ Add your commit body here
#on-behalf-of: @ORG [email protected]
# If your commit have clear context included in GitHub Issues or GitHub
# Discussions, please list them as a reference:
-#See: Issue#id <https://github.com/cloudberrydb/cloudberrydb/issues/?>?
-#See: Discussion#id <http://github.com/apache/cloudberrydb/discussions/>?
+#See: Issue#id <https://github.com/apache/cloudberry/issues/?>?
+#See: Discussion#id <http://github.com/apache/cloudberry/discussions/>?
########################################################################
#
#
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 922d7f5069..fba27afa81 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -1,131 +1,8 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
-## Our Pledge
+Apache Cloudberry (Incubating) follows the ASF [Code of
+Conduct](https://www.apache.org/foundation/policies/conduct).
-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
+If you observe behavior that violates those rules please follow the
+[ASF reporting
+guidelines](https://www.apache.org/foundation/policies/conduct#reporting-guidelines).
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index be139b9f8e..6cf5b3370c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,92 +1,88 @@
-Cloudberry Database community welcomes contributions from anyone, new
+Apache Cloudberry (Incubating) 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 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 appropriate to the circumstances. The moderator team is
-obligated to maintain confidentiality regarding the reporter of an
-incident.
+Everyone who participates in Cloudberry, either as a user or a
+contributor, is obliged to follow the [Code of
+Conduct](./CODE_OF_CONDUCT.md).
-Some behaviors that contribute to creating a positive environment
-include:
+We strive to:
-* Use welcoming and inclusive language.
-* Respect differing viewpoints and experiences.
-* Accept constructive criticism gracefully.
-* Foster what's best for the community.
-* Show empathy for community members.
+* Be open.
+* Be empathetic, welcoming, friendly, and patient.
+* Be collaborative.
+* Be inquisitive.
+* Be careful in the words that we choose.
+* Be concise.
+* Step down considerately.
## Find a Way to Contribute
-There are many ways to contribute to Cloudberry Database. Here are
-some ways you need to get started. The most common contributions
-include code, documentation, and community support.
+There are many ways to contribute to Cloudberry. Here are some ways
+you need to get started. The most common contributions include code,
+documentation, and community support.
You can participate by:
-* [Contributing code](https://cloudberrydb.org/contribute/code).
-* [Improving documentation](https://cloudberrydb.org/contribute/doc).
+* [Contributing code](https://cloudberry.apache.org/contribute/code).
+* [Improving
+ documentation](https://cloudberry.apache.org/contribute/doc).
* Helping out in the Slack channels, see [Slack
- Guide](https://cloudberrydb.org/community/slack)
+ Guide](https://cloudberry.apache.org/community/slack)
* Answering questions on [GitHub
-
Discussions](https://github.com/apache/cloudberrydb/discussions/categories/q-a).
+
Discussions](https://github.com/apache/cloudberry/discussions/categories/q-a).
* Investigating [GitHub
- issues](https://github.com/cloudberrydb/cloudberrydb/issues).
+ issues](https://github.com/apache/cloudberry/issues).
* [Reporting a new
- bug](https://github.com/cloudberrydb/cloudberrydb/issues/new/choose).
+ bug](https://github.com/apache/cloudberry/issues/new/choose).
* [Sharing ideas for new
-
features](https://github.com/apache/cloudberrydb/discussions/new?category=ideas-feature-requests).
+
features](https://github.com/apache/cloudberry/discussions/new?category=ideas-feature-requests).
* Helping review [Pull
- Requests](https://github.com/cloudberrydb/cloudberrydb/pulls) or
-
[Proposals](https://github.com/apache/cloudberrydb/discussions/categories/proposal).
-* Proposing your proposal, see [Proposal
Guide](https://cloudberrydb.org/contribute/proposal).
+ Requests](https://github.com/apache/cloudberry/pulls) or
+
[Proposals](https://github.com/apache/cloudberry/discussions/categories/proposal).
+* Proposing your proposal, see [Proposal
+ Guide](https://cloudberry.apache.org/contribute/proposal).
* [Reporting security issues](./SECURITY.md).
* Testing code, testing releases.
* Creating educational content (Blog posts, tutorials, videos, etc.)
* Spreading the word about Cloudberry Database on social media(eg,
Twitter, LinkedIn).
* ...
-* More things to make Cloudberry Database better.
+* More things to make Cloudberry better.
## Getting Help
Feel free to reach out to us in [Slack `#dev`
-channels](https://cloudberrydb.org/community/slack) or [GitHub
-Discussions](https://github.com/cloudberrydb/cloudberrydb/discussions)
-when your contribution is blocked, especially when making your first
+channels](https://cloudberry.apache.org/community/slack) or [GitHub
+Discussions](https://github.com/apache/cloudberry/discussions) when
+your contribution is blocked, especially when making your first
contribution. Don't be shy, we're happy to help.
-As the next-generation unified database, Cloudberry Database cannot
-grow without the support from the community. Hope to make our mission
-with you!
+Cloudberry cannot grow without the support from the community. Hope to
+make our mission with you!
## Benefits of Contribution
-There are many reasons to contribute to Cloudberry Database and open
-source projects in general. Here are some of the benefits of
-participating:
+There are many reasons to contribute to Cloudberry and open source
+projects in general. Here are some of the benefits of participating:
-* Growing your network. Working with Cloudberry Database in open
-source can help connect you with people working on similar things. You
-can get help or give help, and you might even make a real-life
-acquaintance!
+* Growing your network. Working with Cloudberry in open source can
+help connect you with people working on similar things. You can get
+help or give help, and you might even make a real-life acquaintance!
-* Improving your skills. When you work on a Cloudberry Database issue
-or Pull Request, inevitably you'll learn more about how something
-works in our project; either by asking questions and gathering info or
-by digging deeper into the code yourself. There’s a skill-building
-benefit to contributing to open source projects.
+* Improving your skills. When you work on a Cloudberry issue or Pull
+Request, inevitably you'll learn more about how something works in our
+project; either by asking questions and gathering info or by digging
+deeper into the code yourself. There’s a skill-building benefit to
+contributing to open source projects.
* Becoming an expert. You might start new to a project like Cloudberry
-Database or PostgreSQL, and by building things and opening issues when
-you encounter a new challenge or a bug, you’ll learn a ton over
-time. You could find your knowledge of said project has grown so much
-that you’ve become an expert.
+or PostgreSQL, and by building things and opening issues when you
+encounter a new challenge or a bug, you’ll learn a ton over time. You
+could find your knowledge of said project has grown so much that
+you’ve become an expert.
* Speaking at conferences or more community events. With those skills
you’ve earned yourself working in open source, you can let other
@@ -95,7 +91,7 @@ these community activities.
* Getting free swag! By participating in GitHub and other community
channels, you can become eligible for free swag that the Cloudberry
-Database team offers as a way to say thank you.
+team offers as a way to say thank you.
There are undoubtedly more benefits than those listed here. Hope you
-enjoy your contribution to the Cloudberry Database community!
+enjoy your contribution to the Cloudberry community!
diff --git a/README.md b/README.md
index c2adb781d2..29eceb5f9f 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,5 @@
+# Apache Cloudberry (Incubating)
+
<p align="center">
<picture>
<source media="(prefers-color-scheme: light)"
srcset="./.github/full_color_black.svg">
@@ -6,79 +8,55 @@
</picture>
</p>
-<p align="center">
- Next Generation Unified Database for Analytics and AI
-</p>
-
-[](https://cloudberrydb.org)
-[](https://cloudberrydb.org/docs)
-[](https://communityinviter.com/apps/cloudberrydb/welcome)
-[](https://twitter.com/cloudberrydb)
-[](https://cloudberrydb.org/community/wechat)
-[](https://youtube.com/@cloudberrydb)
-[](https://github.com/apache/cloudberrydb/discussions)
-
-
-
-
-[](https://github.com/cloudberrydb/cloudberrydb/actions/workflows/build.yml)
+[](https://cloudberry.apache.org)
+[](https://cloudberry.apache.org/docs)
+[](https://inviter.co/apache-cloudberry)
+[](https://twitter.com/ASFCloudberry)
+[](https://cloudberry.apache.org/community/wechat)
+[](https://youtube.com/@ApacheCloudberry)
+[](https://github.com/apache/cloudberry/discussions)
+
+
+
+[](https://github.com/apache/cloudberry/actions/workflows/build-cloudberry.yml)
---------
-## What's Cloudberry Database
-
-Cloudberry Database (`CBDB` or `CloudberryDB` for short) is created by a bunch
-of original Greenplum Database developers and ASF committers. We aim to bring
-modern computing capabilities to the traditional distributed MPP database to
-support Analytics and AI/ML workloads in one platform.
-
-As a derivative of Greenplum Database 7, Cloudberry Database is compatible
-with Greenplum Database, but it's shipped with a newer PostgreSQL 14.4 kernel
-(scheduled kernel upgrade yearly) and a bunch of features Greenplum Database
-lacks or does not support. View the [Cloudberry Database vs Greenplum
-Database](https://cloudberrydb.org/docs/cbdb-vs-gp-features) doc for details.
-
-## Roadmap
+## Introduction
-You can check our [Cloudberry Database Roadmap
-2024](https://github.com/apache/cloudberrydb/discussions/369) out to see the
-product plans and goals we want to achieve in 2024. Welcome to share your
-thoughts and ideas to join us in shaping the future of the Cloudberry
-Database.
+Apache Cloudberry (Incubating), created by the original developers of
+Greenplum Database, is one advanced and mature open-source Massively Parallel
+Processing (MPP) database, which evolves from the open-source version of the
+Pivotal Greenplum Database®️ but features a newer PostgreSQL kernel and more
+advanced enterprise capabilities. It can serve as a data warehouse and can
+also be used for large-scale analytics and AI/ML workloads.
## Build and try out
### Build from source
-You can follow [these guides](./deploy/build) to build the Cloudberry Database
on
-Linux OS(including CentOS, RHEL/Rocky Linux, and Ubuntu) and macOS.
+You can follow [these guides](./deploy/build) to build Cloudberry on
+Linux OS (including RHEL/Rocky Linux, and Ubuntu) and macOS.
### Try out quickly
-Welcome to try out Cloudberry Database via building [one Docker-based
-Sandbox](https://github.com/cloudberrydb/bootcamp), which is tailored to help
-you gain a basic understanding of Cloudberry Database's capabilities and
-features a range of materials, including tutorials, sample code, and crash
-courses.
+Welcome to try out Cloudberry via building [one Docker-based
+Sandbox](https://github.com/apache/cloudberry-bootcamp), which is tailored to
+help you gain a basic understanding of Cloudberry's capabilities and features
+a range of materials, including tutorials, sample code, and crash courses.
## Repositories
-This is the main repository for Cloudberry Database. Alongside this, there are
-several ecosystem repositories for the Cloudberry Database, including the
+This is the main repository for Apache Cloudberry (Incubating). Alongside
+this, there are several ecosystem repositories for Cloudberry, including the
website, extensions, connectors, adapters, and other utilities.
-*
[cloudberrydb/cloudberrydb-site](https://github.com/cloudberrydb/cloudberrydb-site):
website and documentation sources.
-* [cloudberrydb/bootcamp](https://github.com/cloudberrydb/bootcamp): help you
quickly try out Cloudberry Database via one Docker-based Sandbox.
-* [cloudberrydb/gpbackup](https://github.com/cloudberrydb/gpbackup): backup
utility for Cloudberry Database.
-*
[cloudberrydb/gp-common-go-libs](https://github.com/cloudberrydb/gp-common-go-libs):
gp-common-go-libs for Cloudberry Database.
-*
[cloudberrydb/gpbackup-s3-plugin](https://github.com/cloudberrydb/gpbackup-s3-plugin):
S3 plugin for use with Cloudberry Database backup utility.
-* [cloudberrydb/filedump](https://github.com/cloudberrydb/filedump): format
heap/index/control files into a human-readable form.
-* [cloudberrydb/postgis](https://github.com/cloudberrydb/postgis): PostGIS for
Cloudberry Database.
-* [cloudberrydb/pxf](https://github.com/cloudberrydb/pxf): Platform Extension
Framework (PXF) for Cloudberry Database.
-* [cloudberrydb/madlib](https://github.com/cloudberrydb/madlib): MADlib® for
Cloudberry Database.
-* [cloudberrydb/plr](https://github.com/cloudberrydb/plr): PL/R for Cloudberry
Database.
-* [cloudberrydb/pljava](https://github.com/cloudberrydb/pljava): PL/Java for
Cloudberry Database.
-* More is coming...
+* [apache/cloudberry-site](https://github.com/apache/cloudberry-site): website
and documentation sources.
+* [apache/cloudberry-bootcamp](https://github.com/apache/cloudberry-bootcamp):
help you quickly try out Cloudberry via one Docker-based Sandbox.
+* [apache/cloudberry-gpbackup](https://github.com/apache/cloudberry-gpbackup):
backup utility for Cloudberry.
+* [apache/cloudberry-go-libs](https://github.com/apache/cloudberry-go-libs):
go-libs for Cloudberry.
+*
[apache/cloudberry-gpbackup-s3-plugin](https://github.com/apache/cloudberry-gpbackup-s3-plugin):
S3 plugin for use with Cloudberry backup utility.
+* [apache/cloudberry-pxf](https://github.com/apache/cloudberry-pxf): Platform
Extension Framework (PXF) for Cloudberry.
## Community & Support
@@ -87,55 +65,55 @@ feedback, and chat:
| Type | Description |
|------|-------------|
-| Slack | [Click to
Join](https://communityinviter.com/apps/cloudberrydb/welcome) the real-time
chat on Slack for QA, Dev, Events, and more. Don't miss out! Check out the
[Slack guide](https://cloudberrydb.org/community/slack) to learn more. |
-| Q&A | Ask for help when running/developing Cloudberry Database, visit
[GitHub Discussions -
QA](https://github.com/apache/cloudberrydb/discussions/categories/q-a). |
-| New ideas / Feature Requests | Share ideas for new features, visit [GitHub
Discussions -
Ideas](https://github.com/apache/cloudberrydb/discussions/categories/ideas-feature-requests).
|
-| Report bugs | Problems and issues in Cloudberry Database core. If you find
bugs, welcome to submit them
[here](https://github.com/cloudberrydb/cloudberrydb/issues). |
-| Report a security vulnerability | View our [security
policy](https://github.com/cloudberrydb/cloudberrydb/security/policy) to learn
how to report and contact us. |
-| Community events | Including meetups, webinars, conferences, and more
events, visit the [Events page](https://cloudberrydb.org/community/events) and
subscribe events calendar. |
-| Documentation | [Official documentation](https://cloudberrydb.org/docs/) for
Cloudberry Database. You can explore it to discover more details about us. |
-
-When you are involved, please follow our community [Code of
-Conduct](https://cloudberrydb.org/community/coc) to help create a safe space
-for everyone.
+| Slack | [Click to Join](https://inviter.co/apache-cloudberry) the real-time
chat on Slack for QA, Dev, Events, and more. Don't miss out! Check out the
[Slack guide](https://cloudberry.apache.org/community/slack) to learn more. |
+| Q&A | Ask for help when running/developing Cloudberry, visit [GitHub
Discussions -
QA](https://github.com/apache/cloudberry/discussions/categories/q-a). |
+| New ideas / Feature Requests | Share ideas for new features, visit [GitHub
Discussions -
Ideas](https://github.com/apache/cloudberry/discussions/categories/ideas-feature-requests).
|
+| Report bugs | Problems and issues in Apache Cloudberry core. If you find
bugs, welcome to submit them
[here](https://github.com/apache/cloudberrydb/issues). |
+| Report a security vulnerability | View our [security
policy](https://github.com/apache/cloudberry/security/policy) to learn how to
report and contact us. |
+| Community events | Including meetups, webinars, conferences, and more
events, visit the [Events page](https://cloudberry.apache.org/community/events)
and subscribe events calendar. |
+| Documentation | [Official
documentation](https://cloudberry.apache.org/docs/) for Cloudberry. You can
explore it to discover more details about us. |
## Contribution
-We believe in the Apache Way "Community Over Code" and we want to make
-Cloudberry Database a community-driven project.
-
Contributions can be diverse, such as code enhancements, bug fixes, feature
proposals, documents, marketing, and so on. No contribution is too small, we
-encourage all types of contributions. Cloudberry Database community welcomes
+encourage all types of contributions. Cloudberry community welcomes
contributions from anyone, new and experienced! Our [contribution
-guide](https://cloudberrydb.org/contribute) will help you get started with the
-contribution.
+guide](https://cloudberry.apache.org/contribute) will help you get started
+with the contribution.
| Type | Description |
|----|---------------|
-| Code contribution | Learn how to contribute code to the Cloudberry Database,
including coding preparation, conventions, workflow, review, and checklist
following the [code contribution
guide](https://cloudberrydb.org/contribute/code).|
-| Submit the proposal | Proposing major changes to Cloudberry Database through
[proposal guide](https://cloudberrydb.org/contribute/proposal).|
-| Doc contribution | We need you to join us to help us improve the
documentation, see the [doc contribution
guide](https://cloudberrydb.org/contribute/doc).|
-
-## Contributors Wall
-
-Thanks to all the people who already contributed!
+| Code contribution | Learn how to contribute code to the Cloudberry,
including coding preparation, conventions, workflow, review, and checklist
following the [code contribution
guide](https://cloudberry.apache.org/contribute/code).|
+| Submit the proposal | Proposing major changes to Cloudberry through
[proposal guide](https://cloudberry.apache.org/contribute/proposal).|
+| Doc contribution | We need you to join us to help us improve the
documentation, see the [doc contribution
guide](https://cloudberry.apache.org/contribute/doc).|
-<a href="https://github.com/cloudberrydb/cloudberrydb/graphs/contributors";>
- <img
src="https://contrib.rocks/image?repo=cloudberrydb/cloudberrydb&max=800&columns=20&anon=0";
/>
-</a>
+## Roadmap
-<sub>Please note that the images shown above highlight the avatars of our
-active and upstream contributors while not including anonymous
-contributors. To view all the contributors, you can click on the images.</sub>
+You can check our [Cloudberry Roadmap
+2024](https://github.com/orgs/cloudberrydb/discussions/369) out to see the
+product plans and goals we want to achieve in 2024. Welcome to share your
+thoughts and ideas to join us in shaping the future of Apache Cloudberry
+(Incubating). (We will update the Roadmap after entering the Incubator.)
## Acknowledgment
Thanks to [PostgreSQL](https://www.postgresql.org/), [Greenplum
Database](https://greenplum.org/) and other great open source projects to make
-Cloudberry Database has a sound foundation.
+Apache Cloudberry has a sound foundation.
## License
-Cloudberry Database is released under the [Apache License, Version
-2.0](https://github.com/cloudberrydb/cloudberrydb/blob/main/LICENSE).
+Cloudberry is licensed under the Apache License, Version 2.0. For details, see
+the [LICENSE](./LICENSE).
+
+## ASF Incubator disclaimer
+
+Apache Cloudberry is an effort undergoing incubation at The Apache Software
+Foundation (ASF), sponsored by the Apache Incubator. Incubation is required
+for all newly accepted projects until a further review indicates that the
+infrastructure, communications, and decision making process have stabilized in
+a manner consistent with other successful ASF projects. While incubation
+status is not necessarily a reflection of the completeness or stability of the
+code, it does indicate that the project has yet to be fully endorsed by the
+ASF.
diff --git a/SECURITY.md b/SECURITY.md
index 36b48877d2..1b586a9a27 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -1,64 +1,8 @@
-Thanks for helping make Cloudberry Database safe!
+# Security Policy
----
+The Apache Cloudberry (Incubating) project follows the standard processes as
+set out by the [ASF security team](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:
-
-* 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
-
-This information will help us triage your report more quickly.
-
-## Do not
-
-For better collaboration, we hope you:
-
-- 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.
-
-## Handling Process
-
-Here's an overview of the security issues handling process:
-
-* 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.
-
-## Preferred Languages
-
-We prefer all communications to be in English.
+Please report any security issues to
+[[email protected]](mailto:[email protected]) or to
+([email protected])[mailto:[email protected]].
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
