Creator reveals!
Feb. 21st, 2019 06:00 amAll creators should now be revealed! Congratulations everyone on another successful Chocolate Box.
A reminder to those we had to default at deadline, you are required to complete your assignment before you can sign up next year. If you're not sure whether you were defaulted by us at deadline or not, please email us at chocolateboxmod@gmail.com so we can check.
Now is your opportunity to provide feedback! We will not be commenting (unless we are asked a direct question), but we will be reading!
One of the things that came up during nominations was that some of the relationship tags were, in the eyes of some people, potentially in bad taste. Our default position is (as it has been in all years) that we are not going to be rejecting relationship tags unless the tag includes the nomination of a real life child in a RPF fandom. That said, given the sheer number of complaints we got this year, we thought that we should open this for discussion. Should we continue to allow essentially all nominations? And if the answer is "no", what criteria should we be using?
Talking about nominations, it's looking like the change in numbers worked for the better - we went a lot longer this time before the admin console started to break down, and we didn't get the complete shutdown from the previous round. If you have suggestions for nomination numbers, we're interested to hear them.
Finally, we remind you all that anon comments are screened by default, but will be unscreened if you include your AO3 name.
A reminder to those we had to default at deadline, you are required to complete your assignment before you can sign up next year. If you're not sure whether you were defaulted by us at deadline or not, please email us at chocolateboxmod@gmail.com so we can check.
Now is your opportunity to provide feedback! We will not be commenting (unless we are asked a direct question), but we will be reading!
One of the things that came up during nominations was that some of the relationship tags were, in the eyes of some people, potentially in bad taste. Our default position is (as it has been in all years) that we are not going to be rejecting relationship tags unless the tag includes the nomination of a real life child in a RPF fandom. That said, given the sheer number of complaints we got this year, we thought that we should open this for discussion. Should we continue to allow essentially all nominations? And if the answer is "no", what criteria should we be using?
Talking about nominations, it's looking like the change in numbers worked for the better - we went a lot longer this time before the admin console started to break down, and we didn't get the complete shutdown from the previous round. If you have suggestions for nomination numbers, we're interested to hear them.
Finally, we remind you all that anon comments are screened by default, but will be unscreened if you include your AO3 name.
no subject
Date: 2019-02-23 06:40 am (UTC)As someone who nominates/requests/offers a lot of single relationships, I don't think this is an issue worth stressing over. The tagset is visible and continually updated throughout the nominations period. Anyone who's concerned about additional ships being added to their single relationship fandoms can keep an eye on the tagset and add ships to their own noms as necessary.
Alternatively, some people choose to nominate both the romantic and platonic versions of their ship from the beginning, just to be safe. Or they nominate their OTP and an unrelated ship they can tolerate, despite the fact that it's not required by the signup form.
Or they do as I typically do, which is to drop certain fandoms from my offers if I really want to avoid offering my NOTPs. Chocolate Box has a huge number of nominated fandoms each year, and it's no big deal for me to drop some of my fandoms from my offers and to add others, if that's what suits me best in the end.
tl;dr; The current system gives participants more flexibility while still providing them with plenty of options to avoid their NOTPs. It also, as mentioned in an above comment, helps keep the tagset to a more manageable size, which is really important for AO3 exchanges.