GitHub user tuhaihe added a comment to the discussion: [Ideas] Remove Bundled
Python Packages in Cloudberry Main Repo
Here, I can provide more information based on the research work for the
reference:
| Packages | License| Used by
Hi all,
Our repo has some bundled Python packages[1], one of which is
`pylint-0.21.0.tar.gz`, which is under the GPL v2 license. Since the
GPL v2 license is categorized as CatX[2], we cannot include `pylint`
in our repo.
We discussed this topic[3], such as removing these packages or using
`ruff`
GitHub user tuhaihe added a comment to the discussion: Cloudberry Command Center
For now, share one Cloudberry monitor repo by @gspiegelberg :
https://github.com/gspiegelberg/cloudberry-mon , FYI.
GitHub link:
https://github.com/apache/cloudberry/discussions/1046#discussioncomment-12797990
-
GitHub user my-ship-it added a comment to the discussion: Cloudberry Command
Center
Yes, we have already supported command center in commercial version and plan to
open source it, you can see it is already in the roadmap:
https://github.com/apache/cloudberry/discussions/868
GitHub link:
http
+1, I'm encountering the same problem.
张明礼 于2025年4月9日周三 11:19写道:
> Hi,
>
>
> It has come to my attention that the Apache Cloudberry GitHub repository’s
> Discussion page https://github.com/apache/cloudberry/discussions has been
> abruptly removed, resulting in the loss of all prior community di
There is one error in the .asf.yaml, FYI.
Also, the ASF infra team has helped report one issue on it:
https://github.com/apache/cloudberry/issues/1035.
We need to see how to fix it. Otherwise, we cannot enable the Wiki
feature for Cloudberry because of the error.
Best,
Dianjin Wang
--
Hey,
I just created a PR to bring the Discussions feature back:
https://github.com/apache/cloudberry/pull/1039. Don't worry; it is
still there, just disabled.
I have no idea, but guess it should be related to the discussion here
[1] - the asf.yaml processing way changed about a month ago.
[1] htt
GitHub user edespino edited a comment on the discussion: [Ideas] Remove Bundled
Python Packages in Cloudberry Main Repo
@tuhaihe I'm curious whether anyone is currently using pylint during
development or testing. Personally, I'm not aware of it being in active use. It
might be worth cross-pos
Hi all,
My colleagues and I have internally discussed the option of using a "merge
main" approach to bypass the "100+ commit rebase and merge problem".
Why not "merge main"?
- Non-linear History: Merging main would create a non-linear commit graph.
- Impact on Git Bisect: This could com
Hi Jiaqi,
Thanks again for explaining the reasoning behind splitting the PAX PR.
Your concerns about "merge main" are well-taken — it introduces
non-linear history, complicates git bisect, and can lead to downstream
integration issues. It's clear that the decision to split was made
carefully under
Hi all,
I’d like to raise a contribution workflow concern we're currently
encountering in Apache Cloudberry (Incubating), and propose that we
establish a preferred approach for handling similar situations going
forward.
Contributor *@jiaqizho* submitted a significant pull request:
*#1002 – Featur
Hi all,
There is one PR on adding the SonarQube workflow to the Cloudberry:
https://github.com/apache/cloudberry/pull/1004. Need more reviewers to
merge it. Appreciate your help!
Best,
Dianjin Wang
On Mon, Mar 24, 2025 at 9:12 PM Dianjin Wang wrote:
>
> Yes, exactly. Hope we can make use of the
Hey Ed,
Thanks for your updates. Now the PAX PR[1] has 300+ commits in one
single PR, cicd workflow passed, but cannot rebase and merge into the
main branch - that's limited by the GitHub product[1]. We're thinking
of splitting this huge PR into small PRs and tagging them `skip ci`.
Hope this can
Hi all,
We’ve recently added three new pages to the Cloudberry website `Team`
module to help streamline the committer onboarding process:
* Inviting New Committers:
https://cloudberry.apache.org/team/new-committers
A quick reference for PPMC members on the steps for inviting a new committer.
* Q
14 matches
Mail list logo