<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Dealing with Dormant Packages: Ensuring Debian’s High Standards</title>
        <link>https://peertube.debian.social/videos/watch/d89732c5-3041-4b9f-9d37-f2bb2c8e672e</link>
        <description>by Andreas Tille At: DebConf25 https://debconf25.debconf.org/talks/2-dealing-with-dormant-packages-ensuring-debians-high-standards/ Through the Bug of the Day effort, I have noticed a significant number of packages that have not been uploaded for a long time. In most cases, the maintainer is unresponsive to ITS bug reports or other attempts to reach them. Currently, we have three main options for handling such situations: The MIA process, ITS (Intent to Salvage), NMUs (Non-Maintainer Uploads), However, these mechanisms are not always sufficient to uphold Debian’s high-quality standards. In this BoF, I want to discuss potential improvements to our approach, based on conversations during DebCamp, and explore additional strategies to better maintain package quality in Debian. Room: Méridienne Scheduled start: 2025-07-14 14:00:00+02:00</description>
        <lastBuildDate>Sat, 29 Aug 2026 07:54:37 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://peertube.debian.social</generator>
        <image>
            <title>Dealing with Dormant Packages: Ensuring Debian’s High Standards</title>
            <url>https://peertube.debian.social/client/assets/images/icons/icon-96x96.png</url>
            <link>https://peertube.debian.social/videos/watch/d89732c5-3041-4b9f-9d37-f2bb2c8e672e</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://peertube.debian.social/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://peertube.debian.social/feeds/video-comments.xml?videoId=d89732c5-3041-4b9f-9d37-f2bb2c8e672e" rel="self" type="application/rss+xml"/>
    </channel>
</rss>