We Stand for a Welcoming Community
During the last weekend, several events have shaken the Ruby community. We feel that due to the gravity of these issues, a direct statement in addition to those of individual members of the Ruby Berlin e. V. is necessary.
This boils down to 4 points
- We are against harassment and ignorance
- We are for diversity
- We are not in this for the drinks
- We care
Against Harassment and Ignorance
Two incidents caught our eye this weekend (in the order they came to our knowledge):
A RailsBridge member wrote a mild rant about inappropriate gem names. It fostered a healthy debate, but he was also attacked and subsequently banned from the Ruby Facebook group by an administrator citing Mykeru's law for having posted a link. We distance ourselves from this group and we will recommend leaving it until there has been a change of administration.
A community member came out about her harassment experience (heed the trigger warnings given in the post) at a conference, backed by two colleagues' accounts. Sadly, instead of seeing this as a clear reminder that such things are a sad reality, quite a few people took the opportunity to shame Justine or come up with crude interpretations, if not outright insults or threats. We are shocked by the lack of empathy in those reactions. We thank Justine for speaking up.
We all joined the Ruby community because it is a warm and welcoming place - sadly, the aforementioned events draw a very different and very real picture. This is why we feel the need to speak out:
We strongly oppose any form of harassment or discrimination, including, but not limited to, all forms of sexism and racism.
For Diversity
The Ruby Berlin e. V. member roster is very diverse and we are proud to carry that outwards. All events run by Ruby Berlin e. V. in recent years have been run under a Code of Conduct. This has been taken seriously and underlined by additional actions such as running CFPs that ensure a diverse set of speakers and by providing childcare and significant others tickets to accommodate families. Our role of community organisers is first and foremost to provide safe and enjoyable spaces for people to exchange ideas and master their craft.
We will try to lobby other organisations in the Ruby space to make similar announcements.
We would like to reach out to anyone organising community events, not only in the Ruby space, to help tackle the problems that affect our community. Though imperfect, we do have a few things worked out and are happy to share. We are proud of what we have achieved so far and will strive to make our values known and accepted to make such incidents a thing of the past.
We are Not in this for the Drinks
Yet, over the same weekend, one healthy discussion has taken place: rethinking "Drinkups". Quite a few people have come out publicly, criticising the drinking-focused evening culture present at meetups and conferences, stressing that they did not feel welcome at the evening events. We have, through Rails Girls and eurucamp, experimented with different forms of organising the evenings and will continue to do so.
We will review our way of organising parties and gatherings and come up with proper solutions and guidelines for our events and announce these well before our next event. We certainly don't want to patronise attendees, but we do want to ensure that everybody feels welcome and has a good time. We appreciate feedback very much and welcome constructive suggestions.
We Care
Over the last few years, we have organised many gatherings and brought joy to a lot of people. We can safely say that everyone we have worked with as Ruby Berlin e. V. is humble and caring and would go to great lengths to make the Ruby community a welcoming one. Our mission is to foster that part of the community.
The Ruby Berlin e. V. and friends, namely:
- Rails Girls Berlin orga team
- RUG::B orga team
- eurucamp orga team
- JRubyConf.eu orga team
- RedFrog Conf orga team
- nerdkunde podcast
- geekstammtisch podcast
- up.front orga team
In person:
- Thilo Utke @freaklikeme
- Dajana Günther @dg_tweety
- Alex Coles @myabc
- Guillermo Tirelli @wordgraphy
- Florian Gilcher @argorak
- Fanny Krebs @fannivuniconnu
- Lucas Pinto @medk_
- Jana Vogel @janacharlotte
- Robert Schulze @fnordfish
- Sergio Gil Pérez de la Manga @porras
- Mari Carmen Gutierrez De La Ossa @valakirka
- Piotr Gęga @piotrgega
- Ute Mayer @nerdbabe
- Tobias Pfeiffer @PragTob
- Nico Hagenburger @hagenburger
- Klaus Zanders @klaustopher
- Essy Hentrich @casheeew
- Lucas Dohmen @moonbeamlabs
- Bodo Tasche @bitboxer
- Tobias Eilert @l_ama
- Dirk Breuer @railsbros_dirk
- Sebastian Cohnen @tisba
- Matthias Günther @wikimatze
- Ernesto Míguez Rodríguez @xemig
- Erik Michaels-Ober @sferik
- Christoph Bünte @chriscando
- Matt Patterson @fidothe
- Greg Karékinian @gkarekinian
- Sven Fuchs @svenfuchs
- Anika Lindtner @langziehohr
- Jan Lelis @happycode
- Robert Schmidl @othertimes
- Christoph Grabo @asaaki
- Yannick Schutz @yann_ck
- Kerstin Kollmann @kkvie
- Carlos Moutinho @carlosmoutinho
- Simon Kröger @kroegerberlin
- Julius de Bruijn pimeys
- Tilmann Singer @til
- Christoph Olszowka @thedeadserious
- Marek Rosa @marekrosa
- Caio Filipini caiofilipini
- The Berlin JavaScript Community @berlinjs
- Robin Mehner @rmehner
- Jan Lehnardt @janl
- Garret Alfert @galfert
- André Wendt @awendt
- Txus @txustice
- Markus Krogemann @mkrogemann
- Sebastian Schulze @bascht
- Florian Plank @polarblau
- Tom Stuart @mortice
- Simão Mata @simaom
- Ivan Kamatovic @ikamatovic
- Florian Ebeling @febeling
- Alexander Sulim @soulim
Want to support us and feel missing on this list? Mail us or send a pull request.
October 16th, 2013