You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudberry.apache.org by Dianjin Wang <wa...@gmail.com> on 2024/10/28 03:31:28 UTC
Transfer the GitHub repos to ASF
Hi everyone,
I’d like to update you on our progress. Since nearly all the initial
committers have signed the ICLAs, obtained the Apache IDs, and subscribed
to the private mailing list, we are in a good position. Additionally,
HashData has signed the SGA and has been recorded (see the private@c.a.o).
With this in mind, I would like to create an Infra issue to request
transferring the Cloudberry-related repos to ASF.
As is common with most ASF project repos, one project's repo names are in
the format: projectname-xxx, such as:
- flink-xxx: https://github.com/apache?q=flink-&type=all&language=&sort=
- skywalking-xxx:
https://github.com/apache?q=skywalking-&type=all&language=&sort=
So Cloudberry repos will be renamed:
1) https://github.com/cloudberrydb/cloudberrydb ~>
https://github.com/apache/cloudberry
2) https://github.com/cloudberrydb/cloudberrydb-site ~>
https://github.com/apache/cloudberry-site
3) https://github.com/cloudberrydb/bootcamp ~>
https://github.com/apache/cloudberry-bootcamp
4) https://github.com/cloudberrydb/gpbackup ~>
https://github.com/apache/cloudberry-gpbackup
5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
https://github.com/apache/cloudberry-gpbackup-s3-plugin
6) https://github.com/cloudberrydb/pxf ~>
https://github.com/apache/cloudberry-pxf
7) https://github.com/cloudberrydb/gp-common-go-libs ~>
https://github.com/apache/cloudberry-go-libs
8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
https://github.com/apache/cloudberry-devops-release
Would like to have your feedback! Thanks!
Best,
Dianjin Wang
Re: Transfer the GitHub repos to ASF
Posted by Dianjin Wang <wa...@gmail.com>.
Hi Roman,
Thanks for your suggestion.
After creating the infra issue to request the repos transfer, I will focus
on figuring out how to make it work.
For now, we can refer to the incubator branding policy:
https://incubator.apache.org/guides/branding.html. To build the website, I
think we may need to use the `.asf.yml` file as described here:
https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#deploy.
If need further assistance, I will reach out to the infra team or get you
guys to help.
Best,
Dianjin Wang
On Tue, Oct 29, 2024 at 7:55 AM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> +1 -- all good steps.
>
> Related: we should probably start talking about what mechanisms and infra
> would be required to convert
> https://github.com/apache/cloudberry-site
> into
> https://cloudberry.incubator.apache.org/
>
> Note that there are some legal requirement around including Incubator
> disclaimer
> on all of the sites of the incubation projects. See the example footer
> (at the very
> bottom of the page) here for example:
> https://annotator.incubator.apache.org/
>
> Thanks,
> Roman.
>
> On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
> >
> > +1 from me.
> >
> > Great progress on getting the initial commitments in place with the ICLAs
> > and HashData's SGA completion. The proposed repository naming structure
> > follows ASF conventions well, aligning with established patterns. The
> > mapping from current Cloudberry repos to their Apache equivalents looks
> > comprehensive and logical.
> >
> > The streamlined naming from "gp-common-go-libs" to "cloudberry-go-libs"
> is
> > a particularly good change that maintains clarity while fitting the
> Apache
> > naming scheme.
> >
> > Thanks for the detailed breakdown,
> > -=e
> >
> > On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com>
> wrote:
> >
> > > Hi everyone,
> > >
> > > I’d like to update you on our progress. Since nearly all the initial
> > > committers have signed the ICLAs, obtained the Apache IDs, and
> subscribed
> > > to the private mailing list, we are in a good position. Additionally,
> > > HashData has signed the SGA and has been recorded (see the
> private@c.a.o).
> > >
> > > With this in mind, I would like to create an Infra issue to request
> > > transferring the Cloudberry-related repos to ASF.
> > >
> > > As is common with most ASF project repos, one project's repo names are
> in
> > > the format: projectname-xxx, such as:
> > > - flink-xxx:
> https://github.com/apache?q=flink-&type=all&language=&sort=
> > > - skywalking-xxx:
> > > https://github.com/apache?q=skywalking-&type=all&language=&sort=
> > >
> > > So Cloudberry repos will be renamed:
> > >
> > > 1) https://github.com/cloudberrydb/cloudberrydb ~>
> > > https://github.com/apache/cloudberry
> > > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> > > https://github.com/apache/cloudberry-site
> > > 3) https://github.com/cloudberrydb/bootcamp ~>
> > > https://github.com/apache/cloudberry-bootcamp
> > > 4) https://github.com/cloudberrydb/gpbackup ~>
> > > https://github.com/apache/cloudberry-gpbackup
> > > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> > > https://github.com/apache/cloudberry-gpbackup-s3-plugin
> > > 6) https://github.com/cloudberrydb/pxf ~>
> > > https://github.com/apache/cloudberry-pxf
> > > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> > > https://github.com/apache/cloudberry-go-libs
> > > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> > > https://github.com/apache/cloudberry-devops-release
> > >
> > > Would like to have your feedback! Thanks!
> > >
> > > Best,
> > > Dianjin Wang
> > >
> >
> >
> > --
> > Ed Espino
> > Apache Cloudberry & MADlib
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> For additional commands, e-mail: dev-help@cloudberry.apache.org
>
>
Re: Transfer the GitHub repos to ASF
Posted by Dianjin Wang <wa...@gmail.com>.
Hello everyone,
As you may know, the related repos have already been transferred to ASF. To
follow up on this, I created pull requests for each repository that include
an `asf.yaml` file and an updated README.md. These PRs will configure the
repository settings and update the project name information.
- https://github.com/apache/cloudberry/pull/694 (Already got approved, but
still need to wait for the CICD checks to work)
- https://github.com/apache/cloudberry-site/pull/168
- https://github.com/apache/cloudberry-bootcamp/pull/38
- https://github.com/apache/cloudberry-devops-release/pull/1
- https://github.com/apache/cloudberry-pxf/pull/2
- https://github.com/apache/cloudberry-go-libs/pull/3
- https://github.com/apache/cloudberry-gpbackup-s3-plugin/pull/3
- https://github.com/apache/cloudberry-gpbackup/pull/10 (Still need to wait
for the CICD checks to work)
Please help review and approve them, thank you so much!
Best,
Dianjin Wang
On Wed, Oct 30, 2024 at 3:05 AM Ed Espino <es...@apache.org> wrote:
> Thank you Champ!
>
> On Tue, Oct 29, 2024 at 12:00 PM Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > On Tue, Oct 29, 2024 at 11:50 AM Ed Espino <es...@apache.org> wrote:
> > >
> > > I do believe we'll be running into GitHub Action resource utilization
> > > constraints. The team has been using AWS EC2 resources (utilizing
> > > philips-labs/terraform-aws-github-runner
> > > <https://github.com/philips-labs/terraform-aws-github-runner>) to
> > support
> > > building and testing CI/CD activities. Sep. 2024's total cost
> > > was $2,282.81. This will undoubtedly grow as we need to introduce
> > > additional testing processes.
> >
> > Then start talking to the ASF INFRA now ;-)
> >
> > Thanks,
> > Roman.
> >
> > >
> > > -=e
> > >
> > > On Tue, Oct 29, 2024 at 11:01 AM Roman Shaposhnik <
> roman@shaposhnik.org>
> > > wrote:
> > >
> > > > On Tue, Oct 29, 2024 at 1:35 AM Dianjin Wang <wa...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hey all,
> > > > >
> > > > > I just created one Infra issue to request the repos transfer to
> ASF:
> > > > > https://issues.apache.org/jira/browse/INFRA-26238. If any more
> > feedback,
> > > > > please let me know.
> > > > >
> > > > > As Roman mentioned, we need to make the website work under
> > > > > `apache/cloudberry-site`. Also, I would like to bring up the CICD
> > > > workflow,
> > > > > do we need to request the GitHub Actions resources or other
> > resources to
> > > > > make the PR tests run smoothly? cc @Max @Ed, FYI.
> > > >
> > > > IIRC you don't have to request anything upfront -- you get a certain
> > amount
> > > > of free GitHub Actions utilization and if you start bumping into
> > > > limitations
> > > > you need to talk to ASF's INFRA team.
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > > > For additional commands, e-mail: dev-help@cloudberry.apache.org
> > > >
> > > >
> > >
> > > --
> > > Ed Espino
> > > Apache Cloudberry & MADlib
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > For additional commands, e-mail: dev-help@cloudberry.apache.org
> >
> >
>
> --
> Ed Espino
> Apache Cloudberry & MADlib
>
Re: Transfer the GitHub repos to ASF
Posted by Ed Espino <es...@apache.org>.
Thank you Champ!
On Tue, Oct 29, 2024 at 12:00 PM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Tue, Oct 29, 2024 at 11:50 AM Ed Espino <es...@apache.org> wrote:
> >
> > I do believe we'll be running into GitHub Action resource utilization
> > constraints. The team has been using AWS EC2 resources (utilizing
> > philips-labs/terraform-aws-github-runner
> > <https://github.com/philips-labs/terraform-aws-github-runner>) to
> support
> > building and testing CI/CD activities. Sep. 2024's total cost
> > was $2,282.81. This will undoubtedly grow as we need to introduce
> > additional testing processes.
>
> Then start talking to the ASF INFRA now ;-)
>
> Thanks,
> Roman.
>
> >
> > -=e
> >
> > On Tue, Oct 29, 2024 at 11:01 AM Roman Shaposhnik <ro...@shaposhnik.org>
> > wrote:
> >
> > > On Tue, Oct 29, 2024 at 1:35 AM Dianjin Wang <wa...@gmail.com>
> > > wrote:
> > > >
> > > > Hey all,
> > > >
> > > > I just created one Infra issue to request the repos transfer to ASF:
> > > > https://issues.apache.org/jira/browse/INFRA-26238. If any more
> feedback,
> > > > please let me know.
> > > >
> > > > As Roman mentioned, we need to make the website work under
> > > > `apache/cloudberry-site`. Also, I would like to bring up the CICD
> > > workflow,
> > > > do we need to request the GitHub Actions resources or other
> resources to
> > > > make the PR tests run smoothly? cc @Max @Ed, FYI.
> > >
> > > IIRC you don't have to request anything upfront -- you get a certain
> amount
> > > of free GitHub Actions utilization and if you start bumping into
> > > limitations
> > > you need to talk to ASF's INFRA team.
> > >
> > > Thanks,
> > > Roman.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > > For additional commands, e-mail: dev-help@cloudberry.apache.org
> > >
> > >
> >
> > --
> > Ed Espino
> > Apache Cloudberry & MADlib
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> For additional commands, e-mail: dev-help@cloudberry.apache.org
>
>
--
Ed Espino
Apache Cloudberry & MADlib
Re: Transfer the GitHub repos to ASF
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, Oct 29, 2024 at 11:50 AM Ed Espino <es...@apache.org> wrote:
>
> I do believe we'll be running into GitHub Action resource utilization
> constraints. The team has been using AWS EC2 resources (utilizing
> philips-labs/terraform-aws-github-runner
> <https://github.com/philips-labs/terraform-aws-github-runner>) to support
> building and testing CI/CD activities. Sep. 2024's total cost
> was $2,282.81. This will undoubtedly grow as we need to introduce
> additional testing processes.
Then start talking to the ASF INFRA now ;-)
Thanks,
Roman.
>
> -=e
>
> On Tue, Oct 29, 2024 at 11:01 AM Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > On Tue, Oct 29, 2024 at 1:35 AM Dianjin Wang <wa...@gmail.com>
> > wrote:
> > >
> > > Hey all,
> > >
> > > I just created one Infra issue to request the repos transfer to ASF:
> > > https://issues.apache.org/jira/browse/INFRA-26238. If any more feedback,
> > > please let me know.
> > >
> > > As Roman mentioned, we need to make the website work under
> > > `apache/cloudberry-site`. Also, I would like to bring up the CICD
> > workflow,
> > > do we need to request the GitHub Actions resources or other resources to
> > > make the PR tests run smoothly? cc @Max @Ed, FYI.
> >
> > IIRC you don't have to request anything upfront -- you get a certain amount
> > of free GitHub Actions utilization and if you start bumping into
> > limitations
> > you need to talk to ASF's INFRA team.
> >
> > Thanks,
> > Roman.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > For additional commands, e-mail: dev-help@cloudberry.apache.org
> >
> >
>
> --
> Ed Espino
> Apache Cloudberry & MADlib
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: dev-help@cloudberry.apache.org
Re: Transfer the GitHub repos to ASF
Posted by Ed Espino <es...@apache.org>.
I do believe we'll be running into GitHub Action resource utilization
constraints. The team has been using AWS EC2 resources (utilizing
philips-labs/terraform-aws-github-runner
<https://github.com/philips-labs/terraform-aws-github-runner>) to support
building and testing CI/CD activities. Sep. 2024's total cost
was $2,282.81. This will undoubtedly grow as we need to introduce
additional testing processes.
-=e
On Tue, Oct 29, 2024 at 11:01 AM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Tue, Oct 29, 2024 at 1:35 AM Dianjin Wang <wa...@gmail.com>
> wrote:
> >
> > Hey all,
> >
> > I just created one Infra issue to request the repos transfer to ASF:
> > https://issues.apache.org/jira/browse/INFRA-26238. If any more feedback,
> > please let me know.
> >
> > As Roman mentioned, we need to make the website work under
> > `apache/cloudberry-site`. Also, I would like to bring up the CICD
> workflow,
> > do we need to request the GitHub Actions resources or other resources to
> > make the PR tests run smoothly? cc @Max @Ed, FYI.
>
> IIRC you don't have to request anything upfront -- you get a certain amount
> of free GitHub Actions utilization and if you start bumping into
> limitations
> you need to talk to ASF's INFRA team.
>
> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> For additional commands, e-mail: dev-help@cloudberry.apache.org
>
>
--
Ed Espino
Apache Cloudberry & MADlib
Re: Transfer the GitHub repos to ASF
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, Oct 29, 2024 at 1:35 AM Dianjin Wang <wa...@gmail.com> wrote:
>
> Hey all,
>
> I just created one Infra issue to request the repos transfer to ASF:
> https://issues.apache.org/jira/browse/INFRA-26238. If any more feedback,
> please let me know.
>
> As Roman mentioned, we need to make the website work under
> `apache/cloudberry-site`. Also, I would like to bring up the CICD workflow,
> do we need to request the GitHub Actions resources or other resources to
> make the PR tests run smoothly? cc @Max @Ed, FYI.
IIRC you don't have to request anything upfront -- you get a certain amount
of free GitHub Actions utilization and if you start bumping into limitations
you need to talk to ASF's INFRA team.
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: dev-help@cloudberry.apache.org
Re: Transfer the GitHub repos to ASF
Posted by Dianjin Wang <wa...@gmail.com>.
Hey all,
I just created one Infra issue to request the repos transfer to ASF:
https://issues.apache.org/jira/browse/INFRA-26238. If any more feedback,
please let me know.
As Roman mentioned, we need to make the website work under
`apache/cloudberry-site`. Also, I would like to bring up the CICD workflow,
do we need to request the GitHub Actions resources or other resources to
make the PR tests run smoothly? cc @Max @Ed, FYI.
Best,
Dianjin Wang
On Tue, Oct 29, 2024 at 1:40 PM Dianjin Wang <wa...@gmail.com> wrote:
> Hi Kent,
>
> No problem, let me recall my SVN skills back and try it. :)
>
> Best,
> Dianjin Wang
>
>
> On Tue, Oct 29, 2024 at 11:10 AM Kent Yao <ya...@apache.org> wrote:
>
>> LGTM.
>>
>> BTW, Can you update the IP clearance and sga fields here?
>>
>>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
>>
>> Kent Yao
>>
>> Roman Shaposhnik <ro...@shaposhnik.org> 于2024年10月29日周二 07:55写道:
>> >
>> > +1 -- all good steps.
>> >
>> > Related: we should probably start talking about what mechanisms and
>> infra
>> > would be required to convert
>> > https://github.com/apache/cloudberry-site
>> > into
>> > https://cloudberry.incubator.apache.org/
>> >
>> > Note that there are some legal requirement around including Incubator
>> disclaimer
>> > on all of the sites of the incubation projects. See the example footer
>> > (at the very
>> > bottom of the page) here for example:
>> > https://annotator.incubator.apache.org/
>> >
>> > Thanks,
>> > Roman.
>> >
>> > On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
>> > >
>> > > +1 from me.
>> > >
>> > > Great progress on getting the initial commitments in place with the
>> ICLAs
>> > > and HashData's SGA completion. The proposed repository naming
>> structure
>> > > follows ASF conventions well, aligning with established patterns. The
>> > > mapping from current Cloudberry repos to their Apache equivalents
>> looks
>> > > comprehensive and logical.
>> > >
>> > > The streamlined naming from "gp-common-go-libs" to
>> "cloudberry-go-libs" is
>> > > a particularly good change that maintains clarity while fitting the
>> Apache
>> > > naming scheme.
>> > >
>> > > Thanks for the detailed breakdown,
>> > > -=e
>> > >
>> > > On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com>
>> wrote:
>> > >
>> > > > Hi everyone,
>> > > >
>> > > > I’d like to update you on our progress. Since nearly all the initial
>> > > > committers have signed the ICLAs, obtained the Apache IDs, and
>> subscribed
>> > > > to the private mailing list, we are in a good position.
>> Additionally,
>> > > > HashData has signed the SGA and has been recorded (see the
>> private@c.a.o).
>> > > >
>> > > > With this in mind, I would like to create an Infra issue to request
>> > > > transferring the Cloudberry-related repos to ASF.
>> > > >
>> > > > As is common with most ASF project repos, one project's repo names
>> are in
>> > > > the format: projectname-xxx, such as:
>> > > > - flink-xxx:
>> https://github.com/apache?q=flink-&type=all&language=&sort=
>> > > > - skywalking-xxx:
>> > > > https://github.com/apache?q=skywalking-&type=all&language=&sort=
>> > > >
>> > > > So Cloudberry repos will be renamed:
>> > > >
>> > > > 1) https://github.com/cloudberrydb/cloudberrydb ~>
>> > > > https://github.com/apache/cloudberry
>> > > > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
>> > > > https://github.com/apache/cloudberry-site
>> > > > 3) https://github.com/cloudberrydb/bootcamp ~>
>> > > > https://github.com/apache/cloudberry-bootcamp
>> > > > 4) https://github.com/cloudberrydb/gpbackup ~>
>> > > > https://github.com/apache/cloudberry-gpbackup
>> > > > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
>> > > > https://github.com/apache/cloudberry-gpbackup-s3-plugin
>> > > > 6) https://github.com/cloudberrydb/pxf ~>
>> > > > https://github.com/apache/cloudberry-pxf
>> > > > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
>> > > > https://github.com/apache/cloudberry-go-libs
>> > > > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
>> > > > https://github.com/apache/cloudberry-devops-release
>> > > >
>> > > > Would like to have your feedback! Thanks!
>> > > >
>> > > > Best,
>> > > > Dianjin Wang
>> > > >
>> > >
>> > >
>> > > --
>> > > Ed Espino
>> > > Apache Cloudberry & MADlib
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
>> > For additional commands, e-mail: dev-help@cloudberry.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
>> For additional commands, e-mail: dev-help@cloudberry.apache.org
>>
>>
Re: Transfer the GitHub repos to ASF
Posted by Dianjin Wang <wa...@gmail.com>.
Hi Kent,
No problem, let me recall my SVN skills back and try it. :)
Best,
Dianjin Wang
On Tue, Oct 29, 2024 at 11:10 AM Kent Yao <ya...@apache.org> wrote:
> LGTM.
>
> BTW, Can you update the IP clearance and sga fields here?
>
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
>
> Kent Yao
>
> Roman Shaposhnik <ro...@shaposhnik.org> 于2024年10月29日周二 07:55写道:
> >
> > +1 -- all good steps.
> >
> > Related: we should probably start talking about what mechanisms and infra
> > would be required to convert
> > https://github.com/apache/cloudberry-site
> > into
> > https://cloudberry.incubator.apache.org/
> >
> > Note that there are some legal requirement around including Incubator
> disclaimer
> > on all of the sites of the incubation projects. See the example footer
> > (at the very
> > bottom of the page) here for example:
> > https://annotator.incubator.apache.org/
> >
> > Thanks,
> > Roman.
> >
> > On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
> > >
> > > +1 from me.
> > >
> > > Great progress on getting the initial commitments in place with the
> ICLAs
> > > and HashData's SGA completion. The proposed repository naming structure
> > > follows ASF conventions well, aligning with established patterns. The
> > > mapping from current Cloudberry repos to their Apache equivalents looks
> > > comprehensive and logical.
> > >
> > > The streamlined naming from "gp-common-go-libs" to
> "cloudberry-go-libs" is
> > > a particularly good change that maintains clarity while fitting the
> Apache
> > > naming scheme.
> > >
> > > Thanks for the detailed breakdown,
> > > -=e
> > >
> > > On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com>
> wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I’d like to update you on our progress. Since nearly all the initial
> > > > committers have signed the ICLAs, obtained the Apache IDs, and
> subscribed
> > > > to the private mailing list, we are in a good position. Additionally,
> > > > HashData has signed the SGA and has been recorded (see the
> private@c.a.o).
> > > >
> > > > With this in mind, I would like to create an Infra issue to request
> > > > transferring the Cloudberry-related repos to ASF.
> > > >
> > > > As is common with most ASF project repos, one project's repo names
> are in
> > > > the format: projectname-xxx, such as:
> > > > - flink-xxx:
> https://github.com/apache?q=flink-&type=all&language=&sort=
> > > > - skywalking-xxx:
> > > > https://github.com/apache?q=skywalking-&type=all&language=&sort=
> > > >
> > > > So Cloudberry repos will be renamed:
> > > >
> > > > 1) https://github.com/cloudberrydb/cloudberrydb ~>
> > > > https://github.com/apache/cloudberry
> > > > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> > > > https://github.com/apache/cloudberry-site
> > > > 3) https://github.com/cloudberrydb/bootcamp ~>
> > > > https://github.com/apache/cloudberry-bootcamp
> > > > 4) https://github.com/cloudberrydb/gpbackup ~>
> > > > https://github.com/apache/cloudberry-gpbackup
> > > > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> > > > https://github.com/apache/cloudberry-gpbackup-s3-plugin
> > > > 6) https://github.com/cloudberrydb/pxf ~>
> > > > https://github.com/apache/cloudberry-pxf
> > > > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> > > > https://github.com/apache/cloudberry-go-libs
> > > > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> > > > https://github.com/apache/cloudberry-devops-release
> > > >
> > > > Would like to have your feedback! Thanks!
> > > >
> > > > Best,
> > > > Dianjin Wang
> > > >
> > >
> > >
> > > --
> > > Ed Espino
> > > Apache Cloudberry & MADlib
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > For additional commands, e-mail: dev-help@cloudberry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> For additional commands, e-mail: dev-help@cloudberry.apache.org
>
>
Re: Transfer the GitHub repos to ASF
Posted by Kent Yao <ya...@apache.org>.
Thank you for the update, Tianjin!
Bests,
Kent
Dianjin Wang <wa...@gmail.com> 于2024年12月5日周四 12:33写道:
> Hi Kent,
>
> Sorry for the late reply.
> I just updated these two fields, PTAL:
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
> .
>
> Best,
> Dianjin Wang
>
>
> On Tue, Oct 29, 2024 at 11:10 AM Kent Yao <ya...@apache.org> wrote:
>
> > LGTM.
> >
> > BTW, Can you update the IP clearance and sga fields here?
> >
> >
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
> >
> > Kent Yao
> >
> > Roman Shaposhnik <ro...@shaposhnik.org> 于2024年10月29日周二 07:55写道:
> > >
> > > +1 -- all good steps.
> > >
> > > Related: we should probably start talking about what mechanisms and
> infra
> > > would be required to convert
> > > https://github.com/apache/cloudberry-site
> > > into
> > > https://cloudberry.incubator.apache.org/
> > >
> > > Note that there are some legal requirement around including Incubator
> > disclaimer
> > > on all of the sites of the incubation projects. See the example footer
> > > (at the very
> > > bottom of the page) here for example:
> > > https://annotator.incubator.apache.org/
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
> > > >
> > > > +1 from me.
> > > >
> > > > Great progress on getting the initial commitments in place with the
> > ICLAs
> > > > and HashData's SGA completion. The proposed repository naming
> structure
> > > > follows ASF conventions well, aligning with established patterns. The
> > > > mapping from current Cloudberry repos to their Apache equivalents
> looks
> > > > comprehensive and logical.
> > > >
> > > > The streamlined naming from "gp-common-go-libs" to
> > "cloudberry-go-libs" is
> > > > a particularly good change that maintains clarity while fitting the
> > Apache
> > > > naming scheme.
> > > >
> > > > Thanks for the detailed breakdown,
> > > > -=e
> > > >
> > > > On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com>
> > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > I’d like to update you on our progress. Since nearly all the
> initial
> > > > > committers have signed the ICLAs, obtained the Apache IDs, and
> > subscribed
> > > > > to the private mailing list, we are in a good position.
> Additionally,
> > > > > HashData has signed the SGA and has been recorded (see the
> > private@c.a.o).
> > > > >
> > > > > With this in mind, I would like to create an Infra issue to request
> > > > > transferring the Cloudberry-related repos to ASF.
> > > > >
> > > > > As is common with most ASF project repos, one project's repo names
> > are in
> > > > > the format: projectname-xxx, such as:
> > > > > - flink-xxx:
> > https://github.com/apache?q=flink-&type=all&language=&sort=
> > > > > - skywalking-xxx:
> > > > > https://github.com/apache?q=skywalking-&type=all&language=&sort=
> > > > >
> > > > > So Cloudberry repos will be renamed:
> > > > >
> > > > > 1) https://github.com/cloudberrydb/cloudberrydb ~>
> > > > > https://github.com/apache/cloudberry
> > > > > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> > > > > https://github.com/apache/cloudberry-site
> > > > > 3) https://github.com/cloudberrydb/bootcamp ~>
> > > > > https://github.com/apache/cloudberry-bootcamp
> > > > > 4) https://github.com/cloudberrydb/gpbackup ~>
> > > > > https://github.com/apache/cloudberry-gpbackup
> > > > > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> > > > > https://github.com/apache/cloudberry-gpbackup-s3-plugin
> > > > > 6) https://github.com/cloudberrydb/pxf ~>
> > > > > https://github.com/apache/cloudberry-pxf
> > > > > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> > > > > https://github.com/apache/cloudberry-go-libs
> > > > > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> > > > > https://github.com/apache/cloudberry-devops-release
> > > > >
> > > > > Would like to have your feedback! Thanks!
> > > > >
> > > > > Best,
> > > > > Dianjin Wang
> > > > >
> > > >
> > > >
> > > > --
> > > > Ed Espino
> > > > Apache Cloudberry & MADlib
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > > For additional commands, e-mail: dev-help@cloudberry.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > For additional commands, e-mail: dev-help@cloudberry.apache.org
> >
> >
>
Re: Transfer the GitHub repos to ASF
Posted by Dianjin Wang <wa...@gmail.com>.
Hi Kent,
Sorry for the late reply.
I just updated these two fields, PTAL:
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
.
Best,
Dianjin Wang
On Tue, Oct 29, 2024 at 11:10 AM Kent Yao <ya...@apache.org> wrote:
> LGTM.
>
> BTW, Can you update the IP clearance and sga fields here?
>
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
>
> Kent Yao
>
> Roman Shaposhnik <ro...@shaposhnik.org> 于2024年10月29日周二 07:55写道:
> >
> > +1 -- all good steps.
> >
> > Related: we should probably start talking about what mechanisms and infra
> > would be required to convert
> > https://github.com/apache/cloudberry-site
> > into
> > https://cloudberry.incubator.apache.org/
> >
> > Note that there are some legal requirement around including Incubator
> disclaimer
> > on all of the sites of the incubation projects. See the example footer
> > (at the very
> > bottom of the page) here for example:
> > https://annotator.incubator.apache.org/
> >
> > Thanks,
> > Roman.
> >
> > On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
> > >
> > > +1 from me.
> > >
> > > Great progress on getting the initial commitments in place with the
> ICLAs
> > > and HashData's SGA completion. The proposed repository naming structure
> > > follows ASF conventions well, aligning with established patterns. The
> > > mapping from current Cloudberry repos to their Apache equivalents looks
> > > comprehensive and logical.
> > >
> > > The streamlined naming from "gp-common-go-libs" to
> "cloudberry-go-libs" is
> > > a particularly good change that maintains clarity while fitting the
> Apache
> > > naming scheme.
> > >
> > > Thanks for the detailed breakdown,
> > > -=e
> > >
> > > On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com>
> wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I’d like to update you on our progress. Since nearly all the initial
> > > > committers have signed the ICLAs, obtained the Apache IDs, and
> subscribed
> > > > to the private mailing list, we are in a good position. Additionally,
> > > > HashData has signed the SGA and has been recorded (see the
> private@c.a.o).
> > > >
> > > > With this in mind, I would like to create an Infra issue to request
> > > > transferring the Cloudberry-related repos to ASF.
> > > >
> > > > As is common with most ASF project repos, one project's repo names
> are in
> > > > the format: projectname-xxx, such as:
> > > > - flink-xxx:
> https://github.com/apache?q=flink-&type=all&language=&sort=
> > > > - skywalking-xxx:
> > > > https://github.com/apache?q=skywalking-&type=all&language=&sort=
> > > >
> > > > So Cloudberry repos will be renamed:
> > > >
> > > > 1) https://github.com/cloudberrydb/cloudberrydb ~>
> > > > https://github.com/apache/cloudberry
> > > > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> > > > https://github.com/apache/cloudberry-site
> > > > 3) https://github.com/cloudberrydb/bootcamp ~>
> > > > https://github.com/apache/cloudberry-bootcamp
> > > > 4) https://github.com/cloudberrydb/gpbackup ~>
> > > > https://github.com/apache/cloudberry-gpbackup
> > > > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> > > > https://github.com/apache/cloudberry-gpbackup-s3-plugin
> > > > 6) https://github.com/cloudberrydb/pxf ~>
> > > > https://github.com/apache/cloudberry-pxf
> > > > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> > > > https://github.com/apache/cloudberry-go-libs
> > > > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> > > > https://github.com/apache/cloudberry-devops-release
> > > >
> > > > Would like to have your feedback! Thanks!
> > > >
> > > > Best,
> > > > Dianjin Wang
> > > >
> > >
> > >
> > > --
> > > Ed Espino
> > > Apache Cloudberry & MADlib
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> > For additional commands, e-mail: dev-help@cloudberry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> For additional commands, e-mail: dev-help@cloudberry.apache.org
>
>
Re: Transfer the GitHub repos to ASF
Posted by Kent Yao <ya...@apache.org>.
LGTM.
BTW, Can you update the IP clearance and sga fields here?
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/cloudberry.yml
Kent Yao
Roman Shaposhnik <ro...@shaposhnik.org> 于2024年10月29日周二 07:55写道:
>
> +1 -- all good steps.
>
> Related: we should probably start talking about what mechanisms and infra
> would be required to convert
> https://github.com/apache/cloudberry-site
> into
> https://cloudberry.incubator.apache.org/
>
> Note that there are some legal requirement around including Incubator disclaimer
> on all of the sites of the incubation projects. See the example footer
> (at the very
> bottom of the page) here for example:
> https://annotator.incubator.apache.org/
>
> Thanks,
> Roman.
>
> On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
> >
> > +1 from me.
> >
> > Great progress on getting the initial commitments in place with the ICLAs
> > and HashData's SGA completion. The proposed repository naming structure
> > follows ASF conventions well, aligning with established patterns. The
> > mapping from current Cloudberry repos to their Apache equivalents looks
> > comprehensive and logical.
> >
> > The streamlined naming from "gp-common-go-libs" to "cloudberry-go-libs" is
> > a particularly good change that maintains clarity while fitting the Apache
> > naming scheme.
> >
> > Thanks for the detailed breakdown,
> > -=e
> >
> > On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com> wrote:
> >
> > > Hi everyone,
> > >
> > > I’d like to update you on our progress. Since nearly all the initial
> > > committers have signed the ICLAs, obtained the Apache IDs, and subscribed
> > > to the private mailing list, we are in a good position. Additionally,
> > > HashData has signed the SGA and has been recorded (see the private@c.a.o).
> > >
> > > With this in mind, I would like to create an Infra issue to request
> > > transferring the Cloudberry-related repos to ASF.
> > >
> > > As is common with most ASF project repos, one project's repo names are in
> > > the format: projectname-xxx, such as:
> > > - flink-xxx: https://github.com/apache?q=flink-&type=all&language=&sort=
> > > - skywalking-xxx:
> > > https://github.com/apache?q=skywalking-&type=all&language=&sort=
> > >
> > > So Cloudberry repos will be renamed:
> > >
> > > 1) https://github.com/cloudberrydb/cloudberrydb ~>
> > > https://github.com/apache/cloudberry
> > > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> > > https://github.com/apache/cloudberry-site
> > > 3) https://github.com/cloudberrydb/bootcamp ~>
> > > https://github.com/apache/cloudberry-bootcamp
> > > 4) https://github.com/cloudberrydb/gpbackup ~>
> > > https://github.com/apache/cloudberry-gpbackup
> > > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> > > https://github.com/apache/cloudberry-gpbackup-s3-plugin
> > > 6) https://github.com/cloudberrydb/pxf ~>
> > > https://github.com/apache/cloudberry-pxf
> > > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> > > https://github.com/apache/cloudberry-go-libs
> > > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> > > https://github.com/apache/cloudberry-devops-release
> > >
> > > Would like to have your feedback! Thanks!
> > >
> > > Best,
> > > Dianjin Wang
> > >
> >
> >
> > --
> > Ed Espino
> > Apache Cloudberry & MADlib
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
> For additional commands, e-mail: dev-help@cloudberry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: dev-help@cloudberry.apache.org
Re: Transfer the GitHub repos to ASF
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
+1 -- all good steps.
Related: we should probably start talking about what mechanisms and infra
would be required to convert
https://github.com/apache/cloudberry-site
into
https://cloudberry.incubator.apache.org/
Note that there are some legal requirement around including Incubator disclaimer
on all of the sites of the incubation projects. See the example footer
(at the very
bottom of the page) here for example:
https://annotator.incubator.apache.org/
Thanks,
Roman.
On Mon, Oct 28, 2024 at 4:48 PM Ed Espino <es...@apache.org> wrote:
>
> +1 from me.
>
> Great progress on getting the initial commitments in place with the ICLAs
> and HashData's SGA completion. The proposed repository naming structure
> follows ASF conventions well, aligning with established patterns. The
> mapping from current Cloudberry repos to their Apache equivalents looks
> comprehensive and logical.
>
> The streamlined naming from "gp-common-go-libs" to "cloudberry-go-libs" is
> a particularly good change that maintains clarity while fitting the Apache
> naming scheme.
>
> Thanks for the detailed breakdown,
> -=e
>
> On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com> wrote:
>
> > Hi everyone,
> >
> > I’d like to update you on our progress. Since nearly all the initial
> > committers have signed the ICLAs, obtained the Apache IDs, and subscribed
> > to the private mailing list, we are in a good position. Additionally,
> > HashData has signed the SGA and has been recorded (see the private@c.a.o).
> >
> > With this in mind, I would like to create an Infra issue to request
> > transferring the Cloudberry-related repos to ASF.
> >
> > As is common with most ASF project repos, one project's repo names are in
> > the format: projectname-xxx, such as:
> > - flink-xxx: https://github.com/apache?q=flink-&type=all&language=&sort=
> > - skywalking-xxx:
> > https://github.com/apache?q=skywalking-&type=all&language=&sort=
> >
> > So Cloudberry repos will be renamed:
> >
> > 1) https://github.com/cloudberrydb/cloudberrydb ~>
> > https://github.com/apache/cloudberry
> > 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> > https://github.com/apache/cloudberry-site
> > 3) https://github.com/cloudberrydb/bootcamp ~>
> > https://github.com/apache/cloudberry-bootcamp
> > 4) https://github.com/cloudberrydb/gpbackup ~>
> > https://github.com/apache/cloudberry-gpbackup
> > 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> > https://github.com/apache/cloudberry-gpbackup-s3-plugin
> > 6) https://github.com/cloudberrydb/pxf ~>
> > https://github.com/apache/cloudberry-pxf
> > 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> > https://github.com/apache/cloudberry-go-libs
> > 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> > https://github.com/apache/cloudberry-devops-release
> >
> > Would like to have your feedback! Thanks!
> >
> > Best,
> > Dianjin Wang
> >
>
>
> --
> Ed Espino
> Apache Cloudberry & MADlib
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: dev-help@cloudberry.apache.org
Re: Transfer the GitHub repos to ASF
Posted by Ed Espino <es...@apache.org>.
+1 from me.
Great progress on getting the initial commitments in place with the ICLAs
and HashData's SGA completion. The proposed repository naming structure
follows ASF conventions well, aligning with established patterns. The
mapping from current Cloudberry repos to their Apache equivalents looks
comprehensive and logical.
The streamlined naming from "gp-common-go-libs" to "cloudberry-go-libs" is
a particularly good change that maintains clarity while fitting the Apache
naming scheme.
Thanks for the detailed breakdown,
-=e
On Sun, Oct 27, 2024 at 8:31 PM Dianjin Wang <wa...@gmail.com> wrote:
> Hi everyone,
>
> I’d like to update you on our progress. Since nearly all the initial
> committers have signed the ICLAs, obtained the Apache IDs, and subscribed
> to the private mailing list, we are in a good position. Additionally,
> HashData has signed the SGA and has been recorded (see the private@c.a.o).
>
> With this in mind, I would like to create an Infra issue to request
> transferring the Cloudberry-related repos to ASF.
>
> As is common with most ASF project repos, one project's repo names are in
> the format: projectname-xxx, such as:
> - flink-xxx: https://github.com/apache?q=flink-&type=all&language=&sort=
> - skywalking-xxx:
> https://github.com/apache?q=skywalking-&type=all&language=&sort=
>
> So Cloudberry repos will be renamed:
>
> 1) https://github.com/cloudberrydb/cloudberrydb ~>
> https://github.com/apache/cloudberry
> 2) https://github.com/cloudberrydb/cloudberrydb-site ~>
> https://github.com/apache/cloudberry-site
> 3) https://github.com/cloudberrydb/bootcamp ~>
> https://github.com/apache/cloudberry-bootcamp
> 4) https://github.com/cloudberrydb/gpbackup ~>
> https://github.com/apache/cloudberry-gpbackup
> 5) https://github.com/cloudberrydb/gpbackup-s3-plugin ~>
> https://github.com/apache/cloudberry-gpbackup-s3-plugin
> 6) https://github.com/cloudberrydb/pxf ~>
> https://github.com/apache/cloudberry-pxf
> 7) https://github.com/cloudberrydb/gp-common-go-libs ~>
> https://github.com/apache/cloudberry-go-libs
> 8) https://github.com/cloudberrydb/cloudberry-devops-release ~>
> https://github.com/apache/cloudberry-devops-release
>
> Would like to have your feedback! Thanks!
>
> Best,
> Dianjin Wang
>
--
Ed Espino
Apache Cloudberry & MADlib