Skip to content

"MQP-CUDAQ-Provider" Naming and Purpose #1

@mnfarooqi

Description

@mnfarooqi
  • I think it is better to create a repo after a name is decided as the name still will be there as part of URL if the code is kept in the same repo.
  • Provider is a qiskit terminology and doesn't seem to fit here.
  • I assume the repo is for the component that enable submitting quantum circuits via MQP from CUDAQ. It can be kept in the same repo where CUDAQ is. Why we need it in a separate repo? Do we keep a separate repo for each submission workflow e.g. for HPCQC workflow?
  • If the purpose is something like a MQPClient but in C/C++ then it can be a general client MQPClient that can be used by any C/C++ frontend and not just CUQAQ (for example QPI).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions