From 93b50d342b83a56fd71766f43b50fbdb398a0c53 Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Wed, 11 Dec 2024 12:22:57 -0700 Subject: [PATCH 1/8] deleting stuff --- SECURITY - Copy.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 SECURITY - Copy.md diff --git a/SECURITY - Copy.md b/SECURITY - Copy.md deleted file mode 100644 index ce102ab..0000000 --- a/SECURITY - Copy.md +++ /dev/null @@ -1,19 +0,0 @@ - - -# Security - -NI views the security of our software products as an important part of our commitment to our users. This includes source code repositories managed through the [NI](https://github.com/ni) GitHub organization. - -## Reporting Security Issues - -We encourage you to report security vulnerabilities to us privately so we can follow the principle of [Coordinated Vulnerability Disclosure (CVD)](https://vuls.cert.org/confluence/display/CVD). This allows us time to thoroughly investigate security issues and publicly disclose them when appropriate. - -**Please do not report security vulnerabilities through public GitHub issues.** - -Instead, please report them by sending an email to [security@ni.com](mailto:security@ni.com) with sufficient details about the type of issue, the impact of the issue, and how to reproduce the issue. You may use the [NI PGP key](https://www.ni.com/en/support/security/pgp.html) to encrypt any sensitive communications you send to us. When you notify us of a potential security issue, our remediation process includes acknowledging receipt and coordinating any necessary response activities with you. - -## Learn More - -To learn more about NI Security, please see [https://ni.com/security](https://ni.com/security) - - \ No newline at end of file From 4cfca679bbec73d969eb656160047703c1641a37 Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Wed, 11 Dec 2024 12:46:02 -0700 Subject: [PATCH 2/8] no message --- README - Copy.md | 80 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 README - Copy.md diff --git a/README - Copy.md b/README - Copy.md new file mode 100644 index 0000000..35a4bca --- /dev/null +++ b/README - Copy.md @@ -0,0 +1,80 @@ +# Icon Editor for LabVIEW # + +This repo contains the source files and automated build tools for the LabVIEW icon editor. +You can use this code as a starting point for creating a custom icon editor. Refer to the [CONTRIBUTING](CONTRIBUTING.md) document for information about submitting changes for inclusion with future versions of LabVIEW. + +## Compatible LabVIEW Versions + +LabVIEW source is saved in 21.0 (__LabVIEW 2021__) format. Either LabVIEW 2021 or LabVIEW 2024 can be used to do development work. + +To build using the automated build process, ensure you have LabVIEW 2021 *both 32 and 64 bits* installed, latest VIPM, and apply the dependencies located on *Tooling\deployment\Dependencies.vipc* to both LabVIEW versions. + +## Editing Guide + +Because the icon editor is part of the LabVIEW development environment, you need to make changes to installed files before editing this project. There is an manual process, and an automated process made following it for ease of use. + +### Automated process + +Before following this process, create a backup of the following files and folder: + - \\\resource\\plugins\\lv_icon.lvlibp + - \\\vi.lib\\LabVIEW Icon API\\* + +After cloning the repo into a development location, and applying the dependencies located on *Tooling\deployment\Dependencies.vipc* to LabVIEW 2021 32 and 64 bits, follow this process to use the automation layer. + +1. Open Powershell in *Admin* mode and navigate to *.pipeline\scripts* from your github repo. +2. Modify the following command to point to your github repo and run it: *.\DevelopmentMode.ps1 -RelativePath "C:\labview-icon-editor"* +3. Open lv_icon_editor.lvproj in LabVIEW. +4. The top-level VI is in the Project Explorer at __My Computer » resource/plugins » lv_icon.lvlib » lv_icon.vi__. + +### Manual process + +Complete the following steps to edit this project: +1. Clone this repo into a development location (e.g., C:\dev). +2. Run __Tooling\Prepare LV to Use Icon Editor Source.vi__. +This will perform the following steps, which you can alternatively perform manually: + * Delete \\\resource\\plugins\\lv_icon.lvlipb + * Delete \\\vi.lib\\LabVIEW Icon API + * Set LocalHost.LibraryPaths in your labview.ini file to the location of this project. For example:* + * LocalHost.LibraryPaths="C:\\dev\\labview-icon-editor" +3. Open lv_icon_editor.lvproj in LabVIEW. +4. The top-level VI is in the Project Explorer at __My Computer » resource/plugins » lv_icon.lvlib » lv_icon.vi__. + +## Distribution Guide + +Complete the following steps to distribute your custom icon editor to another machine. + +### Automated process + +This automated build process will follow these steps: + +1. Apply the dependencies +2. Run the unit test, +build the icon editor packed project library + +1. Open powershell in *Admin* mode and navigate to *.pipeline\scripts* from your github repo. +2. Modify the following command to point to your github repo and run it: *.\build.ps1 -RelativePath "C:\labview-icon-editor"* +3. A VI package named *ni_icon_editor-x.x.x.x* will be built on *builds\VI Package*. +4. You can now install this VI package on any LabVIEW version after 2020. + +*NOTE: The VI package makes no backup of your current lv_icon.lvlibp because the VI Package itself contains a zip file with all combinations of lv_icon.lvlibp for all LabVIEW versions and bitnesses, which gets deployed to your LabVIEW application files on uninstall. This ensures that a user doesnt get locked out of his icon editor and having to copy it from another LabVIEW installation if somehow he deletes the backup he did manually.* + +### Manual process + +First, build the __Editor Packed Library__ build specification in the project to create __lv_icon.lvlibp__. + +Then, on the machine where you want to install your custom icon editor: +1. Rename __\\\resource\\plugins\\lv_icon.lvlibp__, the shipping icon editor, to __lv_icon.lvlibp.ship__ to "hide" it. +2. Archive __\\\vi.lib\\LabVIEW Icon API__ to preserve the shipping copy. Use your archive program of choice (e.g. 7-Zip). +3. Copy the packed library and support files that you developed with this project into the \ directory: + - \\\resource\\plugins\\lv_icon.lvlibp + - \\\vi.lib\\LabVIEW Icon API\\* + +## CI using an Azure DevOps pipeline + +An Azure Devops pipeline is used as an additional check to approve pull requests from *feature* to *development* branches. This pipeline runs the unit tests, builds the packed project libraries for both 32 and 64 bit LabVIEW, and builds the VI Package. + +## CI using github actions + +An example of a github action that can manually trigger a CI/CD workflow is located at "C:\labview-icon-editor\.github\workflows\Build VI packages.yml" + + From 24ee310fb76de6e10b0fccd99d9efbc66e342091 Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Wed, 11 Dec 2024 12:48:51 -0700 Subject: [PATCH 3/8] twerw --- README - Copy - Copy.md | 80 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 README - Copy - Copy.md diff --git a/README - Copy - Copy.md b/README - Copy - Copy.md new file mode 100644 index 0000000..35a4bca --- /dev/null +++ b/README - Copy - Copy.md @@ -0,0 +1,80 @@ +# Icon Editor for LabVIEW # + +This repo contains the source files and automated build tools for the LabVIEW icon editor. +You can use this code as a starting point for creating a custom icon editor. Refer to the [CONTRIBUTING](CONTRIBUTING.md) document for information about submitting changes for inclusion with future versions of LabVIEW. + +## Compatible LabVIEW Versions + +LabVIEW source is saved in 21.0 (__LabVIEW 2021__) format. Either LabVIEW 2021 or LabVIEW 2024 can be used to do development work. + +To build using the automated build process, ensure you have LabVIEW 2021 *both 32 and 64 bits* installed, latest VIPM, and apply the dependencies located on *Tooling\deployment\Dependencies.vipc* to both LabVIEW versions. + +## Editing Guide + +Because the icon editor is part of the LabVIEW development environment, you need to make changes to installed files before editing this project. There is an manual process, and an automated process made following it for ease of use. + +### Automated process + +Before following this process, create a backup of the following files and folder: + - \\\resource\\plugins\\lv_icon.lvlibp + - \\\vi.lib\\LabVIEW Icon API\\* + +After cloning the repo into a development location, and applying the dependencies located on *Tooling\deployment\Dependencies.vipc* to LabVIEW 2021 32 and 64 bits, follow this process to use the automation layer. + +1. Open Powershell in *Admin* mode and navigate to *.pipeline\scripts* from your github repo. +2. Modify the following command to point to your github repo and run it: *.\DevelopmentMode.ps1 -RelativePath "C:\labview-icon-editor"* +3. Open lv_icon_editor.lvproj in LabVIEW. +4. The top-level VI is in the Project Explorer at __My Computer » resource/plugins » lv_icon.lvlib » lv_icon.vi__. + +### Manual process + +Complete the following steps to edit this project: +1. Clone this repo into a development location (e.g., C:\dev). +2. Run __Tooling\Prepare LV to Use Icon Editor Source.vi__. +This will perform the following steps, which you can alternatively perform manually: + * Delete \\\resource\\plugins\\lv_icon.lvlipb + * Delete \\\vi.lib\\LabVIEW Icon API + * Set LocalHost.LibraryPaths in your labview.ini file to the location of this project. For example:* + * LocalHost.LibraryPaths="C:\\dev\\labview-icon-editor" +3. Open lv_icon_editor.lvproj in LabVIEW. +4. The top-level VI is in the Project Explorer at __My Computer » resource/plugins » lv_icon.lvlib » lv_icon.vi__. + +## Distribution Guide + +Complete the following steps to distribute your custom icon editor to another machine. + +### Automated process + +This automated build process will follow these steps: + +1. Apply the dependencies +2. Run the unit test, +build the icon editor packed project library + +1. Open powershell in *Admin* mode and navigate to *.pipeline\scripts* from your github repo. +2. Modify the following command to point to your github repo and run it: *.\build.ps1 -RelativePath "C:\labview-icon-editor"* +3. A VI package named *ni_icon_editor-x.x.x.x* will be built on *builds\VI Package*. +4. You can now install this VI package on any LabVIEW version after 2020. + +*NOTE: The VI package makes no backup of your current lv_icon.lvlibp because the VI Package itself contains a zip file with all combinations of lv_icon.lvlibp for all LabVIEW versions and bitnesses, which gets deployed to your LabVIEW application files on uninstall. This ensures that a user doesnt get locked out of his icon editor and having to copy it from another LabVIEW installation if somehow he deletes the backup he did manually.* + +### Manual process + +First, build the __Editor Packed Library__ build specification in the project to create __lv_icon.lvlibp__. + +Then, on the machine where you want to install your custom icon editor: +1. Rename __\\\resource\\plugins\\lv_icon.lvlibp__, the shipping icon editor, to __lv_icon.lvlibp.ship__ to "hide" it. +2. Archive __\\\vi.lib\\LabVIEW Icon API__ to preserve the shipping copy. Use your archive program of choice (e.g. 7-Zip). +3. Copy the packed library and support files that you developed with this project into the \ directory: + - \\\resource\\plugins\\lv_icon.lvlibp + - \\\vi.lib\\LabVIEW Icon API\\* + +## CI using an Azure DevOps pipeline + +An Azure Devops pipeline is used as an additional check to approve pull requests from *feature* to *development* branches. This pipeline runs the unit tests, builds the packed project libraries for both 32 and 64 bit LabVIEW, and builds the VI Package. + +## CI using github actions + +An example of a github action that can manually trigger a CI/CD workflow is located at "C:\labview-icon-editor\.github\workflows\Build VI packages.yml" + + From 0cede358a83da65cac38201c9891f83ea1a0b9e1 Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Wed, 11 Dec 2024 12:58:46 -0700 Subject: [PATCH 4/8] something --- README - Copy - Copy.md | 80 ----------------------------------------- 1 file changed, 80 deletions(-) delete mode 100644 README - Copy - Copy.md diff --git a/README - Copy - Copy.md b/README - Copy - Copy.md deleted file mode 100644 index 35a4bca..0000000 --- a/README - Copy - Copy.md +++ /dev/null @@ -1,80 +0,0 @@ -# Icon Editor for LabVIEW # - -This repo contains the source files and automated build tools for the LabVIEW icon editor. -You can use this code as a starting point for creating a custom icon editor. Refer to the [CONTRIBUTING](CONTRIBUTING.md) document for information about submitting changes for inclusion with future versions of LabVIEW. - -## Compatible LabVIEW Versions - -LabVIEW source is saved in 21.0 (__LabVIEW 2021__) format. Either LabVIEW 2021 or LabVIEW 2024 can be used to do development work. - -To build using the automated build process, ensure you have LabVIEW 2021 *both 32 and 64 bits* installed, latest VIPM, and apply the dependencies located on *Tooling\deployment\Dependencies.vipc* to both LabVIEW versions. - -## Editing Guide - -Because the icon editor is part of the LabVIEW development environment, you need to make changes to installed files before editing this project. There is an manual process, and an automated process made following it for ease of use. - -### Automated process - -Before following this process, create a backup of the following files and folder: - - \\\resource\\plugins\\lv_icon.lvlibp - - \\\vi.lib\\LabVIEW Icon API\\* - -After cloning the repo into a development location, and applying the dependencies located on *Tooling\deployment\Dependencies.vipc* to LabVIEW 2021 32 and 64 bits, follow this process to use the automation layer. - -1. Open Powershell in *Admin* mode and navigate to *.pipeline\scripts* from your github repo. -2. Modify the following command to point to your github repo and run it: *.\DevelopmentMode.ps1 -RelativePath "C:\labview-icon-editor"* -3. Open lv_icon_editor.lvproj in LabVIEW. -4. The top-level VI is in the Project Explorer at __My Computer » resource/plugins » lv_icon.lvlib » lv_icon.vi__. - -### Manual process - -Complete the following steps to edit this project: -1. Clone this repo into a development location (e.g., C:\dev). -2. Run __Tooling\Prepare LV to Use Icon Editor Source.vi__. -This will perform the following steps, which you can alternatively perform manually: - * Delete \\\resource\\plugins\\lv_icon.lvlipb - * Delete \\\vi.lib\\LabVIEW Icon API - * Set LocalHost.LibraryPaths in your labview.ini file to the location of this project. For example:* - * LocalHost.LibraryPaths="C:\\dev\\labview-icon-editor" -3. Open lv_icon_editor.lvproj in LabVIEW. -4. The top-level VI is in the Project Explorer at __My Computer » resource/plugins » lv_icon.lvlib » lv_icon.vi__. - -## Distribution Guide - -Complete the following steps to distribute your custom icon editor to another machine. - -### Automated process - -This automated build process will follow these steps: - -1. Apply the dependencies -2. Run the unit test, -build the icon editor packed project library - -1. Open powershell in *Admin* mode and navigate to *.pipeline\scripts* from your github repo. -2. Modify the following command to point to your github repo and run it: *.\build.ps1 -RelativePath "C:\labview-icon-editor"* -3. A VI package named *ni_icon_editor-x.x.x.x* will be built on *builds\VI Package*. -4. You can now install this VI package on any LabVIEW version after 2020. - -*NOTE: The VI package makes no backup of your current lv_icon.lvlibp because the VI Package itself contains a zip file with all combinations of lv_icon.lvlibp for all LabVIEW versions and bitnesses, which gets deployed to your LabVIEW application files on uninstall. This ensures that a user doesnt get locked out of his icon editor and having to copy it from another LabVIEW installation if somehow he deletes the backup he did manually.* - -### Manual process - -First, build the __Editor Packed Library__ build specification in the project to create __lv_icon.lvlibp__. - -Then, on the machine where you want to install your custom icon editor: -1. Rename __\\\resource\\plugins\\lv_icon.lvlibp__, the shipping icon editor, to __lv_icon.lvlibp.ship__ to "hide" it. -2. Archive __\\\vi.lib\\LabVIEW Icon API__ to preserve the shipping copy. Use your archive program of choice (e.g. 7-Zip). -3. Copy the packed library and support files that you developed with this project into the \ directory: - - \\\resource\\plugins\\lv_icon.lvlibp - - \\\vi.lib\\LabVIEW Icon API\\* - -## CI using an Azure DevOps pipeline - -An Azure Devops pipeline is used as an additional check to approve pull requests from *feature* to *development* branches. This pipeline runs the unit tests, builds the packed project libraries for both 32 and 64 bit LabVIEW, and builds the VI Package. - -## CI using github actions - -An example of a github action that can manually trigger a CI/CD workflow is located at "C:\labview-icon-editor\.github\workflows\Build VI packages.yml" - - From a9dfd1ed13a28e0318fe86c9ac19b0fc422e393f Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Wed, 11 Dec 2024 13:25:04 -0700 Subject: [PATCH 5/8] Delete SECURITY - Copy.md --- SECURITY - Copy.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 SECURITY - Copy.md diff --git a/SECURITY - Copy.md b/SECURITY - Copy.md deleted file mode 100644 index ce102ab..0000000 --- a/SECURITY - Copy.md +++ /dev/null @@ -1,19 +0,0 @@ - - -# Security - -NI views the security of our software products as an important part of our commitment to our users. This includes source code repositories managed through the [NI](https://github.com/ni) GitHub organization. - -## Reporting Security Issues - -We encourage you to report security vulnerabilities to us privately so we can follow the principle of [Coordinated Vulnerability Disclosure (CVD)](https://vuls.cert.org/confluence/display/CVD). This allows us time to thoroughly investigate security issues and publicly disclose them when appropriate. - -**Please do not report security vulnerabilities through public GitHub issues.** - -Instead, please report them by sending an email to [security@ni.com](mailto:security@ni.com) with sufficient details about the type of issue, the impact of the issue, and how to reproduce the issue. You may use the [NI PGP key](https://www.ni.com/en/support/security/pgp.html) to encrypt any sensitive communications you send to us. When you notify us of a potential security issue, our remediation process includes acknowledging receipt and coordinating any necessary response activities with you. - -## Learn More - -To learn more about NI Security, please see [https://ni.com/security](https://ni.com/security) - - \ No newline at end of file From 18f704686449d967bb25da303e907e47b420d80b Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Fri, 13 Dec 2024 18:18:20 -0700 Subject: [PATCH 6/8] Delete CODE_OF_CONDUCT - Copy.md --- CODE_OF_CONDUCT - Copy.md | 128 -------------------------------------- 1 file changed, 128 deletions(-) delete mode 100644 CODE_OF_CONDUCT - Copy.md diff --git a/CODE_OF_CONDUCT - Copy.md b/CODE_OF_CONDUCT - Copy.md deleted file mode 100644 index c4453b8..0000000 --- a/CODE_OF_CONDUCT - Copy.md +++ /dev/null @@ -1,128 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -We as members, contributors, and leaders pledge to make participation in our -community a harassment-free experience for everyone, regardless of age, body -size, visible or invisible 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. - -We pledge to act and interact in ways that contribute to an open, welcoming, -diverse, inclusive, and healthy community. - -## Our Standards - -Examples of behavior that contributes to a positive environment for our -community include: - -* Demonstrating empathy and kindness toward other people -* Being respectful of differing opinions, viewpoints, and experiences -* Giving and gracefully accepting constructive feedback -* Accepting responsibility and apologizing to those affected by our mistakes, - and learning from the experience -* Focusing on what is best not just for us as individuals, but for the - overall community - -Examples of unacceptable behavior include: - -* The use of sexualized language or imagery, and sexual attention or - advances of any kind -* Trolling, insulting or derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or email - address, without their explicit permission -* Other conduct which could reasonably be considered inappropriate in a - professional setting - -## Enforcement Responsibilities - -Community leaders are responsible for clarifying and enforcing our standards of -acceptable behavior and will take appropriate and fair corrective action in -response to any behavior that they deem inappropriate, threatening, offensive, -or harmful. - -Community leaders 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, and will communicate reasons for moderation -decisions when appropriate. - -## Scope - -This Code of Conduct applies within all community spaces, and also applies when -an individual is officially representing the community in public spaces. -Examples of representing our community include using an official e-mail address, -posting via an official social media account, or acting as an appointed -representative at an online or offline event. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported to the community leaders responsible for enforcement at -Elijah.Kerry@ni.com. -All complaints will be reviewed and investigated promptly and fairly. - -All community leaders are obligated to respect the privacy and security of the -reporter of any incident. - -## Enforcement Guidelines - -Community leaders will follow these Community Impact Guidelines in determining -the consequences for any action they deem in violation of this Code of Conduct: - -### 1. Correction - -**Community Impact**: Use of inappropriate language or other behavior deemed -unprofessional or unwelcome in the community. - -**Consequence**: A private, written warning from community leaders, providing -clarity around the nature of the violation and an explanation of why the -behavior was inappropriate. A public apology may be requested. - -### 2. Warning - -**Community Impact**: A violation through a single incident or series -of actions. - -**Consequence**: A warning with consequences for continued behavior. No -interaction with the people involved, including unsolicited interaction with -those enforcing the Code of Conduct, for a specified period of time. This -includes avoiding interactions in community spaces as well as external channels -like social media. Violating these terms may lead to a temporary or -permanent ban. - -### 3. Temporary Ban - -**Community Impact**: A serious violation of community standards, including -sustained inappropriate behavior. - -**Consequence**: A temporary ban from any sort of interaction or public -communication with the community for a specified period of time. No public or -private interaction with the people involved, including unsolicited interaction -with those enforcing the Code of Conduct, is allowed during this period. -Violating these terms may lead to a permanent ban. - -### 4. Permanent Ban - -**Community Impact**: Demonstrating a pattern of violation of community -standards, including sustained inappropriate behavior, harassment of an -individual, or aggression toward or disparagement of classes of individuals. - -**Consequence**: A permanent ban from any sort of public interaction within -the community. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 2.0, available at -https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. - -Community Impact Guidelines were inspired by [Mozilla's code of conduct -enforcement ladder](https://github.com/mozilla/diversity). - -[homepage]: https://www.contributor-covenant.org - -For answers to common questions about this code of conduct, see the FAQ at -https://www.contributor-covenant.org/faq. Translations are available at -https://www.contributor-covenant.org/translations. From c5a7d99cf9e6ea04f9e39f13b750027863841701 Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Fri, 13 Dec 2024 18:36:56 -0700 Subject: [PATCH 7/8] Create CODE_OF_CONDUCT - Copy.md --- CODE_OF_CONDUCT - Copy.md | 128 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT - Copy.md diff --git a/CODE_OF_CONDUCT - Copy.md b/CODE_OF_CONDUCT - Copy.md new file mode 100644 index 0000000..c4453b8 --- /dev/null +++ b/CODE_OF_CONDUCT - Copy.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible 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. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders 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, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +Elijah.Kerry@ni.com. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From b89316da67a990ff65575521b0cc356d3fc350bd Mon Sep 17 00:00:00 2001 From: sergiov-ni Date: Fri, 13 Dec 2024 18:45:53 -0700 Subject: [PATCH 8/8] Delete CODE_OF_CONDUCT - Copy.md --- CODE_OF_CONDUCT - Copy.md | 128 -------------------------------------- 1 file changed, 128 deletions(-) delete mode 100644 CODE_OF_CONDUCT - Copy.md diff --git a/CODE_OF_CONDUCT - Copy.md b/CODE_OF_CONDUCT - Copy.md deleted file mode 100644 index c4453b8..0000000 --- a/CODE_OF_CONDUCT - Copy.md +++ /dev/null @@ -1,128 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -We as members, contributors, and leaders pledge to make participation in our -community a harassment-free experience for everyone, regardless of age, body -size, visible or invisible 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. - -We pledge to act and interact in ways that contribute to an open, welcoming, -diverse, inclusive, and healthy community. - -## Our Standards - -Examples of behavior that contributes to a positive environment for our -community include: - -* Demonstrating empathy and kindness toward other people -* Being respectful of differing opinions, viewpoints, and experiences -* Giving and gracefully accepting constructive feedback -* Accepting responsibility and apologizing to those affected by our mistakes, - and learning from the experience -* Focusing on what is best not just for us as individuals, but for the - overall community - -Examples of unacceptable behavior include: - -* The use of sexualized language or imagery, and sexual attention or - advances of any kind -* Trolling, insulting or derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or email - address, without their explicit permission -* Other conduct which could reasonably be considered inappropriate in a - professional setting - -## Enforcement Responsibilities - -Community leaders are responsible for clarifying and enforcing our standards of -acceptable behavior and will take appropriate and fair corrective action in -response to any behavior that they deem inappropriate, threatening, offensive, -or harmful. - -Community leaders 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, and will communicate reasons for moderation -decisions when appropriate. - -## Scope - -This Code of Conduct applies within all community spaces, and also applies when -an individual is officially representing the community in public spaces. -Examples of representing our community include using an official e-mail address, -posting via an official social media account, or acting as an appointed -representative at an online or offline event. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported to the community leaders responsible for enforcement at -Elijah.Kerry@ni.com. -All complaints will be reviewed and investigated promptly and fairly. - -All community leaders are obligated to respect the privacy and security of the -reporter of any incident. - -## Enforcement Guidelines - -Community leaders will follow these Community Impact Guidelines in determining -the consequences for any action they deem in violation of this Code of Conduct: - -### 1. Correction - -**Community Impact**: Use of inappropriate language or other behavior deemed -unprofessional or unwelcome in the community. - -**Consequence**: A private, written warning from community leaders, providing -clarity around the nature of the violation and an explanation of why the -behavior was inappropriate. A public apology may be requested. - -### 2. Warning - -**Community Impact**: A violation through a single incident or series -of actions. - -**Consequence**: A warning with consequences for continued behavior. No -interaction with the people involved, including unsolicited interaction with -those enforcing the Code of Conduct, for a specified period of time. This -includes avoiding interactions in community spaces as well as external channels -like social media. Violating these terms may lead to a temporary or -permanent ban. - -### 3. Temporary Ban - -**Community Impact**: A serious violation of community standards, including -sustained inappropriate behavior. - -**Consequence**: A temporary ban from any sort of interaction or public -communication with the community for a specified period of time. No public or -private interaction with the people involved, including unsolicited interaction -with those enforcing the Code of Conduct, is allowed during this period. -Violating these terms may lead to a permanent ban. - -### 4. Permanent Ban - -**Community Impact**: Demonstrating a pattern of violation of community -standards, including sustained inappropriate behavior, harassment of an -individual, or aggression toward or disparagement of classes of individuals. - -**Consequence**: A permanent ban from any sort of public interaction within -the community. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 2.0, available at -https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. - -Community Impact Guidelines were inspired by [Mozilla's code of conduct -enforcement ladder](https://github.com/mozilla/diversity). - -[homepage]: https://www.contributor-covenant.org - -For answers to common questions about this code of conduct, see the FAQ at -https://www.contributor-covenant.org/faq. Translations are available at -https://www.contributor-covenant.org/translations.