From 13960ab88811a85ddf92ca4b17a313eb2960a440 Mon Sep 17 00:00:00 2001 From: Kattni Date: Fri, 24 Oct 2025 01:37:48 -0400 Subject: [PATCH 01/10] Update to Contributor Covenant version 3.0. --- CODE_OF_CONDUCT.md | 231 ++++++++++++++++++--------------------------- 1 file changed, 92 insertions(+), 139 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index a0568c77..c54fabf8 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,139 +1,92 @@ -# Code of Conduct - -*This Code of Conduct is adapted from the [Contributor Covenant, version -1.3.0](https://www.contributor-covenant.org/version/1/3/0/code-of-conduct.html)* - -As contributors and maintainers of this project, and in the interest of -fostering an open and welcoming community, we pledge to respect all people who -contribute through reporting issues, posting feature requests, updating -documentation, submitting pull requests or patches, and other activities. - -We are committed to making participation in this project a harassment-free -experience for everyone, regardless of level of experience, gender, gender -identity and expression, sexual orientation, disability, personal appearance, -body size, race, ethnicity, age, religion, or nationality. - -Examples of unacceptable behaviour by participants include: - -* The use of sexualized language or imagery -* Personal attacks -* Trolling or insulting/derogatory comments -* Public or private harassment -* Publishing other's private information, such as physical or electronic - addresses, without explicit permission -* Other unethical or unprofessional conduct -* Project maintainers have the right and responsibility to remove, edit, or - reject comments, commits, code, wiki edits, issues, and other contributions - that are not aligned to this Code of Conduct, or to ban temporarily or - permanently any contributor for other behaviours that they deem - inappropriate, threatening, offensive, or harmful. - -By adopting this Code of Conduct, project maintainers commit themselves to -fairly and consistently applying these principles to every aspect of managing -this project. Project maintainers who do not follow or enforce the Code of -Conduct may be permanently removed from the project team. - -This code of conduct applies both within project spaces and in public spaces -when an individual is representing the project or its community. - - -## Making a CoC complaint - -*This reporting guide draws heavily from the [Django Software Foundation Code -of Conduct Reporting Guide](https://www.djangoproject.com/conduct/reporting/).* - -If you believe someone is violating the BeeWare Project Code of Conduct we ask -that you report it to the BeeWare Project by emailing one or more of the -senior project maintainers: - -* Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) -* Katie McLaughlin (@glasnt; [katie@beeware.org](mailto:katie@beeware.org)) -* Philip James (@phildini [philip@beeware.org](mailto:philip@beeware.org)) - -All reports will be kept confidential. In some cases we may determine that a -public statement will need to be made. If that's the case, the identities of -all victims and reporters will remain confidential unless those individuals -instruct us otherwise. - -**If you believe anyone is in physical danger, please notify appropriate law -enforcement first.** If you are unsure what law enforcement agency is -appropriate, please include this in your report and we will attempt to notify -them. - -In your report please include: - -* **Your contact info** (so we can get in touch with you if we need to follow up) -* **Names (real, nicknames, or pseudonyms) of any individuals involved.** If - there were other witnesses besides you, please try to include them as well. -* When and where the incident occurred. Please be as specific as possible. -* Your account of what occurred. If there is a publicly available record (e.g. - a mailing list archive or a public IRC logger) please include a link. -* Any extra context you believe existed for the incident. -* If you believe this incident is ongoing. -* If you believe any member of the core team has a conflict of interest in - adjudicating the incident. -* What, if any, corrective response you believe would be appropriate. -* Any other information you believe we should have. - -Core team members are obligated to maintain confidentiality with regard to the -reporter and details of an incident. - -## What happens after you file a report? - -You will receive an email acknowledging receipt of your complaint. We promise -to acknowledge receipt within 24 hours (and will aim for much quicker than -that). - -The core team will immediately meet to review the incident and determine: - -* What happened. -* Whether this event constitutes a code of conduct violation. -* Who the bad actor was. -* Whether this is an ongoing situation, or if there is a threat to anyone's - physical safety. -* If this is determined to be an ongoing incident or a threat to physical - safety, the working groups' immediate priority will be to protect everyone - involved. This means we may delay an "official" response until we believe - that the situation has ended and that everyone is physically safe. -* If a member of the core team is one of the named parties, they will not be - included in any discussions, and will not be provided with any confidential - details from the reporter. - -If anyone on the core team believes they have a conflict of interest in -adjudicating on a reported issue, they will inform the other core team members, -and recuse themselves from any discussion about the issue. Following this -declaration, they will not be provided with any confidential details from the -reporter. - -Once the working group has a complete account of the events they will make a -decision as to how to response. Responses may include: - -* Nothing (if we determine no violation occurred). -* A private reprimand from the working group to the individual(s) involved. -* A public reprimand. -* An imposed vacation (i.e. asking someone to "take a week off" from a mailing - list or IRC). -* A permanent or temporary ban from some or all BeeWare spaces (GitHub - repositories, Gitter rooms, etc.) -* A request for a public or private apology. - -We'll respond within one week to the person who filed the report with either a -resolution or an explanation of why the situation is not yet resolved. - -Once we've determined our final action, we'll contact the original reporter to -let them know what action (if any) we'll be taking. We'll take into account -feedback from the reporter on the appropriateness of our response, but we don't -guarantee we'll act on it. - -Finally, depending on the specifics of the incident and the potential for -ongoing harm, the core team may choose to make a public report of the incident -on The Buzz, the BeeWare blog. - -## Changes - -Major substantive changes are listed here; for a complete list of changes see -the Github changelog. - -* **July 4, 2016:** Added instructions and guidelines for reporting incidents. - -* **December 5, 2015:** Initial Code of Conduct adopted. + +# Contributor Covenant 3.0 Code of Conduct + +## Our Pledge + +We pledge to make our community welcoming, safe, and equitable for all. + +We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant. + + +## Encouraged Behaviors + +While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language. + +With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including: + +1. Respecting the **purpose of our community**, our activities, and our ways of gathering. +2. Engaging **kindly and honestly** with others. +3. Respecting **different viewpoints** and experiences. +4. **Taking responsibility** for our actions and contributions. +5. Gracefully giving and accepting **constructive feedback**. +6. Committing to **repairing harm** when it occurs. +7. Behaving in other ways that promote and sustain the **well-being of our community**. + + +## Restricted Behaviors + +We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct. + +1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop. +2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people. +3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits. +4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community. +5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission. +6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group. +7. Behaving in other ways that **threaten the well-being** of our community. + +### Other Restrictions + +1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions. +2. **Failing to credit sources.** Not properly crediting the sources of content you contribute. +3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community. +4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors. + + +## Reporting an Issue + +Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. + +When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]** + +Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. + + +## Addressing and Repairing Harm + +**[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]** + +If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped. + +1) Warning + 1) Event: A violation involving a single incident or series of incidents. + 2) Consequence: A private, written warning from the Community Moderators. + 3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations. +2) Temporarily Limited Activities + 1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation. + 2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members. + 3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over. +3) Temporary Suspension + 1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation. + 2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions. + 3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted. +4) Permanent Ban + 1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member. + 2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior. + 3) Repair: There is no possible repair in cases of this severity. + +This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community. + + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. + + +## Attribution + +This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/). + +Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/) + +For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion). From 0401dccf871d8bea08af10bfec1ce43d6147330d Mon Sep 17 00:00:00 2001 From: Kattni Date: Fri, 24 Oct 2025 01:46:12 -0400 Subject: [PATCH 02/10] Apply BeeWare adapatation of CC3.0. --- CODE_OF_CONDUCT.md | 160 ++++++++++++++++++++++++++++++--------------- 1 file changed, 106 insertions(+), 54 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index c54fabf8..6eda3b9f 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,92 +1,144 @@ +# BeeWare Community Code of Conduct -# Contributor Covenant 3.0 Code of Conduct - -## Our Pledge +## Our pledge We pledge to make our community welcoming, safe, and equitable for all. We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant. +The guidelines within and enforcement of the BeeWare Community Code of Conduct applies equally to everyone participating in the BeeWare community, including members of the Code of Conduct Response Team. -## Encouraged Behaviors +## Encouraged behaviors While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language. With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including: -1. Respecting the **purpose of our community**, our activities, and our ways of gathering. -2. Engaging **kindly and honestly** with others. -3. Respecting **different viewpoints** and experiences. -4. **Taking responsibility** for our actions and contributions. -5. Gracefully giving and accepting **constructive feedback**. -6. Committing to **repairing harm** when it occurs. -7. Behaving in other ways that promote and sustain the **well-being of our community**. - + 1. Respecting the **purpose of our community**, our activities, and our ways of gathering. + 2. Engaging **kindly and honestly** with others. + 3. Respecting **different viewpoints** and experiences. + 4. **Taking responsibility** for our actions and contributions. + 5. Gracefully giving and accepting **constructive feedback**. + 6. Committing to **repairing harm** when it occurs. + 7. Behaving in other ways that promote and sustain the **well-being of our community**. -## Restricted Behaviors +## Restricted behaviors We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct. -1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop. -2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people. -3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits. -4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community. -5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission. -6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group. -7. Behaving in other ways that **threaten the well-being** of our community. + 1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop. + 2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people. + 3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits. + 4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community. + 5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission. + 6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group. + 7. Behaving in other ways that **threaten the well-being** of our community. -### Other Restrictions +### Other restrictions -1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions. -2. **Failing to credit sources.** Not properly crediting the sources of content you contribute. -3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community. -4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors. + 1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions. + 2. **Misrepresenting project affiliation.** Speaking or acting in a way that implies an official affiliation with the BeeWare project, where one does not exist. + 3. **Failing to credit sources.** Not properly crediting the sources of content you contribute. + 4. **Promotional materials.** Sharing marketing or other commercial content in a way that is outside the norms of the community. + 5. **Excessive communication.** Disrespecting the time and space of others by engaging in an unacceptable volume of communication. + 6. **Unnecessary interactions.** Unnecessarily reacting to or involving yourself in interactions that do not require a response from you. + 7. **Irresponsible messaging.** Failing to responsibly present content which includes, links or describes any other restricted behaviors. + 8. Other conduct that could reasonably be considered **unprofessional or inappropriate**. +## Reporting an issue -## Reporting an Issue +Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. Reporting even minor issues is important, as they can be helpful in identifying patterns of behavior that may not be concerning in isolation, however, when viewed collectively may be more significant. -Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. +When an incident does occur, it is important to report it promptly to the BeeWare Code of Conduct Response Team. -When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]** +**If you believe you or anyone else is in physical danger, please notify appropriate law enforcement first.** -Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. +To report a possible violation, you email the Team at [conduct@beeware.org](mailto:conduct@beeware.org). If necessary, you can reach out to individual team members. On the BeeWare Discord server, you can also direct message anyone on the Response Team, or, if appropriate, mention @moderators in a public channel. Team members can be reached by the following usernames on Discord or GitHub, or the provided email addresses: +* Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) +* Kattni (@kattni; [kattni@beeware.org](mailto:kattni@beeware.org)) -## Addressing and Repairing Harm +The Response Team takes reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. The Team will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. If we determine that a public statement will need to be made, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. -**[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]** +In your report, please include: -If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped. + * **Your contact info** so we can get in touch with you if we need to follow up. + * **Names (real, nicknames, or pseudonyms) of any individuals involved.** If there were other witnesses besides you, please try to include them as well. + * **When and where the incident occurred.** Please be as specific as possible. + * **Your account of what occurred.** If there is a publicly available record (e.g. a Discord or GitHub message) please include a link. + * **Any extra context** you believe existed for the incident. + * **If you believe this incident is ongoing.** + * **If you believe any member of the Response Team has a conflict of interest** in adjudicating the incident. + * **What, if any, corrective response** you believe would be appropriate. + * **Any other information** you believe we should have. -1) Warning - 1) Event: A violation involving a single incident or series of incidents. - 2) Consequence: A private, written warning from the Community Moderators. - 3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations. -2) Temporarily Limited Activities - 1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation. - 2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members. - 3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over. -3) Temporary Suspension - 1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation. - 2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions. - 3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted. -4) Permanent Ban - 1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member. - 2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior. - 3) Repair: There is no possible repair in cases of this severity. +Code of Conduct Response Team members are obligated to maintain confidentiality with regard to the reporter and details of an incident. -This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community. +## The Response Team's report follow-up + +You will receive a response acknowledging receipt of your report. We promise to acknowledge receipt within 24 hours (and will aim for much quicker than that). + +The Response Team will immediately meet to review the incident and determine: + + * What happened. + * Whether this event constitutes a code of conduct violation. + * Who the reported person was. + * Whether this is an ongoing situation, or if there is a threat to anyone's physical safety. + * If this is determined to be an ongoing incident or a threat to physical safety, the Response Team's immediate priority will be to protect everyone involved. This means we may delay an official response until we believe that the situation has concluded and that everyone is physically safe. + * If a member of the Response Team is one of the named parties, they will not be included in any discussions, and will not be provided with any confidential details from the reporter. + +If anyone on the Response Team believes they have a conflict of interest in adjudicating on a reported issue, they will inform the other Response Team members, and recuse themselves from any discussion about the issue. Following this declaration, they will not be provided with any confidential details from the reporter. + +We'll respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved. + +Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but we don't guarantee we'll act on it. + +Finally, depending on the specifics of the incident and the potential for ongoing harm, the Response Team may choose to make a public report of the incident on The Buzz, the BeeWare blog. + +## Enforcement: addressing and repairing harm +If an investigation by the Response Team finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped. -## Scope + 1. Warning + * Event: A violation involving a single incident or series of incidents. + * Consequence: A private, written warning from the Response Team. + * Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations. -This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. + 2. Temporarily Limited Activities + * Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation. + * Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members. + * Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over. + 3. Temporary Suspension + * Event: A pattern of repeated violation which the Response Team has tried to address with warnings, or a single serious violation. + * Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions. + * Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted. -## Attribution + 4. Permanent Ban + * Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Response Team determine there is no way to keep the community safe with this person as a member. + * Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior. + * Repair: There is no possible repair in cases of this severity. + +This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community. + +## Scope + +This Code of Conduct applies within all community spaces, including GitHub, the BeeWare Discord server, and in-person events, such as conferences, meetups, and sprints. It also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. + +## Attribution This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/). -Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/) +Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). + +For answers to common questions about Contributor Covenant, see the [FAQ](https://www.contributor-covenant.org/faq). [Translations](https://www.contributor-covenant.org/translations) are provided. There are [additional enforcement and community guideline resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion). + +## Changes + +Major substantive changes are listed here; for a complete list of changes see the GitHub commit history. + + * **TODO: add date:** Updated to adapt the Contributor Covenant, version 3.0. + + * **July 4, 2016:** Added instructions and guidelines for reporting incidents. -For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion). + * **December 5, 2015:** Initial Code of Conduct adopted. From c1f2a8717c6af02a97226380868ebcc7cbaeb4f0 Mon Sep 17 00:00:00 2001 From: Kattni Date: Fri, 24 Oct 2025 22:20:39 -0400 Subject: [PATCH 03/10] Update Response Team list. --- CODE_OF_CONDUCT.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 6eda3b9f..b5e7a9b0 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -49,7 +49,7 @@ We agree to restrict the following behaviors in our community. Instances, threat Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. Reporting even minor issues is important, as they can be helpful in identifying patterns of behavior that may not be concerning in isolation, however, when viewed collectively may be more significant. -When an incident does occur, it is important to report it promptly to the BeeWare Code of Conduct Response Team. +When an incident does occur, it is important to report it promptly to the BeeWare Code of Conduct Response Team. **If you believe you or anyone else is in physical danger, please notify appropriate law enforcement first.** @@ -57,6 +57,8 @@ To report a possible violation, you email the Team at [conduct@beeware.org](mail * Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) * Kattni (@kattni; [kattni@beeware.org](mailto:kattni@beeware.org)) +* Katie McLaughlin (@glasnt; [katie@beeware.org](mailto:katie@beeware.org)) +* Philip James (@phildini; [philip@beeware.org](mailto:philip@beeware.org)) The Response Team takes reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. The Team will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. If we determine that a public statement will need to be made, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. @@ -74,7 +76,7 @@ In your report, please include: Code of Conduct Response Team members are obligated to maintain confidentiality with regard to the reporter and details of an incident. -## The Response Team's report follow-up +## The Response Team's report followup You will receive a response acknowledging receipt of your report. We promise to acknowledge receipt within 24 hours (and will aim for much quicker than that). From b0352ff82eafd98fd4cae5469813f52ff0fb83e6 Mon Sep 17 00:00:00 2001 From: Kattni Date: Sun, 26 Oct 2025 19:32:18 -0400 Subject: [PATCH 04/10] Update CoC team list. --- CODE_OF_CONDUCT.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index b5e7a9b0..f8e9008d 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -55,10 +55,11 @@ When an incident does occur, it is important to report it promptly to the BeeWar To report a possible violation, you email the Team at [conduct@beeware.org](mailto:conduct@beeware.org). If necessary, you can reach out to individual team members. On the BeeWare Discord server, you can also direct message anyone on the Response Team, or, if appropriate, mention @moderators in a public channel. Team members can be reached by the following usernames on Discord or GitHub, or the provided email addresses: -* Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) -* Kattni (@kattni; [kattni@beeware.org](mailto:kattni@beeware.org)) -* Katie McLaughlin (@glasnt; [katie@beeware.org](mailto:katie@beeware.org)) -* Philip James (@phildini; [philip@beeware.org](mailto:philip@beeware.org)) + * Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) + * Kattni (@kattni; [kattni@beeware.org](mailto:kattni@beeware.org)) + * Katie McLaughlin (@glasnt; [katie@beeware.org](mailto:katie@beeware.org)) + * Philip James (@phildini; [philip@beeware.org](mailto:philip@beeware.org)) + * Charles Whittington (@HalfWhitt; [charles@beeware.org](mailto:charles@beeware.org)) The Response Team takes reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. The Team will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. If we determine that a public statement will need to be made, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. From b2c2f24a170e8f9ac4de97025d1e7efd863f5caa Mon Sep 17 00:00:00 2001 From: Kattni Date: Sun, 30 Nov 2025 19:24:06 -0500 Subject: [PATCH 05/10] Apply suggestions from code review Co-authored-by: Russell Keith-Magee --- CODE_OF_CONDUCT.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index f8e9008d..203082c8 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -30,7 +30,7 @@ We agree to restrict the following behaviors in our community. Instances, threat 2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people. 3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits. 4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community. - 5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission. + 5. **Violating confidentiality.** Sharing or acting on someone's personal or private information without their permission. 6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group. 7. Behaving in other ways that **threaten the well-being** of our community. @@ -41,7 +41,7 @@ We agree to restrict the following behaviors in our community. Instances, threat 3. **Failing to credit sources.** Not properly crediting the sources of content you contribute. 4. **Promotional materials.** Sharing marketing or other commercial content in a way that is outside the norms of the community. 5. **Excessive communication.** Disrespecting the time and space of others by engaging in an unacceptable volume of communication. - 6. **Unnecessary interactions.** Unnecessarily reacting to or involving yourself in interactions that do not require a response from you. + 6. **Unhelpful communication.** Offering opinions without relevant experience in the topic being discussed, entering into an ongoing discussion without first gaining familiarity with the history of the topic, or making contributions that are off-topic or otherwise distracting. 7. **Irresponsible messaging.** Failing to responsibly present content which includes, links or describes any other restricted behaviors. 8. Other conduct that could reasonably be considered **unprofessional or inappropriate**. @@ -96,7 +96,7 @@ We'll respond within one week to the person who filed the report with either a r Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but we don't guarantee we'll act on it. -Finally, depending on the specifics of the incident and the potential for ongoing harm, the Response Team may choose to make a public report of the incident on The Buzz, the BeeWare blog. +Finally, to maintain transparency in the reporting and enforcement process, whenever possible, the Response Team will make a public report of the incident on [The Buzz](https://beeware.org/news/buzz), the BeeWare blog. A public report may not be made if the specifics of the incident do not allow us to preserve anonymity, or if there is potential for ongoing harm from a report. ## Enforcement: addressing and repairing harm @@ -128,6 +128,8 @@ This enforcement ladder is intended as a guideline. It does not limit the abilit This Code of Conduct applies within all community spaces, including GitHub, the BeeWare Discord server, and in-person events, such as conferences, meetups, and sprints. It also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. +Behavior outside of official BeeWare spaces may also be considered as supporting evidence for a report if that behavior establishes a pattern, or represents a potential risk to the BeeWare community. + ## Attribution This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/). From 13471809ac076b3f56fde46d3cd6bad0f9110aa5 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Mon, 1 Dec 2025 10:03:30 +0800 Subject: [PATCH 06/10] Two minor tweaks. Co-authored-by: Kattni --- 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 203082c8..c865a24e 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -96,7 +96,7 @@ We'll respond within one week to the person who filed the report with either a r Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but we don't guarantee we'll act on it. -Finally, to maintain transparency in the reporting and enforcement process, whenever possible, the Response Team will make a public report of the incident on [The Buzz](https://beeware.org/news/buzz), the BeeWare blog. A public report may not be made if the specifics of the incident do not allow us to preserve anonymity, or if there is potential for ongoing harm from a report. +Finally, to maintain transparency in the reporting and enforcement process, whenever possible, the Response Team will make a public report of the incident on [The Buzz](https://beeware.org/news/buzz), the BeeWare blog. A public report may not be made if the specifics of the incident do not allow us to preserve anonymity, or if there is potential for ongoing harm. ## Enforcement: addressing and repairing harm @@ -128,7 +128,7 @@ This enforcement ladder is intended as a guideline. It does not limit the abilit This Code of Conduct applies within all community spaces, including GitHub, the BeeWare Discord server, and in-person events, such as conferences, meetups, and sprints. It also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. -Behavior outside of official BeeWare spaces may also be considered as supporting evidence for a report if that behavior establishes a pattern, or represents a potential risk to the BeeWare community. +Behavior outside of official BeeWare spaces may also be considered as supporting evidence for a report if that behavior establishes a pattern, or represents a potential risk to the BeeWare community. ## Attribution From 2b72b0a0d5953103ffb4715dc6c40f3a343700c5 Mon Sep 17 00:00:00 2001 From: Kattni Date: Mon, 1 Dec 2025 21:21:59 -0500 Subject: [PATCH 07/10] Clarify temporary suspensions. --- 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 c865a24e..5303cb83 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -114,7 +114,7 @@ If an investigation by the Response Team finds that this Code of Conduct has bee 3. Temporary Suspension * Event: A pattern of repeated violation which the Response Team has tried to address with warnings, or a single serious violation. - * Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions. + * Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions. Suspensions will be based on where the violation occurs, and may be limited to the space in which the violation occurs. In the event of a more serious violation, the suspension may apply to all spaces. * Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted. 4. Permanent Ban From 0f58b5ddbd18e81b95cdf299bd53441bcb3d2389 Mon Sep 17 00:00:00 2001 From: Kattni Date: Thu, 4 Dec 2025 15:05:40 -0500 Subject: [PATCH 08/10] Apply suggestions from code review Co-authored-by: Charles Whittington --- CODE_OF_CONDUCT.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 5303cb83..ddc51f2b 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -6,7 +6,7 @@ We pledge to make our community welcoming, safe, and equitable for all. We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant. -The guidelines within and enforcement of the BeeWare Community Code of Conduct applies equally to everyone participating in the BeeWare community, including members of the Code of Conduct Response Team. +The guidelines within and enforcement of the BeeWare Community Code of Conduct apply equally to everyone participating in the BeeWare community, including members of the Code of Conduct Response Team. ## Encouraged behaviors @@ -47,13 +47,13 @@ We agree to restrict the following behaviors in our community. Instances, threat ## Reporting an issue -Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. Reporting even minor issues is important, as they can be helpful in identifying patterns of behavior that may not be concerning in isolation, however, when viewed collectively may be more significant. +Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. Reporting even minor issues is important, as they can be helpful in identifying patterns of behavior that may not be concerning in isolation, but when viewed collectively may be more significant. When an incident does occur, it is important to report it promptly to the BeeWare Code of Conduct Response Team. **If you believe you or anyone else is in physical danger, please notify appropriate law enforcement first.** -To report a possible violation, you email the Team at [conduct@beeware.org](mailto:conduct@beeware.org). If necessary, you can reach out to individual team members. On the BeeWare Discord server, you can also direct message anyone on the Response Team, or, if appropriate, mention @moderators in a public channel. Team members can be reached by the following usernames on Discord or GitHub, or the provided email addresses: +To report a possible violation, email the Team at [conduct@beeware.org](mailto:conduct@beeware.org). If necessary, you can reach out to individual team members. On the BeeWare Discord server, you can also direct message anyone on the Response Team, or, if appropriate, mention @moderators in a public channel. Team members can be reached by the following usernames on Discord or GitHub, or the provided email addresses: * Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) * Kattni (@kattni; [kattni@beeware.org](mailto:kattni@beeware.org)) @@ -61,7 +61,7 @@ To report a possible violation, you email the Team at [conduct@beeware.org](mail * Philip James (@phildini; [philip@beeware.org](mailto:philip@beeware.org)) * Charles Whittington (@HalfWhitt; [charles@beeware.org](mailto:charles@beeware.org)) -The Response Team takes reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. The Team will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. If we determine that a public statement will need to be made, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. +The Response Team takes reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. The Team will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. If we determine that a public statement needs to be made, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. In your report, please include: @@ -85,7 +85,7 @@ The Response Team will immediately meet to review the incident and determine: * What happened. * Whether this event constitutes a code of conduct violation. - * Who the reported person was. + * Who the reported person is. * Whether this is an ongoing situation, or if there is a threat to anyone's physical safety. * If this is determined to be an ongoing incident or a threat to physical safety, the Response Team's immediate priority will be to protect everyone involved. This means we may delay an official response until we believe that the situation has concluded and that everyone is physically safe. * If a member of the Response Team is one of the named parties, they will not be included in any discussions, and will not be provided with any confidential details from the reporter. @@ -118,7 +118,7 @@ If an investigation by the Response Team finds that this Code of Conduct has bee * Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted. 4. Permanent Ban - * Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Response Team determine there is no way to keep the community safe with this person as a member. + * Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Response Team determines there is no way to keep the community safe with this person as a member. * Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior. * Repair: There is no possible repair in cases of this severity. From 19c1632e760a345e63c813e4ca4babe18ea71eff Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Mon, 15 Dec 2025 12:01:20 +0800 Subject: [PATCH 09/10] Final revisions --- CODE_OF_CONDUCT.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index ddc51f2b..8e24919d 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -28,7 +28,7 @@ We agree to restrict the following behaviors in our community. Instances, threat 1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop. 2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people. - 3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits. + 3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of a personal identity or trait. 4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community. 5. **Violating confidentiality.** Sharing or acting on someone's personal or private information without their permission. 6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group. @@ -42,7 +42,7 @@ We agree to restrict the following behaviors in our community. Instances, threat 4. **Promotional materials.** Sharing marketing or other commercial content in a way that is outside the norms of the community. 5. **Excessive communication.** Disrespecting the time and space of others by engaging in an unacceptable volume of communication. 6. **Unhelpful communication.** Offering opinions without relevant experience in the topic being discussed, entering into an ongoing discussion without first gaining familiarity with the history of the topic, or making contributions that are off-topic or otherwise distracting. - 7. **Irresponsible messaging.** Failing to responsibly present content which includes, links or describes any other restricted behaviors. + 7. **Irresponsible messaging.** Presenting content which includes, links, or describes other restricted behaviors without a relevant reason and appropriate prior warnings for consumers of that content. 8. Other conduct that could reasonably be considered **unprofessional or inappropriate**. ## Reporting an issue @@ -53,7 +53,7 @@ When an incident does occur, it is important to report it promptly to the BeeWar **If you believe you or anyone else is in physical danger, please notify appropriate law enforcement first.** -To report a possible violation, email the Team at [conduct@beeware.org](mailto:conduct@beeware.org). If necessary, you can reach out to individual team members. On the BeeWare Discord server, you can also direct message anyone on the Response Team, or, if appropriate, mention @moderators in a public channel. Team members can be reached by the following usernames on Discord or GitHub, or the provided email addresses: +To report a possible violation, email the Team at [conduct@beeware.org](mailto:conduct@beeware.org). If necessary, you can reach out to individual team members. On the BeeWare Discord server, you can also direct message anyone on the Response Team, or, if appropriate, mention `@moderators` in a public channel. Team members can be reached by the following usernames on Discord or GitHub, or the provided email addresses: * Russell Keith-Magee (@freakboy3742; [russell@beeware.org](mailto:russell@beeware.org)) * Kattni (@kattni; [kattni@beeware.org](mailto:kattni@beeware.org)) @@ -130,6 +130,7 @@ This Code of Conduct applies within all community spaces, including GitHub, the Behavior outside of official BeeWare spaces may also be considered as supporting evidence for a report if that behavior establishes a pattern, or represents a potential risk to the BeeWare community. +This Code of Conduct operates in parallel to any Code of Conduct that is in effect in a given context (e.g., the Code of Conduct for a conference). If an incident occurs, we encourage reporting that incident to all relevant conduct groups. Known violations of other Codes of Conduct may be considered as supporting evidence for a report under this Code of Conduct. The BeeWare Code of Conduct Response Team will cooperate with other Code of Conduct teams, but will not disclose any identifying details without the prior consent of the reporting party. ## Attribution This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/). @@ -142,7 +143,7 @@ For answers to common questions about Contributor Covenant, see the [FAQ](https: Major substantive changes are listed here; for a complete list of changes see the GitHub commit history. - * **TODO: add date:** Updated to adapt the Contributor Covenant, version 3.0. + * **15 Dec 2025: ** Updated to adapt the Contributor Covenant, version 3.0, with some modifications for BeeWare-specific guidelines and procedures. * **July 4, 2016:** Added instructions and guidelines for reporting incidents. From f49d177d6a3a83ac226dcdb198e9602881c89064 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Mon, 15 Dec 2025 12:04:07 +0800 Subject: [PATCH 10/10] Correct markup of acceptance date --- 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 8e24919d..470640e1 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -143,7 +143,7 @@ For answers to common questions about Contributor Covenant, see the [FAQ](https: Major substantive changes are listed here; for a complete list of changes see the GitHub commit history. - * **15 Dec 2025: ** Updated to adapt the Contributor Covenant, version 3.0, with some modifications for BeeWare-specific guidelines and procedures. + * **December 15, 2025:** Updated to adapt the Contributor Covenant, version 3.0, with some modifications for BeeWare-specific guidelines and procedures. * **July 4, 2016:** Added instructions and guidelines for reporting incidents.