Hi, On Mon, 30 Apr 2018, Markus Koschany wrote: > tracker's package overview is very helpful in gathering a lot of > information about certain packages. It would be even more useful if > maintainers or teams were able to add custom information to it. I > currently count nine "tables" (lists), general, versions, versioned links, > binaries, action needed, news, bugs, links and ubuntu.
The old PTS was able to display "static news" provided by the maintainer. We got rid of that feature which was not really used. Example here: https://packages.qa.debian.org/d/debian-cd.html > It would be great if we (maintainers or teams) could add a new > column/table and customize it with additional information and add new > entries to one of the existing tables. I think we need to be a more specific here. I don't think we need to be able add arbitrary tables with custom content. There must be some pre-defined structure. Also you mention adding new entries to existing tables. Which tables are you thinking of? It certainly doesn't make sense to be able to add custom data to all tables. I think "news" and "links" (maybe general) are the only ones where it might be interesting. Combining all those three, I'm not sure that I see any need to have a new table with content provided by the maintainer. Also when you think of team-provided data, you probably want a way to add the same news or link to all packages belonging to the team. But a package can be part of multiple teams and only of those team is the true maintainance team. How do we decide which one is the authoritative one? > The reasoning for that could be that teams want to highlight contact > information, work flows or announce important issues, transitions, > things to be aware of. The downside is that this is yet more data to maintain and that is likely to become stale/outdated at some point. 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/
