rubyberlin / code-of-conduct Goto Github PK

As seen in #149, hashtags might be useful as an additional field for each event.

Suggested format:

{
  "usergroups": [
    {
      "name": "ThoughtWorks Tech Talks NYC Meetup",
      "city": "New York",
      "country": "USA",
      "link": "https://www.meetup.com/ThoughtWorks-Tech-Talks-NYC/",
      "hashtag": "ThoughtWorksNYC",
      "contacts": []
    }
  ]
}

Which links to https://twitter.com/search?q=%23ThoughtWorksNYC.

In polish texts, some polish letters are displayed for me in a different font than desirable museo sans.

I'm not sure if it's my computer and if the page is serving any fonts to the user but I believe it should avoid this kind of situations.

Screnshoot:

We had an incident today, which still saddens me and I'm sorry about. :'(

The incident was about a display of brutal violence against animals. This was triggering to an attendee and others found it to be inappropriate as well.

I'm for adding this to the code of conduct, that such pictures are unwelcome. It can be tricky to formulate.

I'm happy to hear about ideas, input, whatever.

We have to figure out and implement #39 before we can move along with this.

Tobi

Would be cool if the CoC would be accessible through a domain like this. 🌻

PS: By anyone I kinda mean Ruby Berlin e.V.

Hi, shouldn't eURUCAMP be here under conferences in the suppporters json file?

"Wenn ein Community-Mitglied sich auf inakzeptable Art und Weise verhält, steht es den Veranstaltenden zu, jegliche ihnen angemessen erscheinende Maßnahme zu ergreifen, bis einschließlich einem befristeten oder permanenten Ausschluss aus der Community ohne Warnung (sowie im Falle einer zahlungspflichtigen Veranstaltung ohne Rückerstattung von Kosten)."

Ich bin zwar kein Jurist, aber ich glaube diese Formulierung darf man im Deutschen so nicht machen, da es auch als Selbstjustiz ausgelegt werden könnte. Hier wäre die rechtssichere Formulierung in etwa: jegliche mit dem gesetzlichen Bestimmungen konformen ihnen angemessenen ... In besonders schweren Fällen kann dies auch zu einer Anzeige bei den Strafverfolgungsbehörden führen.

Meine Intension mit dem 'Anzeigen' orientiert sich an Aktivitäten die als Straftat gelten. Ich denke wenn man den gesamten Abschnitt noch ein wenig ausbaut und etwas erklärt schafft das zudem mehr Verständnis, Es sollte ja nicht wie Willkür und Drohgebärden klingen sondern den Menschen aufzeigen und bewusst machen, das sich manche Handlungen im Rahmen der Strafverfolgung bewegen. Dazu zählt ja auch schwere Beleidigung und Verleumdung. Es muss nicht immer gleich 'handgreiflich' zugehen.

Beste Grüße /E.D.

It seems like there's a number of recruiters using our page as a source for phone numbers.

We should either find some way of hiding those numbers (which I prefer not to) or clarify what the numbers are there for.

We should also devise a course of action. I'm perfectly fine with name-and-shame in this case.

Due to a dicussion about the German version (#61), we realized that we are missing perspectives by other marginalized groups on the Code of Conduct. It makes sense to ask groups that have collected vast knowledge and experience over some time about these subjects.
For example, the Migrationsrat (mrbb.de) or lesmigras (lesmigras.de) as well as LeidMedien (leidmedien.de).

The idea is to ask them for a review and input on the CoC. However, we need to value their expertise financially (can we donate, for example). Otherwise, we would be exploiting their hard work - not cool.

How can we approach this?

Hi there, first of all, thanks so much for all of the effort put into this! 🙌 Really amazing to have this open standard that can be used in so many environments.

I noticed that the English version of the website at https://berlincodeofconduct.org/ had some Czech text content under:

• document.title
• header h1
• header p
• #supporters
• footer

I checked in the English translation file, and it seems ok, but I am also not well versed in how this repository is set up.

I'd suggest changing it to main to comply with your own advice:

Exercise consideration and respect in your speech and actions.

https://sfconservancy.org/news/2020/jun/23/gitbranchname/

BTW: Love the project, keep up the good work

• The website should always use HTTPS and redirect if it doesn’t.
• The path (= language) must to be kept during the redirect.
• When running locally (http://localhost:4567) it must not redirect to https://localhost:4567.

If possible, we should use an HTTP redirect. If not, at least we should have it written in JavaScript.

Hey all, thanks for maintaining this delicate topic.

We are in the process of picking a CoC for our user group. I suggested this one, but one of my co-organizers opposed it, as it does not condemn the use of sexual language explicitly. I quote in here the email he wrote to make his point:

The incident in October was when the presenter said "But now I feel like the male heterosexual porn star trying to grab all the attention while you want to see the real actors.". Unless we decide that words are totally malleable, "harassment" is something which has a target. A presenter addressing the entire audience, talking in general terms, is never harassing anyone. But even if we would redefine language like that, I would say that there is no item on this list that includes use of sexual imagery. If you disagree, please tell me which one would apply.

I've separated the items [of the paragraph that begins with Harassment includes:] to make it easier to read:

• harmful or prejudicial verbal or written comments related to gender,
• harmful or prejudicial verbal or written comments related to sexual orientation,
• harmful or prejudicial verbal or written comments related to race,
• harmful or prejudicial verbal or written comments related to religion,
• harmful or prejudicial verbal or written comments related to disability
• inappropriate use of nudity (including presentation slides)
• inappropriate use of sexual images (including presentation slides)
• inappropriate depictions of violence (including presentation slides)
• deliberate intimidation
• deliberate stalking
• deliberate following
• harassing photography
• harassing recording
• sustained disruption of talks
• sustained disruption of other events
• inappropriate physical contact
• unwelcome sexual attention

The other paragraph under the heading "Unacceptable Behavior", starts ​"Unacceptable behaviors include". I think it is this one that should talk about verbal sexual imagery, and I don't think it does so now.

I won't suggest an exact wording. But if others feel this is worth picking up and including in this CoC, please let me know :-)

Ich schreib das mal auf deutsch, betrifft ja sonst niemanden :).

Es ist die Frage aufgekommen, warum der deutsche Text nicht gegendert ist, also darauf geachtet wurde, keine Worte zu verwenden, die standardmässig einem Geschlecht zugeordnet sind - zum Beispiel "Teilnehmer" (generisches Maskulinum).

Wenn wir das machen wollen, müssen wir uns auch überlegen, wie.

Ich persönlich bin im allgemeinen Freund von Neutralisierung - da stört sich am Ende niemand dran und ich finds eigentlich auch selten holprig. Zum Beispiel ließe sich "Teilnehmer" durch "Teilnehmende" ersetzen. Das stößt selten jemandem auf und ich bin da gerne diplomatisch.

Alternative ist natürlich auch die Sichtbarmachung - zu den Beispielen dazu gibt es natürlich noch die Formen mit * und _. Ich hab da auch kein grundsätzliches Problem mit und kann das gut vertreten, kann mir aber mehr Diskussionen an der Stelle vorstellen.

To get a better overview of current open and cross-referenced tickets and pull requests, here is an overview list for our next in-person-meeting in march. :)
#1. Versioning

• 1. Versioning – Jun 3, 2014 (open)
• 1.1 Change process – Febr 6, 2015 (open)
• 1.1.1 Display of Violence – Febr 6, 2015 (merged & closed with comment on further adjustment, 2017-09-10)
• 1.1.1.1 Statement addressing the display of inappropriate content (PR) – Mar 25, 2015 (unmerged, closed)
  #2. Content (Behavior)
• 2. "Attempt collaboration before conflict." – Jun 3, 2014 (open)
• 2.1 Added a first draft for the spanish translation of the CoC. – Jun 3, 2014 (closed)
• 2.1.1 Changed writing of some phrases to be more gender inclusive. – Aug 8, 2014 (merged)
• 2.1.2 Expected behavior – May 19, 2015 (open)
• 2.1.2.1 In-Person meeting for future changes – Febr 18, 2016 (closed, meeting happened on 2017-09-10)
  #3. Content (Jokes)
• 3. “Jokes” Against Other Programming Languages – Jul 21, 2014 (open)
  #4. Licence
• 4. A note regarding a license for the BCoC? – Sept 8, 2014 (open)
• 4.1 Added license section to CoC – (PR) Sept 8, 2014 (closed)
  #5. Orga (Change process)
• 5. Change process – Febr 6, 2015 (open) – DUPLICATE
• 5.1 Display of Violence – Febr 6, 2015 (open) – DUPLICATE 2
• 5.2 Include statement addressing violent imagery (PR) Mar 2, 2015 (open)
• 5.2.1 Display of Violence – Febr 6, 2015 (open) – DUPLICATE 3
• 5.2.2 Statement addressing the display of inappropriate content – (PR) Mar 25, 2015 (unmerged, closed)
• 5.2.2.1 Display of Violence – Febr 6, 2015 (open) – DUPLICATE 4
• 5.2.2.2 Include statement addressing violent imagery (PR) Mar 2, 2015 (open) – DUPLICATE 2
• 5.3 Adjust language to be more gender neutral (PR) Jun 5, 2015 (merged)
  #6. Content (Violence Display)
• 6. Display of Violence – Febr 6, 2015 (open) – DUPLICATE 5
• 6.1 Include statement addressing violent imagery – (PR) Mar 2, 2015 – DUPLICATE 2
• 6.2 Statement addressing the display of inappropriate content – (PR) Mar 25, 2015 (unmerged, closed) – DUPLICATE 2
  #7. Content (Schools & Organizations)
• 7. Add organisations or schools as a separate group Febr 27, 2015 (open)
• 7.1 Display of Violence – Febr 6, 2015 (open) – DUPLICATE 6
  #8. Content (Gender)
• 8. Gendering in der deutschen Version – Febr 28, 2015 (open)
• 8.1 Adjust language to be more gender neutral – Jun 5, 2015 (PR) - DUPLICATE 2
• 8.2 In-Person meeting for future changes – Febr 18, 2016 (open) - DUPLICATE 3
  #9. Licence
• 9. What is the license for this work? – Apr 28, 2015 (open)
  #10. Content (Expected Behavior)
• 10. Expected Behavior – May 19, 2015 (open)
• 10.1 In-Person meeting for future changes – Febr 18, 2016 (open) - DUPLICATE 4
  #11. Content (Origin & Ability)
• 11. "Herkunft" und "Befähigung" – May 21, 2015 (open)
• 11.1 Adjust language to be more gender neutral – Jun 5, 2015 (PR) - DUPLICATE 3
• 11.2 Get professional expertise by foundations – May 23, 2015 (open)
• 11.2.1 Improvements to comprehensibility and extension of categories – May 23, 2015 (open)
• 11.2.1.1 Include statement addressing violent imagery – (PR) Mar 2, 2015 (open) – DUPLICATE 3
• 11.2.1.2 Add gender identity and expression – (PR) Nov 2, 2015 (open)
• 11.2.1.2.1 In-Person meeting for future changes – (PR) Febr 18, 2016 (open) - DUPLICATE 5
  #12. Content & Collaboration (Get Expertise)
• 12.2 Get professional expertise by foundations – May 23, 2015 (open) - DUPLICATE 2
  #13. Content (Authentic Behavior)
• 13. Remove authentic behaviour? – Jan 2, 2016 (open)
• 13.1 In-Person meeting for future changes – Febr 18, 2016 (open) - DUPLICATE 6
  #14. Content (CoC Short Version for Slides)
• 14. Short summary for slides – Febr 2016 (open)
  #15. Orga: In-Person-Meeting
• 15. In-Person meeting for future changes – Febr 18, 2016 (open) - DUPLICATE 6
  #16. PULL REQUESTS
• 16.1 Include statement addressing violent imagery (PR) Mar 2, 2015 (open) - DUPLICATE 4
• 16.2 Improvements to comprehensibility and extension of categories – May 23, 2015 (open) - DUPLICATE 2
• 16.3 Add gender identity and expression – (PR) Nov 2, 2015 (open) - DUPLICATE 2

This would enable entering a Mastodon or similar URL.

Hi just got the request to build on our Code of Conduct. Do we allow derived work? And can we add this to the repo? does MIT apply for example of Creative Commons?

Thanks to @alextewpin for reporting it (source)

Some letters in cyrillic are buggy :(

Example: the small letter c in the word Кодекс:

And the whole text looking not quite.. good.

Currently it is not easy for people outside of the team to know who they can address directly/privately or in mentions when they have specific/sensitive questions and concerns.

One of the improvement ideas we had is to make the maintainer team visible and addressable, for example by listing the team on the README file (or anywhere else).

We need a change process for our code of conduct.

When we want to add something, remove or hugely reformulate there are a couple of steps that need to be taken, this is an idea (can be improved) of what that probably entails:

• Formulate a change idea and probably a first version in English as a pull request
• Inform all involved parties (I guess most of all other meetups who signed this CoC) of the incoming addition and invite them to collaborate and discuss
• We need some method of finding an agreement or a point where we say, nah we do this and bump the version
• Afterwards we need to contact translators to add translations in our supported languages

What do we need to accomplish this?

• Versioning, see #7 we need to have all versions accessible
• List/contact information of translators (right now I know most of them personally, so it's not THAT important)
• A change process/idea for one (see above)
• easier accessible list of the emails of meetup organizers (just need to extract them from the json, we have that)

Input highly welcome.

From the community, for the community. For an open, welcoming, inclusive and steadily improving tech community.

Cheers,
Tobi

I really like this code of conduct, but I think the first paragraph of "expected behaviour" is quite weird:

Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.

What is authentic participation supposed to mean? And if someone is an introvert and does not like to participate in an active way, isn't that just fine as long as that person does not violate any other points of the CoC?

It is also noteworthy that the Unacceptable Behaviour section has negations of most of the expected behaviours, but it doesn't list "unauthentic" and "passive" behaviour.

I value clear writing and it seems to me that this phrase means well but adds little to the essence of the CoC.

I don't feel strongly about this and if there are others like it then I will not lobby any further for removal of the passage, but I think it would be an improvment to remove this passage.

@PragTob
cc @lauralindal @hagenburger @skade

Hey there, what is the purpose of these categories

usergroups
conferences

in the supporters.json when they are finally not displayed on the website? As far as I can see we currently don't have a proper order, right? Should we fix this?

In #59 gab es einen guten Einwand gegen die Worte "Herkunft" und Befähigung.

#59 (comment)

Wenn ich das jetzt richtig gelesen habe, ist der generelle Konsens, diese Worte zu ersetzen, auch in allen Übersetzungen, sofern notwendig.

Alternativen können hier diskutiert werden.

WIP issue

• See #232
• Add issues for all languages

Currently all our e-mails are displayed in clear, which is great for receiving spam...

Sorry all. The transfer of the domain wasn't as swift as I hoped it would be, so at the moment, berlincodeofconduct.org does not resolve.

I'm sorry. Looking into it.

As soon as it is live it should be tagged as v1.0.0 and included in the live version.

Hi @chastell, @lucaspinto, @10ko, @catalanojuan, @porras,

we changed some sizeable pieces of the CoC today, of which some need translator attendance.

These issues are labeled with "translation needed".

https://github.com/rubyberlin/code-of-conduct/pulls?utf8=%E2%9C%93&q=is%3Apr%20label%3A%22translation%20needed%22%20

Please leave a note on the issue and tick of the bullet point here once you checked the translations.

• Polish
• Spanish
• French
• Italian

Thanks for your efforts!

I'm not sure if this is necessary or not but I've seen it in other CoCs like:

https://us.pycon.org/2012/codeofconduct/
https://amsterdam2014.drupal.org/code-of-conduct

Both of them use Creative Commons Attribution 3.0. I'm opening this issue as I couldn't find any discussion on this matter in the repo.

I think it might be in favor of the use and distribution of it, but I'm no expert at all.

Hey,

i've started to work on a french version.

Coucou @fannivuniconnu @thegcat!

I need to emulate this doc and need to know how to adhere to the license.

@StephanSchmidt pointed out the often shown hate agains other programming languages within slides. Should we include that in our code of conduct?
https://twitter.com/codemonkeyism/status/491121132922486784

Right now the margin take up too much space so it doesn't look too good on mobile phones etc.:

The issue

There are many translations of the CoC (I'm not even talking cached versions, etc.), and sometimes translations are not quite up-to-date with the original.

How can we confidently enforce some rule on the level of 300-ppl European conference..

..while such rule itself highly depends on the language button you've clicked on?

The suggested solution

Let's introduce some sort of semantic versioning to the document. Let's say English (original) version would become 1.1, that means Russian version 1.0 should be updated soon. This is an explicit and transparent way of handling things.

This is a follow-up ticket for #98.

We want to insert a preambel to shortly explain the meaning, motivation and goals behind a CoC.

@schoolofma suggested in #42 to add schools and groups as a separate kind of entities.

I think that makes sense, even if we don't display it yet: if we're doing grouping, we shouldn't shoe-horn too many in the pre-existing groups.

We had the idea to start a wiki where we can put infos, for example:

• why a code of conduct is necessary for us
• how we organize usergroups & conferences to make them more inclusive
• term explanations & helpful links
• general examples how we handle/have handled some situations
• other documentation reasons

Happy to get feedback. :)

esp Speaker.

I got mentioned today that it's hard to fit the most important points of the CoC on a slide (e.g. for introductions).

Providing a short summary for slides is worthwhile.

Hi,

it seems that this issue tracker is not the place to get stuff done and some needs to be done.

Therefore, I propose we spend an evening on this thing to decided on some of the open, lingering issues and also make sure the current maintainers are properly introduced.

I propose the end of march for such a date. I would enjoy if some translators could join in (possibly via Skype/Hangouts)

Please mention open topics that can be covered in an evening in this thread. My list is:

• #81 ; #58
• #44
• #7
• #76

Best,
Florian

The ruby berlin homepage needs serious work, I know. But I think we should link the code of conduct there on the first page on a very prominent spot.

Hey :)

I have a few problems with the Expected Behavior section. I feel like the last bullet point is the only part I would mention here and remove the rest. Telling people how to behave specifically seems to be out of the scope of this code of conduct in general to me.

Here are things that I think are problematic with the other bullet points:

Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.

I don't think attendees should have to be active and authentic. It's totally cool to be passive as well. For many people this is also not a choice, but a personal limit. Brian Brennan actually describes why it is okay and normal to be a lurker in this talk. Authentic on the other hand to me also doesn't carry any meaning. What is it like to be authentic?

Exercise consideration and respect in your speech and actions.

Seems ok to me, but could be used by people for tone arguments

Attempt collaboration before conflict.

There is already an issue describing what is wrong with this: #8

Refrain from demeaning, discriminatory, or harassing behavior and speech.

Totally ok, but it's covered in the unacceptable behavior section.

Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.

This is quite important I think.

Would love to hear your opinions on this.

please be respectful to all patrons of these locations.

The use of "patron" immediately jumped out at me. It comes from Latin for "father" and is related to "paternalistic", "patriarchy" etc.

Maybe just use "visitors of these locations"?

http://en.wiktionary.org/wiki/patron#Etymology

Thanks to @catalanojuan, this is already started: https://docs.google.com/document/d/1v2vBT7VhSaV0cINWj-EdpuMe5X7fE7LeaJffWdU60rc/edit?usp=sharing

We should turn it into a pull request to discuss details over there.

I have a problem with this phrase. It can be seen as a handling instruction, which is not the scope of the code of conduct.

This has been rightfully criticized with other code of conducts, as it makes expectations on how the targets of a perceived code of conduct violations should react.

I would actually remove it or replace it by "value collaboration as a core value of our community" or similar.