Hello from the Qiskit/Quantum Metal maintainers 👋

[zlatko-minev]

Hi Onri,

Friendly hello from the Quantum Metal maintainers 👋

We've been mapping the open-source ecosystem around Quantum Metal,
and your Qiskit-Metal-to-Litho repo is exactly the kind of end-to-end
design → fab workflow story we like to highlight for new users —
especially the headless Colab install scripts and the bridge from
GDS export through e-beam lithography.

We've added a card linking to your repo on Quantum Metal's new
"Ecosystem" docs page and in the main README under "Built on Quantum
Metal." Wanted to:

1. Give you a heads-up so you'd see we're crediting you rather than
   discovering it from a stranger.
2. Ask — is the short description we used accurate, and does it frame
   your work the way you'd want? Happy to adjust wording or the emoji
   if you'd prefer something different.
3. Mention that if you're ever interested in contributing a tutorial
   or "recipe" page upstream into Quantum Metal proper (e.g. a
   "Quantum Metal in Colab, fully headless" walkthrough), we'd love
   that. Totally optional; your repo as-is already serves the
   community well.
4. See you at QDW 2026 https://qdw-ucla.squarespace.com/qdw2026

No urgency on any of this. Wanted to do this with a hello rather than
silently.

Cheers,
Quantum Metal maintainers

Links:

• Docs page: https://qiskit-community.github.io/qiskit-metal/ecosystem.html
• README ecosystem: https://github.com/qiskit-community/qiskit-metal#-ecosystem

[OJB-Quantum]

Wonderful news. I think the short description is perfect. We can likely talk more during or at the end of QDW 2026. Thanks. - Onri

[zlatko-minev]

Great On May 31, 2026, at 11:07 AM, Onri Jay Benally ***@***.***> wrote:OJB-Quantum left a comment (OJB-Quantum/Qiskit-Metal-to-Litho#1) Wonderful news. I think the short description is perfect. We can likely talk more during or at the end of QDW 2026. Thanks. - Onri —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>