Figured I might as well post some examples of what we've been working on. Not like it's classified information or anything~
First, an example image of the issues and their links:
https://www.dropbox.com/s/cpb0i5uwil9ke ... xample.svgThe preview will probably fail, cause the image is too large for Dropbox I assume, so just download it to your PC. For those who don't know, SVG's can be opened with your browser. Just don't use Internet Explorer cause, well, it's sh*t for one, and the issue descriptions don't show either. Use Chrome or something. Then you'll probably want to zoom out as much as your browser will allow so you can see the bigger picture properly.
Mantis Updaters and lurkers should recognize the issue colors, as they're the same the Bug Tracker uses. I.E.: pink for new issues, purple for feedback, gray for dupes, etc... You can mouse over an issue to see its summary, or click the bubble itself to go directly to the issue's URL page. The issues' bubble sizes are determined by the amount of supporters for said issue. Supporters are also passed from children to their parents and from duplicates to their duplicees(or something?), per Reef's request. Issues with a red border are in the Bug Tracker's top 10 list, feel free to note not all of them are actually that big in comparison to other issues.
As Reef mentioned, the amount of issues that haven't been linked yet is painfully apparent. And there's a lot of 'em. The example I posted is from the Tracker's state at the fifth of July (05/07), so it's a tad outdated, but still. Thus Reef, again as mentioned earlier, proposed the idea of creating a collection of trees of sorts to connect these issues faster and more comprehensibly.
And here it is so far:
https://www.dropbox.com/s/pddupkdmhoy57 ... xample.svgEvery tree consists of a trunk, possibly branches, and leaves. If you know how trees work you can probably guess what the basic idea is there. Trunks can have branches or leaves, branches can have more branches or leaves, and leaves are supposed to be the "end of the line". Ideally, bugs sit on leaves (the nature lesson is real). How big a tree needs to be (read: how many branches and leaves are specified) is completely up to the Updaters of course (Reef, Mazetar, etc...). What I've mapped out so far mostly contains example leaves. I've proposed that the best way to work is just to start as small as possible, and only turn a leaf into a branch when there are too many bugs sitting on top of it, which Reef seemingly agreed with.
The advantages of structuring the Bug Tracker in this fashion should be painfully apparent. Reef is a better public speaker than me so just read his post again or something if you still don't get what we're trying to do here~ Everything you see is my attempt at visualizing Reef's ideas, so pretty much 95% of all credit goes to him. I'm just the guy who had more free time to do the work Reef couldn't :3