Am Tue, Dec 03, 2024 at 01:49:33PM +0500 schrieb Andrey Rakhmatullin:
> raise certain
> barriers between the package and other people.
The current barrier appears to be the ITS procedure[1], which I now
engage with nearly daily through the "Bug of the Day"[2] workflow.
Previously, the requirement to wait 21+10 days (ITS waiting period +
delayed upload) deterred me from using this procedure. This delay
necessitates revisiting the issue multiple times and managing related
calendar entries, which can be burdensome. However, in the context of
"Bug of the Day", the regularity of the work has made it practical to
develop a workflow that accommodates these requirements, so it's now
manageable.
In my experience, more than 50% of ITS requests receive no response from
maintainers at any stage of the salvaging process. As a result, we have
effectively raised barriers for cases where maintainers have stopped
caring about their packages and failed to communicate this before
stepping away.
I wonder if we should reconsider the default assumption of package
ownership. Instead, we could introduce a file, such as
debian/dont_touch_my_package (or a similarly named file), where
maintainers can document their reasons for discouraging others from
uploading the package. This file could include a timestamp, and we could
establish an agreed-upon timeframe for refreshing the statement to
ensure its continued validity.
We could introduce this change starting with Debian Policy version X.
Maintainers who adopt this policy version by updating the
Standards-Version in their packages would implicitly agree that, in the
absence of a debian/dont_touch_my_package file, any Debian Developer is
permitted to upload the package.
Do you think this would lower the barrier between a package and other
people?
Kind regards
Andreas.
[1]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks
--
https://fam-tille.de
