Bug#897227: tracker.debian.org: allow overriding values
Control: retitle -1 tracker.debian.org: manage metadata like Vcs/Homepage/Maintainer/Uploaders
Hi Markus,
On Mon, 30 Apr 2018, Markus Koschany wrote:
> some information in packages can get quickly outdated like VCS links,
> homepage addresses or the information about the actual uploaders of
> team maintained packages. It is often neither practical nor useful
> to do mass-uploads just for changing an outdated VCS link.
>
> Please allow overriding certain values in tracker.debian.org. For
there are multiples similar issues mentioned in your bug report
and you are doing many shortcuts which make it not really actionable
The tracker is currently not the canonical place to store all those
values. The information contained in Packages/Sources files are the
reference. Currently they come straight from the source package and you
want to change this.
I don't think we want to have this data only in the tracker. We want
to keep it at least in Packages/Sources files. For this we probably want
to use the dak override mechanism to inject up-to-date data.
So any realistic transition should involve tracker.d.o being able to
export the override data for dak, and being able to manage the data
on its own (while still importing/syncing with whatever is available
in the source package).
Then not all fields are equal. While homepage is relative clear, the way
to handle maintainer/uploaders is probably different, do we want to
handle it as a simple text field or shall it be generated out of the
package subscription (for example by letting each subscriber choose a
role, eg "follower/lurker", "maintainer", "bug triager", etc.)
Some of the fields might be set a the package-level, some at the
team-level (and here we come again to the problem of which team is the
authoritative team for the package).
So while it's great to have a bug report to have this conversation, I
believe that we want to split the problem further down (and possibly
open more bug reports) because right now this request is just too broad
and is lacking too many details to be actionable.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
Reply to: