Skip to content

Commit

Permalink
feat: adding coc
Browse files Browse the repository at this point in the history
  • Loading branch information
martinheidegger committed Apr 15, 2024
1 parent 18eebb9 commit 7b4ba1f
Show file tree
Hide file tree
Showing 3 changed files with 277 additions and 1 deletion.
2 changes: 1 addition & 1 deletion components/SiteFooter.vue
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
<template>
<footer>
<p><span class="capitalize">Copyright</span> © {{ new Date().getFullYear() }} Osaka/Kyoto Web Designers and web developers meetup</p>
<p><span class="capitalize">Copyright</span> © {{ new Date().getFullYear() }} Osaka/Kyoto Web Designers and web developers meetup - <a href="/coc">Code of Conduct</a></p>
</footer>
</template>

Expand Down
150 changes: 150 additions & 0 deletions pages/coc-report.vue
Original file line number Diff line number Diff line change
@@ -0,0 +1,150 @@

<template>
<section>
<div class="coc-content">
<h1 class="coc-title">Code of Conduct - Reporting Guide</h1>
<div class="coc-description-container">
<p>
If you believe someone is violating <a href="/coc">the code of conduct</a>
we ask that you report it to the OWDDM・KWDDM organizer using the

Check warning on line 9 in pages/coc-report.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (OWDDM)

Check warning on line 9 in pages/coc-report.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (KWDDM)
<a href="mailto:owddm@proton.me">owddm@proton.me</a> email address.
</p>
<p>
All reports will be kept confidential. In some cases we may determine
that a public statement will need to be made. If that's the case, the
identities of all victims and reporters will remain confidential unless
those individuals instruct us otherwise.
</p>
<p>
If you believe anyone is in physical danger, please notify appropriate
law enforcement first.<br/>
If you are unsure what law enforcement agency is appropriate, please include
this in your report and we will attempt to notify them.
</p>
<p>
If you are unsure whether the incident is a violation, or whether the
space where it happened is covered by our code of conduct, we encourage
you to still report it.
</p>
<p>
We would much rather have a few extra reports where we decide to take
no action, than miss a report of an actual violation.
</p>
<p>
We do not look negatively on you if we find the incident is not a violation.
</p>
<p>
And knowing about incidents that are not violations, or happen outside
our spaces, can also help us to improve the Code of Conduct or the processes
surrounding it.
</p>
<h3>In your report please include:</h3>
<ul>
<li>Your contact info <em>(so we can get in touch with you if we need
to follow up)</em></li>
<li>Names <em>(real, nicknames, or pseudonyms)</em> of any individuals
involved. If there were other witnesses besides you, please try to include
them as well.
</li>
<li>When and where the incident occurred. Please be as specific as possible.</li>
<li>Your account of what occurred. If there is a publicly available record
(e.g. a mailing list archive or a public IRC logger) please include
a link and/or screenshot.
</li>
<li>Any extra context you believe existed for the incident.</li>
<li>If you believe this incident is ongoing.</li>
<li>Any other information you believe we should have.</li>
</ul>
<h3>What happens after you file a report?</h3>
<p>
We promise to acknowledge the issue with a reply within 72 hours
<em>(and will aim for much quicker than that)</em>.
</p>
<p>
The organizers will meet to review the incident and determine:
</p>
<ul>
<li>What happened.</li>
<li>Whether this event constitutes a code of conduct violation.</li>
<li>Who the bad actor was.</li>
<li>Whether this is an ongoing situation, or if there is a threat to anyone's
physical safety.</li>
<li>If this is determined to be an ongoing incident or a threat to physical
safety, the organizers' immediate priority will be to protect everyone
involved. This means we may delay an "official" response until we believe
that the situation has ended and that everyone is physically safe.
</li>
</ul>
<p>
The organizers will give their best effort responding to the situation
and responses may include:
</p>
<ul>
<li>Nothing <em>(if we determine no violation occurred)</em>.</li>
<li>A private reprimand from the organizers to the individual(s) involved.</li>
<li>A public reprimand.</li>
<li>An imposed vacation <em>(i.e. asking someone to "take a week off"
from Discord and skip the next meetup)</em>.</li>
<li>A permanent or temporary ban from some or all OWDDM・KWDDM spaces

Check warning on line 88 in pages/coc-report.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (OWDDM)

Check warning on line 88 in pages/coc-report.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (KWDDM)
<em>(Discord Chat, Meetups, etc.)</em>.</li>
<li>A request for a public or private apology.</li>
<li>A public incident report.</li>
</ul>
<p>
We'll respond as soon as we can to the person who filed the report with
either a resolution or an explanation of why the situation is not yet
resolved.
</p>
<p>
Futhermore, once we've determined our final action, we'll let them know
what action <em>(if any)</em> we'll be taking.
</p>
<p>
We'll take into account feedback from the reporter on the appropriateness
of our response, but we don't guarantee we'll act on it.
</p>
<h3>What if your report concerns a possible violation by the organizer?</h3>
<p>
If your report concerns the organizer, you may not feel comfortable sending
your report to the committee, as all members will see the report.
</p>
<p>
In that case, you can make a report directly to any or all other organizers.
</p>
<p>
The members you contact will respond to the issue, to the best of their
ability, in a group excluding the member(s) that the report concerns.
</p>
<h3>Reconsideration</h3>
<p>
Any of the parties directly involved or affected can request reconsideration
of the organizers’s decision.
</p>
<p>
To make such a request, contact the organizer using
<a href="mailto:owddm@proton.me">owddm@proton.me</a> with your request
and motivation and the organizer will review the case.
</p>
</div>
</div>
</section>
</template>

