-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
226 additions
and
226 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,76 +1,76 @@ | ||
| # Contributor Covenant Code of Conduct | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to make 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. | ||
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment | ||
| include: | ||
|
|
||
| * Using welcoming and inclusive language | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| * 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 | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ## Our Responsibilities | ||
|
|
||
| Project maintainers are responsible for clarifying the standards of acceptable | ||
| behavior and are expected to take appropriate and fair corrective action in | ||
| response to any instances of unacceptable behavior. | ||
|
|
||
| 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 behaviors that they deem inappropriate, | ||
| threatening, offensive, or harmful. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies within all project spaces, and it also applies when | ||
| an individual is representing the project or its community in public spaces. | ||
| 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 representative at an online or offline event. Representation of | ||
| a project may be further defined and clarified by project maintainers. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team. All complaints will be reviewed and | ||
| investigated and will result in a response that is deemed necessary and appropriate | ||
| to the circumstances. The project team is obligated to maintain confidentiality with | ||
| regard to the reporter of an incident. Further details of specific enforcement | ||
| policies may be posted separately. | ||
|
|
||
| Project maintainers who do not follow or enforce the Code of Conduct in good | ||
| faith may face temporary or permanent repercussions as determined by other | ||
| members of the project's leadership. | ||
|
|
||
| ## Attribution | ||
|
|
||
| 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 | ||
| # Contributor Covenant Code of Conduct | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to make 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. | ||
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment | ||
| include: | ||
|
|
||
| * Using welcoming and inclusive language | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| * 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 | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ## Our Responsibilities | ||
|
|
||
| Project maintainers are responsible for clarifying the standards of acceptable | ||
| behavior and are expected to take appropriate and fair corrective action in | ||
| response to any instances of unacceptable behavior. | ||
|
|
||
| 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 behaviors that they deem inappropriate, | ||
| threatening, offensive, or harmful. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies within all project spaces, and it also applies when | ||
| an individual is representing the project or its community in public spaces. | ||
| 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 representative at an online or offline event. Representation of | ||
| a project may be further defined and clarified by project maintainers. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team. All complaints will be reviewed and | ||
| investigated and will result in a response that is deemed necessary and appropriate | ||
| to the circumstances. The project team is obligated to maintain confidentiality with | ||
| regard to the reporter of an incident. Further details of specific enforcement | ||
| policies may be posted separately. | ||
|
|
||
| Project maintainers who do not follow or enforce the Code of Conduct in good | ||
| faith may face temporary or permanent repercussions as determined by other | ||
| members of the project's leadership. | ||
|
|
||
| ## Attribution | ||
|
|
||
| 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,43 +1,43 @@ | ||
| # Contribution guidelines | ||
|
|
||
| ## How can I contribute? | ||
|
|
||
| 1. [Reporting bugs or feature ideas](https://github.com/Lieturd/aperture-control-recipes/issues): It's definitely helpful to know what kind of problems people are having, or would like to see solved. Even if you yourself don't know the solutions, someone else might come up with one. | ||
| 2. Creating recipes to the [Aperture Control Recipes](https://github.com/Lieturd/aperture-control-recipes) -collection | ||
| 3. Spreading the word: The more people know of Aperture Control, the more time we save together, and the more likely it is for us to find more people able and willing to contribute more useful things. | ||
| 4. Testing the recipes: See if the contributions work for you, and report if they don't. | ||
|
|
||
|
|
||
| ## Recipes | ||
|
|
||
| Anything you contribute must be contributed with the license of Aperture Control, BSD 3-clause, or a more permissive license (e.g. CC-0, Public Domain, WTFPL). If no other license declaration is in the file when it is added, it is published with the BSD 3-clause license. | ||
|
|
||
| Additionally these rules apply to everything contributed here: | ||
|
|
||
| - Nothing illegal or shady | ||
| - Contributions should be generally useful, i.e. not specific to YOUR workflow | ||
| - The task can be small or large, as long as it seems generic enough and doesn't do a lot of seemingly unrelated things, e.g. changing multiple unrelated settings should be done via multiple recipes, even if you might want all of them changed for yourself | ||
| - Do not add any order numbers or similar into the scripts, whoever takes them into use will determine the order they want to run them in | ||
| - If there's any prerequisites for the scripts, e.g. [Chocolatey](https://chocolatey.org/), make it clear in the script's comments | ||
| - Try to stick to a max line length of 88 characters, unless absolutely necessary, also in recipe comments | ||
| - Follow the [Code of Conduct](./CODE_OF_CONDUCT.md) | ||
|
|
||
| Feel free to [send PRs](https://github.com/Lieturd/aperture-control-recipes/pull/new/master) to add files to `cmd-scripts`, `ps-scripts`, and `registry`. However, try to ensure the filename gives a good idea as to what it is for, and add a "plain English" explanation about it in the `README.md`. Additionally if there's any extra details you need to explain, e.g. about how to determine the correct values for some variables, do so in the file with clear instructions. | ||
|
|
||
| In PowerShell files you can include comments by prefixing the comments with `#`, so: | ||
|
|
||
| ```powershell | ||
| # This configures ... | ||
| ``` | ||
|
|
||
| In Cmd scripts you can include comments by prefixing the lines with `rem`, so: | ||
|
|
||
| ```batch | ||
| rem This helps ... | ||
| ``` | ||
|
|
||
| In Registry files you can include comments (after the `Windows Registry Editor ...` line) by prefixing the comments with `;`, so: | ||
|
|
||
| ```Windows Registry Entries | ||
| ; This disables ... | ||
| ``` | ||
| # Contribution guidelines | ||
|
|
||
| ## How can I contribute? | ||
|
|
||
| 1. [Reporting bugs or feature ideas](https://github.com/Lieturd/aperture-control-recipes/issues): It's definitely helpful to know what kind of problems people are having, or would like to see solved. Even if you yourself don't know the solutions, someone else might come up with one. | ||
| 2. Creating recipes to the [Aperture Control Recipes](https://github.com/Lieturd/aperture-control-recipes) -collection | ||
| 3. Spreading the word: The more people know of Aperture Control, the more time we save together, and the more likely it is for us to find more people able and willing to contribute more useful things. | ||
| 4. Testing the recipes: See if the contributions work for you, and report if they don't. | ||
|
|
||
|
|
||
| ## Recipes | ||
|
|
||
| Anything you contribute must be contributed with the license of Aperture Control, BSD 3-clause, or a more permissive license (e.g. CC-0, Public Domain, WTFPL). If no other license declaration is in the file when it is added, it is published with the BSD 3-clause license. | ||
|
|
||
| Additionally these rules apply to everything contributed here: | ||
|
|
||
| - Nothing illegal or shady | ||
| - Contributions should be generally useful, i.e. not specific to YOUR workflow | ||
| - The task can be small or large, as long as it seems generic enough and doesn't do a lot of seemingly unrelated things, e.g. changing multiple unrelated settings should be done via multiple recipes, even if you might want all of them changed for yourself | ||
| - Do not add any order numbers or similar into the scripts, whoever takes them into use will determine the order they want to run them in | ||
| - If there's any prerequisites for the scripts, e.g. [Chocolatey](https://chocolatey.org/), make it clear in the script's comments | ||
| - Try to stick to a max line length of 88 characters, unless absolutely necessary, also in recipe comments | ||
| - Follow the [Code of Conduct](./CODE_OF_CONDUCT.md) | ||
|
|
||
| Feel free to [send PRs](https://github.com/Lieturd/aperture-control-recipes/pull/new/master) to add files to `cmd-scripts`, `ps-scripts`, and `registry`. However, try to ensure the filename gives a good idea as to what it is for, and add a "plain English" explanation about it in the `README.md`. Additionally if there's any extra details you need to explain, e.g. about how to determine the correct values for some variables, do so in the file with clear instructions. | ||
|
|
||
| In PowerShell files you can include comments by prefixing the comments with `#`, so: | ||
|
|
||
| ```powershell | ||
| # This configures ... | ||
| ``` | ||
|
|
||
| In Cmd scripts you can include comments by prefixing the lines with `rem`, so: | ||
|
|
||
| ```batch | ||
| rem This helps ... | ||
| ``` | ||
|
|
||
| In Registry files you can include comments (after the `Windows Registry Editor ...` line) by prefixing the comments with `;`, so: | ||
|
|
||
| ```Windows Registry Entries | ||
| ; This disables ... | ||
| ``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,13 @@ | ||
| # "New BSD" / "BSD 3-clause" -license | ||
|
|
||
| Copyright 2019 Lieturd OÜ | ||
|
|
||
| Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: | ||
|
|
||
| 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. | ||
|
|
||
| 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. | ||
|
|
||
| 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. | ||
|
|
||
| THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. | ||
| # "New BSD" / "BSD 3-clause" -license | ||
|
|
||
| Copyright 2019 Lieturd OÜ | ||
|
|
||
| Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: | ||
|
|
||
| 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. | ||
|
|
||
| 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. | ||
|
|
||
| 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. | ||
|
|
||
| THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
Oops, something went wrong.