furuhashilab / README

古橋研究室(古橋ゼミ)に興味のある学生は、最初に読んでください。これを熟読できていない学生は指導対象から外します。
http://furuhashilab.com/
Creative Commons Attribution 4.0 International
17 stars 3 forks source link

古橋研究室 行動規範 Code of Conduct #4

Open mapconcierge opened 5 years ago

mapconcierge commented 5 years ago

行動規範 v1.1

2019-11-11 updated

古橋研究室は、一億総伊能化社会の実現のために必要とされる様々な諸問題を解決し、世界中のすべての人々が地図を自由に利活用できる時代を作るべく学生と様々な方々と共に教育/研究を行っているゼミです。

我々は我々が企画・主催する全てのプロジェクト及びイベント参加者の方々を大切に思っており、参加者全員に楽しんで、充実した体験をして欲しいと思っています。 そのため、これらのプロジェクト及びイベントにおいて、参加者全員がその他の参加者に対して敬意と礼儀をもって参加することを求めています。

求められる行動を明確にするために、古橋研究室のプロジェクト及びイベントに参加する全ての代表者・学生・参加者・登壇者・出店者・主催者・ボランティアの方々は次の行動規範に合わせて行動することを求めています。そして、我々のプロジェクト及びイベント主催者はこの行動規範を実施します。


短いバージョン

古橋研究室のプロジェクト及びイベントはどの性別、性的指向、身体障害、外見、体型、人種や宗教であっても参加者全員にとってハラスメントが無いイベント体験を提供することに注力しています。どのような形のハラスメントも容認しません。

全てのコミュニケーションは様々な経歴をもつプロフェッショナルな参加者にとってふさわしい内容が求められます。我々のプロジェクト及びイベントで性的な言葉や画を用いたプレゼンテーションはふさわしくありません。

ハラスメントや性差別、人種差別や排他的な冗談はふさわしくないことを覚えていてください。

これらのルールに違反する参加者は、我々が主催するプロジェクト及びイベント管理者の独断によってそれらプロジェクト及びイベントから退出を求められることもあります。

全ての人にとって快適で、友好的な場を提供することへの協力に感謝いたします。


長いバージョン

ハラスメントとは性別、性的指向、身体障害、外見、体型、人種、宗教、公共の場での性的表現に関する侮辱的な発言、意図的な脅迫、ストーカー行為、付きまとい、嫌がらせな撮影、録音、録画、トークやその他イベントに対しての持続的な妨害、不適切な身体的接触や望まれない性的な注目等を意味します。

嫌がらせ行為を止めるように警告された参加者は直ぐに応じることが求められます。

言葉の選択も考えましょう。

性差別、人種差別や排他的な冗談は周りにいる人に対して侮辱的な発言になることもあるのを覚えていてください。侮辱的な冗談は古橋研究室のプロジェクト及びイベントにふさわしくなく、古橋研究室のプロジェクト及びイベントではどのような状況であっても容認はされません。

参加者が行動規範に反する行動を行った場合には、主催者は違反者を注意したり、返金無しでイベント・カンファレンスから退出させる等を含む主催者が必要と思ったどのような処置でも行えます。

連絡情報

ハラスメントを受けた場合、参加者のハラスメントを目撃した場合、その他気になる事を見た場合は遠慮なく古橋研究室のメンバーに伝えてください。

古橋研究室のメンバーは参加者が警備や警察への連絡、付き添いの提供や、その他ハラスメントを受けた参加者がイベントの参加中に安心して参加出来るよう、喜んでその手助けを行います。皆さまの参加を大切に思っています。

ライセンス

この行動規範の英語版は、Ada Initiative及びボランティアによって作成された Geek Feminism wiki 上のものをforkしたものです。元のCode of Conduct は Creative Commons Zeroライセンス で公開されています。

mapconcierge commented 5 years ago

http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy

==Introduction==

This is an example anti-harassment policy suitable for most open source, computing, or technology-related conferences. It may be adopted unchanged or tweaked to suit your conference.

