├── docs ├── voting.md └── election.md ├── .github └── ISSUE_TEMPLATE │ └── project-proposal.md ├── projects ├── project-landscape.md ├── SandBox Project Proposal.md ├── graduation-proposal-template.md ├── pull_request_template.md └── readme.md ├── sigs ├── readme.md └── proposed.md └── README.md /docs/voting.md: -------------------------------------------------------------------------------- 1 | In various situations the NextArch TOC shall hold a vote. These votes can happen on the email, or via meeting when appropriate. TOC members can either respond "agree, yes, +1", "disagree, no, -1", or "abstain". A vote passes with at least fifty percent of votes cast. An abstain vote equals not voting at all. 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-proposal.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Proposal 3 | about: Template of donating a project. 4 | title: "[Project Name] donates proposal." 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | # Project Name 11 | - 12 | # Link of the Code 13 | - https://github.com/ 14 | # Abstract 15 | - 16 | # Area 17 | - 18 | # SIG Belonging 19 | - 20 | # Goal 21 | - 22 | # Link of Presentation Materials 23 | - 24 | -------------------------------------------------------------------------------- /projects/project-landscape.md: -------------------------------------------------------------------------------- 1 | # Project Landscape 2 | 3 | The Project Landscape contains all donated, collaborated, upstream, downstream projects in NextArch Foundation. 4 | 5 | The information should contain the project name, Area, Abstract, Link, SIG belonging, and Introduction Materials. 6 | 7 | 8 | | Project Name | Area | Absract | Link | SIG Belonging | Contact | Email | Introduction Materials | 9 | | --------------|-------------|-----------|-------|----------------| --------|-------|----------------------- | 10 | ||||||||| 11 | -------------------------------------------------------------------------------- /projects/SandBox Project Proposal.md: -------------------------------------------------------------------------------- 1 | # SandBoxProject Proposal 2 | 3 | # Background 4 | 5 | **[TOC PR](xxx)** 6 | 7 | **[Presentation Slide](xxx)** 8 | 9 | **[GitHub](xxx)** 10 | 11 | **Name of Project:** xxxx 12 | 13 | **Description**: 14 | xxxx 15 | 16 | **Sponsor from TOC**: TBD 17 | 18 | **Unique Identifier**: xxx 19 | 20 | **Preferred Maturity Level**: Sandbox 21 | 22 | **License**: xxx 23 | 24 | **Source control repositories:** 25 | xxx 26 | 27 | **Issue tracker**: 28 | xxx 29 | 30 | **Infrastructure Required**: 31 | xxx 32 | 33 | **Website**: 34 | xxx 35 | 36 | **Documentation:** 37 | xxx 38 | 39 | **Release methodology and mechanics:** 40 | xxx 41 | 42 | **External dependencies (including licenses):** 43 | 44 | xxx 45 | 46 | **Initial committers:** 47 | xxx 48 | 49 | **Roadmap**: 50 | 51 | xxx 52 | 53 | **Social media accounts**: 54 | 55 | xxx 56 | 57 | **Communication channels**: 58 | 59 | xxx 60 | 61 | **Adopters or potential users?**: 62 | 63 | xxx 64 | 65 | **Existing sponsorship**: 66 | 67 | xx 68 | 69 | **Statement on alignment with NextArch Foundation charter mission**: 70 | xxx 71 | 72 | **What are we looking for from NextArch Foundation**: 73 | xxx 74 | 75 | -------------------------------------------------------------------------------- /projects/graduation-proposal-template.md: -------------------------------------------------------------------------------- 1 | # [Project] Graduation Proposal 2 | 3 | _**Insert introduction. See previous proposals for examples. This section should address from a broad perspective why the project feels they are ready to graduation and can state any major accomplishments or milestones.**_ 4 | 5 | ## Graduation State Criteria 6 | _**Project should address each graduation criteria listed below**_ 7 | 8 | ### * Have committers from at least two organizations. 9 | 10 | ### * Have achieved and maintained a [Core Infrastructure Initiative Best Practices Badge](https://bestpractices.coreinfrastructure.org/). 11 | 12 | ### * Have completed an independent and third party security audit with results published of similar scope and quality as [this example](https://github.com/envoyproxy/envoy#security-audit) which includes all critical vulnerabilities and all critical vulnerabilities need to be addressed before graduation. 13 | 14 | ### * Explicitly define a Project governance and committer process. This preferably is laid out in a GOVERNANCE.md file and references an OWNERS.md file showing the current and emeritus committers. 15 | 16 | ### * Have a public list of Project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the Project website). For a specification, have a list of adopters for the implementation(s) of the spec. 17 | 18 | ## Incubation Details 19 | _**Project should address each area listed below**_ 20 | 21 | ### * Link to Incubation Due Diligence(DD) Document 22 | 23 | ### * Address any concerns or recommendations from the TAG and/or TOC sponsor(s) from the DD Document 24 | -------------------------------------------------------------------------------- /projects/pull_request_template.md: -------------------------------------------------------------------------------- 1 | Thank you for submitting your project proposal to NextArch! 2 | 3 | Before you submit your project, please ensure that: 4 | - [ ] Understand the project proposal process and reqs: [project_proposals](https://docs.google.com/forms/d/1D5GmtBI2K45_inFpt4HZcWqlsKjLHWGy697Lvpn4NHU/prefill) #introduction 5 | - [ ] Understand the services available for your project at NextArch https://www.cncf.io/services-for-projects/ 6 | - [ ] Ensure your project meets the NextArch IP Policy: https://github.com/nextarch/foundation/blob/main/technical-charter.md 7 | - [ ] Has your project adopted open governing already? see http://opengovernance.dev 8 | 9 | If your project secures enough TOC sponsors or successful vote, you will be onboarded: 10 | - [ ] Domain: transfer domain to NextArch/LF (ITx) 11 | - [ ] Trademarks: transfer any trademark and logo mark assets over to the LF 12 | - [ ] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners 13 | - [ ] Artwork: Ensure logos present on https://github.com/nextarch/artwork 14 | - [ ] Website: ensure LF footer is there and website guidelines followed, analytics transferred 15 | - [ ] Create maintainer list + added to aggregated https://maintainers.cncf.io list - OWNERS file needed 16 | - [ ] Devstats: add to devstats https://devstats.cncf.io/ 17 | - [ ] Marketing: update relevant intro + slide decks 18 | - [ ] Trail Map: update NextArch trail map if relevant (incubating projects and above) 19 | - [ ] Update https://landscape.nextarch.io 20 | - [ ] Events: update CFP + Registration + CFP Area forms 21 | - [ ] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/ 22 | - [ ] NextArch Welcome Email Sent to confirm maintainer list access 23 | - [ ] Schedule monthly project sync with NextArch staff 24 | -------------------------------------------------------------------------------- /projects/readme.md: -------------------------------------------------------------------------------- 1 | # NextArch Project Proposal Process 2 | 3 | ## Introduction 4 | This governance policy sets forth the proposal process for projects to be accepted into the NextArch Foundation. 5 | 6 | ## Project Landscape 7 | 8 | The Project Landscape contains all donated, collaborated, upstream, downstream projects in NextArch Foundation. 9 | 10 | The information should contain the project name, Area, Abstract, Link, SIG belonging, and Introduction Materials. 11 | 12 | You can update the project-landscape by setting a [Pull Request](project-landscape.md) to submit projects. 13 | 14 | ## Project stages 15 | NextArch projects have a maturity level of incubating and graduated, which corresponds to the Innovators, Early Adopters, and Early Majority tiers of the Crossing the Chasm diagram. 16 | 17 | The maturity level is a signal by NextArch as to what sorts of enterprises should be adopting different projects. 18 | 19 | Projects increase their maturity by demonstrating their sustainability to NextArch’s Technical Oversight Committee(TOC). 20 | 21 | ### Project donation process 22 | - You can set up a proposal by submitting an issue in the [TOC repo](https://github.com/nextarch/toc). 23 | - The information should contain the project name, Area, Abstract, Goal, SIG belonging, and Presentation Materials. 24 | - If the project doesn’t belong to any existing SIG, you can submit an issue in the toc repo to discuss whether to set up a new SIG. 25 | 26 | - The SIG that the new project belongs will review the project and give advice. After improvement, the SIG Tech Leader will recommend the project to TOC. 27 | - TOC will vote for the project at the TOC meeting and announce it at the meeting (approved by at least fifty percent). 28 | - The incubation of the projects will be determined by TOC in the future. 29 | 30 | ### Incubation process 31 | All exceptions (and "no" outcomes) are handled by the TOC. 32 | 33 | 1. Project Proposal 34 | - Project proposed through a issue in the [TOC repo](https://github.com/nextarch/toc). 35 | 36 | 2. TOC Review 37 | - The TOC may agree that the project does not (yet) meet the Incubation requirements and give feedback on why this is the case. 38 | - TOC reviews proposal and presentation materials in issue, project passes for inclusion with at least fifty percent of TOC 39 | - TOC may engage with project to ask further questions 40 | - If the vote is not conclusive after 6 weeks, TOC may extend vote, or conclude that silence = abstain 41 | 42 | ### Graduation process 43 | TBD 44 | -------------------------------------------------------------------------------- /sigs/readme.md: -------------------------------------------------------------------------------- 1 | # NextArch Foundation Special Interest Groups ("SIGs") 2 | 3 | ## Overall Purpose 4 | Scale contributions by the NextArch Foundation technical and user community, while retaining integrity and increasing quality in support of our mission. 5 | 6 | ## Introduction 7 | NextArch SIGs will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects. 8 | The area overseen by a SIG is typically met by a set of NextArch Foundation projects, and may also represent a cross-cutting feature group shared by several projects. SIG’s are: 9 | 10 | long lived groups that report to the TOC 11 | led primarily by recognised experts in the relevant field(s), supported by other contributors. 12 | 13 | ## Tech Lead list of SIGs 14 | | SIG Name | Name of Tech Lead | Email | 15 | | -------- | ----------------- | ----- | 16 | | SIG-DevOps | Yun Jing | jingyun@greatops.net | 17 | | SIG-CloudDev | Weida Zhao| gskzhao@tencent.com | 18 | | SIG-Edge | C.C. | cc@yomo.run| 19 | | SIG-MSG(Streaming and Messaging) | Dezhi Liu |dezhi.liu@streamnative.io| 20 | | SIG-Open Observability| Tonghao Zhang |zhangtonghao@didiglobal.com| 21 | | SIG-Microservice | Hongzhi Wang |ranchowang@tencent.com| 22 | | SIG-Load Balance | Wanlong Lu |wanlong.lu@yeepay.com| 23 | | SIG-DataBase | Chun Chang |xxx@xxx.com　| 24 | | SIG-Chaos Engineering | Yili Chen |xxx@xxx.com　| 25 | | SIG-Open HardWare | Guangbi Zhang |zhang.guangbin@e7acad.com| 26 | 27 | 28 | Tips： 29 | Tech Lead Responsibilities. 30 | - Assist TOC in the daily operation of SIG and develop SIG annual plan. 31 | - Tech Lead is valid for 1 year (elected by the initiating member or voted by everyone, can be elected continuously). 32 | - Regularly synchronize with TOC on SIG status (e.g. email/toc meeting, etc.). 33 | 34 | ## Responsibilities of Specific SIGs 35 | **Project Handling:** 36 | 37 | - Understand and document a high level roadmap of projects within this space, including NextArch and non-NextArch projects. Identify gaps in project landscape. 38 | - For projects that fall within the NextArch, perform health checks. 39 | - Perform discovery of and outreach to candidate projects. 40 | - Help candidate projects prepare for presentation to the TOC. 41 | - Every project should choose one suitable SIG to join as a necessary part of donating to NextArch. 42 | 43 | **End User Education (Outbound Communication)** 44 | - Provide up-to-date, high quality, unbiased and easy-to-consume material to help end users to understand and effectively adopt technologies and practises within the SIG’s area, for example: 45 | - White papers, presentations, videos, or other forms of training clarifying terminology, comparisons of different approaches, available projects or products, common or recommended practises, trends, illustrative successes and failures, etc. 46 | - As far as possible, information should be based on research and fact gathering, rather than pure marketing or speculation. 47 | 48 | **End User Input Gathering (Inbound Communication)** 49 | - Gather useful end user input and feedback regarding expectations, pain points, primary use cases etc. 50 | 51 | **Community Enablement** 52 | - SIGs are open organizations with meetings, meeting agendas and notes, mailing lists, and other communications in the open. 53 | 54 | 55 | ## Operating Model 56 | - Organize internal Meeting regularly to ensure the efficiency of SIG annual plan implementation. 57 | - Discover and promote the candidate projects. 58 | 59 | ## Exit Model 60 | - If the SIG is not active enough for one year, it is recommended that SIG Tech Lead/TOC members initiate a SIG withdrawal/adjustment request. 61 | 62 | ## How to Set Up SIGs 63 | You can set up a SIG by submitting an [issue](https://github.com/nextarch/toc/issues) and a [PR for approval](proposed.md). 64 | 65 | The proposed SIGs will be reported to the TOC, and the TOC will vote to determine the launch and SIG Tech Lead. 66 | -------------------------------------------------------------------------------- /sigs/proposed.md: -------------------------------------------------------------------------------- 1 | # Proposed SIGs 2 | 3 | The information should contain SIG name, Area, Abstract, Goal, and Presentation Materials. 4 | 5 | The proposed SIGs will be reported to the TOC, and the TOC will vote to determine the launch (approved by a two-thirds vote). 6 | 7 | The proposed SIGs must include the participation of 3-5 Foundation members, as well as the election of a SIG Tech Lead. 8 | 9 | A new repo of the SIG will be created after that. 10 | 11 | 12 | | Name (to be finalised) | Area | SIG Abstract | SIG Goal | PPT/Doc or Any Reference| 13 | | ------------------------|-------------|---------------|------------| ----------------------- | 14 | | SIG-Edge (Proposal)| Edge Computing | Edge computing includes many concepts, include On-Premise solution, Distributed Cloud, Geo-distributed Database, Edge-aware Serverless, etc., which can be roughly understood as "non-public cloud" architecture projects. | Clarify landscape, manage sub SIG-Edge, Collaborate and interrelate projects, Atract new projects. | | 15 | | SIG-MSG (Proposal)| Streaming and Messaging | Streaming and Messaging projects are the key architect component of the enterprise infrastructure, which include Apache Pulsar, Apache Kafka, RabitMQ, etc. | Clarify landscape, manage sub SIG-MSG, Collaborate and interrelate projects, Atract new projects. | | 16 | | SIG-CloudDev (Proposal)| Cloud Dev, Cloud Hosting, Low-Code, No-Code, Cloud Funtion, Serverless, etc. | Compared with traditional development, people only need to write a few codes or no code to build a complete application by the low-code development method. FaaS, BaaS, aPaaS, low-code even no-code are becoming popular these years. SIG-CloudDev will combine these tools or platforms to ease building applications. | SIG-CloudDev will combine low-code, no-code, and serverless tools or platforms to help users build applications more efficiently and digital transformation more easily. | | 17 | | SIG-DevOps | DevOps(CI/CD etc) | DevOps is the 3rd generation of Software Engineering.Every enterprise in digital transformation needs DevOps to digitalize its way to produce software,SIG-DevOps is founded to support the open-source software in DevOps area. | Attract and incubate more open-source software in DevOps area and promote the adoption of DevOps way to help enterprise build software more efficiently and in high quality and security.| | 18 | |SIG-OpenObservability (Proposal) |Cloud Native Computing, Troubleshooting, Performance| With the rapid scaling of cloud native computing, the probability of system/application fault is dramatically increasing. Consequently, troubleshooting becomes more difficult and complicated. SIG-OpenObservability aims to make troubleshooting as efficient and painless as possible, either from the perspective of tackling issues or tracing performance. The eBPF-based SIG-OpenObservability will be used extensively to drive a wide variety of use cases, e.g., extracting fine-grained key observability data at low overhead from linux kernel subsystems (MM, CPU, Net, Block IO, etc.), helping application developers trace applications, providing insights for performance troubleshooting, and much more. | SIG-OpenObservability is event driven, i.e., it extracts observability data when linux kernel events that we take care of, occurs. With this data, it is easy to figure out what the root cause of issues. More importantly, SIG-OpenObservability can trace linux kernel/applications for performance troubleshooting because we can also sample the data, then generate a CPU flame graph effectively.| | 19 | | SIG-Microservice (Proposal)| Microservice Governance | The microservice architecture is an architectural style that structures an application as a collection of services that are highly maintainable and testable, loosely coupled, independently deployable, owned by a small team. It enables the rapid, frequent and reliable delivery of large and complex applications. It also enables an organization to evolve its technology stack. | SIG-Microservice is committed to providing a standardized service discovery and governance solution for distributed and microservice architecture. It applies to heterogeneous infrastructure such as multi-language, multi-framework, different runtime environments and hybrid cloud scenario. | | 20 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # NextArch Technical Oversight Committee (TOC) 2 | NextArch Technical Oversight Committee (TOC) 3 | The NextArch TOC is the technical governing body of the NextArch Foundation. It admits and oversees all projects in the NextArch Foundation and has a mandate to facilitate driving neutral consensus for: 4 | 5 | - defining and maintaining the technical vision for the NextArch Foundation, 6 | - approving new projects within the scope for NextArch, and create a conceptual architecture for the projects, aligning projects, removing or archiving projects, 7 | - accepting feedback from end user committee and map to projects, 8 | - aligning interfaces to components under management (code reference implementations before standardizing), and defining common practices to be implemented across NextArch projects, if any. 9 | 10 | ## Election schedule 11 | Candidate can nominate and participate in the election by submitting a [PR for approval](docs/election.md). For new TOC nominations, TOC will vote for them at the TOC meeting and announce them in real-time at the meeting (at least fifty percent). 12 | 13 | 14 | 15 | ## Meeting Time 16 | - **Every other Thursday at 05 pm Pacific Time / 9 am UTC+8 Beijing Time**. 17 | 18 | - **Zoom Meeting:** 19 | https://zoom.us/j/99538043503?pwd=SXI5alZSVG5TQ3E0aURRUllTOHV6QT09 20 | 21 | You could also add this meeting to your calendar by downloading [NextArch TOC Meeting.ics](https://zoom.us/meeting/tJ0odOGoqjgvGtf6yhpbV1hNhbpUyzOBZqoI/ics?icsToken=98tyKuChqzgiGtCWtRmERox5GYjCWfTwiHZYjbdbygbtEyJlMwvYPuBSB6tlP_rq) 22 | 23 | - **Working Doc and Agenda:** 24 | 25 | https://docs.google.com/document/d/1Md45HROaYR2172l6YYum9QTZKeRWnivkvQVm18W6NuI/edit?usp=sharing 26 | 27 | ## TOC Member 28 | List of NextArch Foundation official TOC members：[here](docs/election.md) 29 | 30 | ## TOC Responsibilities 31 | a. The TOC will be responsible for all technical oversight of the open source Project. 32 | 33 | b. The TOC voting members are initially the Project’s Committers. At the inception of the project, the Committers of the Project will be as set forth within the “CONTRIBUTING” file within the Project’s code repository. The TOC may choose an alternative approach for determining the voting members of the TOC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Oversight Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person. 34 | 35 | c. TOC projects generally will involve Contributors and Committers. The TOC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented: 36 | 37 | - Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project; 38 | 39 | - Committers are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository; 40 | 41 | - A Contributor may become a Committer by a majority approval of the existing Committers. A Committer may be removed by a majority approval of the other existing Committers. 42 | 43 | d. Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of this Charter. 44 | 45 | e. The TOC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Committer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TOC roles, as it sees fit. 46 | 47 | f. The TOC may elect a TOC Chair, who will preside over meetings of the TOC and will serve until their resignation or replacement by the TOC. The TOC Chair, or any other TOC member so designated by the TOC, will serve as the primary communication contact between the Project and the NextArch Foundation of The Linux Foundation. 48 | 49 | g. Responsibilities: The TOC will be responsible for all aspects of oversight relating to the Project, which may include: 50 | 51 | - coordinating the technical direction of the Project; 52 | 53 | - approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope); 54 | 55 | - organizing sub-projects and removing sub-projects; 56 | - creating sub-committees or working groups to focus on cross-project technical issues and requirements; 57 | - appointing representatives to work with other open source or open standards communities; 58 | - establishing community norms, workflows, issuing releases, and security issue reporting policies; 59 | - approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the “Series Manager”) to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; 60 | - discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; 61 | - coordinating any marketing, events, or communications regarding the Project. 62 | 63 | 64 | ## TOC Voting 65 | a. While the Project aims to operate as a consensus-based community, if any TOC decision requires a vote to move the Project forward, the voting members of the TOC will vote on a one vote per voting member basis. 66 | 67 | b. Quorum for TOC meetings requires at least fifty percent of all voting members of the TOC to be present. The TOC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting. 68 | 69 | c. Except as provided in Section 7.c. and 8.a in the [Technical Charter](https://github.com/nextarch/foundation/blob/main/technical-charter.md), decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TOC. 70 | 71 | d. In the event a vote cannot be resolved by the TOC, any voting member of the TOC may refer the matter to the Series Manager for assistance in reaching a resolution. 72 | 73 | ### Voting Policy 74 | This is our [voting policy](docs/voting.md). Only TOC members can cast binding votes. (+1 Binding) 75 | 76 | ## Special Interest Groups (SIGs) 77 | The TOC will approved the formation of SIGs. You can see more informations about SIGs proposal in [here](sigs/proposed.md). 78 | -------------------------------------------------------------------------------- /docs/election.md: -------------------------------------------------------------------------------- 1 | # TOC Election 2 | 3 | 4 | Candidate can nominate and participate in the election by submitting a PR for approval. 5 | 6 | 7 | | Name | Title| Bio | Email | 8 | | ---- | -----| ------------------------| ----- | 9 | | Zheng Ran | Outstanding R&D Architect of Baidu | Head of Baidu Cloud Native Technology. More than 13 years of experience in distributed system development. Since joining Baidu, he has been focusing on distributed systems, high-availability architecture, cluster management and microservice technology, etc. He led the transformation and implementation of cloud native technologies such as Baidu's ultra-large-scale K8S cluster and service mesh architecture, and realized the core technologies of enterprise level cost reduction and efficiency increase, such as large-scale service hybrid deployment technology. | zhengran@baidu.com | 10 | | Wen Yang | AfterShip Senior Manager | Open Source Fans, Creator of TalkGo | w.yang@aftership.com | 11 | | Feng Qiang | ChinaUnicom Cloud Department Director | Supporter and practitioner of cloud native | fengqiang5@chinaunicom.cn | 12 | | Zhihong SHEN | Professor, Director of Big Data Department, CNIC-CAS(Computer Network Information Center, Chinese Academy of Sciences) | He is the chief engineer of the National and Local Joint Engineering Laboratory of Big Data Analysis and Computing Technology, in charge of the national key R & D plan project "scientific big data management system". He is responsible for the development of the open source big data pipeline system PiFlow, which was selected into the first batch of MULAN open source community incubation projects. PiFlow also won the new technology award of 2021 digital Expo for "leading scientific and technological achievements", and the excellent open source project award of China Open Source Cloud Alliance. | bluejoe@cnic.cn | 13 | | C.C. | Co-founder of Allegro Networks | maintainer of [hashids](https://hashids.org/) and [YoMo](https://yomo.run) | cc@yomo.run | 14 | | Tianguo Xiao | CEO, Huayou Technology | XOps Practitioner, Founder of GreatOPS Community | xiaotianguo@greatops.net | 15 | | Mark Shan | Chair, Tencent Open Source Alliance | Board Observer, Linux Foundation | markshan@tencent.com | 16 | | Nan Qi |DiDi Principal Engineer | Years of Experience in distributed systems.I'm responsible for building software ecosystem around k8s in DiDi.| qinan@didiglobal.com | 17 | | ZhiYong Dong | DongTai Product Manager | Years of Experience in application security, maintainer of [DongTai](https://dongtai.io/). Responsible for improving the core security capabilities of IAST and building a DevSecOps ecosystem based on IAST. | dongzhiyong@huoxian.cn | 18 | | Gary Xu | Technical partner of Harmonycloud | Domestic cloud native evangelist, with more than 10 years of IT basic platform research and development experience. Chief designer of Harmonycloud super large scale container PaaS platform, financial cloud capability open platform and hybrid cloud platform. | garyxu@harmonycloud.cn | 19 | | Junpeng WANG | Technical Partner and VP of DataCanvas | WANG is the technical partner of DataCanvas, which is one China-based leading AI platform software company, Vice President of China Business, technical expert in key industries and innovation business division, big data and financial technology, former Vice President of NTTData and Pactera, and President of Shanghai Branch of TGO Association, Invited lecturer of MSE Software Engineering School of Fudan University, guest lecturer of Lingnan MBA School of Sun Yat-sen University, researcher of artificial intelligence industry think tank in Meizhou City, Guangdong Province, and member of Shanghai Artificial Intelligence Industry Alliance； | wangjp@zetyun.com | 20 | | Liang Zhang | SphereEx Founder & CEO | Apache Member, Apache ShardingSphere PMC Chair | zhangliang@apache.org | 21 | | Sting Feng | Technical VP of Agora| Sting Feng graduated from Tsinghua University and then worked for Philips Healthcare and Microsoft. Now he is the technical VP of Agora, as the chief architect of Agora SDK, he leads the architecture design and best engineering practice of front-end. | fengyue@agora.io | 22 | | CHEN Su | CTO, DataPipeline | CHEN received his doctorate in software theory from the University of the Chinese Academy of Sciences in 2010. In 2017, he joined DataPipeline as CTO. He has rich experiences in the field of machine learning and big data, and is also keen to participate in open source projects under Apache and Linux Foundation. | chensu@datapipeline.com | 23 | | Rui Li | Associate Professor，Peng Cheng Lab. | Li Rui received her doctorate in computer software and theory from the BeiHang University in 2016. In 2016, she joined the school of computer science at National University of Defense Technology as lecturer. In 2018，She was promoted to associate Professor. In 2020, She joined the Peng Cheng Lab.. She has rich experiences in the field of computer architecture and operating system, and is also keen to participate in the construction of open source community under Linux Foundation. | lir@pcl.ac.cn | 24 | | Xudong Guo | Senior Cloud Native Architect at Jihu Gitlab | Cloud native and open source project enthusiast, Member of the Steering Committee of the Cloud Native Community(China), LF APAC open source evangelist, MVP of AliCloud | guoxd@gitlab.cn | 25 | | Yili Chen | Director, Cloud Computing Dept,CAICT | Secretary General,Cloud Native Industry Alliance | chenyili@caict.ac.cn | 26 | | Xiaobo Wang | Technical AVP of LY.com | Years of experience in distributed system architecture design, responsible for the overall system architecture of ly.com.| wangxiaobo82@vip.163.com | 27 | | Jet Lou | YunJi Tech VP | Jet graduated from Tsinghua University as Master of Software Engineering, specialized in Cloud arch design | louwei_1980@163.com | 28 | | Qiangning HONG | CTO, Yashi Technology | HONG is a senior Python programmer and has years of experience in large scale website architecture. He graduated from Tsinghua University and worked as Chief Architect in Douban and CreditEase. Now he is co-founder of Yashi Technology. | hongqn@yashihq.com | 29 | | Ming Wen | api7.ai co-founder & CEO | Apache Member, Apache APISIX PMC Chair | wenming@apache.org | 30 | | Liyun Yang | Research Director，CESI & Mulan Community | Executive Deputy Secretary-General of China Open Source Cloud Alliance, Convener of the Cross-Strait Cloud Computing Sub-Forum of the Ministry of Industry and Information Technology, and Head of the Secretariat of the Cloud Computing Standards Working Group of the National Beacon Commission. He has been engaged in standardization work in the field of information technology for a long time, leading and participating in more than 20 national standards and cloud computing open source technical group standards in the fields of cloud computing, middleware and programming languages. He has been engaged in the construction and operation, standardization and technical research of open source communities for a long time. He is the core initiator and leader of the domestic independent Mulan open source community and the Mulan open source license. | yangly@cesi.cn&6618225@qq.com | 31 | | He Zhang | Full Professor of Software Engineering and the Director of DevOps+ Research Laboratory at the Nanjing University | Internationally recognized researcher and expert in software architecture | hezhang@nju.edu.cn | 32 | | Zhao Zheng | VP of Engineering & Principle Infrastructure Architect, 4Paradigm| Zhao is leading the whole engineering function at 4Paradigm. He dedicates to lower the barriers of scaling AI technology and advance AI for everyone. Before joining 4Paradigm, Zhao has years of working experience on large-scale machine learning system, recommender system and distributed system. He won ACM-ICPC world championship, as well as the 2011 KDD Cup Best Single Model Award. | zhengzhao@4paradigm.com | 33 | | TJ Tang| Tapdata Founder & CEO | Former rock band member, world traveler, open source software advocate, founder of MongoDB Chinese Community. Previously worked at MongoDB. Founded Tapdata in 2019, currently focusing on building a heterogeneously replicated data platform that is capable of providing consistency guarantee to the data driven applications | tj@tapdata.io | 34 | | Feng Wang | Head of Infrastructure of Qihoo360, Toc Member of OpenAtom foundation. | Thirteen years of experience in infrastructure, including cloud native, storage, and bitdata. | fengw136@gmail.com | 35 | | Tina Tsou | Enterprise Architect, Arm; TSC Chair, Akraino | Passion - community building, technology enablement, mentoring new open source developers and contributors
Experience –
• Enterprise Architect, Arm (currently)
o Design and implement ARM open-source technical strategies and ecosystem building.
o Build win-win partnerships and grow communities to support ARM invested open source projects
o Specialize in 5G, AI Edge, Cloud Computing, HPC, NFV/SDN open source initiatives; open source development tools, processes, build systems, packaging, continuous integration, and test methodologies.
o Have been deeply involved in the LF Edge Akraino project for ~4 years. Currently serving as the Chair of TSC for the Akraino project (1+ year as Chair, 2+ years as co-Chair)
o Regularly host large technical meetings to help grow the Akraino project
o During the pandemic, lead and supported various developers/contributors virtual events to keep the Akraino momentum going
o Regular blogger, blueprint submission as well as reviews and approvals
o Integrated LF Edge projects like EdgeX Foundry, Fledge, EVE, etc.
o Success in building the Akraino Community Lab which was later transformed into LF Edge Community Lab
o Collaboration with upstream communities like CNCF, ETSI MEC, O-RAN, etc.
• Prior to Arm, I worked in various technical leadership positions in the area of Connectivity, NB-IoT solution, IPv6 network migration, etc.
• I have also been awarded 100+ patents and 15 IETF RFCs.
• 10+ years of work experience of open source
• Mother of two children; animal lover (currently has 2 dogs, 2 cats, 2 rabbits, 2 chickens, 2 birds, 1 fish in our family) | tina.tsou@arm.com | 36 | | Dingding Ye | Co-founder & CTO of GrowingIO | Dingding is the co-founder and CTO of GrowingIO, the leading big data intelligence analytics company in China. And also He is an open source enthusiast with 20 years experience and a serial tech entrepreneur. | dingding@growingio.com | 37 | | Zuoyan Qin | Chair, Xiaomi Open Source Committee | Years of Experience in distributed systems. Director of Database and Storage team in Xiaomi. | qinzuoyan@xiaomi.com | 38 | | Jim Xu | Principal Engineer, Zenlayer; LF Edge Board member | Jim Xu is a principal Engineer at Zenlayer leading distributed edge cloud and global cloud networking. Zenlayer is an innovative company in the Edge Cloud business. Before joining Zenlayer, he was a Technical Leader in Cisco’s flagship products, a Principal Engineer at Futurewei Technologies for the enterprise networking and Edge Computing platforms. He also partnered with several companies before in the areas of the Edge Computing IoT and Decentralized infrastructure. He has been granted over 20+ US and international patents. He is a current LF Edge Board member. | jim.xu@zenlayer.com | 39 | | Yang Shen | CIO&VP，Digital China Group Co., Ltd. | Mr. Shen Yang has been serving as Vice President and CIO in Digital China Group Co., Ltd., person in charge of the cloud base, and member of the Group Technical Committee. Leading the group's digital transformation, digital middle office, marketing private domain operations, etc., leading the development and management of distributed databases, open source ERP, SAAS and other fields. He is a professional technical expert in the field of information technology for more than 12 years.Prior to joining Digital China, he worked as a technical architect for SAP America for 7 years, leading an international professional service team in the fields of data analysis, EPM (enterprise performance management) and GRC (governance, risk and compliance). Provided digital transformation consulting services for more than 150 Fortune 500 clients. | alexshen@digitalchina.com | 40 | | Wanlong Lu | Director，Yeepay Co., Ltd. | Mr. Lu Wanlong is responsible for the architecture design and implementation of infrastructure such as kubernetes, virtualization, distributed storage and automatic operation and maintenance, and likes technology sharing. He has written books like "openstack learning from scratch" and articles like "the road to enterprise cloud", "the road to enterprise cloud storage construction", "uncertainty is absent, chaos is eternal".. | wanlong.lu@yeepay.com | 41 | --------------------------------------------------------------------------------