From 38d2776e07836e01fc35c924a7814602eac17ef6 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Mon, 8 Apr 2024 12:41:44 +0300 Subject: [PATCH 1/8] Add PyCon US code of conduct --- README.md | 2 +- _layouts/{index.html => default.html} | 15 ++- code-of-conduct.md | 155 ++++++++++++++++++++++++++ enforcement-procedures.md | 116 +++++++++++++++++++ index.md | 15 ++- procedures-for-reporting-incidents.md | 83 ++++++++++++++ 6 files changed, 374 insertions(+), 12 deletions(-) rename _layouts/{index.html => default.html} (64%) create mode 100644 code-of-conduct.md create mode 100644 enforcement-procedures.md create mode 100644 procedures-for-reporting-incidents.md diff --git a/README.md b/README.md index be6eb20..dcb0a91 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ alt="Helsinki Python logo">

-# helsinki-python.github.io +# Helsinki Python https://helsinki-python.github.io diff --git a/_layouts/index.html b/_layouts/default.html similarity index 64% rename from _layouts/index.html rename to _layouts/default.html index e2fa184..1bb588c 100644 --- a/_layouts/index.html +++ b/_layouts/default.html @@ -15,7 +15,16 @@ type="image/x-icon" href="https://raw.githubusercontent.com/helsinki-python/logo/main/HelPy-200.png"> - -
{{ content }}
- + +
+
+ Helsinki Python logo +
+ {{ content }} +
+ diff --git a/code-of-conduct.md b/code-of-conduct.md new file mode 100644 index 0000000..02cfb4f --- /dev/null +++ b/code-of-conduct.md @@ -0,0 +1,155 @@ +# PyCon US Code of Conduct + +PyCon US is a community conference intended for networking and collaboration in the developer community. + +We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the conference and at all conference events. + +To make clear what is expected, all staff, attendees, speakers, exhibitors, organizers, and volunteers at any PyCon US event are required to conform to the following Code of Conduct, as set forth by the Python Software Foundation. Organizers will enforce this code throughout the event. + +## OUR COMMUNITY + +Members of the Python community are open, considerate, and respectful. Behaviors that reinforce these values contribute to a positive environment, and include: + +- Being open. Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise. +- Focusing on what is best for the community. We're respectful of the processes set forth in the community, and we work within them. +- Acknowledging time and effort. We're respectful of the volunteer efforts that permeate the Python community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. +- Being respectful of differing viewpoints and experiences. We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. +- Showing empathy towards other community members. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views. +- Being considerate. Members of the community are considerate of their peers -- other Python users. +- Being respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. +- Gracefully accepting constructive criticism. When we disagree, we are courteous in raising our issues. +- Using welcoming and inclusive language. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference. + +## OUR STANDARDS + +Every member of our community has the right to have their identity respected. The Python community is dedicated to providing a positive experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status. + +### INAPPROPRIATE BEHAVIOR + +Examples of unacceptable behavior by participants include: + +- Harassment of any participants in any form +- Deliberate intimidation, stalking, or following +- Logging or taking screenshots of online activity for harassment purposes +- Publishing others' private information, such as a physical or electronic address, without explicit permission +- Violent threats or language directed against another person +- Incitement of violence or harassment towards any individual, including encouraging a person to commit suicide or to engage in self-harm +- Creating additional online accounts in order to harass another person or circumvent a ban +- Sexual language and imagery in online communities or in any conference venue, including talks +- Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that hold others up for ridicule +- Excessive swearing +- Unwelcome sexual attention or advances +- Unwelcome physical contact, including simulated physical contact (eg, textual descriptions like "hug" or "backrub") without consent or after a request to stop +- Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others +- Sustained disruption of online community discussions, in-person presentations, or other in-person events +- Continued one-on-one communication after requests to cease +- Other conduct that is inappropriate for a professional audience including people of many different backgrounds + +Community members asked to stop any inappropriate behavior are expected to comply immediately. + +### WEAPONS POLICY + +No weapons are allowed at PyCon US or Python Software Foundation events. Weapons include but are not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. + +### CONSEQUENCES + +If a participant engages in behavior that violates this code of conduct, the Python community Code of Conduct team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behavior is listed in the [Enforcement Procedures](Enforcement-Procedures). + +Thank you for helping make this a welcoming, friendly community for everyone. + +## SCOPE + +### PSF/PYCON EVENTS + +This Code of Conduct applies to the following people at PyCon: + +- staff +- PyCon US and Python Software Foundation board members +- speakers +- panelists +- tutorial or workshop leaders +- poster presenters +- people invited to meetings or summits +- exhibitors +- organizers +- volunteers +- all attendees + +The Code of Conduct applies in official venue event spaces, including: + +- exhibit hall or vendor tabling area +- panel and presentation rooms +- hackathon or sprint rooms +- tutorial or workshop rooms +- poster session rooms +- summit or meeting rooms +- staff areas +- con suite +- meal areas +- party suites +- walkways, hallways, elevators, and stairs that connect any of the above spaces + +The Code of Conduct applies to interactions with official event accounts on social media spaces and phone applications, including: + +- comments made on official conference phone apps +- comments made on event video hosting services +- comments made on the official event hashtag or panel hashtags + +Event organizers will enforce this code throughout the event. + +### PSF/PYCON ONLINE SPACES + +This Code of Conduct applies to the following online spaces: + +- The [PyCon US site](https://us.pycon.org/) +- Any other online space administered by PyCon US or the Python Software Foundation + +This Code of Conduct applies to the following people in official PyCon US or Python Software Foundation online spaces: + +- admins of the online space +- maintainers +- reviewers +- contributors +- all community members + +The PyCon US Code of Conduct work group will receive and evaluate incident reports from the online communities listed above. The PyCon US Code of Conduct work group will work with online community administrators/moderators to suggest actions to take in response to a report. In cases where the administrators/moderators disagree on the suggested resolution for a report, the PyCon US Code of Conduct work group may choose to notify the Python Software Foundation Code of Conduct work group or the Python Software Foundation board. + +## CONTACT INFORMATION + +If you believe that someone is violating the code of conduct, or have any other concerns, please contact a member of the event staff immediately. They can be reached by emailing which is monitored by Deb Nicholson, Łukasz Langa, Olivia Sauls and Ee Durbin. + +In case of a conflict of interest, you can individually contact: + +- Ee Durbin + - Director of Infrastructure + - +- Olivia Sauls + - Program Director + - + +Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration of the conference. We value your attendance. + +## PROCEDURE FOR HANDLING INCIDENTS + +[Procedure For Reporting Code of Conduct Incidents](Procedures-for-Reporting-Incidents) + +[Enforcement Procedures](Enforcement-Procedures) + +## LICENSE + +This Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](https://creativecommons.org/licenses/by-sa/3.0/). + +## ATTRIBUTIONS + +This Code of Conduct was forked from the example policy from the [Geek Feminism wiki, created by the Ada Initiative and other volunteers](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy), which is under a [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). + +Additional new language and modifications were created by Sage Sharp of [Otter Tech](https://otter.technology/code-of-conduct-training/). + +Language was incorporated from the following Codes of Conduct: + +- [Affect Conf Code of Conduct](https://affectconf.com/coc/), licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/). +- [Contributor Covenant version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct), licensed [Creative Commons Attribution 4.0 License](https://github.com/ContributorCovenant/contributor_covenant/blob/master/LICENSE.md). +- [Django Project Code of Conduct](https://www.djangoproject.com/conduct/), licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). +- [LGBTQ in Tech Slack Code of Conduct](https://lgbtq.technology/coc.html), licensed under a [Creative Commons Zero License](https://creativecommons.org/publicdomain/zero/1.0/). +- [PyCon US 2018 Code of Conduct](https://us.pycon.org/2018/about/code-of-conduct/), licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). +- [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html) diff --git a/enforcement-procedures.md b/enforcement-procedures.md new file mode 100644 index 0000000..902eebf --- /dev/null +++ b/enforcement-procedures.md @@ -0,0 +1,116 @@ +# PyCon US Code of Conduct Enforcement Procedures + +This document summarizes the procedures the PyCon US staff uses to enforce the Code of Conduct. + +### Summary of processes + +When the work group receives a report of a possible Code of Conduct violation, it will: + +1. Acknowledge the receipt of the report. +2. Evaluate conflicts of interest. +3. Call a meeting of Code of Conduct responders who do not have a conflict of interest. +4. Evaluate the reported incident. +5. Propose a behavioral modification plan. +6. Propose consequences for the reported behavior. +7. Vote on behavioral modification plan and consequences for the reported person. +8. Contact online community administrators/moderators to approve the behavioral modification plan and consequences. +9. Follow up with the reported person. +10. Decide further responses. +11. Follow up with the reporter. + +### Acknowledge the report + +Reporters should receive an emailed acknowledgment of the receipt of their report within 24 hours. + +### Conflict of interest policy + +Examples of conflicts of interest include: + +- The reporter or reported person is your manager +- You have a romantic or platonic relationship with either the reporter or the reported person. It's fine to participate if they are an acquaintance. +- The reporter or reported person is your metamour. (This is a term used in the poly community; the short definition is [here](https://www.urbandictionary.com/define.php?term=Metamour), and a longer description is [here](https://solopoly.net/2012/09/29/whats-a-metamour-on-my-terms/)). +- The reporter or reported person is your family member +- The reporter or reported person is your direct client +- The reporter or reported person is someone you work closely with. This could be someone on your team or someone who works on the same project as you. +- The reporter or reported person is a maintainer who regularly reviews your contributions + +Committee members do not need to state why they have a conflict of interest, only that one exists. Other work group members should not ask why the person has a conflict of interest. + +Anyone who has a conflict of interest will remove themselves from the discussion of the incident, and recuse themselves from voting on a response to the report. + +### Evaluating a report + +#### JURISDICTION + +- *Is this a Code of Conduct violation?* Is this behavior on our list of inappropriate behavior? Is it borderline inappropriate behavior? Does it violate our community norms? +- *Did this occur in a space that is within our Code of Conduct's scope?* If the incident occurred outside the community, but a community member's mental health or physical safety may be negatively impacted if no action is taken, the incident may be in scope. Private conversations in community spaces are also in scope. + +#### IMPACT + +- *Did this incident occur in a private conversation or in a public space?* Incidents that all community members can see will have more negative impact. +- *Does this behavior negatively impact a marginalized group in our community?* Is the reporter a person from a marginalized group in our community? How is the reporter being negatively impacted by the reported person's behavior? Are members of the marginalized group likely to disengage with the community if no action was taken on this report? +- *Does this incident involve a community leader?* Community members often look up to community leaders to set the standard of acceptable behavior. + +#### RISK + +- *Does this incident include sexual harassment?* +- *Does this pose a safety risk?* Does the behavior put a person's physical safety at risk? Will this incident severely negatively impact someone's mental health? +- *Is there a risk of this behavior being repeated?* Does the reported person understand why their behavior was inappropriate? Is there an established pattern of behavior from past reports? + +Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact. + +### Propose a behavioral modification plan + +The event staff will determine a concrete behavioral modification plan that ensures the inappropriate behavior is not repeated. The event staff will also discuss what actions may need to be taken if the reported person does not agree to the behavioral modification plan. + +What follows are examples of possible behavioral modification plans for incidents that occur in online spaces under the scope of this Code of Conduct. This behavioral modification list is not inclusive, and the event staff reserves the right to take any action it deems necessary. + +- Requiring that the reported person not use specific language +- Requiring that the reported person not join in on specific types of discussions +- Requiring that the reported person not send private messages to a community member +- Requiring that the reported person not join specific communication channels +- Removing the reported person from administrator or moderator rights to community infrastructure +- Removing a volunteer from their duties and responsibilities +- Removing a person from leadership of relevant organizations +- Removing a person from membership of relevant organizations + +### Propose consequences + +What follows are examples of possible consequences to an incident report. This consequences list is not inclusive, and the event staff reserves the right to take any action it deems necessary. + +Possible private responses to an incident include: + +- Nothing, if the behavior was determined to not be a Code of Conduct violation +- A verbal or emailed warning +- A final warning +- Temporarily removing the reported person from the online community +- Permanently removing the reported person from the online community +- Publishing an account of the incident + +### Follow up with the reported person + +The event staff will work with online community administrators/moderators to draft a response to the reported person. The email should contain: + +- A description of the person's behavior in neutral language +- The negative impact of that behavior +- A concrete behavioral modification plan +- Any consequences of their behavior + +The work group should not state who reported this incident. They should attempt to anonymize any identifying information from the report. The reported person should be discouraged from contacting the reporter to discuss the report. If they wish to apologize to the reporter, the work group can accept the apology on behalf of the reporter. + +Decide further responses + +If the reported person provides additional context, the event staff may need to re-evaluate the behavioral modification plan and consequences. + +### Follow up with the reporter + +A person who makes a report should receive a follow up email stating what action was taken in response to the report. If the work group decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation. Reports that are not made in good faith (such as "reverse sexism" or "reverse racism") may receive no response. + +The follow up email should be sent no later than one week after the receipt of the report. If deliberation or follow up with the reported person takes longer than one week, the work group should send a status email to the reporter. + +Attribution + +- The [PyCon US Code of Conduct](../) is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). +- Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)" is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/) +- Audrey Eschright of [Safety First PDX](http://safetyfirstpdx.org/) provided the impact vs risk assessment framework, which is licensed under a [Creative Commons Attribution Share-Alike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/)by Audrey Eschright of [Safety First PDX](http://safetyfirstpdx.org/) +- [Code of Conduct template](https://github.com/sagesharp/code-of-conduct-template/) was created by [Otter Tech](https://otter.technology/code-of-conduct-training) and is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/) diff --git a/index.md b/index.md index b7258c4..0b8bdff 100644 --- a/index.md +++ b/index.md @@ -1,18 +1,13 @@ --- -layout: index +layout: default title: Helsinki Python --- -
- -

