[Bug 45912] New: Add a 'Forum link' field which link to an existing/ new forum topic, for mundane discussion about the issue.
https://bugs.winehq.org/show_bug.cgi?id=45912 Bug ID: 45912 Summary: Add a 'Forum link' field which link to an existing/new forum topic, for mundane discussion about the issue. Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be CC: austinenglish(a)gmail.com Distribution: --- Add a 'Forum Thread' field which should be set to a link to an existing forum topic, for mundane discussion about the issue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add a 'Forum link' field |Add a 'Forum Thread' field |which link to an |which link to an |existing/new forum topic, |existing/new forum topic, |for mundane discussion |for mundane discussion |about the issue. |about the issue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> --- You can post it as a comment or See Also link. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Nikolay Sivov from comment #1)
You can post it as a comment or See Also link.
That's the current way to do it. The 'Forum Thread' field is meant to improve that. It should function like the URL field, but for a forum thread URL instead of a download URL. 'See Also' should be renamed 'Upstream bugs' to fit with its own field description (or separated into dedicated fields). I don't like having a single field for URLs to different kind of resources. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio(a)earthlink.net --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- Rosanne, do you have any thoughts? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #4 from Rosanne DiMesio <dimesio(a)earthlink.net> --- "See also" would be the logical place to put forum links, but my impression from bug 34256 and https://bugzilla.mozilla.org/show_bug.cgi?id=577847 is that at present that field by design only accepts a limited number of URLs, ones that have been deemed acceptable upstream. The problem with putting the links in a comment is that they are easily overlooked, especially in bugs with lots of comments. I'm not entirely convinced that enough bugs have active user discussions on the forum to warrant a custom field in bugzilla. OTOH, adding the field might make it somewhat easier to move user chatter out of bugzilla and back to the forum where it belongs. So I guess you can put me in the "can't hurt/might be worth a try" camp. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I made a forum topic as a test case for the proposed feature. I tried adding the URL of that topic to the 'See Also' field. Here's the error message that shown up: --- start --- https://forum.winehq.org/viewtopic.php?f=11&t=31262 is not a valid URL to a bug. See Also URLs should point to one of: show_bug.cgi in a Bugzilla installation. A bug on launchpad.net An issue on code.google.com. A bug on bugs.debian.org. An issue in a JIRA installation. A ticket in a Trac installation. A bug in a MantisBT installation. A bug on sourceforge.net. An issue on github.com. --- end --- As pointed out, the 'See Also' field only accepts URLs to a few bug trackers. It should really be labeled 'External Bug Reports'.
From the upstream link above I gather that the 'See Also' field may allow for non-validated URLs in the future. If they actually implement that feature, then my proposal could be discarded.
In the current state, it's not possible to put a link to the forum anywhere but in the comments. Regards. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 Robert Walker <bob.mt.wya(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #6 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Created attachment 63219 --> https://bugs.winehq.org/attachment.cgi?id=63219 Add a 'Forum Thread' custom field. I've come up with two possible implementations. The first is adding a custom field to the local WineHQ bugzilla installation. The patch make the field a URL in the edit form. The bugzilla administrator will have to add the cf_forum_thread field to the database. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #7 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Created attachment 63220 --> https://bugs.winehq.org/attachment.cgi?id=63220 Add a rule for WineHQ forum topics to MoreBugUrl bugzilla extension The second is to use the MoreBugUrl bugzilla extension. Though I can see the use for other bugzilla (wine forks/dependent products may want to refer to a topic on WineHQ Forums in their bugs), I don't know if upstream is willing to add non-bug trackers URLs to their extension. It may still be patched locally. This requires enabling the extension locally (i.e. remove the disabled file in the MoreBugUrl extension directory). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #8 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Forgot to say that the second implementation modifies the existing See Also field with a custom URL filter that accepts WineHQ Forums URLs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #9 from Rosanne DiMesio <dimesio(a)earthlink.net> --- The general policy here is to avoid custom patches to bugzilla, as they would have to be rebased and reapplied every time bugzilla is updated. A custom Forum Thread field could simply be added through the admin interface as a custom free text field. Links would not be clickable, but that doesn't seem to have been a problem with the Staged Patchset field, which was created that way. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Rosanne DiMesio from comment #9)
The general policy here is to avoid custom patches to bugzilla, as they would have to be rebased and reapplied every time bugzilla is updated.
The patch in comment 7 is to be sent upstream. If they do accept it, the only change required to WineHQ bugzilla is to remove the 'disable' file from the MoreBugURL extension to enable it. This will allow WineHQ forum thread links (and a few other trackers too but that's not a problem) in the 'See Also' field.
A custom Forum Thread field could simply be added through the admin interface as a custom free text field. Links would not be clickable, but that doesn't seem to have been a problem with the Staged Patchset field, which was created that way.
The patch in comment 6 is for that. It makes a to-be-added custom field cf_forum_thread a URL field just like the Staged Patchset field. I think the best approach would be to try to send the patch for the MoreBugURL extension first, and if it's not accepted upstream, then go the custom field way. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard(a)winehq.org --- Comment #11 from Austin English <austinenglish(a)gmail.com> --- @AJ, given that you maintain the bugzilla codebase, do you have any opinion on this? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 --- Comment #12 from Alexandre Julliard <julliard(a)winehq.org> --- I don't feel it would be used enough to warrant a custom field. I'm not opposed to making "See Also" usable for that purpose. The patch could be added locally if upstream doesn't want it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45912 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.mozilla.or | |g/show_bug.cgi?id=1523814 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org