The Python community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences great successes and continued growth. When you're working with members of the community, we encourage you to follow these guidelines which help steer our interactions and strive to keep Python a positive, successful, and growing community.

A member of the Python community is:


Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise. We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. 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 community are considerate of their peers -- other Python users. 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. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.


Members of the community are respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. We're respectful of the volunteer efforts that permeate the Python community. We're respectful of the processes set forth in the community, and we work within them. When we disagree, we are courteous in raising our issues.

Overall, we're good to each other. We contribute to this community not because we have to, but because we want to. If we remember that, these guidelines will come naturally.

Slovak Python Community

PyCon SK and Python Meetup fully identify with the Code of Conduct of the Python community. We create an environment, which is open to everyone, independently of sex, sexual orientation, race, education or religion. All communication should be respectful and on professional level. We will be tolerant to each other.

We do not offend, vilify other members. We behave professionally. Harassment, sexist, racist or otherwise demeaning jokes are improper at our meetings. We will not tolerate any harassment of participants of meetups in any form.

Read more about code of conduct

How we handle CoC incidents

This section summarizes the procedures the PyCon SK staff uses to enforce the Code of Conduct.

We will acknowledge all receipts of the reports and evaluate conflicts of interest. All reported incidents will be evaluated and consequences for the reported behavior will be proposed. We plan to follow up with the reported person as well as with the reporter.

Code of Conduct enforcement team:

  • - Veronika Antalová,
  • - Ján Gondoľ,

Conflicts of interests 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 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.

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.

Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact.

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

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 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.

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.

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.