This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-13
Channels
- # admin-announcements (6)
- # beginners (51)
- # boot (164)
- # braid-chat (49)
- # cider (10)
- # clara (17)
- # cljs-dev (13)
- # cljsjs (51)
- # cljsrn (10)
- # clojars (42)
- # clojure (195)
- # clojure-bangladesh (102)
- # clojure-berlin (8)
- # clojure-canada (1)
- # clojure-chicago (19)
- # clojure-colombia (4)
- # clojure-denmark (6)
- # clojure-russia (15)
- # clojure-ukraine (7)
- # clojurescript (257)
- # code-reviews (10)
- # community-development (292)
- # core-async (13)
- # datomic (26)
- # dirac (4)
- # dunaj (5)
- # dysphemism (5)
- # events (21)
- # funcool (15)
- # hoplon (115)
- # instaparse (31)
- # ldnclj (15)
- # mori-fork (43)
- # mount (5)
- # off-topic (18)
- # om (195)
- # onyx (13)
- # proton (9)
- # re-frame (11)
- # reagent (44)
- # slack-help (14)
- # slackpocalypse (1)
- # spacemacs (10)
- # yada (23)
and there will be a lightning talk session, so there is still a chance to have female speakers "at least" for that
@nblumoe: That sounds great! Maybe you could promote those options at the upcoming ClojureBridge Berlin workshop 😉
yes, sure. @martinklepsch is taking care of that we are also going to promote it tonight at the Clojure Meetup
@maria: while I'm really excited about the speaker lineup I definitely share your sentiment wrt to speaker diversity. I think I/we have probably not put in enough effort to reach underrepresented groups but at the current point in time there is not much more that we can do except taking notes for future events. (If you have ideas what we could still do I'm all ears :))
@martinklepsch: Some ideas for next time -> there are the #C050YB2HH and #C052W592N channels that could be a first step to spread to some underrepresented groups. There might be other channels I missed. Also reaching out directly to people you know / you've met from underrepresented groups.
@eleonore: thank you! I'll take note and hopefully we'll get a chance to do better next time
@martinklepsch: you're welcome! Glad I can help While we're at it I'd like to point out that expending on your Code of Conduct might help get more diverse speakers and attendees. What comes to my mind now is adding something about what kind of actions could be taken and who can be contacted to report a breach of the CoC. Here are a few examples: https://plone.org/foundation/materials/foundation-resolutions/code-of-conduct, https://www.djangoproject.com/conduct/, http://www.pyconuk.org/codeofconduct/
Also found that for CoC inspiration: https://github.com/python/pycon-code-of-conduct. It's inspired from http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Having people to contact in case of problems/breaches is on my list I'll consider a more explicit code of conduct again, if we change it we'd probably use http://berlincodeofconduct.org/
@eleonore: thanks for all your input, really appreciate it keep it coming
@martinklepsch: no problem! I'll try and gather this type of info in a gist or gh repo so they can easily be shared.
@martinklepsch: fyi, Lynn and I would be happy to serve as a resource for anything related to Clojure events (including events that we have no part in) - feel free to ping us in tandem at <mailto:[email protected]|[email protected]>
I think the idea of a resource guide for Clojure events sounds pretty great, certainly things like this exist generally but having something Clojure specific would increase the odds of it being found in our community