Updated repo configuration files (#5)

* Update repo configuration

* Update repo config

.github/CODEOWNERS

@@ -1,43 +1,43 @@
-# Explanation of this file
-# https://help.github.com/articles/about-codeowners/
-
-*    @aessing
-
-###############################################################################
-# This is a comment.
-# Each line is a file pattern followed by one or more owners.
-
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
-#*       @global-owner1 @global-owner2
-
-# Order is important; the last matching pattern takes the most
-# precedence. When someone opens a pull request that only
-# modifies JS files, only @js-owner and not the global
-# owner(s) will be requested for a review.
-#*.js    @js-owner
-
-# You can also use email addresses if you prefer. They'll be
-# used to look up users just like we do for commit author
-# emails.
-#*.go docs@example.com
-
-# In this example, @doctocat owns any files in the build/logs
-# directory at the root of the repository and any of its
-# subdirectories.
-#/build/logs/ @doctocat
-
-# The `docs/*` pattern will match files like
-# `docs/getting-started.md` but not further nested files like
-# `docs/build-app/troubleshooting.md`.
-#docs/*  docs@example.com
-
-# In this example, @octocat owns any file in an apps directory
-# anywhere in your repository.
-#apps/ @octocat
-
-# In this example, @doctocat owns any file in the `/docs`
-# directory in the root of your repository.
+# Explanation of this file
+# https://help.github.com/articles/about-codeowners/
+
+*    @aessing
+
+###############################################################################
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+#*       @global-owner1 @global-owner2
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+#*.js    @js-owner
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+#*.go docs@example.com
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+#/build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+#docs/*  docs@example.com
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+#apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository.
 #/docs/ @doctocat

.github/FUNDING.yml

@@ -1 +1 @@
-github: aessing
+github: aessing

.github/ISSUE_TEMPLATE/bug_report.md

@@ -3,7 +3,7 @@ name: Bug report
 about: Create a report to help to improve the project
 title: ''
 labels: 'bug'
-assignees: '@aessing'
+assignees: ''
 ---
 
 <!-- Please provide a general summary of the issue in the title above -->

.github/ISSUE_TEMPLATE/critical_bug_report.md

@@ -3,7 +3,7 @@ name: Critical bug report
 about: Create a report for a critical issue
 title: ''
 labels: 'bug, critical'
-assignees: '@aessing'
+assignees: ''
 ---
 
 <!-- Please provide a general summary of the issue in the title above -->

.github/ISSUE_TEMPLATE/documentation_issue.md

@@ -3,7 +3,7 @@ name: Documentation issue
 about: Report issues in the documentation
 title: ''
 labels: 'documentation'
-assignees: '@aessing'
+assignees: ''
 ---
 
 <!-- Please provide a general summary of the issue in the title above -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -3,7 +3,7 @@ name: Feature request
 about: Suggest an idea for this project
 title: ''
 labels: 'feature'
-assignees: '@aessing'
+assignees: ''
 ---
 
 <!-- Please provide a general summary of the feature request in the title above -->

.github/ISSUE_TEMPLATE/question.md

@@ -3,7 +3,7 @@ name: Question
 about: You have a question about the project?
 title: ''
 labels: 'question'
-assignees: '@aessing'
+assignees: ''
 ---
 
-<!-- Please ask your question and provide as much detail as you can. So you help me to provide the best possible answer -->
+<!-- Please ask your question and provide as much detail as you can. So you help us to provide the best possible answer -->

.github/dependabot.yml

@@ -11,4 +11,4 @@ updates:
       include: "scope"
     labels:
       - "dependencies"
-    open-pull-requests-limit: 10
+    open-pull-requests-limit: 10

.github/pull_request_template.md

@@ -1,24 +1,24 @@
-<!-- Please provide a general summary of your changes in the Title above -->
+<!-- Please provide a general summary of your changes in the title above -->
 
 # Pull Request
 Thank you for your contribution.
 
 Before submitting this Pull Request, please make sure: _Put an `x` in the boxes that apply_
-- [ ] You reviewed my [guidelines for contributing](../CONTRIBUTING.md) to this repository
+- [ ] You reviewed our [guidelines for contributing](../CONTRIBUTING.md) to this repository
 - [ ] Does an issue exists which is related to this Pull Request <!--- This project only accepts Pull Requests related to open issues -->
 - [ ] Your code builds clean without any errors or warnings
 - [ ] You are using approved terminology
 - [ ] You have added necessary documentation (if appropriate)
 - [ ] You have added unit tests
 
 ## Proposed changes
-<!-- Please describe the big picture of your changes here to communicate why I should accept this Pull Request. Why is this change required? What problem does it solve? -->
+<!-- Please describe the big picture of your changes here to communicate to the maintainers why we should accept this Pull Request. Why is this change required? What problem does it solve? -->
 
 ## Types of changes
 What types of changes does your change introduce? _Put an `x` in the boxes that apply_
 - [ ] New feature (adds functionality)   <!-- If suggesting a new feature or change, please discuss it in an issue first -->
 - [ ] Bugfix (fixes an issue)            <!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
-- [ ] Security (fixes an security issue) | Please have a look at my [Security Policy](../SECURITY.md) first.
+- [ ] Security (fixes an security issue) | Please have a look at our [Security Policy](../SECURITY.md) first.
 - [ ] Code style cleaning or Refactoring (formatting, renaming, restructuring, etc.)
 - [ ] Documentation Update
 - [ ] Other (please describe):

CODE_OF_CONDUCT.md

@@ -1,6 +1,6 @@
 # :cop: Code of Conduct
 
-This Code of Conduct outlines expectations for participation in the community, as well as steps for reporting unacceptable behavior. I am committed to providing a welcoming and inspiring community for all. People violating this code of conduct may be banned from the community.
+This Code of Conduct outlines expectations for participation in the community, as well as steps for reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all. People violating this code of conduct may be banned from the community.
 
 This community strive to:
 
@@ -17,11 +17,11 @@ This community strive to:
   - Other conduct which could reasonably be considered inappropriate in a professional setting.
   - Advocating for or encouraging any of the above behaviors.
 - __Understand disagreements__: Disagreements, both social and technical, are useful learning opportunities. Seek to understand the other viewpoints and resolve differences constructively.
-- This code is not exhaustive or complete. It serves to capture the common understanding of a productive, collaborative environment. I expect the code to be followed in spirit as much as in the letter.
+- This code is not exhaustive or complete. It serves to capture the common understanding of a productive, collaborative environment. We expect the code to be followed in spirit as much as in the letter.
 
 ## :telescope: Scope
 
-This code of conduct applies to all repos and communities for my projects regardless of whether or not the repo explicitly calls out its use of this code. The code also applies in public spaces when an individual is representing a project or its community. Examples 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.
+This code of conduct applies to all repos and communities for our projects regardless of whether or not the repo explicitly calls out its use of this code. The code also applies in public spaces when an individual is representing a project or its community. Examples 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.
 
 ## :man_in_tuxedo: Responsibilities
 

CONTRIBUTING.md

@@ -4,7 +4,7 @@ Below is the guidance for how to report issues, propose new features, and submit
 
 ## :beetle: Before you start, file an issue
 
-Please follow this simple rule to help me stop any unnecessary effort and frustration, so we all can ensure an efficient and effective use of everyone's time - yours, mine, and the time of other community members.
+Please follow this simple rule to help us stop any unnecessary effort and frustration, so we all can ensure an efficient and effective use of everyone's time - yours, ours, and the time of other community members.
 
 > If you have a question, or do you think you have discovered an issue, or would you like to propose a new feature, etc., then find/file an issue before starting work to fix or implement it.
 >
@@ -29,10 +29,10 @@ If no existing item describes your issue/feature, great - please file a new issu
 
 Please include as much information as possible in your issue. The more information you provide, the more likely your issue/ask will be understood, accepted, and implemented.
 
-- Do not assume somebody other than you is an expert in setting up your environment and do not assume somebody else is an expert in your workflow. Please tell me as much details you can, so I can help you as good as possible!
-- What steps are needed to reproduce the issue? Assume I love to read repro steps. As much detail as you can stand is probably barely enough detail for me.
-- I prefer error message text where possible, or screenshots of errors if the error text cannot be captured.
-- If you intend to implement the fix/feature yourself, please say so! If you do not indicate you want to contribute, I assume that the issue is mine to solve.
+- Do not assume somebody other than you is an expert in setting up your environment and do not assume somebody else is an expert in your workflow. Please tell us as much details you can, so we can help you as good as possible!
+- What steps are needed to reproduce the issue? Assume we love to read repro steps. As much detail as you can stand is probably barely enough detail for us.
+- We prefer error message text where possible, or screenshots of errors if the error text cannot be captured.
+- If you intend to implement the fix/feature yourself, please say so! If you do not indicate you want to contribute, we assume that the issue is our to solve.
 
 ### :+1: Do not post "+1" comments
 
@@ -56,7 +56,7 @@ Once you have filed an issue and discussed your proposed feature/fix, it is time
 
 ### :eyeglasses: Code Review
 
-When you would like me to take a look, (even if the work is not yet fully-complete), mark the Pull Request as 'Ready For Review' so that I can review your work and provide comments, suggestions, and request changes. I would like to encourage you to use the Pull Request as tool to start a conversation around your ideas and recruit people to help if necessary. It may take several cycles, but the result will be solid, testable, conformant code that is safe to merge.
+When you would like the project team to take a look, (even if the work is not yet fully-complete), mark the Pull Request as 'Ready For Review' so that the team can review your work and provide comments, suggestions, and request changes. We would like to encourage you to use the Pull Request as tool to start a conversation around your ideas and recruit people to help if necessary. It may take several cycles, but the result will be solid, testable, conformant code that is safe to merge.
 
 ### :jigsaw: Merge
 

README.md

@@ -6,23 +6,23 @@ This repository contains a demo / example of a approval process backed by a Logi
 
 The idea is to have somebody request permissions, for example via a formular hosted in an Azure website, which will trigger a Logic App, which will start the approval process. This demo / example send the request via mail to an approver and write the request to after approval (or after the request was rejected) to a table in a Azure SQL Database and into an Azure Data Lake Store Gen 2 as a JSON.
 
-![Architecture diagram of the sample approval process](.img/architecture.png)
+![Architecture diagram of the sample approval process](.media/architecture.png)
 
 
 ## Screenshots
 
 ### The web form
-![Screenshot of the web formular to request permission](.img/web-form.png)
+![Screenshot of the web formular to request permission](.media/web-form.png)
 
 ### The Logic App flow
-![Screenshot of the approval flow build in Azure Logic App](.img/logic-app-flow.png)
+![Screenshot of the approval flow build in Azure Logic App](.media/logic-app-flow.png)
 
 
 ---
 
 ## :ambulance: Support Information
 
-For further information about this project, how to [contribute](CONTRIBUTING.md), or how to contact me, please have a look at the [support document](SUPPORT.md) of this repository. It also contains information about [security related topics](SECURITY.md), [licensing](LICENSE.md), and more.  
+For further information about this project, how to [contribute](CONTRIBUTING.md), or how to contact us, please have a look at the [support document](SUPPORT.md) of this repository. It also contains information about [security related topics](SECURITY.md), [licensing](LICENSE.md), and more.  
 
 ## :man_judge: Disclaimer
 

SECURITY.md

@@ -1,18 +1,18 @@
 # :detective: Security Policy
 
-I take the security of my software and services serious, which includes all of my repositories.
+We take the security of our software and services serious, which includes all of our repositories.
 
-If you believe you have found a security vulnerability in any of my repositories, please report it as described below.
+If you believe you have found a security vulnerability in any of our repositories, please report it as described below.
 
 ## :mega: Reporting Security Issues
 
 __Please do not report security vulnerabilities through public GitHub issues.__
 
-Instead, please report them directly via mail to me [codesec@essing.org](mailto:codesec@essing.org).
+Instead, please report them directly via mail to our [Security Team](mailto:codesec@essing.org).
 
-You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure I received your original message.
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
 
-Please include the requested information listed below (as much as you can provide) to help me better understand the nature and scope of the possible issue:
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
 
 - Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, credentials stored in code, etc.)
 - Full paths of source file(s) related to the manifestation of the issue
@@ -22,8 +22,8 @@ Please include the requested information listed below (as much as you can provid
 - Proof-of-concept or exploit code (if possible)
 - Impact of the issue, including how an attacker might exploit the issue
 
-This information will help me to understand your report more quickly.
+This information will help us to understand your report more quickly.
 
 ## :white_flag: Preferred Languages
 
-I prefer all communications to be in English.
+We prefer all communications to be in English.

SUPPORT.md

@@ -2,32 +2,21 @@
 
 ## :cop: Code of conduct
 
-My [Code of Conduct](CODE_OF_CONDUCT.md) outlines expectations for participation in the community, as well as steps for reporting unacceptable behavior. I am committed to provide a welcoming and inspiring community for all. People violating this code of conduct may be banned from the community.
+Our [Code of Conduct](CODE_OF_CONDUCT.md) outlines expectations for participation in the community, as well as steps for reporting unacceptable behavior. We are committed to provide a welcoming and inspiring community for all. People violating this code of conduct may be banned from the community.
 
-For more information, or any additional questions or comments, please contact me at [codeofconduct@essing.org](mailto:codeofconduct@essing.org)
+For more information, or any additional questions or comments, please contact us at [codeofconduct@essing.org](mailto:codeofconduct@essing.org)
 
 ## :construction_worker: Contributor's Guide
 
-In my [Contributor's Guide](CONTRIBUTING.md) you can find some guidance for how to report issues, propose new features, and submit contributions via Pull Requests. Please read it, before you start working.
+In our [Contributor's Guide](CONTRIBUTING.md) you can find some guidance for how to report issues, propose new features, and submit contributions via Pull Requests. Please read it, before you start working.
 
 ## :scroll: License
 
 You can find the license information for this repository in its [license](LICENSE.md) file.
 
 ## :detective: Security Policy
 
-I take the security of my software and services seriously, which includes all of my repositories. 
-If you believe you have found a security vulnerability in any of my repositories, please report it as described in my [Security Policy](SECURITY.md).
+We take the security of our software and services serious, which includes all of our repositories. 
+If you believe you have found a security vulnerability in any of our repositories, please report it as described in our [Security Policy](SECURITY.md).
 
-For more information, or any additional questions or comments, please contact me at [codesec@essing.org](mailto:codesec@essing.org)
-
-## :compass: Find me on the web
-
-If you have a question, or you just want to contact me, you can find and follow me on:
-
-[<img alt="Link to Andres website" src="https://img.shields.io/static/v1?label=My%20website&message=Visit%20me&labelColor=56B7E6&logoColor=ffffff&style=for-the-badge&logo=microsoft-edge" />](https://www.andre-essing.de)
-[<img alt="Link to the GitHub profile of Andre" src="https://img.shields.io/static/v1?label=GitHub&message=Follow%20me&labelColor=181717&logoColor=ffffff&style=for-the-badge&logo=GitHub" />](https://github.com/aessing) 
-[<img alt="Link to the LinkedIn profile of Andre" src="https://img.shields.io/static/v1?label=LinkedIn&message=Follow%20me&labelColor=0077B5&logoColor=ffffff&style=for-the-badge&logo=linkedin" />](https://www.linkedin.com/in/aessing/)
-[<img alt="Link to the Twitter profile of Andre" src="https://img.shields.io/static/v1?label=Twitter&message=Follow%20me&labelColor=1DA1F2&logoColor=ffffff&style=for-the-badge&logo=twitter" />](https://twitter.com/aessing)
-
-Or just send a mail to [opensource@essing.org](mailto:opensource@essing.org)
+For more information, or any additional questions or comments, please contact us at [codesec@essing.org](mailto:codesec@essing.org)