Helsinki Python

+# Helsinki Python ## About -A local usergroup for the [Uusimaa](https://en.wikipedia.org/wiki/Uusimaa) +A local usergroup for the [Greater Helsinki](https://en.wikipedia.org/wiki/Greater_Helsinki) region meeting up roughly every month. - [Join on meetup.com](https://www.meetup.com/helpy-meetups/) @@ -33,3 +28,7 @@ region meeting up roughly every month. - 3rd April 2024 - [April Helsinki Python meetup - Wolt x Aiven](https://www.meetup.com/helpy-meetups/events/299649951/) + +## See also + +- [Code of Conduct](/code-of-conduct) diff --git a/procedures-for-reporting-incidents.md b/procedures-for-reporting-incidents.md new file mode 100644 index 0000000..3f2e36d --- /dev/null +++ b/procedures-for-reporting-incidents.md @@ -0,0 +1,83 @@ +# PyCon US Procedures for Reporting Code of Conduct Incidents + +If you believe someone is in physical danger, including from themselves, the most important thing is to get that person help. Please contact the appropriate crisis number, non-emergency number, or police number. If you are a PyCon US attendee, you can consult with a volunteer or staff member to help find an appropriate number. + +If you believe someone has violated the [PyCon US Code of Conduct](..), we encourage you to report it. If you are unsure whether the incident is a violation, or whether the space where it happened is covered by the Code of Conduct, we encourage you to still report it. We are fine with receiving reports where we decide to take no action for the sake of creating a safer space. + +If you find that you need to make a report, and you cannot find the appropriate Code of Conduct reporting contact, you may report to the PyCon US Code of Conduct email alias below. PyCon US event staff will handle your report. If this happens, please also mention that you could not find specific reporting information so that we can improve. + +*General reporting procedure:* + +The best way to contact the PyCon US Code of Conduct event staff is by email at . The members of the PyCon US event staff who monitor this account are: + +- Deb Nicholson +- Łukasz Langa +- Olivia Sauls +- Ee Durbin + +In the event of a conflict of interest, you may directly contact any of the lead incident responders: + +- Ee Durbin + - Python Software Foundation - Director of Infrastructure + - +- Olivia Sauls + - Python Software Foundation - Program Director + - + +REPORT DATA +----------- + +When you make a report via email or phone, please include: + +- Your contact info (so we can get in touch with you if we need to follow up) +- Date and time of the incident +- Location of incident +- Whether the incident is ongoing +- Description of the incident +- Identifying information of the reported person: name, physical appearance, height, clothing, voice accent, identifying badge information such as company name, ribbons, or badge number +- Additional circumstances surrounding the incident +- Other people involved in or witnesses to the incident and their contact information or description + +Please provide as much information as possible. + +CONFIDENTIALITY +--------------- + +All reports will be kept confidential. When we discuss incidents with people who are reported, we will anonymize details as much as we can to protect reporter privacy. + +However, some incidents happen in one-on-one interactions, and even if the details are anonymized, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, please note those in your report. We still encourage you to report, so that we can support you while keeping our conference attendees safe. In some cases, we can compile several anonymized reports into a pattern of behavior, and take action on that pattern. + +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. + +REPORT HANDLING PROCEDURE +------------------------- + +When you make a report to an incident responder, they will gather information about the incident according to the [Procedure For Incident Response](../Enforcement-Procedures). + +After an incident responder takes the report, they will immediately consult with the PyCon US event staff, unless there is a conflict of interest, in which case any non-interested parties will be contacted. + +If the incident is ongoing and needs to be immediately addressed, any lead incident responder may take appropriate action to ensure the safety of everyone involved. If the situation requires it, this may take the form of a referral to an appropriate non-PyCon US agency, including the local police. PyCon US is not equipped to handle emergency situations. + +If the incident is less urgent, the report will be discussed by the event staff, who will meet to determine an appropriate response. Examples of possible incident responses are outlined in the [Procedure For Incident Response](../Enforcement-Procedures). + +Before any large in-person gathering conference, staff will have a mandatory meeting where incident response procedures will be outlined. After the conference, all incident responders will attend a debriefing session with the lead responders to discuss all incidents and determine any necessary follow-up actions. + +FOLLOWING UP WITH REPORTERS +--------------------------- + +Within one week of an incident report, a member of the event staff, or one of the lead responders, will follow up with the person who made the report and provided their contact information. The follow up may include: + +- An acknowledgment that the Code of Conduct responders discussed the situation +- Whether or not the report was determined to be a violation of the Code of Conduct +- What actions (if any) were taken to correct the reported behavior + +In some cases, the lead responders may need to ask additional questions about the incident in order to identify the reported person. + +CONFLICTS OF INTEREST +--------------------- + +If an incident responder has a conflict of interest for a report, they will recuse themselves from the discussion and handling of the incident. The incident documentation will not be available to them, and they will excuse themselves from any conversations involving handling the incident. + +Should more than two of the PyCon US lead incident responders need to recuse themselves, another PyCon US staff member will step in as a temporary lead incident responder. + +This procedure was adapted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)", the [Django Project reporting guidelines](https://www.djangoproject.com/conduct/reporting/) (CC BY 3.0), with additions by [Otter Tech](https://otter.technology/). From 5d41232bb68b51225349f870607218baaab1ddcd Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Mon, 8 Apr 2024 16:16:05 +0300 Subject: [PATCH 2/8] PyCon US -> Helsinki Python --- code-of-conduct.md | 122 +++++++++++++------------- enforcement-procedures.md | 90 +++++++++---------- procedures-for-reporting-incidents.md | 78 ++++++++-------- 3 files changed, 142 insertions(+), 148 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 02cfb4f..45012c2 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -1,32 +1,37 @@ -# PyCon US Code of Conduct +--- +layout: default +title: Helsinki Python - Code of conduct +--- -PyCon US is a community conference intended for networking and collaboration in the developer community. +# Code of conduct -We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the conference and at all conference events. +Helsinki Python events are intended for networking and collaboration in the developer community. -To make clear what is expected, all staff, attendees, speakers, exhibitors, organizers, and volunteers at any PyCon US event are required to conform to the following Code of Conduct, as set forth by the Python Software Foundation. Organizers will enforce this code throughout the event. +We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees at all Helsinki Python events. -## OUR COMMUNITY +To make clear what is expected, all staff, attendees, speakers, exhibitors, organisers, and volunteers at any Helsinki Python event are required to conform to the following Code of Conduct, as set forth by the Python Software Foundation. Organisers will enforce this code throughout the event. -Members of the Python community are open, considerate, and respectful. Behaviors that reinforce these values contribute to a positive environment, and include: +### Our community -- Being open. Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise. -- Focusing on what is best for the community. We're respectful of the processes set forth in the community, and we work within them. -- Acknowledging time and effort. We're respectful of the volunteer efforts that permeate the Python community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. -- Being respectful of differing viewpoints and experiences. We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. -- Showing empathy towards other community members. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views. -- Being considerate. Members of the community are considerate of their peers -- other Python users. -- Being respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. -- Gracefully accepting constructive criticism. When we disagree, we are courteous in raising our issues. -- Using welcoming and inclusive language. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference. +Members of the Python community are open, considerate, and respectful. Behaviours that reinforce these values contribute to a positive environment, and include: -## OUR STANDARDS +- **Being open.** Members of the community are open to collaboration. +- **Focusing on what is best for the community.** We're respectful of the processes set forth in the community, and we work within them. +- **Acknowledging time and effort.** We're respectful of the volunteer efforts that permeate the Python community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. +- **Being respectful of differing viewpoints and experiences.** We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. +- **Showing empathy towards other community members.** We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views. +- **Being considerate.** Members of the community are considerate of their peers -- other Python users. +- **Being respectful.** We're respectful of others, their positions, their skills, their commitments, and their efforts. +- **Gracefully accepting constructive criticism.** When we disagree, we are courteous in raising our issues. +- **Using welcoming and inclusive language.** We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference. + +### Our standards Every member of our community has the right to have their identity respected. The Python community is dedicated to providing a positive experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status. -### INAPPROPRIATE BEHAVIOR +#### Inappropriate behaviour -Examples of unacceptable behavior by participants include: +Examples of unacceptable behaviour by participants include: - Harassment of any participants in any form - Deliberate intimidation, stalking, or following @@ -35,7 +40,7 @@ Examples of unacceptable behavior by participants include: - Violent threats or language directed against another person - Incitement of violence or harassment towards any individual, including encouraging a person to commit suicide or to engage in self-harm - Creating additional online accounts in order to harass another person or circumvent a ban -- Sexual language and imagery in online communities or in any conference venue, including talks +- Sexual language and imagery in online communities or in any event venue, including talks - Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that hold others up for ridicule - Excessive swearing - Unwelcome sexual attention or advances @@ -45,33 +50,32 @@ Examples of unacceptable behavior by participants include: - Continued one-on-one communication after requests to cease - Other conduct that is inappropriate for a professional audience including people of many different backgrounds -Community members asked to stop any inappropriate behavior are expected to comply immediately. +Community members asked to stop any inappropriate behaviour are expected to comply immediately. -### WEAPONS POLICY +#### Weapons policy -No weapons are allowed at PyCon US or Python Software Foundation events. Weapons include but are not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. +No weapons are allowed at Helsinki Python events. Weapons include but are not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. -### CONSEQUENCES +#### Consequences -If a participant engages in behavior that violates this code of conduct, the Python community Code of Conduct team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behavior is listed in the [Enforcement Procedures](Enforcement-Procedures). +If a participant engages in behaviour that violates this code of conduct, the Helsinki Python team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behaviour is listed in the [Enforcement Procedures](enforcement-procedures). Thank you for helping make this a welcoming, friendly community for everyone. -## SCOPE +### Scope -### PSF/PYCON EVENTS +#### Helsinki Python events -This Code of Conduct applies to the following people at PyCon: +This Code of Conduct applies to the following people at Helsinki Python events: - staff -- PyCon US and Python Software Foundation board members - speakers - panelists - tutorial or workshop leaders - poster presenters - people invited to meetings or summits - exhibitors -- organizers +- organisers - volunteers - all attendees @@ -84,27 +88,26 @@ The Code of Conduct applies in official venue event spaces, including: - poster session rooms - summit or meeting rooms - staff areas -- con suite - meal areas - party suites - walkways, hallways, elevators, and stairs that connect any of the above spaces The Code of Conduct applies to interactions with official event accounts on social media spaces and phone applications, including: -- comments made on official conference phone apps +- comments made on official event phone apps - comments made on event video hosting services - comments made on the official event hashtag or panel hashtags -Event organizers will enforce this code throughout the event. +Event organisers will enforce this code throughout the event. -### PSF/PYCON ONLINE SPACES +### Helsinki Python online spaces This Code of Conduct applies to the following online spaces: -- The [PyCon US site](https://us.pycon.org/) -- Any other online space administered by PyCon US or the Python Software Foundation +- The [Helsinki Python site](https://helsinki-python.github.io) +- Any other online space administered by Helsinki Python -This Code of Conduct applies to the following people in official PyCon US or Python Software Foundation online spaces: +This Code of Conduct applies to the following people in official Helsinki Python online spaces: - admins of the online space - maintainers @@ -112,44 +115,37 @@ This Code of Conduct applies to the following people in official PyCon US or Pyt - contributors - all community members -The PyCon US Code of Conduct work group will receive and evaluate incident reports from the online communities listed above. The PyCon US Code of Conduct work group will work with online community administrators/moderators to suggest actions to take in response to a report. In cases where the administrators/moderators disagree on the suggested resolution for a report, the PyCon US Code of Conduct work group may choose to notify the Python Software Foundation Code of Conduct work group or the Python Software Foundation board. +The Helsinki Python Code of Conduct work group will receive and evaluate incident reports from the online communities listed above. The Helsinki Python Code of Conduct work group will work with online community administrators/moderators to suggest actions to take in response to a report. -## CONTACT INFORMATION +### Contact information -If you believe that someone is violating the code of conduct, or have any other concerns, please contact a member of the event staff immediately. They can be reached by emailing which is monitored by Deb Nicholson, Łukasz Langa, Olivia Sauls and Ee Durbin. +If you believe that someone is violating the code of conduct, or have any other concerns, please contact an organiser immediately. They can be reached by emailing which is monitored by +Cal Paterson, Hugo van Kemenade, Jerry Pussinen and Sami Lehtinen. In case of a conflict of interest, you can individually contact: -- Ee Durbin - - Director of Infrastructure - - -- Olivia Sauls - - Program Director - - +- TODO + - Organiser + - +- TODO + - Organiser + - -Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration of the conference. We value your attendance. +Event organisers and staff will be happy to help participants contact venue security or local law enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration of the event. We value your attendance. -## PROCEDURE FOR HANDLING INCIDENTS +### Procedure for handling incidents -[Procedure For Reporting Code of Conduct Incidents](Procedures-for-Reporting-Incidents) +- [Procedure for reporting code of conduct incidents](/procedures-for-reporting-incidents) -[Enforcement Procedures](Enforcement-Procedures) +- [Enforcement procedures](/enforcement-procedures) -## LICENSE +### License This Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](https://creativecommons.org/licenses/by-sa/3.0/). -## ATTRIBUTIONS - -This Code of Conduct was forked from the example policy from the [Geek Feminism wiki, created by the Ada Initiative and other volunteers](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy), which is under a [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). - -Additional new language and modifications were created by Sage Sharp of [Otter Tech](https://otter.technology/code-of-conduct-training/). - -Language was incorporated from the following Codes of Conduct: +### Attributions -- [Affect Conf Code of Conduct](https://affectconf.com/coc/), licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/). -- [Contributor Covenant version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct), licensed [Creative Commons Attribution 4.0 License](https://github.com/ContributorCovenant/contributor_covenant/blob/master/LICENSE.md). -- [Django Project Code of Conduct](https://www.djangoproject.com/conduct/), licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). -- [LGBTQ in Tech Slack Code of Conduct](https://lgbtq.technology/coc.html), licensed under a [Creative Commons Zero License](https://creativecommons.org/publicdomain/zero/1.0/). -- [PyCon US 2018 Code of Conduct](https://us.pycon.org/2018/about/code-of-conduct/), licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). -- [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html) +This Code of Conduct is forked from the +[PyCon US Code of Conduct](https://policies.python.org/us.pycon.org/code-of-conduct/) +which details the sources of its language, and with similar edits as the +[Boston Python Code of Conduct](https://about.bostonpython.com/code-of-conduct). diff --git a/enforcement-procedures.md b/enforcement-procedures.md index 902eebf..bb1e93a 100644 --- a/enforcement-procedures.md +++ b/enforcement-procedures.md @@ -1,69 +1,74 @@ -# PyCon US Code of Conduct Enforcement Procedures +--- +layout: default +title: Helsinki Python - Code of conduct enforcement procedures +--- -This document summarizes the procedures the PyCon US staff uses to enforce the Code of Conduct. +## Code of conduct enforcement procedures -### Summary of processes +This document summarises the procedures the Helsinki Python organisers uses to enforce the Code of Conduct. -When the work group receives a report of a possible Code of Conduct violation, it will: +#### Summary of processes + +When the responders receive a report of a possible Code of Conduct violation, it will: 1. Acknowledge the receipt of the report. 2. Evaluate conflicts of interest. 3. Call a meeting of Code of Conduct responders who do not have a conflict of interest. 4. Evaluate the reported incident. -5. Propose a behavioral modification plan. -6. Propose consequences for the reported behavior. -7. Vote on behavioral modification plan and consequences for the reported person. -8. Contact online community administrators/moderators to approve the behavioral modification plan and consequences. +5. Propose a behavioural modification plan. +6. Propose consequences for the reported behaviour. +7. Vote on behavioural modification plan and consequences for the reported person. +8. Contact online community administrators/moderators to approve the behavioural modification plan and consequences. 9. Follow up with the reported person. 10. Decide further responses. 11. Follow up with the reporter. -### Acknowledge the report +#### Acknowledge the report Reporters should receive an emailed acknowledgment of the receipt of their report within 24 hours. -### Conflict of interest policy +#### Conflict of interest policy Examples of conflicts of interest include: - The reporter or reported person is your manager - You have a romantic or platonic relationship with either the reporter or the reported person. It's fine to participate if they are an acquaintance. -- The reporter or reported person is your metamour. (This is a term used in the poly community; the short definition is [here](https://www.urbandictionary.com/define.php?term=Metamour), and a longer description is [here](https://solopoly.net/2012/09/29/whats-a-metamour-on-my-terms/)). +- The reporter or reported person is your metamour. (This is a term used in the poly community; the short definition is [here](https://www.urbandictionary.com/define.php?term=Metamour), and a longer description is [here](https://solopoly.net/2012/09/29/whats-a-metamour-on-my-terms/).) - The reporter or reported person is your family member - The reporter or reported person is your direct client - The reporter or reported person is someone you work closely with. This could be someone on your team or someone who works on the same project as you. - The reporter or reported person is a maintainer who regularly reviews your contributions -Committee members do not need to state why they have a conflict of interest, only that one exists. Other work group members should not ask why the person has a conflict of interest. +Responders do not need to state why they have a conflict of interest, only that one exists. Other responders should not ask why the person has a conflict of interest. Anyone who has a conflict of interest will remove themselves from the discussion of the incident, and recuse themselves from voting on a response to the report. -### Evaluating a report +#### Evaluating a report -#### JURISDICTION +##### Jurisdiction -- *Is this a Code of Conduct violation?* Is this behavior on our list of inappropriate behavior? Is it borderline inappropriate behavior? Does it violate our community norms? +- *Is this a Code of Conduct violation?* Is this behaviour on our list of inappropriate behaviour? Is it borderline inappropriate behaviour? Does it violate our community norms? - *Did this occur in a space that is within our Code of Conduct's scope?* If the incident occurred outside the community, but a community member's mental health or physical safety may be negatively impacted if no action is taken, the incident may be in scope. Private conversations in community spaces are also in scope. -#### IMPACT +##### Impact - *Did this incident occur in a private conversation or in a public space?* Incidents that all community members can see will have more negative impact. -- *Does this behavior negatively impact a marginalized group in our community?* Is the reporter a person from a marginalized group in our community? How is the reporter being negatively impacted by the reported person's behavior? Are members of the marginalized group likely to disengage with the community if no action was taken on this report? -- *Does this incident involve a community leader?* Community members often look up to community leaders to set the standard of acceptable behavior. +- *Does this behaviour negatively impact a marginalised group in our community?* Is the reporter a person from a marginalised group in our community? How is the reporter being negatively impacted by the reported person's behaviour? Are members of the marginalised group likely to disengage with the community if no action was taken on this report? +- *Does this incident involve a community leader?* Community members often look up to community leaders to set the standard of acceptable behaviour. -#### RISK +##### Risk - *Does this incident include sexual harassment?* -- *Does this pose a safety risk?* Does the behavior put a person's physical safety at risk? Will this incident severely negatively impact someone's mental health? -- *Is there a risk of this behavior being repeated?* Does the reported person understand why their behavior was inappropriate? Is there an established pattern of behavior from past reports? +- *Does this pose a safety risk?* Does the behaviour put a person's physical safety at risk? Will this incident severely negatively impact someone's mental health? +- *Is there a risk of this behaviour being repeated?* Does the reported person understand why their behaviour was inappropriate? Is there an established pattern of behaviour from past reports? Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact. -### Propose a behavioral modification plan +#### Propose a behavioural modification plan -The event staff will determine a concrete behavioral modification plan that ensures the inappropriate behavior is not repeated. The event staff will also discuss what actions may need to be taken if the reported person does not agree to the behavioral modification plan. +The organisers will determine a concrete behavioural modification plan that ensures the inappropriate behaviour is not repeated. The organisers will also discuss what actions may need to be taken if the reported person does not agree to the behavioural modification plan. -What follows are examples of possible behavioral modification plans for incidents that occur in online spaces under the scope of this Code of Conduct. This behavioral modification list is not inclusive, and the event staff reserves the right to take any action it deems necessary. +What follows are examples of possible behavioural modification plans for incidents that occur in online spaces under the scope of this Code of Conduct. This behavioural modification list is not inclusive, and the organisers reserves the right to take any action it deems necessary. - Requiring that the reported person not use specific language - Requiring that the reported person not join in on specific types of discussions @@ -74,43 +79,40 @@ What follows are examples of possible behavioral modification plans for incident - Removing a person from leadership of relevant organizations - Removing a person from membership of relevant organizations -### Propose consequences +#### Propose consequences -What follows are examples of possible consequences to an incident report. This consequences list is not inclusive, and the event staff reserves the right to take any action it deems necessary. +What follows are examples of possible consequences to an incident report. This consequences list is not inclusive, and the organisers reserves the right to take any action it deems necessary. Possible private responses to an incident include: -- Nothing, if the behavior was determined to not be a Code of Conduct violation +- Nothing, if the behaviour was determined to not be a Code of Conduct violation - A verbal or emailed warning - A final warning - Temporarily removing the reported person from the online community - Permanently removing the reported person from the online community - Publishing an account of the incident -### Follow up with the reported person +#### Follow up with the reported person -The event staff will work with online community administrators/moderators to draft a response to the reported person. The email should contain: +The organisers will work with online community administrators/moderators to draft a response to the reported person. The email should contain: -- A description of the person's behavior in neutral language -- The negative impact of that behavior -- A concrete behavioral modification plan -- Any consequences of their behavior +- A description of the person's behaviour in neutral language +- The negative impact of that behaviour +- A concrete behavioural modification plan +- Any consequences of their behaviour -The work group should not state who reported this incident. They should attempt to anonymize any identifying information from the report. The reported person should be discouraged from contacting the reporter to discuss the report. If they wish to apologize to the reporter, the work group can accept the apology on behalf of the reporter. +The responders should not state who reported this incident. They should attempt to anonymise any identifying information from the report. The reported person should be discouraged from contacting the reporter to discuss the report. If they wish to apologise to the reporter, the responders can accept the apology on behalf of the reporter. -Decide further responses +#### Decide further responses -If the reported person provides additional context, the event staff may need to re-evaluate the behavioral modification plan and consequences. +If the reported person provides additional context, the organisers may need to re-evaluate the behavioural modification plan and consequences. -### Follow up with the reporter +#### Follow up with the reporter -A person who makes a report should receive a follow up email stating what action was taken in response to the report. If the work group decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation. Reports that are not made in good faith (such as "reverse sexism" or "reverse racism") may receive no response. +A person who makes a report should receive a follow-up email stating what action was taken in response to the report. If the responders decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation. Reports that are not made in good faith (such as "reverse sexism" or "reverse racism") may receive no response. -The follow up email should be sent no later than one week after the receipt of the report. If deliberation or follow up with the reported person takes longer than one week, the work group should send a status email to the reporter. +The follow-up email should be sent no later than one week after the receipt of the report. If deliberation or follow up with the reported person takes longer than one week, the responders should send a status email to the reporter. -Attribution +### Attribution -- The [PyCon US Code of Conduct](../) is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). -- Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)" is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/) -- Audrey Eschright of [Safety First PDX](http://safetyfirstpdx.org/) provided the impact vs risk assessment framework, which is licensed under a [Creative Commons Attribution Share-Alike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/)by Audrey Eschright of [Safety First PDX](http://safetyfirstpdx.org/) -- [Code of Conduct template](https://github.com/sagesharp/code-of-conduct-template/) was created by [Otter Tech](https://otter.technology/code-of-conduct-training) and is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/) +Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). diff --git a/procedures-for-reporting-incidents.md b/procedures-for-reporting-incidents.md index 3f2e36d..171df07 100644 --- a/procedures-for-reporting-incidents.md +++ b/procedures-for-reporting-incidents.md @@ -1,31 +1,35 @@ -# PyCon US Procedures for Reporting Code of Conduct Incidents +--- +layout: default +title: Helsinki Python - Procedures for reporting code of conduct incidents +--- -If you believe someone is in physical danger, including from themselves, the most important thing is to get that person help. Please contact the appropriate crisis number, non-emergency number, or police number. If you are a PyCon US attendee, you can consult with a volunteer or staff member to help find an appropriate number. +## Procedures for reporting code of conduct incidents -If you believe someone has violated the [PyCon US Code of Conduct](..), we encourage you to report it. If you are unsure whether the incident is a violation, or whether the space where it happened is covered by the Code of Conduct, we encourage you to still report it. We are fine with receiving reports where we decide to take no action for the sake of creating a safer space. +If you believe someone is in physical danger, including from themselves, the most important thing is to get that person help. Please contact the appropriate crisis number, non-emergency number, or police number. If you are a Helsinki Python attendee, you can consult with a volunteer or staff member to help find an appropriate number. -If you find that you need to make a report, and you cannot find the appropriate Code of Conduct reporting contact, you may report to the PyCon US Code of Conduct email alias below. PyCon US event staff will handle your report. If this happens, please also mention that you could not find specific reporting information so that we can improve. +If you believe someone has violated the [Code of Conduct](/code-of-conduct), we encourage you to report it. If you are unsure whether the incident is a violation, or whether the space where it happened is covered by the Code of Conduct, we encourage you to still report it. We are fine with receiving reports where we decide to take no action for the sake of creating a safer space. + +If you find that you need to make a report, and you cannot find the appropriate Code of Conduct reporting contact, you may report to the Helsinki Python Code of Conduct email alias below. Helsinki Python organisers will handle your report. If this happens, please also mention that you could not find specific reporting information so that we can improve. *General reporting procedure:* -The best way to contact the PyCon US Code of Conduct event staff is by email at . The members of the PyCon US event staff who monitor this account are: +The best way to contact the Helsinki Python Code of Conduct organisers is by email at . The organisers who monitor this account are: -- Deb Nicholson -- Łukasz Langa -- Olivia Sauls -- Ee Durbin +- Cal Paterson +- Hugo van Kemenade +- Jerry Pussinen +- Sami Lehtinen -In the event of a conflict of interest, you may directly contact any of the lead incident responders: +In the event of a conflict of interest, you may directly contact any of the incident responders: -- Ee Durbin - - Python Software Foundation - Director of Infrastructure - - -- Olivia Sauls - - Python Software Foundation - Program Director - - +- TODO + - Organiser + - +- TODO + - Organiser + - -REPORT DATA ------------ +### Report data When you make a report via email or phone, please include: @@ -34,50 +38,42 @@ When you make a report via email or phone, please include: - Location of incident - Whether the incident is ongoing - Description of the incident -- Identifying information of the reported person: name, physical appearance, height, clothing, voice accent, identifying badge information such as company name, ribbons, or badge number +- Identifying information of the reported person: name, physical appearance, height, clothing, voice accent - Additional circumstances surrounding the incident - Other people involved in or witnesses to the incident and their contact information or description Please provide as much information as possible. -CONFIDENTIALITY ---------------- +### Confidentiality -All reports will be kept confidential. When we discuss incidents with people who are reported, we will anonymize details as much as we can to protect reporter privacy. +All reports will be kept confidential. When we discuss incidents with people who are reported, we will anonymise details as much as we can to protect reporter privacy. -However, some incidents happen in one-on-one interactions, and even if the details are anonymized, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, please note those in your report. We still encourage you to report, so that we can support you while keeping our conference attendees safe. In some cases, we can compile several anonymized reports into a pattern of behavior, and take action on that pattern. +However, some incidents happen in one-on-one interactions, and even if the details are anonymised, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, please note those in your report. We still encourage you to report, so that we can support you while keeping our conference attendees safe. In some cases, we can compile several anonymised reports into a pattern of behaviour, and take action on that pattern. 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. -REPORT HANDLING PROCEDURE -------------------------- - -When you make a report to an incident responder, they will gather information about the incident according to the [Procedure For Incident Response](../Enforcement-Procedures). - -After an incident responder takes the report, they will immediately consult with the PyCon US event staff, unless there is a conflict of interest, in which case any non-interested parties will be contacted. +### Report handling procedure -If the incident is ongoing and needs to be immediately addressed, any lead incident responder may take appropriate action to ensure the safety of everyone involved. If the situation requires it, this may take the form of a referral to an appropriate non-PyCon US agency, including the local police. PyCon US is not equipped to handle emergency situations. +When you make a report to an incident responder, they will gather information about the incident according to the [procedure for incident response](/enforcement-procedures). -If the incident is less urgent, the report will be discussed by the event staff, who will meet to determine an appropriate response. Examples of possible incident responses are outlined in the [Procedure For Incident Response](../Enforcement-Procedures). +If the incident is ongoing and needs to be immediately addressed, any incident responder may take appropriate action to ensure the safety of everyone involved. If the situation requires it, this may take the form of a referral to an appropriate non-Helsinki Python agency, including the local police. Helsinki Python is not equipped to handle emergency situations. -Before any large in-person gathering conference, staff will have a mandatory meeting where incident response procedures will be outlined. After the conference, all incident responders will attend a debriefing session with the lead responders to discuss all incidents and determine any necessary follow-up actions. +If the incident is less urgent, the report will be discussed by the event staff, who will meet to determine an appropriate response. Examples of possible incident responses are outlined in the [procedure for incident response](/enforcement-procedures). -FOLLOWING UP WITH REPORTERS ---------------------------- +### Following up with reporters -Within one week of an incident report, a member of the event staff, or one of the lead responders, will follow up with the person who made the report and provided their contact information. The follow up may include: +Within one week of an incident report, the responders will follow up with the person who made the report and provided their contact information. The follow up may include: - An acknowledgment that the Code of Conduct responders discussed the situation - Whether or not the report was determined to be a violation of the Code of Conduct -- What actions (if any) were taken to correct the reported behavior +- What actions (if any) were taken to correct the reported behaviour -In some cases, the lead responders may need to ask additional questions about the incident in order to identify the reported person. +In some cases, the responders may need to ask additional questions about the incident in order to identify the reported person. -CONFLICTS OF INTEREST ---------------------- +### Conflicts of interest If an incident responder has a conflict of interest for a report, they will recuse themselves from the discussion and handling of the incident. The incident documentation will not be available to them, and they will excuse themselves from any conversations involving handling the incident. -Should more than two of the PyCon US lead incident responders need to recuse themselves, another PyCon US staff member will step in as a temporary lead incident responder. +### Attribution -This procedure was adapted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)", the [Django Project reporting guidelines](https://www.djangoproject.com/conduct/reporting/) (CC BY 3.0), with additions by [Otter Tech](https://otter.technology/). +Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). From d6bde6dcd0661288b04e86f1298b55f2ff9c9e8c Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Mon, 8 Apr 2024 17:01:50 +0300 Subject: [PATCH 3/8] Add Sami, sort alphabetically --- index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/index.md b/index.md index 0b8bdff..c066c53 100644 --- a/index.md +++ b/index.md @@ -16,9 +16,10 @@ region meeting up roughly every month. ### Organisers +- [Cal Paterson](https://github.com/calpaterson) - [Hugo van Kemenade](https://github.com/hugovk) - [Jerry Pussinen](https://github.com/jerry-git) -- [Cal Paterson](https://github.com/calpaterson) +- [Sami Lehtinen](https://github.com/sjlehtin) ## Next event From e7ff75ad58658c69b522af75084a0c7d31b09708 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Mon, 8 Apr 2024 17:44:10 +0300 Subject: [PATCH 4/8] Remove PSF --- code-of-conduct.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 45012c2..05ca886 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -9,7 +9,7 @@ Helsinki Python events are intended for networking and collaboration in the deve We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees at all Helsinki Python events. -To make clear what is expected, all staff, attendees, speakers, exhibitors, organisers, and volunteers at any Helsinki Python event are required to conform to the following Code of Conduct, as set forth by the Python Software Foundation. Organisers will enforce this code throughout the event. +To make clear what is expected, all staff, attendees, speakers, exhibitors, organisers, and volunteers at any Helsinki Python event are required to conform to the following Code of Conduct. Organisers will enforce this code throughout the event. ### Our community From 8896784b8faf45462cb0e52343cca2dcc1bd5e30 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Mon, 8 Apr 2024 17:44:21 +0300 Subject: [PATCH 5/8] Caps, https --- code-of-conduct.md | 2 +- enforcement-procedures.md | 2 +- procedures-for-reporting-incidents.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 05ca886..0040c29 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -58,7 +58,7 @@ No weapons are allowed at Helsinki Python events. Weapons include but are not li #### Consequences -If a participant engages in behaviour that violates this code of conduct, the Helsinki Python team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behaviour is listed in the [Enforcement Procedures](enforcement-procedures). +If a participant engages in behaviour that violates this code of conduct, the Helsinki Python team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behaviour is listed in the [enforcement procedures](enforcement-procedures). Thank you for helping make this a welcoming, friendly community for everyone. diff --git a/enforcement-procedures.md b/enforcement-procedures.md index bb1e93a..ea4058b 100644 --- a/enforcement-procedures.md +++ b/enforcement-procedures.md @@ -115,4 +115,4 @@ The follow-up email should be sent no later than one week after the receipt of t ### Attribution -Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). +Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/). diff --git a/procedures-for-reporting-incidents.md b/procedures-for-reporting-incidents.md index 171df07..727cced 100644 --- a/procedures-for-reporting-incidents.md +++ b/procedures-for-reporting-incidents.md @@ -76,4 +76,4 @@ If an incident responder has a conflict of interest for a report, they will recu ### Attribution -Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). +Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/). From eafbe25123250e84f66b459be80cc403fe3d50f6 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Mon, 8 Apr 2024 21:31:00 +0300 Subject: [PATCH 6/8] Keep it simple --- README.md | 4 +- code-of-conduct.md | 134 +------------------------- enforcement-procedures.md | 118 ----------------------- index.md | 2 +- procedures-for-reporting-incidents.md | 79 --------------- 5 files changed, 8 insertions(+), 329 deletions(-) delete mode 100644 enforcement-procedures.md delete mode 100644 procedures-for-reporting-incidents.md diff --git a/README.md b/README.md index dcb0a91..ac95d29 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@

