Source: tthsum Version: 1.3.2-1 Severity: important X-Debbugs-Cc: [email protected], Hector Oron <[email protected]>, Package Salvaging Team <[email protected]>
Dear Hector, This is an attempt to introduce a new procedure, which I propose to call Intend To Orphan. While we have an established process for making minimal, fine-grained changes to a package, it does not cover broader improvements such as migrating to Salsa, updating the Standards-Version, or adjusting the debhelper compatibility level. However, some packages could benefit from more extensive changes, and this procedure aims to provide a structured way to implement them. Unlike the well-established Package Salvage procedure[1] which requires an active Uploader, the goal here is to allow collaborative work on a package on Salsa, even if no active uploader expresses interest in maintaining it. --> Maintainer set to Debian QA Group <[email protected]> If you do not agree to large-scale changes to this package, including maintaining it on Salsa, feel free to close this bug or tag it as 'wontfix' to inform others. There is no obligation to continue reading if your stance is clear, and that decision will, of course, be respected. Otherwise, I will follow the well-established timing of the ITS procedure, waiting 21 days before performing a QA Upload to delayed=10. This procedure has not yet reached consensus--I am simply exploring whether it could be accepted. It was disussed at DebConf25 but some consensus is pending. Please keep in mind that the goal of this process is to help ensure that packages remain up to date and well maintained. If you have suggestions for improving it, your feedback is most welcome. I'm interested in orphaning the package tthsum. It meets the following criteria: - Bug filed against the package do not have answers from the maintainer. - There are QA issues with the package. - Not on Salsa but it could profit from team maintenance - No maintainer upload in the last 11 years - Standards-Version < 4 I have set up a repository within Debian/[2]. This team functions similarly to the former collab-maint on Alioth, allowing any Debian Developer to make team uploads[3]. I understand that some maintainers may prefer not to transition to collaborative maintenance, and I want to emphasize that this is not intended as a hostile action. My goal is to make the transition to using a Git repository on Salsa smoother and more convenient for you. This package was highlighted in the Bug of the Day[4] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to help newcomers become familiar with a consistent Git-based workflow. Kind regards Andreas. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://salsa.debian.org/debian/tthsum [3] https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group [4] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks -- System Information: Debian Release: forky/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.12.38+deb13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
