Total posts: 
Reorganize fora in Workshops window + new forum for tech problems:
Anime-tedHere's what I'm thinking. Rather than have the threads as they show up on the screen now, break the listings into two distinct categories organized by what they address with the wiki, in this manner: Wiki Functions: Frequently Asked Questions, Wiki Talk, Wiki Repairs, Tech Wishlist Wiki Content: Special Efforts, Trope Repair Shop, Trope Talk, Image Pickin', Translations, Sandbox Wiki Repairs is something else I'd like to propose — a subforum dedicated to reporting things that are broken or glitching, to keep these threads organized together and out of Wiki Talk and Tech Wishlist. Yea/nay?
Puʻu ʻŌʻōLooks good at the first glance, although I am not sure if Wiki Repairs should be different from Tech Wishlist. After all, wishing for a tech fix isn't that much different from wishing for a tech innovation - they are all admin-only stuff.
Seeking for LightI would support Wiki Repairs. I think it's sufficiently different from Tech Wishlist in that Tech Wishlist is for non-urgent, non-essential stuff that would simply be nice to have, whereas tech issues with the existing wiki often warrant relatively prompt attention and need to be fixed in order to keep things functioning smoothly.
Anime-tedNinja'd; sums up my position perfectly.
edited 17th Feb '12 9:46:45 AM by Willbyr
Puʻu ʻŌʻōSo far, I've dealt with bugs that didn't have actual threads for them with PMs, so I put this info in the FAQ thread. under the understanding that a simple bug would be something too short-term-y to warrant its own thread. However, it's just my idea.
Well, as Eddie is the one who does all the fixes, what's the benefit of splitting these things so he has to check two places?
Reality is that, which when you stop believing in it, doesn't go away. -Philip K. Dick
Anime-tedThe whole point is to have one centralized place where people can report things that aren't working right. What got this started was a discussion in a thread I posted in Wiki Talk about problems with crowners, which got moved to Tech Wishlist. That spawned a discussion between Septimus Heap and I about what these subfora are supposed to be about, which led me to propose this. Right now Wiki Talk and Tech Wishlist are both covering repair issues...a lot of the threads in TW, just based on their titles, would be better suited to the Repairs forum. The proposed splits would allow Wiki Talk to keep to policy/guideline discussions, Tech Wishlist to be a place to suggest improvements, and Wiki Repairs would be solely for fixes. Each forum could then have a banner similar to the one Eddie put on the conversation builder pages for TRS and IP stating the functions. For example, the one for Repairs could say
Use this forum only if you're reporting something that's broken. If you've got a suggestion on how to improve the site tech-wise, please post it in Tech Wishlist. If you have a question/comment/suggestion regarding a site policy or guideline, please post it in Wiki Talk.The proposed reorganization of the forum listings on the Workshops window is more of an aesthetic fix than anything.
edited 21st Feb '12 11:09:09 AM by Willbyr
Puʻu ʻŌʻōThe problem is: Wouldn't be Wiki Repairs be redundant to PMs? Because so far, when there was a bug I always sent a PM to Eddie to ask for a fix - and I just did it a while ago, about fixing an IP tag that had been Morgued years ago, with success.
Anime-tedHow many people think to PM him directly about problems, though? Seems far more often that people post threads asking if anyone else is having the problem they're having; that also has the advantage of showing how widespread an issue may be.
Puʻu ʻŌʻō^Yes, that is true. Many people don't know where to put what on the fora; I made the FAQ thread because of that. Maybe by making it more prominent?
Anime-tedIt definitely needs to be more prominent. EDIT: That being said, who decides how major/minor a tech issue is? That's so subjective that I don't see discouraging threads about them to be a viable solution.
edited 21st Feb '12 12:01:02 PM by Willbyr
Puʻu ʻŌʻōI am not a programmer, but creating new functions would be Tech Wishlist-worthy, while simply "removing a malfunction" would be PM-able. Not very helpful tough. About making it more prominent, we might ask for a pin there.
I have PM'd Eddie about an issue before—after making this thread about it. No discussion was necessary and the problem was so simple and seemed so easy to fix (to a non-programmer, of course). Nothing came of the thread, but when I sent the PM Eddie fixed it immediately. I'd do that with other issues, but that one was so simple that it was like asking someone to sign their name on something. For more complex bugs, like that bug with cut pages' wicks, I just don't know what to do.
Anime-tedI had another thought a coupla days ago. Instead of making a new forum, maybe Tech Wishlist could be renamed to "Tech Repairs/Wishes", and when you make a new thread in the forum, it could be tagged with an icon indicating whether it's something that needs fixing (say, a red exclamation point or ) or a suggestion/tweak (maybe a present or ). That last point is why I keep pushing for this...it's one thing to PM Eddie for simple fixes, but if there's something big or complex happening, I'm not sure that a PM is enough.
edited 25th Feb '12 7:27:40 PM by Willbyr
Great idea. Things like new features are great ideas, but they don't tend to be as urgent as the kinds of threads that get pushed beyond the first page because regular tropers have no way of dealing with the issues.
Puʻu ʻŌʻōWe'll definitively need his opinion here. It's one thing to ask to fix a missing "moderator" tag (as happened again today), but something larger like the Related To bug might need threads.
The system doesn't know you right now, so no post button for you.
You need to Get Known to get one of those.
Total posts: 17
TV Tropes by TV Tropes Foundation, LLC is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Permissions beyond the scope of this license may be available from email@example.com.