diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 1cf484f1..f7137cad 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,18 +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 @@ -32,7 +32,7 @@ Examples of unacceptable behavior by participants include: * Other conduct which could reasonably be considered inappropriate in a 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 @@ -48,18 +48,18 @@ 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 + [homepage]: https://www.contributor-covenant.org For answers to common questions about this code of conduct, see -https://www.contributor-covenant.org/faq + diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 827878e0..978d682a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,16 +1,22 @@ -# Contributing +# Contribute -We welcome any code contributions and hope that this -guide facilitate an understanding of the PyConceptEV code. -It is important to note that while PyConceptEV -is maintained by Ansys and any submissions are reviewed -thoroughly before merging, we still seek to foster a community that can -support user questions and develop new features to make this library -useful to all. As such, we welcome and encourage any -questions or submissions to this repository. +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 +PyConceptEV. -For information on contributing to a PyAnsys library, see the [PyAnsys developer's guide]. -For information specific to contributing to PyConceptEV, see [Contribute]. +[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html -[PyAnsys developer's guide]: https://dev.docs.pyansys.com/index.html -[Contribute]: https://conceptev.docs.pyansys.com/dev/contributing.html + +# 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 + + \ No newline at end of file diff --git a/LICENSE b/LICENSE index 3c96ad89..8a4a9b1a 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2023 - 2025 ANSYS, Inc. and/or its affiliates. +Copyright (c) 2023 - 2026 ANSYS, Inc. and/or its affiliates. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in @@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. +SOFTWARE. \ No newline at end of file diff --git a/SECURITY.md b/SECURITY.md index 5afe0f1e..5a88c014 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,30 +1,16 @@ - +> [!CAUTION] +> Do not use GitHub issues to report any security vulnerabilities. -# Security Policy +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. -## Reporting a Vulnerability +Provide the PyAnsys Core team with this information: -If you detect a vulnerability, please open an issue on GitHub and add the -``security`` label to your issue. The team will address it as soon as possible. +- 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 diff --git a/doc/changelog.d/294.miscellaneous.md b/doc/changelog.d/294.miscellaneous.md new file mode 100644 index 00000000..1d98c690 --- /dev/null +++ b/doc/changelog.d/294.miscellaneous.md @@ -0,0 +1 @@ +CHORE: Update missing or outdated files