Why have an official anti-harassment policy for your conference? First, it is necessary (unfortunately). Harassment at conferences is incredibly common - for example, see this [http://geekfeminism.wikia.com/index.php?title=Timeline_of_incidents timeline of sexist incidents in geek communities]. Second, it sets expectations for behavior at the conference. Simply having an anti-harassment policy can prevent harassment all by itself. Third, it encourages people to attend who have had bad experiences at other conferences. Finally, it gives conference staff instructions on how to handle harassment quickly, with the minimum amount of disruption or bad press for your conference.

We have collected some discussion about common concerns and questions surrounding adoption of an anti-harassment policy here:

; [http://geekfeminism.wikia.com/wiki/Anti-harassment_policy_resources Anti-harassment policy resources and HOWTO]

==Anti-harassment policy text==

Most conferences will want several different versions of an anti-harassment policy: a short, medium, and long version of the policy for public consumption, and an internal version spelling out implementation for use by the conference organizers and staff.

===Short public version===

This is a very short version that refers the reader to a longer version of the policy. Suitable for footers on announcement emails, web pages, news stories, etc.

: $CONFERENCE is dedicated to a harassment-free conference experience for everyone. Our anti-harassment policy can be found at:

: [URL for full anti-harassment policy]

===Medium public version===

This is a statement of the organizers' principles and sets expectations for the tone and style of the conference. Suitable for the conference web site and longer announcements.

: $CONFERENCE is dedicated to providing a harassment-free conference experience for everyone [, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age or religion [insert any other specific concerns here]]. We do not tolerate harassment of conference participants in any form. [Sexual language and imagery is not appropriate for any conference venue, including talks.] Conference participants violating these rules may be sanctioned or expelled from the conference [without a refund] at the discretion of the conference organizers. Our anti-harassment policy can be found at:

: [URL for full anti-harassment policy]

===Long public version===

This version focuses on specific instructions to the participants, with the goal of preventing harassment in the first place through education. Suitable for the conference web site and conference program material.

: [Insert medium public version of policy here.]

: Harassment includes, but is not limited to: : Verbal comments that reinforce social structures of domination [related to gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion, [your specific concern here]. : Sexual images in public spaces : Deliberate intimidation, stalking, or following  : Harassing photography or recording : Sustained disruption of talks or other events : Inappropriate physical contact : Unwelcome sexual attention : Advocating for, or encouraging, any of the above behaviour

: ====Enforcement====

: Participants asked to stop any harassing behavior are expected to comply immediately

: [Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.]

: If a participant engages in harassing behaviour, event organisers retain the right to take any actions to keep the event a welcoming environment for all participants. This includes warning the offender or expulsion from the conference [with no refund].

: Event organisers may take action to redress anything designed to, or with the clear impact of, disrupting the event or making the environment hostile for any participants.

: We expect participants to follow these rules at all event venues and event-related social activities. We think people should follow these rules outside event activities too! : ====Reporting==== :If someone makes you or anyone else feel unsafe or unwelcome, please report it as soon as possible. [Conference staff can be identified by t-shirts/special badges/head sets.] Harassment and other code of conduct violations reduce the value of our event for everyone. We want you to be happy at our event. People like you make our event a better place.

:You can make a report either personally or anonymously. ====Anonymous Report====

: You can make an anonymous report here [Wufoo form or similar that DOES NOT require an email address to submit.

: We can't follow up an anonymous report with you directly, but we will fully investigate it and take whatever action is necessary to prevent a recurrence.

====Personal Report==== :You can make a personal report by:

: Calling or messaging this phone number: [Phone number for reporting]. This phone number will be continuously monitored for the duration of the event. : Contacting a staff member, identified by STAFF badges, buttons, or shirts. :When taking a personal report, our staff will ensure you are safe and cannot be overheard. They may involve other event staff to ensure your report is managed properly. Once safe, we'll ask you to tell us about what happened. This can be upsetting, but we'll handle it as respectfully as possible, and you can bring someone to support you. You won't be asked to confront anyone and we won't tell anyone who you are.

:Our team will be happy to help you contact hotel/venue security, local law enforcement, local support services, provide escorts, or otherwise assist you to feel safe for the duration of the event. We value your attendance.

: [Email address for organizers] : [Phone number for conference security or organizers] : [Phone number for hotel/venue security] : [Local law enforcement] : [Local sexual assault hot line] : [Local emergency and non-emergency medical (e.g., urgent care, day clinic)] : [Local taxi company]

===Internal version for conference staff===

This version is intended for internal use by the conference staff. It defines an example enforcement policy that can be tweaked to suit your conference organization style.

: Warnings

: Any member of conference staff can issue a verbal warning to a participant that their behavior violates the conference's anti-harassment policy. Warnings should be reported to [insert email address/phone number/etc. here] as soon as practical. The report should include: : Identifying information (name/badge number) of the participant : The time you issued the warning : The behavior that was in violation : The approximate time of the behavior (if different than the time of warning) : The circumstances surrounding the incident : Your identity : Other people involved in the incident : [Your guideline here]

:Presentations

: Presentations or similar events should not be stopped for one-time gaffes or minor problems, although a member of conference staff should speak to the presenter afterward. However, staff should take immediate action to politely and calmly stop any presentation or event that repeatedly or seriously violates the anti-harassment policy. For example, simply say "I'm sorry, this presentation cannot be continued at the present time" with no further explanation.

:Taking reports

: When taking a report from someone experiencing harassment you should record what they say and reassure them they are being taken seriously, but avoid making specific promises about what actions the organizers will take. Ask for any other information if the reporter has not volunteered it (such as time, place) but do not pressure them to provide it if they are reluctant. Even if the report lacks important details such as the identity of the person taking the harassing actions, it should still be recorded and passed along to the appropriate staff member(s). If the reporter desires it, arrange for an escort by conference staff or a trusted person, contact a friend, and contact local law enforcement. Do not pressure the reporter to take any action if they do not want to do it. Respect the reporter's privacy by not sharing unnecessary details with others, especially individuals who were not involved with the situation or non-staff members. :: [Repeat information to gather when making a report here]

:Expulsion

: A participant may be expelled by the decision of any of the above listed entities for whatever reasons they deem sufficient. However, here are some general guidelines for when a participant should be expelled:

: A [first/second/third/seventeenth] offense resulting in a warning from staff : Continuing to harass after any "No" or "Stop" instruction : A pattern of harassing behavior, with or without warnings : A single serious offense (e.g., punching or groping someone) : A single obviously intentional offense (e.g., taking up-skirt photos) : [Your guideline here]

: Hotel/venue security and local authorities should be contacted when appropriate.

:: [Repeat conf/hotel/venue/law enforcement/hot line contact info here]

:Public statements

: As a general rule, conference staff should not make any public statements about the behavior of individual people during or after the conference.

: In general, consult with other staff members when possible but act when necessary.

==Conferences in which sex, pornography, racism, etc. are on-topic==

Some conferences are both welcoming to all genders and include discussion on topics which are blanket prohibited in the example anti-harassment policy. For example, conferences about supporting geek women or about social justice will necessarily have discussion about topics banned in the example policy, originally written for mainstream technical conferences. We have written an example addendum to the policy that allows discussion of these topics in a manner friendly to women and people in gender, sexual, and romantic minorities. '''We do not recommended including this addendum unless you have specific real-world examples of content that absolutely require discussion of these topics.''' See [http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Higher_risk_activities higher risk activities at conferences] for guidance on avoiding activities that increase the likelihood of harassment at your conference.

[[Conference anti-harassment/Example exception to policy]]

==License and attribution==

This policy is licensed under the [http://creativecommons.org/publicdomain/zero/1.0/ Creative Commons Zero license] . It is '''public domain''''', ''no credit and no open licencing of your version is required.

If you would like to optionally attribute it, you could use the below text and link to http://geekfeminism.wikia.com/wiki/Conference_anti-harassment:

: This anti-harassment policy is based on the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers.

This policy is based on several other policies, including the Ohio LinuxFest anti-harassment policy, written by Moose Finklestein and Beth Lynn Eicher, and the Con Anti-Harassment Project. Mary Gardiner, Valerie Aurora, Sarah Smith, and Donna Benjamin generalized the policies and added supporting material. Many members of LinuxChix, Geek Feminism and other groups contributed to this work.

== See also ==

mapconcierge commented 5 years ago

参考資料: GNUプロジェクト提唱者のリチャード・ストールマンによる「心あるコミュニケーションのガイドライン」が発表される https://gigazine.net/news/20181023-gnu-kind-communications-guidelines/?fbclid=IwAR2y8r8lsE_yAWN7EG03rG3x-q3Gfx0oVgrpZpafsdlclZqZIy15f_-LfN4


フリーソフトウェア運動の中心的存在でGNUプロジェクトを導く世界的に著名なプログラマーのリチャード・ストールマン氏が、GNUプロジェクトに参加するすべてのプログラマーに向けて、「他者を思いやる寛容的なコミュニケーションをとること」を求める「GNU Kind Communications Guidelines」を発表しました。ソフトウェア開発の舞台に存在する摩擦や軋轢はソフトウェアにとっての、ひいては世界にとっての大きな損失であり、他者を尊重することの大切さを説いたガイドラインは、ソフトウェア開発者だけでなく多くの人が読む価値のある提言になっています。

GNU Kind Communications Guidelines - GNU Project - Free Software Foundation https://www.gnu.org/philosophy/kind-communication.html

ストールマン氏によると、「非友好的で不快で拒絶的で、ときに過酷なコミュニケーションのパターンが存在することで、GNU開発への参加を避けてしまう開発者がいる」とのこと。性別、人種、宗教、文化的背景、政治的な見解など個人的な特徴や思想にかかわらず、GNUシステムの開発を進めることを奨励するために、ストールマン氏は「他者を尊重する心あるコミュニケーションが大切である」と考えています。そのため、GNU開発者には、以下の具体的な方法を実践して目標を達成してほしいと、開発者としてあるべき「心構え」や「姿勢」を説いています。

1:他人の「仕事」に敬意を払う たとえ他の参加者の発言に同意できない場合でも「彼らは誠実に投稿している」と仮定してください。コードやテキストがその「仕事」として提示されているときは、それを「仕事」として受け入れてください。「もしかすると間違っているのではないか?」という他人が犯したかもしれない疑いによって批判することはやめ、実際に何を話し、実際に何をしているかに固執してください。

2:その人自身に敬意を払う 「敬意をもって他の参加者を扱う方法」について考えてください。同意できない人に対しては特に、です。例えば、他の参加者に話しかけるときに、その人が提示している名前で呼びかけてみてください。性の多様性を尊重する上でも、(彼や彼女などの代名詞ではなく)その人の名前で呼びかけるのは重要です。

他の参加者に対して厳しすぎるトーンを向けるのはやめてください。特に、個人攻撃は避けるべきです。「発言」を批判し、決して「個人」を批判しているわけではないことを示すべきです。

3:批判にも敬意を払う 自分の意見に対する批判は、決して個人を攻撃するものではないと認識してください。誰かが攻撃してきたと感じたり、たとえ誰かが尊厳を攻撃したと感じたとしても、それに反撃しないでください。それは、言葉を拡大解釈した攻撃の連鎖を引き起こす傾向にあります。感情は感情として述べつつも、平和を求めてください。物事を鎮めるために、1時間あるいは1日経って怒りを取り除いてから、あらためて返答してみてください。

4:間違った人をフォローする 誰かが失敗したことをとがめられている場合、特にその人に対して親切にしてください。プログラミングとは多くの間違いを犯すことを意味しています。実際に私たちはみな間違いを犯しています。回帰テストが有用なのはそのせいです。誠実なプログラマーは間違いを犯して、その後に修正します。「完璧でないのは普通のこと」と示し、問題を修正し解決してくれるようフォローし、不完全な貢献に感謝を示してください。

5:テーマから外れない 議論の中で誰かが「脱線」しようとしているときは、今のトピックに焦点をあてて議論を進めてください。これは決して「脱線が悪い」ということではなく、また「議論が面白くない」ことを意味するものでもなく、「当面の問題に干渉してはならない」ということです。脱線については、別の場所で議論すべきということです。

6:終わりを明確にすることはない 議論を終わらせる「最後の言葉」を求める必要はありません。「もう返信が不要だ」と判断するタイミングを探してください。おそらく関係するポイントが明らかになっています。囲碁を知っているなら、勝負が決着した時に敗者に直接的な反応が必要ないことを知っているかもしれません。何も言わないで、代わりに別の場所に行ってもOKです。

また、すでに議論が終わっているのに不必要に議論を蒸し返すのはやめてください。それは、活動の進展を妨げる傾向があります。

7:不快にさせないことは説得につながる アイデアの表現の仕方について、他の参加者が不満をもっているなら、どうかそれに応じる努力をしてください。同じことを、他人に心地よいように伝える表現をみつけられるはずです。他人の怒りをかわないことは、他人を説得する可能性を高めるものです。

上記はGNU Kind Communications Guidelinesの中からGNUプロジェクトに固有の問題を除いた提言ですが、複数の人が協力して進めていくことが求められるあらゆるプロジェクトを成功に導くためのコツにもなっていそうです。

mapconcierge commented 5 years ago

OSGeo財団の Code of Conduct

https://www.osgeo.org/code_of_conduct/

FOSS4G Hokkaido による日本語訳

https://foss4g.hokkaido.jp/code-of-conduct/index.html

mapconcierge commented 4 years ago

Suggested Code of Conduct for OpenStreetMap Mailing Lists

https://github.com/osmlab/codes-of-conduct/blob/master/mailing_lists/code_of_conduct.md

In general:

Guideline Violations — 3 Strikes Method

The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who make our community suck.

  1. First occurrence: A moderator will remind the mailing list as a whole of this code of conduct and the specific inappropriate behavior.
  2. Second occurrence: We will send you a private message with a warning that any additional violations will result in removal from the community.
  3. Third occurrence: Depending on the violation, we may need to ban you from the mailing list.

Notes:

Contact [MODERATOR NAME(S) HERE] to report abuse or appeal violations. In the case of appeals, we know that mistakes happen, and we’ll work with you to come up with a fair solution if there has been a misunderstanding.

What is 'Harassment'?

Harassment includes:

Thoughtful mailing list behavior:

Remember, when you post to a community mailing list, you are, in effect, asking a large group of people to give you some of their time and attention — to download your message, read it, and potentially reply to it. It is simply polite to make sure your message is relevant to as many of the people receiving the message as possible. Many of the guidelines below stem from this basic principle.

OpenStreetMap Mailing Lists

You can find a current list of all of the OSM mailing lists here: https://lists.openstreetmap.org/listinfo

Stay on Topic

Avoid Cross-Posting

Keep It Short

More Posting Tips

Do Not Hijack Threads

Subscribers Only

Recipients

--

About this Code of Conduct:

The intention of this CoC is to help provide a safe, welcoming place for constructive discussion about OpenStreetMap and OpenStreetMap-related issues. It was forked by @pdxmele, @KathleenLD, @iandees, and @mvexel from the Puppet Community Guidelines, which itself gives credit to the Fedora Mailing List Guidelines, 01.org, and meego.com. We also used some elements from GeekFeminism.

If you are an OSM mailing list moderator and you would like to adopt this Code of Conduct for your list, all you need to do is:

  1. Put your name where it says [MODERATOR NAME(S) HERE], and post a copy of it on your mailing list subscription page.
  2. Send it to your current subscribers by posting an email to the list with a link, and letting them know that you will be enforcing it as moderator.
  3. Enforce it, and lean on other mailing list moderators and community leaders to help with questions and disputes.
  4. Let us know that you're using it by filing an issue -- we'll be assembling a list of the mailing lists that have adopted this Code of Conduct.
mapconcierge commented 4 years ago

MEMO

技術系イベントにおけるアンチハラスメントポリシーの効果について 2019-12-22 http://takahashim.hatenablog.com/entry/2019/12/22/145034