[Bug] Rename greenplum_path.sh and generate-greenplum-path.sh to remove trademarked references

[edespino]

Apache Cloudberry version

The source release for Apache Cloudberry (Incubating) 2.0.0 RC1 includes two filenames that reference the Greenplum® trademark:

greenplum_path.sh

gpMgmt/bin/generate-greenplum-path.sh

These files are invoked during the installation process and are therefore part of the user-visible and executable surface area of the product.

Why this is a problem

Under Apache Software Foundation policy, release artifacts must not include third-party trademarks in filenames, scripts, generated files, or visible output — unless required for compatibility and accompanied by explicit disclaimers.

These two files risk implying affiliation or endorsement by Broadcom Inc., which owns the Greenplum® trademark. This is especially concerning because:

generate-greenplum-path.sh is executed during installation

It produces an environment script named greenplum_path.sh

There is no contextual disclaimer or namespace isolation

This violates ASF release guidelines and blocks the promotion of RC1.

Context

This issue was flagged during the RC1 vote process by the release manager. A re-roll of RC2 will occur once the rename and install updates are complete.

What happened

Under Apache Software Foundation policy, release artifacts must not include third-party trademarks in filenames, scripts, generated files, or visible output — unless required for compatibility and accompanied by explicit disclaimers.

What you think should happen instead

Proposed Fix

Rename gpMgmt/bin/generate-greenplum-path.sh to generate-cloudberry-env.sh

Update the generated file name to cloudberry_env.sh (or another project-appropriate name)

Update all installation tooling, scripting, and test references accordingly

Validate the renamed script and generated file perform correctly

Document the rename in the changelog or README if needed

How to reproduce

Install from source and the file greenplum_path.sh is created in the installation directory.

Operating System

Linux

Anything else

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct.

[avamingli]

I understand your proposal, but I have some concerns:

The file greenplum_path.sh is widely used, and for many users, the first action during deployment is to run source greenplum_path.sh. Changing this name would disrupt established user behavior, especially for those who have long relied on Greenplum. This alteration could lead to unnecessary confusion and complications for our potential users, developers, and DBAs. Since Cloudberry is built upon Greenplum, it should maintain compatibility with existing behaviors.

I'm not sure how other Apache projects have addressed similar issues, but it might be beneficial to look into their solutions.

Additionally, we have numerous files named postgres.xxx, whose trademark is owned and managed by the PostgreSQL Community Association of Canada (PGCAC).

[leborchuk]

We could create greenplum_path.sh in post-install scripts of our packages. greenplum_path.sh won't exists in a code as a file, but for those who use our packages everything will work as usual.

[yjhjstz]

how about ln -s cloudberry-env.sh greenplum_path.sh in post-install scripts to minimize changes?

[leborchuk]

how about ln -s cloudberry-env.sh greenplum_path.sh in post-install scripts to minimize changes?

Yep, it would be the best

[tuhaihe]

Hi everyone, seems we have a few different views on this item. I would like to ask for help from the ASF brand team to make a confirmation. If any updates, will share them on the Dev mailing list and here.

Updates:

• I created a ticket to the ASF legal team to ask for help on this issue: https://issues.apache.org/jira/browse/LEGAL-703. Welcome to add your comments on it if I did not provide enough background info.

[leborchuk]

Hi, I've been thinking about the best way to fix issue.

And my proposal on how we could solve the issue without disrupting the development process: Let's split up the work into pieces:

1. Add new environment file (quite safe step) - see Add cloudberry-env.sh #1166
2. Switch to using cloudberry-env.sh in the cloudberry-devops-release repository (again quite safe, we could easily check if all works fine).
3. Use cloudberry-env in Makefile and other scripts.Remove greenplum-path from usage (I believe in our tests here).
4. Create a symbolic link in RPM and Debian packages. (step for backward compability)

[tuhaihe]

Hi everyone, seems we have a few different views on this item. I would like to ask for help from the ASF brand team to make a confirmation. If any updates, will share them on the Dev mailing list and here.

Updates:

• I created a ticket to the ASF legal team to ask for help on this issue: https://issues.apache.org/jira/browse/LEGAL-703. Welcome to add your comments on it if I did not provide enough background info.

Hi, I created a mailing thread on the file renaming: https://lists.apache.org/thread/b8o974mnnqk6zpy86dgll2pgqcvqgnwm. Welcome to continue the conversation there.