<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://openprinting.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://openprinting.github.io/" rel="alternate" type="text/html" /><updated>2026-06-08T17:06:36+00:00</updated><id>https://openprinting.github.io/feed.xml</id><title type="html">OpenPrinting</title><subtitle>Making Printing Just Work.</subtitle><author><name>OpenPrinting</name></author><entry><title type="html">HP Printer Application 1.3.1</title><link href="https://openprinting.github.io/hp-printer-app-1.3.1/" rel="alternate" type="text/html" title="HP Printer Application 1.3.1" /><published>2026-06-08T00:00:00+00:00</published><updated>2026-06-08T00:00:00+00:00</updated><id>https://openprinting.github.io/hp-printer-app-1.3.1</id><content type="html" xml:base="https://openprinting.github.io/hp-printer-app-1.3.1/"><![CDATA[<p>HP Printer Application v1.3.1 is a bug fix release.  Changes include:</p>

<ul>
  <li>Improved PCL compression code.</li>
  <li>Fixed CMYK output.</li>
  <li>Fixed a few PCL 6 output bugs.</li>
  <li>Fixed the <code class="language-plaintext highlighter-rouge">--enable-experimental</code> configure option to enable the PCL 6 driver.</li>
</ul>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/michaelrsweet/hp-printer-app/releases/tag/v1.3.1" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download HP Printer Application v1.3.1</a></li>
  <li><a href="https://snapcraft.io/hp-printer-app" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Install HP Printer Application Snap</a></li>
  <li><a href="https://www.msweet.org/hp-printer-app/" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-home" aria-hidden="true"></i>Home Page</a></li>
</ul>]]></content><author><name>Michael Sweet</name></author><summary type="html"><![CDATA[HP Printer Application v1.3.0 is a bug fix release.]]></summary></entry><entry><title type="html">LPrint 1.4.0</title><link href="https://openprinting.github.io/lprint-1.4.0/" rel="alternate" type="text/html" title="LPrint 1.4.0" /><published>2026-06-08T00:00:00+00:00</published><updated>2026-06-08T00:00:00+00:00</updated><id>https://openprinting.github.io/lprint-1.4.0</id><content type="html" xml:base="https://openprinting.github.io/lprint-1.4.0/"><![CDATA[<p>LPrint v1.4.0 is a feature release that adds support for ESC/POS printers and
several other printer models with existing drivers.  Changes include:</p>

<ul>
  <li>Added ESC/POS driver (Issue #123)</li>
  <li>Added Vevor Y428BT driver (Issue #130)</li>
  <li>Added 4 x 7.83 inch label size (Issue #144)</li>
  <li>Added Arkscan 2054a and HP KE103 (Issue #165)</li>
  <li>Added DYMO LabelWriter Twin Turbo driver (Issue #193)</li>
  <li>Now enable the TLS web interface unless the “no-tls” option is specified
(Issue #161)</li>
  <li>Updated the default state file to match current PAPPL defaults (Issue #129)</li>
  <li>Updated the maximum label width of TSPL printers to 105mm (Issue #141)</li>
  <li>Updated the ZPL driver to automatically disable status commands if the target
printer doesn’t implement that part of ZPL (Issue #161)</li>
  <li>Fixed the margins for DYMO printers (Issue #132)</li>
  <li>Fixed some Brother driver problems (Issue #167)</li>
  <li>Fixed a NumCopies issue in the TSPL driver (Issue #188)</li>
  <li>Fixed list of label sizes for DYMO LabelWriter 4XL (Issue #198)</li>
</ul>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/michaelrsweet/lprint/releases/tag/v1.4.0" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download LPrint 1.4.0</a></li>
  <li><a href="https://snapcraft.io/lprint" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Install lprint Snap</a></li>
  <li><a href="https://www.msweet.org/lprint/" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-home" aria-hidden="true"></i>Home Page</a></li>
</ul>]]></content><author><name>Michael Sweet</name></author><summary type="html"><![CDATA[LPrint v1.4.0 is a feature release that adds support for ESC/POS printers.]]></summary></entry><entry><title type="html">libcups v3.0.2</title><link href="https://openprinting.github.io/libcups-3.0.2/" rel="alternate" type="text/html" title="libcups v3.0.2" /><published>2026-06-05T00:00:00+00:00</published><updated>2026-06-05T00:00:00+00:00</updated><id>https://openprinting.github.io/libcups-3.0.2</id><content type="html" xml:base="https://openprinting.github.io/libcups-3.0.2/"><![CDATA[<p>libcups v3.0.2 is bug fix release.  Changes include:</p>

<ul>
  <li>Updated <code class="language-plaintext highlighter-rouge">ipptool</code> to limit the range of supported raster resolutions for the
generated test page content from 1 to 9600dpi.</li>
  <li>Fixed a recursion issue with encoding of nested collections.</li>
  <li>Fixed a potential margin issue when generating A4 PCL from <code class="language-plaintext highlighter-rouge">ipptransform</code>.</li>
  <li>Fixed exporting of JSON with very large numbers.</li>
  <li>Fixed page header validation in <code class="language-plaintext highlighter-rouge">cupsRasterReadHeader</code> and
<code class="language-plaintext highlighter-rouge">cupsRasterWriteHeader</code> for banded raster data.</li>
  <li>Fixed potential crash bug in <code class="language-plaintext highlighter-rouge">cupsCheckDestSupported</code> function.</li>
  <li>Fixed a duplicate printer bug in <code class="language-plaintext highlighter-rouge">cupsEnumDests</code> and <code class="language-plaintext highlighter-rouge">cupsGetDests</code>.</li>
</ul>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/OpenPrinting/libcups/releases/tag/v3.0.2" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download v3.0.2</a></li>
</ul>]]></content><author><name>Michael Sweet</name></author><summary type="html"><![CDATA[libcups v3.0.2 is a bug fix release.]]></summary></entry><entry><title type="html">PAPPL 1.4.11</title><link href="https://openprinting.github.io/pappl-1.4.11/" rel="alternate" type="text/html" title="PAPPL 1.4.11" /><published>2026-06-05T00:00:00+00:00</published><updated>2026-06-05T00:00:00+00:00</updated><id>https://openprinting.github.io/pappl-1.4.11</id><content type="html" xml:base="https://openprinting.github.io/pappl-1.4.11/"><![CDATA[<p>PAPPL v1.4.11 is now available for download and is a bug fix release.  Changes include:</p>

<ul>
  <li>Updated the programmer’s manual (Issue #418, Issue #419)</li>
  <li>Updated Set-Printer-Attributes validations checks.</li>
  <li>Fixed builds on FreeBSD and other systems without a sys/statfs.h header
(Issue #411)</li>
  <li>Fixed a deadlock issue in the USB gadget shutdown code (Issue #417)</li>
  <li>Fixed a truncation bug when decoding SNMP string values.</li>
  <li>Fixed the handling of the finishings option.</li>
</ul>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/michaelrsweet/pappl/releases/tag/v1.4.11" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download v1.4.11</a></li>
</ul>]]></content><author><name>Michael Sweet</name></author><summary type="html"><![CDATA[PAPPL v1.4.11 is a bug fix release.]]></summary></entry><entry><title type="html">OpenPrinting News - Opportunity Open Source 4.0 in the IIIT Allahabad</title><link href="https://openprinting.github.io/OpenPrinting-News-Opportunity-Open-Source-4.0/" rel="alternate" type="text/html" title="OpenPrinting News - Opportunity Open Source 4.0 in the IIIT Allahabad" /><published>2026-05-30T00:00:00+00:00</published><updated>2026-05-30T00:00:00+00:00</updated><id>https://openprinting.github.io/OpenPrinting%20News%20-%20Opportunity%20Open%20Source%204.0</id><content type="html" xml:base="https://openprinting.github.io/OpenPrinting-News-Opportunity-Open-Source-4.0/"><![CDATA[<p><img src="../assets/images/oosc-2.0-2024-1.png" alt="Some pictures of the OOSC 2.0" /><img src="../assets/images/oosc-2.0-2024-2.png" alt="More pictures of the OOSC 2.0" /></p>

<p>After three great Opportunity Open Source conferences we will celebrate the forth one!</p>

<h2 id="iiit-allahabad">IIIT Allahabad</h2>

<p><em>Photos and description of the location contributed by Sudhanshu Sah</em></p>

<p>Our <a href="/OpenPrinting-News-Opportunity-Open-Source-4.0-Call-for-Locations/">Call for Locations</a> showed a lot of interest. Several groups from different places in India have answered (mainly on <a href="https://www.linkedin.com/pulse/opportunity-open-source-40-call-locations-till-kamppeter-ktr2f/">LinkedIn</a>). Some only told in a short answer that they are interested but did not follow up, and 4 groups gave more detailed information and had a video meeting with us. In the end, the most convincing bid came from the Google Developer Group (GDG) IIIT Allahabad and we settled with them.</p>

<p><strong>IIIT Allahabad</strong> stands among <strong>India’s premier technology institutes</strong>, located in the historic and intellectually vibrant city of <strong>Prayagraj</strong>, in the state <strong>Uttar Pradesh</strong> in India. Renowned for its rich cultural legacy, academic excellence, and deep-rooted scholarly atmosphere, Prayagraj has long been a meeting point of ideas, innovation, and learning.</p>

<p><img src="../assets/images/oosc-4.0/Main_Gate_Gate2_IIITA.png" alt="IIIT Allahabad: Main Gate" /><img src="../assets/images/oosc-4.0/Clock_Tower_IIITA.png" alt="IIIT Allahabad: Clock Tower" /><br />
<em>IIT Allahabad: Main Gate and Clock Tower</em></p>

<p>The region hosts some of the country’s most respected educational institutions, including <strong>MNNIT Allahabad</strong>, the historic <strong>University of Allahabad</strong>, <strong>SHUATS</strong>, and several other prominent institutes and research centres. Together, they create a dynamic academic ecosystem that attracts students, researchers, developers, innovators, and technology enthusiasts from across India. With this we also count with many more attendees than just those from IIIT Allahabad.</p>

<p>The conference will be held across selected campus venues at IIIT Allahabad, including <strong>Computer Centre-3 (CC-3 / C. V. Raman Bhavan)</strong>, the <strong>Auditorium</strong> (Plenary), and the <strong>Admin Auditorium</strong> (Breakout). These spaces will host talks, workshops, discussions, and other conference activities. The campus also provides suitable facilities for attendees, including dining options and other essential support for a smooth event experience.</p>

<p><img src="../assets/images/oosc-4.0/Main_Auditorium_IIITA.jpg" alt="Main Auditorium" /><img src="../assets/images/oosc-4.0/Admin_Auditorium_IIITA.jpeg" alt="Admin Auditorium" /><br />
<em>IIT Allahabad: Main Auditorium and Admin Auditorium</em></p>

<p>Details regarding sponsors are currently being finalized and will be shared in due course.</p>

<p><strong>Rishu Kumar</strong>, <strong>Sudhanshu Sah</strong>, and <strong>Aditya Ajay</strong> will be the overall coordinators, and together with faculty coordinator <strong>Prof. Bibhas Ghoshal</strong> they will create a team of volunteers, mostly students who will do the <strong>on-location organization</strong>. They will look for local sponsors, reserve conference rooms and spaces for hallway track and exhibition, accommodation for speakers and non-local attendees, organize meals, prepare and test audio/video setup in the rooms, …</p>

<h2 id="selecting-the-date">Selecting the date</h2>

<p>The date we have set to be <strong>some weeks after the summer break at the IIIT</strong>, so that the <strong>students volunteering in the organization team</strong> are back for some weeks already to have time to <strong>prepare the event</strong>. On the other side we also had to care <strong>not to fall into an exam week</strong>, so that students have time to attend.</p>

<p>Another criteria for the selection of the event date are <strong>other national and international conferences</strong> happening at this time, especially the <strong>aKademy</strong> 2026 in Graz, Austria, on September 19-24, and the <strong>IndiaFOSS</strong> in Bengaluru, on September 26-27.</p>

<p>And in <strong>October</strong> we have the <strong>festive season</strong> in India.</p>

<p>So we ended up choosing <strong>August 28-30 (Fri-Sun), the last weekend of August</strong>.</p>

<h2 id="call-for-proposals-is-open">Call for Proposals is open</h2>

<p>As in the other years we want to motivate students (and also professors and researchers) to learn about free and open-source software and to join the community of developers and contributors. Not only coding and debugging can be contributed, but also designers, technical authors, evangelists, … are highly welcome.</p>

<p>And to make this event really great, we need your contributions: Talks, panels, workshops, demo tables, lightning talks … Show us how you are contributing to free and open-source software, how you make our lives better with it, You do not need to be a coder. also sessions about documentation, design, community, success stories, … are highly welcome.</p>

<p><strong>Our <a href="https://events.canonical.com/event/154/abstracts/">Call for Proposals</a> is open! Until July 3, 2026!</strong></p>

<p>So please post your proposals. We (and also our attendees) are eager to have your contribution on our conference.</p>

<h2 id="let-us-celebrate-a-great-event">Let us celebrate a great event!</h2>

<p>We will again have many sessions about OpenPrinting, Zephyr, Google Summer of Code, AI/LLMs/ML, …</p>

<p>And especially we will again have many interactive workshops where you can learn new skills hands-on. So bring your laptop and experience it by yourself.</p>

<p>We also want to have some demo tables, where things can be tried out and conversations will fuel an exciting hallway track. And if it works out, we will also offer a Hackathon again.</p>

<p><strong>We hope to see you all in India …</strong></p>

<p>… but you are also welcome to attend and/or speak remotely</p>

<ul>
  <li><a href="https://www.linkedin.com/company/opportunityopensource/posts/">LinkedIn Site</a></li>
  <li><a href="https://events.canonical.com/event/154/">Practical info: Location, remote attending/speaking, …</a></li>
  <li><a href="https://events.canonical.com/event/154/abstracts/">Call for proposals</a></li>
  <li>Mastodon: <a href="https://ubuntu.social/tags/OpportunityOpenSource">#OpportunityOpenSource</a></li>
</ul>

<p><strong>And as usual: Stay updated on Mastodon: <a href="https://ubuntu.social/tags/OpenPrinting">#OpenPrinting</a> and <a href="https://ubuntu.social/@till">@till@ubuntu.social</a>.</strong></p>

<p><strong>Or discuss on our mailing lists:</strong></p>
<ul>
  <li><strong>Development:</strong> printing-architecture AT lists DOT linux DOT dev (<a href="https://lore.kernel.org/printing-architecture/">Archive</a>)</li>
  <li><strong>Users:</strong> printing-users AT lists DOT linux DOT dev (<a href="https://lore.kernel.org/printing-users/">Archive</a>)</li>
</ul>

<p>Subscribing/Unsubscribing <a href="https://subspace.kernel.org/subscribing.html">instructions</a></p>

<p><strong>Or on the Telegram <a href="https://t.me/+RizBbjXz4uU2ZWM1">OpenPrinting chat</a></strong></p>]]></content><author><name>Till Kamppeter</name><email>till.kamppeter@gmail.com</email></author><summary type="html"><![CDATA[Opportunity Open Source 4.0, in the IIIT Allahabad in Prayagraj, Uttar Pradesh, India, on Aug 28-30]]></summary></entry><entry><title type="html">CUPS 2.4.19</title><link href="https://openprinting.github.io/cups-2.4.19/" rel="alternate" type="text/html" title="CUPS 2.4.19" /><published>2026-04-27T00:00:00+00:00</published><updated>2026-04-27T00:00:00+00:00</updated><id>https://openprinting.github.io/cups-2.4.19</id><content type="html" xml:base="https://openprinting.github.io/cups-2.4.19/"><![CDATA[<p>CUPS 2.4.19 fixes a regression in shared printing from non-local accounts (Issue #1557).</p>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/OpenPrinting/cups/releases/tag/v2.4.19" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download v2.4.19</a></li>
</ul>]]></content><author><name>Zdenek Dohnal</name></author><summary type="html"><![CDATA[CUPS 2.4.19 fixes a regression in shared printing from non-local accounts.]]></summary></entry><entry><title type="html">CUPS 2.4.18</title><link href="https://openprinting.github.io/cups-2.4.18/" rel="alternate" type="text/html" title="CUPS 2.4.18" /><published>2026-04-22T00:00:00+00:00</published><updated>2026-04-22T00:00:00+00:00</updated><id>https://openprinting.github.io/cups-2.4.18</id><content type="html" xml:base="https://openprinting.github.io/cups-2.4.18/"><![CDATA[<p>The new release 2.4.17 contains hotfix after CVE-2026-27447 fix:</p>

<p>Fixed cupsd crash if user does not exist (Issue #1555)</p>

<p>I’m sorry for inconvenience and enjoy!</p>

<ul>
  <li><a href="https://github.com/OpenPrinting/cups/releases/tag/v2.4.18" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download v2.4.18</a></li>
</ul>]]></content><author><name>Zdenek Dohnal</name></author><summary type="html"><![CDATA[CUPS 2.4.18 brings hotfix after CVE-2026-27447]]></summary></entry><entry><title type="html">CUPS 2.4.17</title><link href="https://openprinting.github.io/cups-2.4.17/" rel="alternate" type="text/html" title="CUPS 2.4.17" /><published>2026-04-17T00:00:00+00:00</published><updated>2026-04-17T00:00:00+00:00</updated><id>https://openprinting.github.io/cups-2.4.17</id><content type="html" xml:base="https://openprinting.github.io/cups-2.4.17/"><![CDATA[<p>The new release 2.4.17 contains the following security fixes:</p>

<ul>
  <li>CVE-2026-27447: The scheduler treated local user and group names as case-
insensitive.</li>
  <li>CVE-2026-34978: The RSS notifier could write outside the scheduler’s RSS 
directory.</li>
  <li>CVE-2026-34980: The scheduler did not filter control characters from option
values.</li>
  <li>CVE-2026-34979: The scheduler did not always allocate enough memory for a
job’s options string.</li>
  <li>CVE-2026-34990: The scheduler incorrectly allowed local certificates over the 
loopback interface.</li>
  <li>CVE-2026-39314: Fixed the range check for job password strings.</li>
  <li>CVE-2026-39316: Fixed a printer subscription bug in the scheduler.</li>
  <li>CVE-2026-NNNNN: Fixed a SNMP string conversion bug in the backends.</li>
</ul>

<p>where the last CVE number is requested from Github for several days now, the number will be corrected once we have one, but we decided to make a release to share the other fixes.</p>

<p>The release includes other fixes as well, listed in CHANGES.md.</p>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/OpenPrinting/cups/releases/tag/v2.4.17" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download v2.4.17</a></li>
</ul>]]></content><author><name>Zdenek Dohnal</name></author><summary type="html"><![CDATA[CUPS 2.4.17 release includes fixes for 8 vulnerabilities]]></summary></entry><entry><title type="html">libcups v3.0.1</title><link href="https://openprinting.github.io/libcups-3.0.1/" rel="alternate" type="text/html" title="libcups v3.0.1" /><published>2026-04-09T00:00:00+00:00</published><updated>2026-04-09T00:00:00+00:00</updated><id>https://openprinting.github.io/libcups-3.0.1</id><content type="html" xml:base="https://openprinting.github.io/libcups-3.0.1/"><![CDATA[<p>libcups v3.0.1 is bug fix release.  Changes include:</p>

<ul>
  <li>Updated the internal implementation of <code class="language-plaintext highlighter-rouge">ipp_t</code> to avoid issues on some
embedded platforms (Issue #141)</li>
  <li>Updated <code class="language-plaintext highlighter-rouge">httpAddrLookup</code> to return a numeric address when the resolver
returns “localhost” for a non-loopback address.</li>
  <li>Updated <code class="language-plaintext highlighter-rouge">cupsFileGetConf</code> and <code class="language-plaintext highlighter-rouge">cupsFilePutConf</code> to escape more characters.</li>
  <li>Updated <code class="language-plaintext highlighter-rouge">cupsRasterReadHeader</code> to validate more of the page header values.</li>
  <li>Updated <code class="language-plaintext highlighter-rouge">ippeveprinter</code> to support custom “printer-state-reasons” keyword
values (Issue #142)</li>
  <li>Fixed a bug when the <code class="language-plaintext highlighter-rouge">ippFindXxx</code> and <code class="language-plaintext highlighter-rouge">ippSetXxx</code> functions were mixed
(Issue #138)</li>
  <li>Fixed error handling in the low-level TLS read/write functions.</li>
</ul>

<p>Enjoy!</p>

<ul>
  <li><a href="https://github.com/OpenPrinting/libcups/releases/tag/v3.0.1" itemprop="sameAs" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-download" aria-hidden="true"></i>Download v3.0.1</a></li>
</ul>]]></content><author><name>Michael Sweet</name></author><summary type="html"><![CDATA[libcups v3.0.1 is a bug fix release.]]></summary></entry><entry><title type="html">OpenPrinting News - Opportunity Open Source 4.0 - Call for Locations</title><link href="https://openprinting.github.io/OpenPrinting-News-Opportunity-Open-Source-4.0-Call-for-Locations/" rel="alternate" type="text/html" title="OpenPrinting News - Opportunity Open Source 4.0 - Call for Locations" /><published>2026-02-13T00:00:00+00:00</published><updated>2026-02-13T00:00:00+00:00</updated><id>https://openprinting.github.io/OpenPrinting%20News%20-%20Opportunity%20Open%20Source%204.0%20-%20Call%20for%20Locations</id><content type="html" xml:base="https://openprinting.github.io/OpenPrinting-News-Opportunity-Open-Source-4.0-Call-for-Locations/"><![CDATA[<h1 id="opportunity-open-source-40---call-for-locations">Opportunity Open Source 4.0 - Call for Locations</h1>

<p>The Opportunity Open Source conferences which take place every year in a university/college/IIT/… in India are for showcasing free and open source software (FOSS) and for motivating students, professors, and researchers to participate in its development, by contributing code, design, documentation, … With talks and hands-on workshops a wide range of FOSS topics is covered, and often also a hackathon (coding competition) day is added. In the last year we got around 300 attendees, and many of them showed interest and started to get involved.</p>

<p>And so after 3 successful editions of the <a href="https://www.linkedin.com/company/opportunityopensource/">Opportunity Open Source conferences</a> in India (<a href="https://openprinting.github.io/OpenPrinting-News-September-2023/#opportunitiy-open-source-in-the-iit-mandi-india">1.0 in Mandi</a>, <a href="https://openprinting.github.io/OpenPrinting-News-August-2024/#opportunity-open-source-in-iit-kanpur">2.0 in Kanpur</a>, <a href="https://openprinting.github.io/OpenPrinting-News-Opportunity-Open-Source-3.0-in-the-IIT-Kanpur,-India/">3.0 in Kanpur</a>) we want to celebrate the fourth one. For that we need a place to do so. It should be somewhere in India and to give people all over India this opportunity of experiencing open source, we want to run each edition at a different place and therefore we are looking for a new location for this year’s edition.</p>

<p>If you are interested, we want to hear from you. First just tell us that you are interested and then we will ask you, and also guide you, for your detailed bid. We will close the call for locations on</p>

<p><strong>March 15, 2026, 23:59 IST</strong></p>

<p>The content for the conference days, talks, workshops, and booths will be supplied by the global organizers of the Opportunity Open Source. Once we have selected the location we will publish a Call for Proposals (CfP) so that people who want to contribute content can propose their talk, workshop, or booth. We will select an appropriate amount of the most interesting proposals to fill the given rooms during the given amount of conference days then.</p>

<h2 id="requirements">Requirements</h2>

<h3 id="city">City</h3>

<p>The city (must be in India) where the event will take place should be easily reachable from all over India, by plane or by train, so that speakers and non-local attendees can participate without problems.</p>

<p>We also prefer cities where not just your university/college/IIT is located but also others (also in nearby cities), as people from there will also attend the Opportunity Open Source.</p>

<h3 id="venue">Venue</h3>

<p>We like to run the conference at universities, colleges, IIT, … places where one can study computer science as here we expect a large audience. Naturally students, professors, and researchers from other areas and people from other institutes nearby can also attend.</p>

<p>For the conference days we will need three rooms for the sessions: A plenary room and a breakout room for the talks, plus a room for the workshops. The 2 rooms for the talks can be lecture halls, the workshop room is ideally a classroom with tables and where one could provide power outlets or power strips for the attendee’s laptops. We expect typically around 300 attendees, so the plenary room should fit this amount of people.</p>

<p>There should also be some area for the “hallway track” where people hang out and chat. There should also be located any exhibition booths, from sponsors and/or from open-source projects. Also tea, coffee, and snacks for the tea breaks could be provided here.</p>

<p>Ideally the 3 rooms are directly connected to this area, but they should at least be nearby.</p>

<p>For a hackathon day we need one big hall (like a gym hall) where tables for each participating team can be placed. The tables need to get supplied with power strips for the participant’s laptops.</p>

<h3 id="date">Date</h3>

<p>The conference should take place on a weekend between mid-August and end-September, or in November. Before mid-August it is too close to the summer holidays and so the local team has not enough time on campus for preparing the event. October is the festive season in India.</p>

<p>Also exam weeks need to be avoided. Not only that the students are preparing themselves for their exams and not attending but also rooms reserved for the conference can get suddenly taken for exams, even on Sundays. Also exam weeks of nearby institutes should be taken into account.</p>

<p>Also to be avoided are the dates of other important conferences, especially the <a href="https://www.ubucon.asia/2026.ubucon.asia/">UbuCon Asia</a> which takes place on August 8-9 in Taipei, Taiwan and the <a href="https://indiafoss.net/">India FOSS</a> by <a href="https://fossunited.org/">FOSS United</a> (date and location TBD).</p>

<h3 id="local-organization-team">Local organization team</h3>

<p>The most important part of a successful conference is the on-location organization team, a group of volunteers, in our case usually students, but could also be some local open source organization, who do everything needed at the conference location.</p>

<p>This is especially talking with the institute’s administration to reserve conference rooms, guest rooms in the on-campus guest house and in student hostels for speakers and non-local attendees, arranging lunch on the conference and hackathon days, organizing the conference dinner/closing party, finding (local) sponsors to cover the costs, assuring the needed technical setup of the rooms: Internet (wired for streaming, wireless for attendees), A/V, booth space, power strips, …, lining up a team of volunteers, including crews for the rooms, local marketing of the event in social media … A lot of things which have to be done on-site …</p>

<p>Here is an example of the <a href="https://oosc3ubucon.netlify.app/team">organization team of last year</a>.</p>

<h3 id="av-requirements">A/V Requirements</h3>

<p>In each of the 3 conference rooms we do not only want to make the slides of the talks being visible for everybody and the speakers being heard by everybody, but we want to, as it is done on practically all conferences nowadays, stream the sessions live, record them, and also allow remote speaking.</p>

<p>For this, each of the 3 rooms will need:</p>

<ul>
  <li>A projector (to project image from laptop, usually built into the room)</li>
  <li>Speakers (to output audio from laptop, usually built into the room)</li>
  <li>Microphones (wireless clip-on, headset, hand microphones, which can send audio to a laptop, usually provided by the room)</li>
  <li>1 or 2 cameras (which can send video to a laptop)</li>
  <li>A powerful laptop which can do video streaming</li>
  <li>Wired internet connection (or phone or travel router which provides unlimited 5G cell data)</li>
  <li>A second laptop for the projection</li>
  <li>A third laptop for checking for questions of remote attendees via chat</li>
</ul>

<p>Note that the A/V setup should be centered by the A/V laptop to assure that the audio in the room and for the remote attendees and remote speakers is the same, without in-person speakers having to use 2 microphones.</p>

<p>We will provide a (remote) server with Nextcloud and VDO.Ninja (planned for now, subject to change).</p>

<p>Each room needs the following crew of volunteers (changing in half-day shifts):</p>

<ul>
  <li>MC: They introduce into the talk, show “15 min left”, …, manage Q\&amp;A</li>
  <li>A/V director: They take care of streaming, remote speaking, and recording, via the A/V laptop</li>
  <li>Mic runner: They bring the hand mic to people to ask questions, can also show “15 min left”, … during the talk.</li>
  <li>Camera operator: Takes care that speaker is in the frame</li>
  <li>Remote chat manager: Checks whether remote attendees have questions</li>
</ul>

<h3 id="accommodation-for-speakers-and-non-local-attendees">Accommodation for speakers and non-local attendees</h3>

<p>The accommodation should be ideally on-campus so that there is no long commute needed, and especially not one which is partially outside and partially inside the campus to avoid that taxis or auto-rickshaws from outside have to go through the security of the campus. It gets much easier if one can walk to the conference rooms or use a campus-internal auto-rickshaw.</p>

<p>For speakers and non-local organizers there should be single rooms in a guest house (where usually international guest professors and researchers stay). The guest house should have 24-hour service to quickly respond if there are any problems with the room.</p>

<p>Non-local attendees can get accommodated in student’s hostels.</p>

<h3 id="meals">Meals</h3>

<p>There needs to be breakfast available for those who are in the accommodations and lunch for all participants on the conference and hackathon days.</p>

<h3 id="conference-dinnerclosing-party">Conference dinner/closing party</h3>

<p>After the second conference day we want to do a closing event, at least a conference dinner of all the organizers and speakers, but ideally a closing party for all participants. For this we need a suitable restaurant in case of a dinner or a suitable location/venue and catering for a party.</p>

<h3 id="hackathon-optional">Hackathon (optional)</h3>

<p>In addition to the actual conference consisting of talks and workshops we also want to do (but it is not required) a hackathon, a programming competition. We as global organizers of the Opportunity Open Source will not organize the hackathon. The content/subject matter has to be organized locally. In the last 2 years sponsors were providing this.</p>

<h3 id="sponsoring">Sponsoring</h3>

<p>All the above usually cannot get supplied free of charge. So the costs of each item need to be estimated and an estimate of the total cost of the conference be made.</p>

<p>To cover the costs sponsors are needed, principally local ones as the event is principally intended for local attendees. National or international sponsors are welcome.</p>

<p>To make it easier for sponsors to contribute, sponsorship tiers (platinum, gold, silver, …) should be offered. Each tier requires to pay a given amount and the sponsor gets perks as compensation, like more or less prominently placed logos, on the web site, on posters at the venue, … mentions in the opening and closing plenaries, a booth of a certain size, …</p>

<p>Dedicated sponsoring, like for the closing party, the hackathon, … should be also accepted.</p>

<h3 id="participation-fees">Participation fees</h3>

<p>In the previous years we have taken fees from the participants for meals and for accommodation, the latter only if needed. Also the accommodation for attendees was a student hostel, so it was not very expensive.</p>

<p>As most participants are students, we should try to cover as much as possible of the costs of the event by sponsors and keep the participation fees as low as possible.</p>

<h2 id="how-to-place-your-bid">How to place your bid?</h2>

<p>If you like to have the Opportunity Open Source 4.0 take place at your institute and you are able to provide the above-mentioned items, you should contact us with a first e-mail/message before end of February, but the earlier, the better, as we need your <strong>complete bid until March 15, 23:59 IST</strong>.</p>

<p>Your complete bid should go through the above items and tell what you have available at your place and who will be the local organizer team, which organization, community and who will be responsible for which part.</p>

<p>Please provide photos of the city and venue, floor plans, and other supporting images.</p>

<p>If your organization/community already has experience with organizing events, especially conferences, perhaps even in the area of open source, please tell.</p>

<p>Please also list estimates for all the costs and the total budget for the event.</p>

<p>If you already have sponsors please tell who they are and how much they want to contribute.</p>

<p>Your first message and your complete bid please send to the global organizers of the Opportunity Open Source, Till Kamppeter and Aveek Basu.</p>

<h3 id="till-kamppeter">Till Kamppeter</h3>

<ul>
  <li>e-Mail: till at linux dot com</li>
  <li>LinkedIn: <a href="https://www.linkedin.com/in/kamppetertill/">https://www.linkedin.com/in/kamppetertill/</a></li>
  <li>Telegram: <a href="https://t.me/tillkamppeter">https://t.me/tillkamppeter</a></li>
  <li>Matrix: @till-kamppeter:ubuntu.com</li>
</ul>

<h3 id="aveek-basu">Aveek Basu</h3>

<ul>
  <li>e-Mail: basu dot aveek at gmail dot com</li>
  <li>LinkedIn: <a href="https://www.linkedin.com/in/basuaveek/">https://www.linkedin.com/in/basuaveek/</a></li>
</ul>

<h3 id="opportunity-open-source-on-linkedin">Opportunity Open Source on LinkedIn</h3>
<p><a href="https://www.linkedin.com/company/opportunityopensource/posts/">@OpportunityOpenSource</a></p>

<p><br /><br /></p>

<p><strong>And as usual: Stay updated on Mastodon: <a href="https://ubuntu.social/tags/OpenPrinting">#OpenPrinting</a> and <a href="https://ubuntu.social/@till">@till@ubuntu.social</a> and on LinkedIn: <a href="https://www.linkedin.com/company/openprinting/posts/">@OpenPrinting</a>.</strong></p>

<p><strong>Or discuss on our mailing lists:</strong></p>
<ul>
  <li><strong>Development:</strong> printing-architecture AT lists DOT linux DOT dev (<a href="https://lore.kernel.org/printing-architecture/">Archive</a>)</li>
  <li><strong>Users:</strong> printing-users AT lists DOT linux DOT dev (<a href="https://lore.kernel.org/printing-users/">Archive</a>)</li>
</ul>

<p>Subscribing/Unsubscribing <a href="https://subspace.kernel.org/subscribing.html">instructions</a></p>]]></content><author><name>Till Kamppeter</name><email>till.kamppeter@gmail.com</email></author><summary type="html"><![CDATA[Where will the 4th edition take place? Please send us your proposal!]]></summary></entry></feed>