<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The project on QuoUSKWe</title><link>https://quouskwe-project.deib.polimi.it/</link><description>Recent content in The project on QuoUSKWe</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://quouskwe-project.deib.polimi.it/index.xml" rel="self" type="application/rss+xml"/><item><title>The QuoUSKWe website is online</title><link>https://quouskwe-project.deib.polimi.it/news/website-online/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/news/website-online/</guid><description>The official website for the project is online.</description></item><item><title>Consortium</title><link>https://quouskwe-project.deib.polimi.it/consortium/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/consortium/</guid><description>&lt;p&gt;The consortium covers the full value chain of quantum software development —
from high-level programming and compiler infrastructure through to hardware
integration and application validation. It is geographically distributed across
Europe and South Korea, in line with the EU–ROK cooperation objectives of the
call.&lt;/p&gt;
&lt;p&gt;Each partner names a &lt;strong&gt;representative&lt;/strong&gt; — the person scientifically responsible
for the project at that institution, its local principal investigator — and a
&lt;strong&gt;deputy&lt;/strong&gt; who stands in for them.&lt;/p&gt;</description></item><item><title>Consortium resources</title><link>https://quouskwe-project.deib.polimi.it/internal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/internal/</guid><description>&lt;p&gt;These services are for consortium members. This page is public — it only
explains how to reach them; the services themselves are behind a login.&lt;/p&gt;
&lt;h2 id="the-services"&gt;The services&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://quouskwe-project.deib.polimi.it/cloud"&gt;Nextcloud&lt;/a&gt;&lt;/strong&gt; — file storage, at &lt;code&gt;/cloud&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://quouskwe-project.deib.polimi.it/git"&gt;Forgejo&lt;/a&gt;&lt;/strong&gt; — code repositories, at &lt;code&gt;/git&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://quouskwe-project.deib.polimi.it/auth"&gt;Authelia&lt;/a&gt;&lt;/strong&gt; — the single sign-on portal, at &lt;code&gt;/auth&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://quouskwe-project.deib.polimi.it/"&gt;This website&lt;/a&gt;&lt;/strong&gt; — public project site&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-signing-in-works"&gt;How signing in works&lt;/h2&gt;
&lt;p&gt;All access goes through &lt;strong&gt;&lt;a href="https://quouskwe-project.deib.polimi.it/auth"&gt;Authelia&lt;/a&gt;&lt;/strong&gt;, the single sign-on portal. There
is no separate username and password for Nextcloud or Forgejo: you sign in once
through Authelia and both accept that login. Direct login with a local password
is not available for regular users.&lt;/p&gt;</description></item><item><title>Contact</title><link>https://quouskwe-project.deib.polimi.it/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/contact/</guid><description>&lt;h2 id="coordination"&gt;Coordination&lt;/h2&gt;
&lt;p&gt;The project is coordinated by &lt;strong&gt;Politecnico di Milano&lt;/strong&gt; (POLIMI), Italy.
&lt;strong&gt;Gerardo Pelosi&lt;/strong&gt; is the project coordinator, with &lt;strong&gt;Giovanni Agosta&lt;/strong&gt; as
deputy.&lt;/p&gt;
&lt;h2 id="partner-contacts"&gt;Partner contacts&lt;/h2&gt;
&lt;p&gt;Each partner&amp;rsquo;s representative and deputy are listed on the
&lt;a href="https://quouskwe-project.deib.polimi.it/consortium/"&gt;consortium page&lt;/a&gt;, and each work package&amp;rsquo;s leader
on the &lt;a href="https://quouskwe-project.deib.polimi.it/work-packages/"&gt;work packages page&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="following-the-project"&gt;Following the project&lt;/h2&gt;
&lt;p&gt;News and results are posted on the &lt;a href="https://quouskwe-project.deib.polimi.it/news/"&gt;news page&lt;/a&gt;, which is
also available as an &lt;a href="https://quouskwe-project.deib.polimi.it/index.xml"&gt;RSS feed&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Events</title><link>https://quouskwe-project.deib.polimi.it/events/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/events/</guid><description>&lt;p&gt;The consortium runs joint EU–ROK workshops and training sessions (WP3), and
presents results at scientific and industrial venues. Public outreach includes
events such as the European Researchers&amp;rsquo; Night and local science fairs.&lt;/p&gt;
&lt;p&gt;By the end of the project the consortium aims for 20 conference participations,
two workshops and one hackathon.&lt;/p&gt;</description></item><item><title>Media kit</title><link>https://quouskwe-project.deib.polimi.it/media-kit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/media-kit/</guid><description>&lt;p&gt;Everything here may be reused to write or talk about QuoUSKWe, provided the
project is credited and the EU funding acknowledgement is kept intact.&lt;/p&gt;
&lt;h2 id="how-to-refer-to-the-project"&gt;How to refer to the project&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Acronym:&lt;/strong&gt; QuoUSKWe (pronounced &lt;em&gt;kwo-us-kwe&lt;/em&gt;, from the Latin &lt;em&gt;quousque&lt;/em&gt;, &amp;ldquo;up to which limit&amp;rdquo;)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full name:&lt;/strong&gt; Quantum computing European Union–South Korea Working Team&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Programme:&lt;/strong&gt; Horizon Europe, call HORIZON-CL4-2025-03-DIGITAL-EMERGING-03&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="boilerplate"&gt;Boilerplate&lt;/h2&gt;
&lt;p&gt;TODO check if the text is correct.&lt;/p&gt;
&lt;p&gt;Short text to copy into articles, press releases and event programmes:&lt;/p&gt;</description></item><item><title>Outcomes</title><link>https://quouskwe-project.deib.polimi.it/outcomes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/outcomes/</guid><description>&lt;p&gt;QuoUSKWe commits to open science. Peer-reviewed publications are made openly
accessible immediately on publication, research data is managed according to
the FAIR principles under the project&amp;rsquo;s data management plan, and the compiler
toolchain and application code are released as open source alongside a
commercial exploitation track.&lt;/p&gt;</description></item><item><title>Use cases</title><link>https://quouskwe-project.deib.polimi.it/use-cases/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/use-cases/</guid><description>&lt;p&gt;The project&amp;rsquo;s software stack is not built in the abstract. Three high-impact
applications drive its requirements and prove its worth: quantum cryptanalysis,
simulation of strongly correlated systems, and Quantum AI for 6G networks.&lt;/p&gt;
&lt;p&gt;All three are executed on IQM&amp;rsquo;s superconducting quantum hardware through the
cloud (T4.5) and assessed against performance, reliability and scalability
criteria (T4.6), creating a feedback loop between algorithm design, hardware
constraints and application needs.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Strategic KPI 3&lt;/strong&gt; — develop and validate at least three killer applications
for quantum computing.&lt;/p&gt;</description></item><item><title>Work packages</title><link>https://quouskwe-project.deib.polimi.it/work-packages/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quouskwe-project.deib.polimi.it/work-packages/</guid><description>&lt;p&gt;Each work package is led by one beneficiary. The &lt;strong&gt;work package leader&lt;/strong&gt; is the
person responsible for running it; each participating institution&amp;rsquo;s
&lt;strong&gt;representative&lt;/strong&gt; is the person scientifically responsible there.&lt;/p&gt;
&lt;p&gt;Tasks list the institution leading them. Named task leaders are still being
settled and will be added here as they are confirmed.&lt;/p&gt;</description></item></channel></rss>