GitHub user edespino added a comment to the discussion: Introducing the
[perfmon] Extension for Cloudberry Database Monitoring
I’ve now reviewed the related PR (#1085), and a few important things came up
that I want to bring back to this proposal thread:
🧬 Code Provenance
It’s now evident that the perfmon extension is derived from the Greenplum
gpperfmon codebase. That’s valuable context, but it needs to be made explicit
in this proposal for transparency and clarity—especially for those unfamiliar
with Greenplum internals.
We should clarify:
What code is reused or adapted from Greenplum?
What was changed or removed?
How licensing is handled (particularly given Cloudberry’s Apache 2.0
license)
🧭 Proposal → PR Flow
Also, I want to respectfully point out that the PR was submitted before the
proposal received any discussion or feedback. This limits the community’s
ability to weigh in on design, naming, and direction—especially for inherited
or complex features.
Can we encourage a clearer process going forward?
Propose the feature
Solicit feedback and refine
Submit the PR once there’s shared understanding
This would help ensure stronger community alignment and make it easier for new
contributors to follow along.
Let me know if you’d like help updating the proposal language to reflect this
background. I believe this feature has real potential — but it deserves a more
transparent and community-driven rollout.
GitHub link:
https://github.com/apache/cloudberry/discussions/1087#discussioncomment-13055973
----
This is an automatically sent email for dev@cloudberry.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@cloudberry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org
For additional commands, e-mail: dev-h...@cloudberry.apache.org
