SASO Referees (
referees) wrote in
sportsanime2016-08-27 04:44 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
SASO 2016: Talkback

The mods still plan to reply to the topics listed at the bottom of the post.
--
This is not the final wrap-up results/etc. post—that's coming in a couple of days. But while the mods tabulate final scores and create prize graphics, now's a good time to look back and reflect on your SASO 2016 experience.
Please leave comments giving us feedback on the event this year! What did you like? What did you dislike or find frustrating? What can we improve for next year, and how can we improve it? What was your favorite part of the event? Least favorite? Would you participate next year or not? Why? If you could mention your team when making your comment, we'd appreciate it.
If you would prefer to submit your comments in private, you can e-mail us at anime.espn@gmail.com or send us a Dreamwidth PM. We would prefer it if you'd put "Talkback" in the subject line.
Here's what the mod team plans to improve for next year:
- Voting program reliability. We'd like to apologize again for all of the server dowtnime, and definitely plan to make it much more stable for next year. The voting system in general, though, will remain the same.
- Bonus round program reliability. We think we got most of the kinks out during this year, but want to keep it stable for next year too.
- Dreamwidth capability for NSFW cross-posting. We didn't have time to implement it this year, but next year it should be ready to go.
- Clarifying the rules, especially on what "popular culture media" is acceptable to include in SASO work.
--
Mod Replies: (updated 12:55PM EDT 8/28/16)
Please note that inclusion of a topic on this list indicates that we're going to address it, not that we've made any decisions on judging/implementing or not implementing it.
Voting:
(frozen comment) no subject
(the only thing about Google forms for a master is that the ships tended to get very complicated when people would give options + with the platonic/romantic option....)
(frozen comment) no subject
re: your comments—you could still notate the & / when putting the ship in, and dictate that characters be ordered alphabetically so they're all grouped together properly. and since this would just be for fills and not prompts you just put in the pairing that you ended up writing, rather than all the options the prompter listed. does that make sense?
(honest to god i'm debating whipping up a sample right now just to see/show what it would look like)
(frozen comment) no subject
A checkbox option for romantic, platonic and poly might also be an option and would allow for better filtering! ...I'm totally itching to try and make a prototype too, haha.
(also ahh get some sleep!)
(frozen comment) no subject
but yeah there's a good amt of potential that i think would be easy for both mods and regular users to keep up.
(frozen comment) no subject
I uh, went ahead and played around a bit just with a spreadsheet to get a feel for a masterlist-y tactic - sheets is of course slower than Excel at calculating things which could be a problem as the doc gets heavier but the two of them import/export fine. I know that all the objectives are theoretically possible? It would be nice to combine the two concepts since Forms needs less upkeep and the masterlist thingy hopefully avoids missing any data, but...[link]
I think the romanisation issues are more pronounced with certain fandoms -- as a tennis participant there are a LOT of characters for whom the o vs ou and even shu vs syu vs syuu vs shuu etc names aren't consistently romanised at all. But then again, since that's usually with smaller fandoms, it'd probably be easy to do a quick touch up here and there.
Also I apologise for just dumping this on you! More putting it down for reference - feel free to ignore. There's definitely a lot of potential - it's just a matter of having the time to hash it out properly.
(frozen comment) no subject
(frozen comment) no subject
(frozen comment) no subject