* [edk2-devel] [PATCH v1 1/1] Maintainers.txt: Add maintainers for Sophgo platform
2023-10-19 13:47 [edk2-devel] [PATCH v1 0/1] Add new entry in Maintainers.txt for Sophgo platform caiyuqing_hz
@ 2023-10-19 13:48 ` caiyuqing_hz
2023-10-19 14:11 ` Laszlo Ersek
2023-10-20 7:51 ` Sunil V L
0 siblings, 2 replies; 5+ messages in thread
From: caiyuqing_hz @ 2023-10-19 13:48 UTC (permalink / raw)
To: devel; +Cc: USER0FISH, Sunil V L, Leif Lindholm, Michael D Kinney,
Laszlo Ersek
From: caiyuqing379 <caiyuqing_hz@outlook.com>
This "Platform/Sophgo/Maintainers.md" file format is useless with
edk2's "BaseTools/Scripts/GetMaintainer.py" utility, so delete this
file. Add add the maintainers to the "Maintainers.txt" file.
Cc: dahogn <dahogn@hotmail.com>
Cc: meng-cz <mengcz1126@gmail.com>
Cc: USER0FISH <libing1202@outlook.com>
Cc: Sunil V L <sunilvl@ventanamicro.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: caiyuqing379 <caiyuqing_hz@outlook.com>
---
Maintainers.txt | 9 ++
Platform/Sophgo/Maintainers.md | 105 --------------------
2 files changed, 9 insertions(+), 105 deletions(-)
diff --git a/Maintainers.txt b/Maintainers.txt
index 78f24cbb7d76..48c730854609 100644
--- a/Maintainers.txt
+++ b/Maintainers.txt
@@ -424,3 +424,12 @@ M: Leif Lindholm <quic_llindhol@quicinc.com>
R: Peng Xie <xiepeng@phytium.com.cn>
R: Ling Jia <jialing@phytium.com.cn>
R: Yiqi Shu <shuyiqi@phytium.com.cn>
+
+Sophgo platforms and silicon
+F: Platform/Sophgo/
+F: Silicon/Sophgo/SG2042Pkg/
+M: Sunil V L <sunilvl@ventanamicro.com>
+R: dahogn <dahogn@hotmail.com>
+R: meng-cz <mengcz1126@gmail.com>
+R: caiyuqing379 <caiyuqing_hz@outlook.com>
+R: USER0FISH <libing1202@outlook.com>
diff --git a/Platform/Sophgo/Maintainers.md b/Platform/Sophgo/Maintainers.md
deleted file mode 100644
index a2f0bda65850..000000000000
--- a/Platform/Sophgo/Maintainers.md
+++ /dev/null
@@ -1,105 +0,0 @@
-##Project Name: EDK2 Sophgo SG2042
-
-##Maintainers:
-1. dahogn - dahogn@hotmail.com
-2. caiyuqing379 - <caiyuqing_hz@outlook.com>
-3. meng-cz - mengcz1126@gmail.com
-4. USER0FISH - <libing1202@outlook.com>
-
-##Contact Information:
-- Academy of Intelligent Innovation, Shandong University, China.P.R.
-- Email: dahogn@hotmail.com
-- Website: http://www.aii.sdu.edu.cn/
-
-##Contributing Guidelines:
-Thank you for your interest in contributing to our project! We welcome contributions from the community, whether it's bug reports,feature requests, or code contributions. Your help is essential to the growth and improvement of the project. Here are some guidelines to help you get started:
-###Reporting Issues
-If you come across any bugs, have feature requests, or encounter any issues while using the project, please follow these steps to report them:
-1. Create a new issue in our Issue Tracker.
-2. Provide a clear and detailed description of the issue, including steps to produce and information about your operating environment.
-3. If possible, include screenshots or relevant code snippets to help us better understand nd address the issue.
-
-We will review your issue promptly and provide updates on its resolution.
-###Submitting Code
-If you have improvements to the codebase or new features to add, we encourage you to follow these steps:
-1. Fork the project on GitHub to create your copy.
-2. Create a new branch for your development and make your code changes on that branch.
-3. Before submitting the code, make sure it adheres to the project's coding standards and passes any existing tests.
-4. Provide a clear commit message that describes your changes and the purpose of your code contributions.
-5. Push your code changes to your forked repository and open a Pull Request (PR) to our GitHub repository.
-
-Our team will review your PR, and we may request changes or discuss improvements with you before merging your code.
-###Notes
-- Please try to keep your code changes concise and focused on the specific issue or feature you are addressing.
-- Before submitting, ensure that your code passes all existing tests and does not introduce any new issues.
-- For significant changes or new feature implementations, it's advisable to start by discussing them in the Issue Tracker to align with the project's direction.
-###License
-By contributing code to this project, you agree to license your contributions under the project's existing license BSD-2-Clause-Patent.
-
-##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, caste, color, 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 [INSERT CONTACT METHOD]. 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, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
-
-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.
-##License:
-BSD-2-Clause-Patent
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109812): https://edk2.groups.io/g/devel/message/109812
Mute This Topic: https://groups.io/mt/102060867/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply related [flat|nested] 5+ messages in thread