- Helsinki Python logo

diff --git a/code-of-conduct.md b/code-of-conduct.md index 0040c29..b795e40 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -9,143 +9,19 @@ Helsinki Python events are intended for networking and collaboration in the deve We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees at all Helsinki Python events. -To make clear what is expected, all staff, attendees, speakers, exhibitors, organisers, and volunteers at any Helsinki Python event are required to conform to the following Code of Conduct. Organisers will enforce this code throughout the event. +To make clear what is expected, all staff, attendees, speakers, exhibitors, organisers, and volunteers at any Helsinki Python event are required to conform to the +[PyCon US Code of Conduct](https://policies.python.org/us.pycon.org/code-of-conduct/). Organisers will enforce this code throughout the event. -### Our community - -Members of the Python community are open, considerate, and respectful. Behaviours that reinforce these values contribute to a positive environment, and include: - -- **Being open.** Members of the community are open to collaboration. -- **Focusing on what is best for the community.** We're respectful of the processes set forth in the community, and we work within them. -- **Acknowledging time and effort.** We're respectful of the volunteer efforts that permeate the Python community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. -- **Being respectful of differing viewpoints and experiences.** We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. -- **Showing empathy towards other community members.** We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views. -- **Being considerate.** Members of the community are considerate of their peers -- other Python users. -- **Being respectful.** We're respectful of others, their positions, their skills, their commitments, and their efforts. -- **Gracefully accepting constructive criticism.** When we disagree, we are courteous in raising our issues. -- **Using welcoming and inclusive language.** We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference. - -### Our standards - -Every member of our community has the right to have their identity respected. The Python community is dedicated to providing a positive experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status. - -#### Inappropriate behaviour - -Examples of unacceptable behaviour by participants include: - -- Harassment of any participants in any form -- Deliberate intimidation, stalking, or following -- Logging or taking screenshots of online activity for harassment purposes -- Publishing others' private information, such as a physical or electronic address, without explicit permission -- Violent threats or language directed against another person -- Incitement of violence or harassment towards any individual, including encouraging a person to commit suicide or to engage in self-harm -- Creating additional online accounts in order to harass another person or circumvent a ban -- Sexual language and imagery in online communities or in any event venue, including talks -- Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that hold others up for ridicule -- Excessive swearing -- Unwelcome sexual attention or advances -- Unwelcome physical contact, including simulated physical contact (eg, textual descriptions like "hug" or "backrub") without consent or after a request to stop -- Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others -- Sustained disruption of online community discussions, in-person presentations, or other in-person events -- Continued one-on-one communication after requests to cease -- Other conduct that is inappropriate for a professional audience including people of many different backgrounds - -Community members asked to stop any inappropriate behaviour are expected to comply immediately. - -#### Weapons policy - -No weapons are allowed at Helsinki Python events. Weapons include but are not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. - -#### Consequences - -If a participant engages in behaviour that violates this code of conduct, the Helsinki Python team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behaviour is listed in the [enforcement procedures](enforcement-procedures). - -Thank you for helping make this a welcoming, friendly community for everyone. - -### Scope - -#### Helsinki Python events - -This Code of Conduct applies to the following people at Helsinki Python events: - -- staff -- speakers -- panelists -- tutorial or workshop leaders -- poster presenters -- people invited to meetings or summits -- exhibitors -- organisers -- volunteers -- all attendees - -The Code of Conduct applies in official venue event spaces, including: - -- exhibit hall or vendor tabling area -- panel and presentation rooms -- hackathon or sprint rooms -- tutorial or workshop rooms -- poster session rooms -- summit or meeting rooms -- staff areas -- meal areas -- party suites -- walkways, hallways, elevators, and stairs that connect any of the above spaces - -The Code of Conduct applies to interactions with official event accounts on social media spaces and phone applications, including: - -- comments made on official event phone apps -- comments made on event video hosting services -- comments made on the official event hashtag or panel hashtags - -Event organisers will enforce this code throughout the event. - -### Helsinki Python online spaces - -This Code of Conduct applies to the following online spaces: - -- The [Helsinki Python site](https://helsinki-python.github.io) -- Any other online space administered by Helsinki Python - -This Code of Conduct applies to the following people in official Helsinki Python online spaces: - -- admins of the online space -- maintainers -- reviewers -- contributors -- all community members - -The Helsinki Python Code of Conduct work group will receive and evaluate incident reports from the online communities listed above. The Helsinki Python Code of Conduct work group will work with online community administrators/moderators to suggest actions to take in response to a report. - -### Contact information +## Contact information If you believe that someone is violating the code of conduct, or have any other concerns, please contact an organiser immediately. They can be reached by emailing which is monitored by Cal Paterson, Hugo van Kemenade, Jerry Pussinen and Sami Lehtinen. In case of a conflict of interest, you can individually contact: +- Cal Paterson + - - TODO - - Organiser - - -- TODO - - Organiser - Event organisers and staff will be happy to help participants contact venue security or local law enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration of the event. We value your attendance. - -### Procedure for handling incidents - -- [Procedure for reporting code of conduct incidents](/procedures-for-reporting-incidents) - -- [Enforcement procedures](/enforcement-procedures) - -### License - -This Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](https://creativecommons.org/licenses/by-sa/3.0/). - -### Attributions - -This Code of Conduct is forked from the -[PyCon US Code of Conduct](https://policies.python.org/us.pycon.org/code-of-conduct/) -which details the sources of its language, and with similar edits as the -[Boston Python Code of Conduct](https://about.bostonpython.com/code-of-conduct). diff --git a/enforcement-procedures.md b/enforcement-procedures.md deleted file mode 100644 index ea4058b..0000000 --- a/enforcement-procedures.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -layout: default -title: Helsinki Python - Code of conduct enforcement procedures ---- - -## Code of conduct enforcement procedures - -This document summarises the procedures the Helsinki Python organisers uses to enforce the Code of Conduct. - -#### Summary of processes - -When the responders receive a report of a possible Code of Conduct violation, it will: - -1. Acknowledge the receipt of the report. -2. Evaluate conflicts of interest. -3. Call a meeting of Code of Conduct responders who do not have a conflict of interest. -4. Evaluate the reported incident. -5. Propose a behavioural modification plan. -6. Propose consequences for the reported behaviour. -7. Vote on behavioural modification plan and consequences for the reported person. -8. Contact online community administrators/moderators to approve the behavioural modification plan and consequences. -9. Follow up with the reported person. -10. Decide further responses. -11. Follow up with the reporter. - -#### Acknowledge the report - -Reporters should receive an emailed acknowledgment of the receipt of their report within 24 hours. - -#### Conflict of interest policy - -Examples of conflicts of interest include: - -- The reporter or reported person is your manager -- You have a romantic or platonic relationship with either the reporter or the reported person. It's fine to participate if they are an acquaintance. -- The reporter or reported person is your metamour. (This is a term used in the poly community; the short definition is [here](https://www.urbandictionary.com/define.php?term=Metamour), and a longer description is [here](https://solopoly.net/2012/09/29/whats-a-metamour-on-my-terms/).) -- The reporter or reported person is your family member -- The reporter or reported person is your direct client -- The reporter or reported person is someone you work closely with. This could be someone on your team or someone who works on the same project as you. -- The reporter or reported person is a maintainer who regularly reviews your contributions - -Responders do not need to state why they have a conflict of interest, only that one exists. Other responders should not ask why the person has a conflict of interest. - -Anyone who has a conflict of interest will remove themselves from the discussion of the incident, and recuse themselves from voting on a response to the report. - -#### Evaluating a report - -##### Jurisdiction - -- *Is this a Code of Conduct violation?* Is this behaviour on our list of inappropriate behaviour? Is it borderline inappropriate behaviour? Does it violate our community norms? -- *Did this occur in a space that is within our Code of Conduct's scope?* If the incident occurred outside the community, but a community member's mental health or physical safety may be negatively impacted if no action is taken, the incident may be in scope. Private conversations in community spaces are also in scope. - -##### Impact - -- *Did this incident occur in a private conversation or in a public space?* Incidents that all community members can see will have more negative impact. -- *Does this behaviour negatively impact a marginalised group in our community?* Is the reporter a person from a marginalised group in our community? How is the reporter being negatively impacted by the reported person's behaviour? Are members of the marginalised group likely to disengage with the community if no action was taken on this report? -- *Does this incident involve a community leader?* Community members often look up to community leaders to set the standard of acceptable behaviour. - -##### Risk - -- *Does this incident include sexual harassment?* -- *Does this pose a safety risk?* Does the behaviour put a person's physical safety at risk? Will this incident severely negatively impact someone's mental health? -- *Is there a risk of this behaviour being repeated?* Does the reported person understand why their behaviour was inappropriate? Is there an established pattern of behaviour from past reports? - -Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact. - -#### Propose a behavioural modification plan - -The organisers will determine a concrete behavioural modification plan that ensures the inappropriate behaviour is not repeated. The organisers will also discuss what actions may need to be taken if the reported person does not agree to the behavioural modification plan. - -What follows are examples of possible behavioural modification plans for incidents that occur in online spaces under the scope of this Code of Conduct. This behavioural modification list is not inclusive, and the organisers reserves the right to take any action it deems necessary. - -- Requiring that the reported person not use specific language -- Requiring that the reported person not join in on specific types of discussions -- Requiring that the reported person not send private messages to a community member -- Requiring that the reported person not join specific communication channels -- Removing the reported person from administrator or moderator rights to community infrastructure -- Removing a volunteer from their duties and responsibilities -- Removing a person from leadership of relevant organizations -- Removing a person from membership of relevant organizations - -#### Propose consequences - -What follows are examples of possible consequences to an incident report. This consequences list is not inclusive, and the organisers reserves the right to take any action it deems necessary. - -Possible private responses to an incident include: - -- Nothing, if the behaviour was determined to not be a Code of Conduct violation -- A verbal or emailed warning -- A final warning -- Temporarily removing the reported person from the online community -- Permanently removing the reported person from the online community -- Publishing an account of the incident - -#### Follow up with the reported person - -The organisers will work with online community administrators/moderators to draft a response to the reported person. The email should contain: - -- A description of the person's behaviour in neutral language -- The negative impact of that behaviour -- A concrete behavioural modification plan -- Any consequences of their behaviour - -The responders should not state who reported this incident. They should attempt to anonymise any identifying information from the report. The reported person should be discouraged from contacting the reporter to discuss the report. If they wish to apologise to the reporter, the responders can accept the apology on behalf of the reporter. - -#### Decide further responses - -If the reported person provides additional context, the organisers may need to re-evaluate the behavioural modification plan and consequences. - -#### Follow up with the reporter - -A person who makes a report should receive a follow-up email stating what action was taken in response to the report. If the responders decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation. Reports that are not made in good faith (such as "reverse sexism" or "reverse racism") may receive no response. - -The follow-up email should be sent no later than one week after the receipt of the report. If deliberation or follow up with the reported person takes longer than one week, the responders should send a status email to the reporter. - -### Attribution - -Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/). diff --git a/index.md b/index.md index c066c53..426e044 100644 --- a/index.md +++ b/index.md @@ -32,4 +32,4 @@ region meeting up roughly every month. ## See also -- [Code of Conduct](/code-of-conduct) +- [Code of conduct](/code-of-conduct) diff --git a/procedures-for-reporting-incidents.md b/procedures-for-reporting-incidents.md deleted file mode 100644 index 727cced..0000000 --- a/procedures-for-reporting-incidents.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -layout: default -title: Helsinki Python - Procedures for reporting code of conduct incidents ---- - -## Procedures for reporting code of conduct incidents - -If you believe someone is in physical danger, including from themselves, the most important thing is to get that person help. Please contact the appropriate crisis number, non-emergency number, or police number. If you are a Helsinki Python attendee, you can consult with a volunteer or staff member to help find an appropriate number. - -If you believe someone has violated the [Code of Conduct](/code-of-conduct), we encourage you to report it. If you are unsure whether the incident is a violation, or whether the space where it happened is covered by the Code of Conduct, we encourage you to still report it. We are fine with receiving reports where we decide to take no action for the sake of creating a safer space. - -If you find that you need to make a report, and you cannot find the appropriate Code of Conduct reporting contact, you may report to the Helsinki Python Code of Conduct email alias below. Helsinki Python organisers will handle your report. If this happens, please also mention that you could not find specific reporting information so that we can improve. - -*General reporting procedure:* - -The best way to contact the Helsinki Python Code of Conduct organisers is by email at . The organisers who monitor this account are: - -- Cal Paterson -- Hugo van Kemenade -- Jerry Pussinen -- Sami Lehtinen - -In the event of a conflict of interest, you may directly contact any of the incident responders: - -- TODO - - Organiser - - -- TODO - - Organiser - - - -### Report data - -When you make a report via email or phone, please include: - -- Your contact info (so we can get in touch with you if we need to follow up) -- Date and time of the incident -- Location of incident -- Whether the incident is ongoing -- Description of the incident -- Identifying information of the reported person: name, physical appearance, height, clothing, voice accent -- Additional circumstances surrounding the incident -- Other people involved in or witnesses to the incident and their contact information or description - -Please provide as much information as possible. - -### Confidentiality - -All reports will be kept confidential. When we discuss incidents with people who are reported, we will anonymise details as much as we can to protect reporter privacy. - -However, some incidents happen in one-on-one interactions, and even if the details are anonymised, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, please note those in your report. We still encourage you to report, so that we can support you while keeping our conference attendees safe. In some cases, we can compile several anonymised reports into a pattern of behaviour, and take action on that pattern. - -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. - -### Report handling procedure - -When you make a report to an incident responder, they will gather information about the incident according to the [procedure for incident response](/enforcement-procedures). - -If the incident is ongoing and needs to be immediately addressed, any incident responder may take appropriate action to ensure the safety of everyone involved. If the situation requires it, this may take the form of a referral to an appropriate non-Helsinki Python agency, including the local police. Helsinki Python is not equipped to handle emergency situations. - -If the incident is less urgent, the report will be discussed by the event staff, who will meet to determine an appropriate response. Examples of possible incident responses are outlined in the [procedure for incident response](/enforcement-procedures). - -### Following up with reporters - -Within one week of an incident report, the responders will follow up with the person who made the report and provided their contact information. The follow up may include: - -- An acknowledgment that the Code of Conduct responders discussed the situation -- Whether or not the report was determined to be a violation of the Code of Conduct -- What actions (if any) were taken to correct the reported behaviour - -In some cases, the responders may need to ask additional questions about the incident in order to identify the reported person. - -### Conflicts of interest - -If an incident responder has a conflict of interest for a report, they will recuse themselves from the discussion and handling of the incident. The incident documentation will not be available to them, and they will excuse themselves from any conversations involving handling the incident. - -### Attribution - -Forked from the [PyCon US Code of Conduct](https://policies.python.org/python.org/code-of-conduct/) and licensed under a [Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/). From 8c873bf17bc9d39d8055c2bf72c7a443c9a31a0c Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Tue, 9 Apr 2024 08:58:29 +0300 Subject: [PATCH 7/8] Add Jerry as a contact --- code-of-conduct.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index b795e40..8748188 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -21,7 +21,7 @@ In case of a conflict of interest, you can individually contact: - Cal Paterson - -- TODO - - +- Jerry Pussinen + - Event organisers and staff will be happy to help participants contact venue security or local law enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration of the event. We value your attendance. From 35e8de12e53b0b034e389500424688dcc8c5ca32 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Tue, 9 Apr 2024 09:42:52 +0300 Subject: [PATCH 8/8] Rearrange, add days --- index.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/index.md b/index.md index 426e044..9f4aae4 100644 --- a/index.md +++ b/index.md @@ -13,6 +13,7 @@ region meeting up roughly every month. - [Join on meetup.com](https://www.meetup.com/helpy-meetups/) - [Propose a talk](https://forms.gle/KjZVgeMGHRd5ECCJ9) - Follow on Mastodon +- Follow the [code of conduct](/code-of-conduct) ### Organisers @@ -23,13 +24,9 @@ region meeting up roughly every month. ## Next event -- 7th May 2024 - to be announced +- Tuesday, 7th May 2024 - to be announced ## Past events -- 3rd April 2024 - [April Helsinki Python meetup - Wolt x +- Wednesday, 3rd April 2024 - [April Helsinki Python meetup - Wolt x Aiven](https://www.meetup.com/helpy-meetups/events/299649951/) - -## See also - -- [Code of conduct](/code-of-conduct)