search

IHPC-Quantum / PEC

Apache License 2.0
0 stars 0 forks source link

Repo structure #1

Open yjmaxpayne opened 4 months ago

yjmaxpayne commented 4 months ago

Hi Matthew and Tan Le,

May I suggest the following:

  1. Create a new public repo on backends and fork a copy of [qibo-cloud-backends main branch] (https://github.com/qiboteam/qibo-cloud-backends) for interface developments
  2. Fork Qibo PEC branch to the current PEC repo
  3. Configure all workflows to ensure they are running correctly
  4. Keep track of development on the Qibo end, and make timely sync-up

For your consideration, thanks.

mho291 commented 4 months ago

Hi Ye Jun,

  1. We can create a branch for qibo-AWS development. 2 & 3. Not a good idea to combine Qibo PEC and IHPC PEC codes. I will keep the already-working PEC codes for AWS use under IHPC PEC. The Qibo PEC will be a separate development between me and them.

Reason is that they move fast and my original codes will undergo scrutiny and I will need to spend a lot of time debugging their comments to make it usable for IHPC PEC when I already have working codes.

yjmaxpayne commented 4 months ago

Hi Ye Jun,

  1. We can create a branch for qibo-AWS development. 2 & 3. Not a good idea to combine Qibo PEC and IHPC PEC codes. I will keep the already-working PEC codes for AWS use under IHPC PEC. The Qibo PEC will be a separate development between me and them.

Reason is that they move fast and my original codes will undergo scrutiny and I will need to spend a lot of time debugging their comments to make it usable for IHPC PEC when I already have working codes.

I see; I think the PEC part is a good point. But I guess 3 (now changed to 4) should be also applicable to the fork (not a branch under the qibo-cloud-backends main branch. You can create a public repo under our IHPC GitHub Org to avoid disruption of Qibo's own progress for the cloud backends.

yjmaxpayne commented 4 months ago

Hi @mho291 , fork created: https://github.com/IHPC-Quantum/qibo-cloud-backends_AWS. I think we can leave the PEC repo for PEC related developments only.