From nobody Wed May 15 02:46:40 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of groups.io designates 66.175.222.108 as permitted sender) client-ip=66.175.222.108; envelope-from=bounce+27952+109812+1787277+3901457@groups.io; helo=mail02.groups.io; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce+27952+109812+1787277+3901457@groups.io; dmarc=fail(p=none dis=none) header.from=163.com ARC-Seal: i=1; a=rsa-sha256; t=1697725002; cv=none; d=zohomail.com; s=zohoarc; b=CTgg/3Kv/rF03Hu+Sn06EWcv5r3mKOjJNVzGYlmyQje0WWKJ6c6v/JvMedBS4tOYbYB94/4eSA5kqQ9rAcni5ruxmDITHbkn6d/+sMkRK6hzMoCh8s4TWtWE7naWEXlmYiZ34deXnl4D0Pit03b2uXsT/3yL6E/BJhK3dM9roKo= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1697725002; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:List-Subscribe:List-Id:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Reply-To:Reply-To:References:Sender:Subject:Subject:To:To:Message-Id; bh=3AHww0vwsjg1aTe61OxNOykCG6epfuA/zPzM3VwZMTk=; b=Ra/MB6upCKy86ig4jnFH8xmnTPKjICT8cXbcQAIXoe0O+yna/1Rby8G6N0gcuOPtTTAnQz0eWuCNMnz32AbFi40PFr984d4gAaJqfbQWWy50lmaW0djY0YjwqRaiTkW7PnWTXwPR7sI5m+6QcJYSmPCG6xCINp9aZFoFD2Z1Jag= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce+27952+109812+1787277+3901457@groups.io; dmarc=fail header.from= (p=none dis=none) Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by mx.zohomail.com with SMTPS id 1697725002886982.4570580798994; Thu, 19 Oct 2023 07:16:42 -0700 (PDT) Return-Path: DKIM-Signature: a=rsa-sha256; bh=IoTcBtDxp7FMJ0MzWE00WyULcxkSvFZhou94mf/4+YY=; c=relaxed/simple; d=groups.io; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References:MIME-Version:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type:Content-Transfer-Encoding; s=20140610; t=1697725002; v=1; b=Mi1niQtrLg9oNvtRhi+8kX8IsNomuLF011lLe98ZIIblU5tTpliU69v0HrPFnyAEBMDcHAj3 ZULp3gyEEcuBl4mUFP1p7rnmt1SeWdbvuemCcqrslZHt94pC61fTQPW4gIxCuK6pvMWpUc6wqX7 mECZBd0IAKicnFU5wIdKbScI= X-Received: by 127.0.0.2 with SMTP id zd2dYY1788612x0gCu7blqFe; Thu, 19 Oct 2023 07:16:42 -0700 X-Received: from m15.mail.163.com (m15.mail.163.com [45.254.50.220]) by mx.groups.io with SMTP id smtpd.web10.28319.1697723304248884210 for ; Thu, 19 Oct 2023 06:48:24 -0700 X-Received: from rv-uefi.. (unknown [211.87.236.31]) by zwqz-smtp-mta-g1-0 (Coremail) with SMTP id _____wBnx+yfMzFlTkTiAw--.13050S2; Thu, 19 Oct 2023 21:48:16 +0800 (CST) From: caiyuqing_hz@163.com To: devel@edk2.groups.io Cc: USER0FISH , Sunil V L , Leif Lindholm , Michael D Kinney , Laszlo Ersek Subject: [edk2-devel] [PATCH v1 1/1] Maintainers.txt: Add maintainers for Sophgo platform Date: Thu, 19 Oct 2023 21:48:15 +0800 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-CM-TRANSID: _____wBnx+yfMzFlTkTiAw--.13050S2 X-Coremail-Antispam: 1Uf129KBjvJXoW3WFyfXF1kKFy3ZF4ftryftFb_yoWfKr45pa ykGF4Yya1kGr1DAa1vy3W2va4ft395GFW7Jry3G3yUZwsIyFn7tr4IyayF9a9rCw4xKws0 qwnFvr1DZ3Z8Z3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07jYXdbUUUUU= X-Originating-IP: [211.87.236.31] X-CM-SenderInfo: 5fdl535tlqwslk26il2tof0z/xtbBogYOxVaEJ6Bv9wAAsi Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,caiyuqing_hz@163.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: GofmoLygWllWG4Ys9xjXVlZGx1787277AA= Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @groups.io) X-ZM-MESSAGEID: 1697725004729100009 From: caiyuqing379 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 Cc: meng-cz Cc: USER0FISH Cc: Sunil V L Cc: Leif Lindholm Cc: Michael D Kinney Cc: Laszlo Ersek Signed-off-by: caiyuqing379 Acked-by: Laszlo Ersek Reviewed-by: Sunil V L --- 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 R: Peng Xie R: Ling Jia R: Yiqi Shu + +Sophgo platforms and silicon +F: Platform/Sophgo/ +F: Silicon/Sophgo/SG2042Pkg/ +M: Sunil V L +R: dahogn +R: meng-cz +R: caiyuqing379 +R: USER0FISH 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 - -3. meng-cz - mengcz1126@gmail.com -4. USER0FISH - - -##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 con= tributions from the community, whether it's bug reports,feature requests, o= r 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 issue= s 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 b= etter 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 encour= age 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 codin= g standards and passes any existing tests. -4. Provide a clear commit message that describes your changes and the purp= ose of your code contributions. -5. Push your code changes to your forked repository and open a Pull Reques= t (PR) to our GitHub repository. - -Our team will review your PR, and we may request changes or discuss improv= ements 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 d= oes not introduce any new issues. -- For significant changes or new feature implementations, it's advisable t= o 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 contributi= ons 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 o= ur 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-econ= omic 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, welcomin= g, diverse, inclusive, and healthy community. - -###Our Standards -Examples of behavior that contributes to a positive environment for our co= mmunity 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 mista= kes, and learning from the experience -- Focusing on what is best not just for us as individuals, but for the ov= erall community - -Examples of unacceptable behavior include: - -- The use of sexualized language or imagery, and sexual attention or adva= nces of any kind -- Trolling, insulting or derogatory comments, and personal or political a= ttacks -- Public or private harassment -- Publishing others=E2=80=99 private information, such as a physical or e= mail address, without their explicit permission -- Other conduct which could reasonably be considered inappropriate in a p= rofessional setting - -###Enforcement Responsibilities -Community leaders are responsible for clarifying and enforcing our standar= ds of acceptable behavior and will take appropriate and fair corrective act= ion in response to any behavior that they deem inappropriate, threatening, = offensive, or harmful. - -Community leaders have the right and responsibility to remove, edit, or re= ject comments, commits, code, wiki edits,issues, and other contributions th= at are not aligned to this Code of Conduct, and will communicate reasons fo= r 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 spac= es. Examples of representing our community include using an official e-mail= address, posting via an official social media account, or acting as an app= ointed 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 C= ONTACT METHOD]. All complaints will be reviewed and investigated promptly a= nd 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 determi= ning 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 u= nprofessional 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 be= havior was inappropriate. A public apology may be requested. - -**2. Warning** -Community Impact: A violation through a single incident or series of actio= ns. - -Consequence: A warning with consequences for continued behavior. No intera= ction with the people involved, including unsolicited interaction with thos= e enforcing the Code of Conduct, for a specified period of time. This inclu= des avoiding interactions in community spaces as well as external channels = like social media. Violating these terms may lead to a temporary or permane= nt ban. - -**3. Temporary Ban** -Community Impact: A serious violation of community standards, including su= stained inappropriate behavior. - -Consequence: A temporary ban from any sort of interaction or public commun= ication with the community for a specified period of time. No public or pri= vate interaction with the people involved, including unsolicited interactio= n 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 standa= rds, including sustained inappropriate behavior, harassment of an individua= l, or aggression toward or disparagement of classes of individuals. - -Consequence: A permanent ban from any sort of public interaction within th= e 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_con= duct.html. - -Community Impact Guidelines were inspired by Mozilla=E2=80=99s code of con= duct 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 ht= tps://www.contributor-covenant.org/translations. -##License: -BSD-2-Clause-Patent --=20 2.34.1 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- 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/1787277 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [importer@patchew.org] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-