<style scoped>
.coc-content {
padding: var(--space) max(var(--space), env(safe-area-inset-right)) var(--space) max(var(--space), env(safe-area-inset-left));
}
.coc-title,
.coc-description-container > p,
.coc-description-container > h3,
.coc-description-container > ul > li {
margin: var(--space) 3rem 0 2rem;
line-height: normal;
}
.coc-content ul {
margin: var(--space) 0 0 0;
}
</style>
126 changes: 126 additions & 0 deletions pages/coc.vue
Original file line number Diff line number Diff line change
@@ -0,0 +1,126 @@
<template>
<section>
<div class="coc-content">
<h1 class="coc-title">Code of Conduct</h1>
<div class="coc-description-container">
<p>
The OWDDM・KWDDM community is made up of a mixture of professionals and

Check warning on line 7 in pages/coc.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (OWDDM)

Check warning on line 7 in pages/coc.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (KWDDM)
volunteers from all over the world, working on every aspect of the whole
- including mentorship, teaching, and connecting people.
</p>
<p>
Diversity is one of our huge strengths, but it can also lead to communication
issues and unhappiness. To that end, we have a few ground rules that we
ask people to adhere to. This code applies to anyone interacting in community
spaces equally, including organizing members.
</p>
<p>
This isn’t an exhaustive list of things that you can’t do. Rather, take
it in the spirit in which it’s intended - a guide to make it easier to
enrich all of us and the technical communities in which we participate.
</p>
<p>
This code of conduct applies to all spaces (real or digital) managed by
the OWDDM・KWDDM group. This includes but is not limited to the our physical

Check warning on line 24 in pages/coc.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (OWDDM)

Check warning on line 24 in pages/coc.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (KWDDM)
events, Discord Chat, Github, LinkedIn, and any other system created or
maintained by the group. In addition, violations of this code outside
these spaces may affect a person's ability to participate within them.
</p>
<p>
If you believe someone is violating the code of conduct, we ask that you
report it to <a href="mailto:owddm@proton.me">owddm@proton.me</a> and follow
the <a href="/coc-report">Reporting Guide</a>.
</p>
<ul>
<li><h4>Be friendly and patient.</h4></li>
<li><h4>Be welcoming.</h4>
<p>
We strive to be a community that welcomes and supports people of all
backgrounds and identities. This includes, but is not limited to members
of any race, ethnicity, culture, national origin, colour, immigration

Check warning on line 40 in pages/coc.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (colour)
status, social and economic class, educational level, sex, sexual orientation,
gender identity and expression, age, size, family status, political
belief, religion, and mental and physical ability.
</p>
</li>
<li><h4>Be considerate.</h4>
<p>
Your work will be used by other people, and you in turn will depend
on the work of others. Any decision you take will affect users and
colleagues, and you should take those consequences into account when
making decisions. Remember that we're a world-wide community, so you
might not be communicating in someone else's primary language.
</p>
</li>
<li>
<h4>Be respectful.</h4>
<p>
Not all of us will agree all the time, but disagreement is no excuse
for poor behavior and poor manners. We might all experience some frustration
now and then, but we cannot allow that frustration to turn into a personal
attack. It’s important to remember that a community where people feel
uncomfortable or threatened is not a productive one. Members of the
OWDDM・KWDDM community should be respectful when dealing with other

Check warning on line 63 in pages/coc.vue

View workflow job for this annotation

GitHub Actions / spellcheck

Unknown word (OWDDM)
members as well as with people outside the OWDDM・KWDDM community.
</p>
</li>
<li>
<h4>Be careful in the words that you choose.</h4>
<p>
We are a community of professionals, and we conduct ourselves professionally.
Be kind to others. Do not insult or put down other participants. Harassment
and other exclusionary behavior aren't acceptable. This includes, but
is not limited to:
</p>
<ul>
<li>Violent threats or language directed against another person.</li>
<li>Discriminatory jokes and language.</li>
<li>Posting sexually explicit or violent material.</li>
<li>Posting (or threatening to post) other people's personally identifying information ("doxing").</li>
<li>Personal insults, especially those using racist or sexist terms.</li>
<li>Unwelcome sexual attention.</li>
<li>Advocating for, or encouraging, any of the above behavior.</li>
<li>Repeated harassment of others. In general, if someone asks you to stop, then stop.</li>
</ul>
</li>
<li>
<h4>When we disagree, try to understand why.</h4>
<p>
Disagreements, both social and technical, happen all the time and
the OWDDM・KWDDM community is no exception. It is important that we
resolve disagreements and differing views constructively. Remember
that we’re different. The strength of the OWDDM・KWDDM community comes
from its varied community, people from a wide range of backgrounds.
Different people have different perspectives on issues. Being unable
to understand why someone holds a viewpoint doesn’t mean that they’re
wrong. Don’t forget that it is human to err and blaming each other
doesn’t get us anywhere. Instead, focus on helping to resolve issues
and learning from mistakes.
</p>
</li>
</ul>
<p>
Adapted from the <a href="https://web.archive.org/web/20141109123859/http://speakup.io/coc.html">Speak Up! project</a>.
</p>
</div>
</div>
</section>
</template>

<style scoped>
.coc-content {
padding: var(--space) max(var(--space), env(safe-area-inset-right)) var(--space) max(var(--space), env(safe-area-inset-left));
}
.coc-title,
.coc-description-container > p,
.coc-description-container > ul > li {
margin: var(--space) 3rem 0 2rem;
line-height: normal;
}
.coc-content ul {
margin: var(--space) 0 0 0;
}
</style>

0 comments on commit 7b4ba1f

Please sign in to comment.