Update project info and tools

Author: stevapple

.github/ISSUE_TEMPLATE.md

@@ -13,8 +13,8 @@ _[what actually happened]_
 
 _[anything to help us reproducing the issue]_
 
-### SwiftAWSLambdaRuntime version/commit hash
+### SwiftTencentSCFRuntime version/commit hash
 
-_[the SwiftAWSLambdaRuntime tag/commit hash]_
+_[the SwiftTencentSCFRuntime tag/commit hash]_
 
 ### Swift & OS version (output of `swift --version && uname -a`)

.mailmap

@@ -1,55 +1,129 @@
-# Code of Conduct
-To be a truly great community, SwiftAWSLambdaRuntime needs to welcome developers from all walks of life,
-with different backgrounds, and with a wide range of experience. A diverse and friendly
-community will have more great ideas, more unique perspectives, and produce more great
-code. We will work diligently to make the SwiftAWSLambdaRuntime community welcoming to everyone.
-
-To give clarity of what is expected of our members, SwiftAWSLambdaRuntime has adopted the code of conduct
-defined by [contributor-covenant.org](https://www.contributor-covenant.org). This document is used across many open source
-communities, and we think it articulates our values well. The full text is copied below:
-
-### Contributor Code of Conduct v1.3
-As contributors and maintainers of this project, and in the interest of fostering an open and
-welcoming community, we pledge to respect all people who contribute through reporting
-issues, posting feature requests, updating documentation, submitting pull requests or patches,
-and other activities.
-
-We are committed to making participation in this project a harassment-free experience for
-everyone, regardless of level of experience, gender, gender identity and expression, sexual
-orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or
-nationality.
-
-Examples of unacceptable behavior by participants include:
-- The use of sexualized language or imagery
-- Personal attacks
-- Trolling or insulting/derogatory comments
-- Public or private harassment
-- Publishing other’s private information, such as physical or electronic addresses, without explicit permission
-- Other unethical or unprofessional conduct
-
-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.
-
-By adopting this Code of Conduct, project maintainers commit themselves to fairly and
-consistently applying these principles to every aspect of managing this project. Project
-maintainers who do not follow or enforce the Code of Conduct may be permanently removed
-from the project team.
-
-This code of conduct applies both within project spaces and in public spaces when an
-individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
-contacting a project maintainer at [[email protected]](mailto:[email protected]). All complaints will be reviewed and
-investigated and will result in a response that is deemed necessary and appropriate to the
-circumstances. Maintainers are obligated to maintain confidentiality with regard to the reporter
-of an incident.
-
-*This policy is adapted from the Contributor Code of Conduct [version 1.3.0](https://contributor-covenant.org/version/1/3/0/).*
-
-### Reporting
-A working group of community members is committed to promptly addressing any [reported issues](mailto:[email protected]).
-Working group members are volunteers appointed by the project lead, with a
-preference for individuals with varied backgrounds and perspectives. Membership is expected
-to change regularly, and may grow or shrink.
+
+# 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
+[[email protected]](mailto:[email protected]).
+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.

CODE_OF_CONDUCT.md

@@ -1,17 +1,16 @@
 ## Legal
 
 By submitting a pull request, you represent that you have the right to license
-your contribution to Apple and the community, and agree by submitting the patch
-that your contributions are licensed under the Apache 2.0 license (see
-`LICENSE.txt`).
+your contribution to the community, and agree by submitting the patch that
+your contributions are licensed under the Apache 2.0 license (see `LICENSE.txt`).
 
 
 ## How to submit a bug report
 
 Please ensure to specify the following:
 
-* SwiftAWSLambdaRuntime commit hash
-* Contextual information (e.g. what you were trying to achieve with SwiftAWSLambdaRuntime)
+* SwiftTencentSCFRuntime commit hash
+* Contextual information (e.g. what you were trying to achieve with )
 * Simplest possible steps to reproduce
   * More complex the steps are, lower the priority will be.
   * A pull request with failing test case is preferred, but it's just fine to paste the test case into the issue description.
@@ -24,10 +23,10 @@ Please ensure to specify the following:
 ### Example
 
 ```
-SwiftAWSLambdaRuntime commit hash: 22ec043dc9d24bb011b47ece4f9ee97ee5be2757
+SwiftTencentSCFRuntime commit hash: 22ec043dc9d24bb011b47ece4f9ee97ee5be2757
 
 Context:
-While load testing my Lambda written with SwiftAWSLambdaRuntime, I noticed
+While load testing my cloud function written with SwiftTencentSCFRuntime, I noticed
 that one file descriptor is leaked per request.
 
 Steps to reproduce:
@@ -50,7 +49,7 @@ My system has IPv6 disabled.
 
 ## Writing a Patch
 
-A good SwiftAWSLambdaRuntime patch is:
+A good SwiftTencentSCFRuntime patch is:
 
 1. Concise, and contains as few changes as needed to achieve the end result.
 2. Tested, ensuring that any tests provided failed before the patch and pass after it.
@@ -65,4 +64,4 @@ We require that your commit messages match our template. The easiest way to do t
 
 ## How to contribute your work
 
-Please open a pull request at https://github.com/apple/swift-nio. Make sure the CI passes, and then wait for code review.
+Please open a pull request at https://github.com/stevapple/swift-tencent-scf-runtime. Make sure the CI passes, and then wait for code review.

CONTRIBUTING.md

@@ -1,34 +1,17 @@
 For the purpose of tracking copyright, this is the list of individuals and
-organizations who have contributed source code to SwiftAWSLambdaRuntime.
+organizations who have contributed source code to SwiftTencentSCFRuntime.
 
 For employees of an organization/company where the copyright of work done
 by employees of that company is held by the company itself, only the company
 needs to be listed here.
 
 ## COPYRIGHT HOLDERS
 
-- Apple Inc. (all contributors with '@apple.com')
+- YR Chen (stevapple@hotmail.com)
 
 ### Contributors
 
-- Adam Fowler <[email protected]>
-- Andrea Scuderi <[email protected]>
-- Brendan Kirchner <[email protected]>
-- Bryan Bartow <[email protected]>
-- Bryan Moffatt <[email protected]>
-- Christoph Walcher <[email protected]>
-- Colton Schlosser <[email protected]>
-- Eneko Alonso <[email protected]>
-- Fabian Fett <[email protected]>
-- George Barnett <[email protected]>
-- Johannes Weiss <[email protected]>
-- Max Desiatov <[email protected]>
-- Norman Maurer <[email protected]>
-- Ro-M <[email protected]>
-- Tomer Doron <[email protected]>
-- Zhibin Cai <[email protected]>
-- pmarrufo <[email protected]>
-- tachyonics <[email protected]>
+- YR Chen ([email protected])
 
 **Updating this list**