(11-10-2015, 09:24 AM)wildgoosespeeder Wrote:(11-10-2015, 07:21 AM)JosJuice Wrote: I don't know enough about the wiki to comment on this as a whole, but looking at the example pages you put up, I see a problem: The templates for each issue will prompt the user to create an issue report if there isn't one, even for things that would be obviously invalid if someone were to submit them to the issue tracker, such as EFB2RAM being needed. (The template is also weirdly positioned, making the first line of text very short.)
MaJoR also noted that. To quote my rebuttal on Template talk:RatingProblemFix:
Quote:I think it's because the awareness of such an issue being sought is not explicitly expressed. I find the duplicate issues stemming from the lack of first reports not being in the Wiki in the first place. I find that a duplicate report is better than not having a known report at all. The Bug Tracker admins have flagged issues as duplicate in the past. This just means to me that the situation will sort itself out eventually if my system were implemented. Then it will be encouraged to replace duplicate reports with first reports (that is something I can't tell MediaWiki to flag because it is too complicated). Recently, it seems that Lucario fixed the URL to search first when clicked in my template. As for templates, I find that the templates are not categorized correctly. Two categories should be templates that are of use to Dolphin Wiki contributors and templates that should be ignored by regular users (and maybe protected from any edits).
I don't see how that is a response to my question. What you and MaJoR were talking about there is about the risk of duplicate issues being created. I agree with MaJoR in that it would create more maintenance work for us on the bug tracker, but what I was talking about has nothing to do with duplicates. My concern is that some of the issues that are listed on wiki pages (like EFB2RAM being required) aren't Dolphin bugs at all but rather problems with the user's configuration. Such issues are good to list on the wiki but are completely inappropriate for the bug tracker. Your system is designed so a wiki issue that does not have a bug report counts as incomplete (i.e. shows the "Create/find bug report" message and makes the page show up in Category:Pages with missing bug reports). This incompleteness can only be resolved if a bug report exists, but bug reports for this kind of issues are invalid and will not be accepted on the bug tracker. If your system succeeds in making people create more bug reports (I don't know if it will or not), this is going to lead to users cluttering the bug tracker up with useless issues for no good reason. The wiki needs to take into account that some issues simply aren't meant to have bug reports.
I don't understand the point of assigning ratings to issues on the wiki, by the way. Users can already read the text and understand how serious "the game crashes" is in comparison to "the reflections on Termina Bay are a bit off". In fact, reading the text can even be better because it lets the user decide how serious the issue is to them instead of having an arbitrary scale of seriousness. I'm not saying the idea is completely worthless, but the advantages seem to be much smaller than the maintenance cost that's needed.