Source: fortunes-mario
Version: 0.21-1.1
Severity: important
X-Debbugs-Cc: Fernando Ike de Oliveira <fike@midstorm.org>, Carlos Henrique Lima Melara <charles@debian.org>, 1073475@bugs.debian.org, 847262@bugs.debian.org, Package Salvaging Team <team+salvage@tracker.debian.org>

Hi,

As per bug #847262 I did not included Otavio in CC. However, I hope
that either you Charles or some of your friends might put a new
maintainer ID and might volunteer to maintain this probably very low maintenance package. At least the RC bug is fixed and the package
can be just uploaded. I would have no problem to put my own name as
maintainer but I'd prefer someone from Brasil taking responsibility.
If this is not happening I will decide what to do in 21 days ...
(Now the ITN template follows ...)

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. Specifically, since we are approaching the freeze
the upload will be delayed until after Trixie 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 FIXME. It meets the following
criteria for the ITN procedure

- NMU
- Bugs 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
- 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/fortunes-mario
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks


-- System Information:
Debian Release: trixie/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.22-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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On Wed, May 07, 2025 at 08:30:05AM +0200, Andreas Tille wrote:

As per bug #847262 I did not included Otavio in CC. However, I hope
that either you Charles or some of your friends might put a new
maintainer ID and might volunteer to maintain this probably very low maintenance package. At least the RC bug is fixed and the package
can be just uploaded. I would have no problem to put my own name as maintainer but I'd prefer someone from Brasil taking responsibility.
If this is not happening I will decide what to do in 21 days ...
(Now the ITN template follows ...)

I'd like to help here and could be added to uploaders or maintainer
field. I'll wait the 21 days and salvage the package if no replies come
from Fernando. I tend to prefer team maintained packages because if I
vanish they can continue to be worked on and won't go through this
process again. Would it be ok to keep under the Salvage team and have
myself as uploader?

Cheers,
Charles

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Charles,

before I need to talk to much I just commited what I would do if I were
in your shoes:

https://salsa.debian.org/debian/fortunes-mario/-/commit/10fbbafd724a5f657e66cd70d0b51d4ea156761e

Explanation:

Am Thu, May 08, 2025 at 10:44:05AM -0300 schrieb Carlos Henrique Lima Melara:

I'd like to help here and could be added to uploaders or maintainer
field.

The Maintainer field has to be changed to fix bug #847262.

I'll wait the 21 days and salvage the package if no replies come
from Fernando.

I do not think you need to wait for Fernando. If you take over
maintainership and by doing so even a RC bug is fixed there is no
point for waiting. I simply added this delay in case nobody might
take over and I would do a NMU (without fixing bug #847262).

There is also no point in respecting the freeze policy since the
package is not in testing (unfortunately). So just upload what's
currently in Git. :-)

I tend to prefer team maintained packages because if I
vanish they can continue to be worked on and won't go through this
process again.

Sure. Its in the Debian/ team now. Many fortunes-* package reside
there and this permits anybody to do a team upload.

Would it be ok to keep under the Salvage team and have
myself as uploader?

If you feel better to use the Salvage team as maintainer, well, that's
OK, but from my point of view Debian/ team is perfectly fine.

Enjoy Brasilian fortunes
Andreas.

--
https://fam-tille.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)