Template talk:Bug

From ArchWiki
Jump to navigation Jump to search

Optional URL for other bug trackers

This template is currently hardcoded for the Arch Linux flyspray (FS) bug tracker. It may be useful to have it variable, i.e. a default but allow an optional URL and descriptor to override it. The main benefits I see for this change are:

  1. trackable, i.e. one could actually use Special:WhatLinksHere/Template:Bug for other bugs.
  2. Uniform appearance of FS#60724 links, making context directly visible. Not always the contributor adds a link name which identifies a bug. It happens frequently that the sentence around the link identifies it.

The disadvantage I see for (1.) would obviously be that we mix tracking results for FS# with other, currently discriminated, bug trackers. The one for (2.) missing out on very brief quotation-style references, like a.[1] I would not mind the both, because a uniform visibility outweighs them IMO. To implement the optional URL, I'd find it most useful to move the FS flyspray acronym to the bug number, and prepend the template output with Bug instead. E.g. {{Bug|FS#60724}} or {{Bug|systemd#60724}}. I have not spend time/tries on implementing it, but hopefully it'll work with examples like Template:Man available.

Thoughts/objections? --Indigo (talk) 13:26, 2 December 2018 (UTC)

I don't think tracking external bugs together with Arch bugs would be useful. How about creating a separate Template:XBug for external bugs instead? It would also save the effort of having to update all {{Bug|60724}} to {{Bug|FS#60724}}. -- nl6720 (talk) 13:53, 2 December 2018 (UTC)
Mixing an existing clean bucket like that is not ideal, I agree. I like your suggestion, though the "X" could perhaps be misinterpreted as abbreviation for Xorg or "ex". Then again the template should feature a label ("systemd", "Xorg", "project", etc) to make that clear.
I'm still not utterly sure myself how much extra benefit we'd gain from it (to track, but primarily readability). In the end the flexibility of using an external hypertext link has benefits too, easy to use and avoiding pitfalls with template-breaking chars et al. --Indigo (talk) 00:36, 4 December 2018 (UTC)