License: address the rc2 IPMC review

PJ Fanning's review of 2.2.0-incubating-rc2 found third-party files
that LICENSE did not cover, and his review of this change found a few
more corrections.  Register and fix them:

- src/include/optimizer/hints.h duplicates structures from
  pg_hint_plan.c and carries NTT's notice; list it under pg_hint_plan.
- googlemock's class generator in the gpcloud googletest copy is
  Apache-2.0, not googletest's BSD-3; say so.
- getopt_long.h and pg_getopt.h carry only a "Portions Copyright ...
  The Regents of the University of California" line, with no BSD
  license text; list them as headers derived from BSD getopt, under
  licenses/LICENSE-bsd3-regents.txt.
- The test_regex module's tests derive from Tcl's reg.test and point
  at src/backend/regex/COPYRIGHT; add them to the regex entry.
- Add a section for the build system files: the Autotools, pkg-config
  and Autoconf Archive files under config/, naming each file's
  licence, and the top-level configure script with its FSF notice.
  The GPL-licensed ones carry an exception for use in
  Autoconf-generated configure scripts, the basis of the ASF's
  build-tools allowance (LEGAL-290).
- In pom.xml, give config/ax_pthread.m4 (GPL-3.0-or-later with the
  Autoconf Macro exception) its own RAT exclude comment instead of
  the GPLv2 one.

Greenplum files carry the copyright notice of whoever owned the code
when they were written: Greenplum, Inc. (about 1050 files), EMC
Corporation (about 1100), Pivotal Software, VMware, Inc. and Broadcom,
plus three gpMgmt scripts with a legacy "Copyright (c) Metapa 2005"
notice.  The Greenplum section of LICENSE named only VMware; name all
of them, and open the section with its Apache License statement.  In
README.apache.md, list these companies as holders of the copyright
notices rather than as contributors under the Apache License 2.0, and
add Metapa, one of the two companies that merged to form Greenplum.
In pom.xml, note where the Metapa and Broadcom notices come from next
to the RAT patterns that classify them.

Assisted-by: Claude Code
3 files changed
tree: 9fc8ae966560ea3fad4321869ce6f94ff59d25bb
  1. .abi-check/
  2. .github/
  3. config/
  4. contrib/
  5. devops/
  6. doc/
  7. gpAux/
  8. gpcontrib/
  9. gpMgmt/
  10. licenses/
  11. mcp-server/
  12. src/
  13. .asf.yaml
  14. .clang-tidy
  15. .dir-locals.el
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gitmessage
  21. .gitmodules
  22. aclocal.m4
  23. AGENTS.md.template
  24. AI_GUIDELINE.md
  25. CODE_OF_CONDUCT.md
  26. configure
  27. configure.ac
  28. CONTRIBUTING.md
  29. DISCLAIMER
  30. getversion
  31. GNUmakefile.in
  32. LICENSE
  33. Makefile
  34. NOTICE
  35. pom.xml
  36. putversion
  37. python-dependencies.txt
  38. README.apache.md
  39. README.md
  40. SECURITY.md
  41. sonar-project.properties
README.md

Apache Cloudberry (Incubating)

Website Documentation Slack Twitter Follow WeChat Youtube GitHub Discussions GitHub commit activity(branch) GitHub contributors GitHub License Apache Cloudberry Build Ask DeepWiki Apache Rat Audit

Introduction

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 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 to build Cloudberry on Linux OS (including RHEL/Rocky Linux, and Ubuntu) and macOS.

Try out quickly

Welcome to try out Cloudberry via building one Docker-based Sandbox, which is tailored to help you gain a basic understanding of Cloudberry's capabilities and features.

Repositories

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.

Community & Support

We have many channels for community members to discuss, ask for help, feedback, and chat:

TypeDescription
SlackClick to Join the real-time chat on Slack for QA, Dev, Events, and more. Don't miss out! Check out the Slack guide to learn more.
Q&AAsk for help when running/developing Cloudberry, visit GitHub Discussions - QA.
New ideas / Feature RequestsShare ideas for new features, visit GitHub Discussions - Ideas.
Report bugsProblems and issues in Apache Cloudberry core. If you find bugs, welcome to submit them here.
Report a security vulnerabilityView our security policy to learn how to report and contact us.
Community eventsIncluding meetups, webinars, conferences, and more events, visit the Events page and subscribe to the events calendar.
DocumentationOfficial documentation for Cloudberry. You can explore it to discover more details about us.

Contribution

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 community welcomes contributions from anyone, new and experienced! Our contribution guide will help you get started with the contribution.

TypeDescription
Code contributionLearn how to contribute code to the Cloudberry, including coding preparation, conventions, workflow, review, and checklist following the code contribution guide.
Submit the proposalProposing major changes to Cloudberry through proposal guide.
Doc contributionWe need you to join us to help us improve the documentation, see the doc contribution guide.
AI guidlineFor AI-assisted development, please review our AI guideline for advice on responsible AI usage.

Roadmap

You can check our Cloudberry Roadmap out to see the product plans and goals we want to achieve. 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, Greenplum Database and other great open source projects to make Apache Cloudberry has a sound foundation.

License

Cloudberry is licensed under the Apache License, Version 2.0. For details, see the LICENSE.

Crypto Export Notice

This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org for more information.

The Apache Software Foundation has classified this software as Export Commodity Control Number (ECCN) 5D002, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the “publicly available” Section 742.15(b) exemption (see the BIS Export Administration Regulations, Section 742.15(b)) for both object code and source code.

The following provides more details on the included cryptographic software:

  • Apache Cloudberry uses OpenSSL for TLS support on client and server connections, and for the SCRAM-SHA-256 authentication method.
  • Apache Cloudberry optionally uses GSSAPI (Kerberos) for authentication and connection encryption, and LDAP over TLS for authentication.
  • The bundled pgcrypto extension provides cryptographic functions to SQL, using either OpenSSL or its own built-in implementations.
  • The gpfdist external table file server can serve over HTTPS, using OpenSSL and X.509 certificates supplied through its --ssl <certificates_directory> option.

Apache Cloudberry does not ship OpenSSL itself; it links against the OpenSSL provided by the operating system.

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.