Source: display-dhammapada
Version: 1.0-0.1
Severity: important
X-Debbugs-Cc: Jakub Nadolny <
jakub.nadolny@ite.pl>, bodhi zazen <
bodhi.zazen@fedoraproject.org>,
806340@bugs.debian.org, Package Salvaging Team <
team+salvage@tracker.debian.org>
Hi,
This is an attempt to introduce a new procedure, which I propose to call
Intend To NMU. 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.
If you do not agree to large-scale changes to your package, including maintaining it on Salsa, you are welcome to close this bug or tag it as 'wont-fix' to inform others. There is no obligation to continue reading
if your stance is clear, and your decision will, of course, be
respected.
Otherwise, I will follow the well-established timing of the ITS
procedure, waiting 21 days before performing a Non-Maintainer Upload
(NMU) to delayed=10. However, due to the freeze the first upload
will be delayed until Trixi is released.
This procedure has not yet reached consensus-I am simply exploring
whether it could be accepted. It remains open for discussion,
particularly at DebConf25. Please keep in mind that the goal of this
process is to assist in keeping your package up to date. If you have suggestions for improving it, your feedback is most welcome.
I'm interested in NMUing your package display-dhammapada. It meets the following criteria for the ITN procedure
- NMUs
- Bug filed against the package do not have answers from the
maintainer.
- Upstream has released several versions, but despite there being
a bug entry asking for it, it has not been packaged.
- There are QA issues with the package.
- Not on Salsa but it could profit from team maintenance
- Not uploaded by you in the last 5 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. 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.
Your package was highlighted in the Bug of the Day[3] 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 familiarize newcomers 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/display-dhammapada
[3]
https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)