4 ms·
This is actually a good example why you should have a code of conduct as a conference. Bad things on stage happen. As an organizer, you can now write an apology
by Argorak 13y ago
This is actually a good example why you should have a code of conduct as a conference. Bad things on stage happen. As an organizer, you can now write an apology that sounds like the one techcrunch wrote:
http://techcrunch.com/2013/09/08/an-apology-from-techcrunch/ http://techcrunch.com/2013/09/08/an-apology-from-techcrunch/
Or, if you had a CoC, it could sound like this:
* "Sorry, we had people on stage that violated the rules we agreed upon beforehand. <list of rules from CoC> They were expelled from the conference immediately."
- pstack 13y agoAnd that would actually seem to be a really reasonable progression for this whole thing. The presenters say "we made an unfortunate judgement call and we apologize" and the conference says "so from now on, here's our short list of rules to avoid uncertainties in the future" and then we all grow up and move on with our lives. Unfortunately the tech industry seems to be enamoured with not merely being offended, but being offended by the potential that they could have been offended. So we'll circle the drain with everyone beating the drum in support of their own personal agendas for awhile more before this is over. By that time, someone else will have done something dumb and we'll be ready to have another go.