Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add to backend.run migration guide for 3rd party provider #2543

Open
jyu00 opened this issue Jan 2, 2025 · 4 comments
Open

Add to backend.run migration guide for 3rd party provider #2543

jyu00 opened this issue Jan 2, 2025 · 4 comments
Assignees
Labels
content request request for new content to be added content 📄

Comments

@jyu00
Copy link
Collaborator

jyu00 commented Jan 2, 2025

URL, if applicable

https://docs.quantum.ibm.com/migration-guides/qiskit-runtime

Describe the new content you are requesting.

Prompted by #2496 (comment), it'd be great to have a section on Migrate from third party provider under Migrate from backend.run to primitives to show people how to migrate to primitives even if the 3rd party provider they use don't support primitives (i.e. via backend primitives). This would allow users to switch between Qiskit Runtime and other 3rd party providers with little code modification.

If this new content request is accepted, do you want to write the content?

I can help the team by providing enough information to write the material

@jyu00 jyu00 added content request request for new content to be added content 📄 needs triage 🤔 this issue needs to be prioritized by the docs team labels Jan 2, 2025
@jyu00
Copy link
Collaborator Author

jyu00 commented Jan 2, 2025

Because I'm too lazy to open another issue, it'd be great to also add the motivation behind the move to primitives (also described in #2496) to the overview page.

@Eric-Arellano
Copy link
Collaborator

closing in favor of #2469

@jyu00
Copy link
Collaborator Author

jyu00 commented Jan 6, 2025

@Eric-Arellano I think this issue is different from #2469. This one is about updating the content of the existing migration guide related to 3rd party provider (target audience being regular users). #2469 is about creating a new migration guide for 3rd party providers (target audience being providers). Sure you can do both in a single PR, but they don't have to be.

@Eric-Arellano Eric-Arellano reopened this Jan 6, 2025
@abbycross abbycross removed the status in Docs Planning Jan 9, 2025
@abbycross abbycross removed the needs triage 🤔 this issue needs to be prioritized by the docs team label Jan 9, 2025
beckykd added a commit that referenced this issue Jan 21, 2025
@beckykd
Copy link
Collaborator

beckykd commented Jan 21, 2025

I think this is all addressed in #2496

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content request request for new content to be added content 📄
Projects
Status: No status
Development

No branches or pull requests

5 participants