search

cloudfoundry / bosh-alicloud-cpi-release

BOSH Alibaba CPI
Apache License 2.0
32 stars 20 forks source link

Move Repository to cloudfoundry organization #168

Closed christopherclark closed 4 months ago

christopherclark commented 9 months ago

Hello @xiaozhu36,

The cloudfoundry-incubator GH organization only has a few active repositories left at this point, and will soon be archived. We'd like to discuss migrating this over to the cloudfoundry GH organization, presumably under the Foundational Infrastructure Working Group. Are you the sole maintainer of this repository at this point?

Adding @rkoster for visibility here.

xiaozhu36 commented 8 months ago

HI @christopherclark I am sorry for late reply. Yes, I am the maintainer and I think that is ok. I tried to transfer it, but I found I am not in cloudfoundry GH organization, does I need to apply joining it at first?

beyhan commented 8 months ago

Hi @xiaozhu36,

It makes sense to add the Ali Cloud CPI to the Foundational Infrastructure Working Group because all other CPI are there. Each working group has its yaml section, which defines sub-areas for the working group, which repositories belong to a corresponding sub-area and who are the approvers and reviewers of that sub-area. For the Foundational Infrastructure WG you can find in the Roles & Technical Assets section that information. Currently, all CPIs are located in the VM deployment lifecycle (BOSH) sub-area of the FI WG because they have the same set of approvers. For the Ali Cloud CPI we will have different set of approvers that is why I will suggest you to create a new sub-area for it, which you could manage. If you think this makes sense you could open a pr following this one but for the FI WG. When you are added as approver for a sub-area you will get automatically member of the cloudfoundry GH organization.

beyhan commented 8 months ago

the new repository has been create https://github.com/cloudfoundry/bosh-alicloud-cpi-release and the move can be executed now.

christopherclark commented 8 months ago

@xiaozhu36 @beyhan The repository has now been transferred. I believe it may take a few hours for the automation to sync and add the correct permissions.

xiaozhu36 commented 8 months ago

@christopherclark @beyhan Thanks a lot. In addition, I also need push permissions of other repos: stemcells-alicloud-index and bosh-alicloud-light-stemcell-builder and can you help me to add?

beyhan commented 7 months ago

@xiaozhu36 could you please comment on https://github.com/cloudfoundry/community/pull/800 that you are OK with this. Merging that pr will give you approver rights for the repositories.

xiaozhu36 commented 7 months ago

@beyhan I noticed cloudfoundry/community#800 has been merged, but I still have not rights to merge the repo PR, like #169 . Do I need more works?

beyhan commented 7 months ago

I'm on it with https://github.com/cloudfoundry/community/pull/806. The wrong default branch in https://github.com/cloudfoundry/community/pull/798 broke our automation.

beyhan commented 7 months ago

@xiaozhu36 the change is merged now but if everything is fine it will take ~3 to 4 hour to apply the changes because we have many repos in our org.

beyhan commented 7 months ago

@xiaozhu36 you should have the approver rights now.

xiaozhu36 commented 7 months ago

@beyhan Thanks a lot. It works now.

bgandon commented 4 months ago

Hi there, it seems the repo has been moved appropriately. Can we close this issue?

beyhan commented 4 months ago

Closing as the move is done.