From 61467fbdb5129693f0f68ba8001564d91e3bd8e0 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 04:58:36 +0100 Subject: [PATCH 1/3] chore: update CODE_OF_CONDUCT.md file --- CODE_OF_CONDUCT.md | 37 +++++++++++++++++++------------------ 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 808012f3a06..5a9533d3caa 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,17 +1,18 @@ -# Contributor Covenant Code of Conduct +# Contributor covenant code of conduct -## Our Pledge +## Pledge -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, body -size, disability, ethnicity, sex characteristics, gender identity and -expression, level of experience, education, socio-economic status, nationality, -personal appearance, race, religion, or sexual identity and orientation. +In the interest of fostering an open and welcoming environment, +all contributors and maintainers pledge to making participation +in the Ansys project and community a harassment-free experience +for everyone, regardless of age, body size, disability, ethnicity, +sex characteristics, gender identity and expression, level of +experience, education, socioeconomic status, nationality, personal +appearance, race, religion, or sexual identity and orientation. -## Our Standards +## Standards -Examples of behavior that contributes to creating a positive environment +Examples of behavior that contribute to creating a positive environment include: * Using welcoming and inclusive language @@ -22,16 +23,16 @@ include: Examples of unacceptable behavior by participants include: -* The use of sexualized language or imagery and unwelcome sexual attention or - advances +* The use of sexualized language or imagery and unwelcome sexual + attention or advances * Trolling, insulting/derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or electronic - address, without explicit permission + address, without explicit permission * Other conduct which could reasonably be considered inappropriate in a - professional setting + professional setting -## Our Responsibilities +## Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in @@ -47,14 +48,14 @@ offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of -representing a project or community include using an official project e-mail -address, posting via an official social media account, or acting as an appointed +representing a project or community include using an official project email +address, posting using an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Attribution -This Code of Conduct is adapted from the [Contributor Covenant][homepage], +This code of conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html From 3341e5058e557e6e7fd1c3f464e36f84b84764ad Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 04:58:38 +0100 Subject: [PATCH 2/3] chore: update CONTRIBUTING.md file --- CONTRIBUTING.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 463035ec6bb..5d752a14cf5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,13 +1,12 @@ -# Contributing - -We absolutely welcome any code contributions and we hope that this guide will -facilitate an understanding of the pyensight code repository. It is important -to note that while the pyensight software package is maintained by ANSYS and -any submissions will be reviewed thoroughly before merging, we still seek to -foster a community that can support user questions and develop new features to -make this software a useful tool for all users. As such, we welcome and -encourage any questions or submissions to this repository. - -Please reference the [PyAnsys Developer's -Guide](https://dev.docs.pyansys.com/) for the full documentation -regarding contributing to the pyensight project. +# Contribute + +Overall guidance on contributing to a PyAnsys library appears in the +[Contributing] topic in the *PyAnsys developer's guide*. Ensure that you +are thoroughly familiar with this guide before attempting to contribute to +{project-name}. + +The following contribution information is specific to {project-name}. + +[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html + + From 602cefc2e147896123d37a814d20849dfb1877a9 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 04:58:40 +0100 Subject: [PATCH 3/3] chore: update SECURITY.md file --- SECURITY.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 00000000000..5a88c0149db --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,16 @@ +# Security Policy + +## Reporting a vulnerability + +> [!CAUTION] +> Do not use GitHub issues to report any security vulnerabilities. + +If you detect a vulnerability, contact the [PyAnsys Core team](mailto:pyansys.core@ansys.com), +mentioning the repository and the details of your finding. The team will address it as soon as possible. + +Provide the PyAnsys Core team with this information: + +- Any specific configuration settings needed to reproduce the problem +- Step-by-step guidance to reproduce the problem +- The exact location of the problematic source code, including tag, branch, commit, or a direct URL +- The potential consequences of the vulnerability, along with a description of how an attacker could take advantage of the issue