Hi, Am 02.05.2018 um 09:43 schrieb Raphael Hertzog: [...] > 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.
More precisely the custom table should be in the center column at the top. This would be a text field and all information therein should be either visible for a single package or all packages maintained by a certain team. I thought it could also be used as an alternative solution to my other feature request in #897227. If overriding values is not practical, we could inform users quickly about news like "Packaging moved to salsa.debian.org. You can find the Git repository for $sourcepackage at https://salsa.debian.org/java-team/$sourcepackage. Ideally tracker would insert the value for $sourcepackage. I was also thinking about being able to add more entries to "links" but I agree it doesn't make much sense to add more entries to the versions table. I had also in mind that it would be nice to customize the layout by changing the order of the tables or by changing the design completely. This could be achieved with user defined templates. Question is if we want to keep the current "corporate design" or allow maintainers/users at all to change the design depending on their tastes. > 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? As I wrote in #897227, I don't believe this is the general case. We usually have one team as maintainer and several uploaders. We definitely need to find a way to allow a certain DD to add such customizations to multiple or all team maintained packages. In case of multiple maintainers I can only imagine that all have the right to decide about customizations. Teams should choose DDs who are responsible for interacting with tracker though. The "owner" role from salsa.debian.org would be a way to determine it automatically. >> 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. For teams it wouldn't be a lot of information. If I can change it in a centralized place and add/remove the same information for multiple packages, is would be definitely maintainable. I would strive for adding as much auto-generated data to tracker as possible. Manual customizations will probably be an exception but are nevertheless useful if you want to visualize something immediately that would otherwise require a source upload. Regards, Markus
signature.asc
Description: OpenPGP digital signature
