1 TPC's Vision and Mission

TPC has build a sustainable ecosystem for third-party libraries of OpenHarmony applications, and created an incubator and a preferred platform for OpenHarmony Third Party Component (TPC) projects.

1. It continuously explores and incubates TPC projects and teams with development potential, and provides TPC governance and engineering guidance and support for project growth.
2. It also selects high-quality components and teams, and continuously iterates the optimal solution of each technical domain using the release version.

2 Roles and Responsibilities

2.1 TPC SIG Leader

TPC SIG governance team, which is responsible for reviewing the technical direction and maturity level of all TPC projects and supervising the project health.

2.2 TPC TAG

Technical Advisory Group (TAG), a group of experts with specific TPC knowledge fields. It provides technical guidance and advice on specific items in TPC-SIG.

2.3 TPC Domain Committer

Committer of a technical domain, who has the permission to manage related technical projects.

2.4 TPC Project Committer

Committer of a project, who has the permission to manage related projects.

3 TPC Project Maturity Level

Based on the use scale of TPC in the applications and the health of open source projects, TPC projects are classified into three levels by maturity: sandbox, incubating, and graduated.

3.1 Sandbox Project

The sandbox project is in the technical verification phase and is not actually depended on by applications.

NOTE
The sandbox project is a TPC project that has not been officially accepted by the OpenHarmony community. The TPC SIG provides technical support for setting up a third-party library ecosystem, completing technical verification, and promoting the project to become an incubating project.

3.1.1 Objectives

1. Send timely technical verification and developers' contribution feedback to this project to determine whether it can be merged into the OpenHarmoy TPC ecosystem.
2. Evaluate the differentiated competitiveness between the sandbox project and the existing TPC project, and the compatibility and consistency between the sandbox project and OpenHarmony platform.
3. Provide necessary services for project development.
4. Ensure that all projects comply with the laws, code of conduct, and Intellectual Property Rights (IPR) policy requirements of the OpenHarmony community, and eliminate potential legal and governance risks to promote adoption and contribution.

3.1.2 Collaboration Process

1. Application:
   1. If a project repository is already created, you can directly create a sandbox application report and issue (TODO) to apply for the project to become a sandbox project.
   2. If a project repository has not been officially built, it can still be a sandbox project.
      1. Establish a candidate solution for third-party library adaptation based on specific requirements, and create a sandbox selection report for the candidate third-party library.
      2. Assess risks on the selection report, and create an issue to apply for becoming a sandbox project.
2. Review: TPC-SIG leaders and domain committers collectively decide whether to turn the sandbox project into an incubating project based on the application issues and related evaluation reports. Decisions are made based on issues first. If there is any undecided item, escalate it to the SIG meeting for review.
3. Repository creation: For sandbox projects that have not been officially accepted by the OpenHarmony community, repositories cannot be created on the official code platform. However, the TPC SIG will provide guidance (TODO) for creating repositories externally.
4. Certification: After a project passes the sandbox review, the sandbox badge certification (TODO) will be obtained (the badge will clearly state that the project has not been officially accepted by the OpenHarmony community) and can be used in the project. The project will also be displayed in the TPC sandbox project LandScape.
5. Governance: Sandbox projects will be displayed on the TPC incubation governance dashboard (TODO) and governed on a daily basis.
6. Development: For details, see section 4 "Development" (TODO).
7. Archiving review: TPC-SIG leaders periodically review sandbox projects and archive related projects based on archiving evaluation indicators (TODO).

3.1.3 Services

The following services are provided for the sandbox project:

1. Governance guidance for open source projects (TODO)
2. Legal services (TODO)
3. User community link (TODO)
4. Marketing activities (TODO)
5. Compliance and vulnerability security support (TODO)
6. Tool sets (TODO)

3.2 Incubating Project

The incubating project has been used by some applications and has a stable contributor group.

3.2.1 Objectives

1. Obtain market feedback and continuous contributions in a timely manner.
2. Increase application usage, expand the community scale, and improve the project quality and stability to become a graduated project.

3.2.2 Collaboration Process

1. Application:
   1. If a project repository has been built outside the OpenHarmony community and does not need to be migrated to OpenHarmony-SIG, you can directly create an incubation application report and an issue (TODO) for the project and apply to become an incubating project.
      NOTE
      A project can be incubated only when it has been used by at least one OpenHarmony application.
   2. If the project does not have a formal repository outside the OpenHarmony community but is a specific requirement raised by an OpenHarmony application, it can still become an incubating project.
      1. Establish a candidate solution for third-party library adaptation based on specific requirements, and create an incubation selection report for the candidate third-party library.
      2. Assess risks on the selection report, and create an issue to apply for becoming an incubating project.
2. Review: TPC-SIG leaders and domain committers collectively decide whether to turn the sandbox project into an incubating project based on the application issues and related evaluation reports. Decisions are made based on issues first. If there is any undecided item, escalate it to the SIG meeting for review.
3. OpenHarmony architecture review: Three TPC-SIG representatives (from TPC-SIG leaders, domain committers, and project committers respectively) state the reasons for the project becoming an OpenHarmony incubating project at the OpenHarmony architecture SIG meeting and obtain review comments from the architecture SIG.
4. Repository creation: Create the repository of incubating projects on OpenHarmony-SIG (TODO) according to guidance.
5. Certification: Projects that have passed the incubation review will obtain the incubation badge certification (TODO), which can be used in projects. The project will also be displayed in the TPC incubating project LandScape.
6. Governance: Incubating projects will be displayed on the TPC incubation governance dashboard (TODO) for routine governance.
7. Development: For details, see section 4 "Development" (TODO).
8. Archiving review: TPC-SIG leaders periodically review incubating projects and archive related projects based on archiving evaluation indicators (TODO).

3.2.3 Services

1. Governance guidance for open source projects (TODO)
2. Legal services (TODO)
3. User community link (TODO)
4. Marketing activities (TODO)
5. Compliance and vulnerability security support(TODO)
6. Tool sets (TODO)

3.3 Graduated Project

Graduated projects are functional, stable, and widely used by applications, with a stable and large number of contributors.

3.3.1 Objectives

1. Keep the technical leading position, continuously increase users and contributors, ensure the stability and sustainability of the project, and promote the development of the entire TPC ecosystem.

3.3.2 Collaboration Process

1. Application:
   1. If a project repository has been built outside the OpenHarmony community and does not need to be migrated to OpenHarmony-TPC, you can directly create a graduation application report and an issue (TODO) to apply for the project to become a graduated project.
   2. If the project has been incubated on OpenHarmony-SIG and you want to continue governing the project on the official community platform, you can directly create a graduation application report and issue (TODO) to apply for the project to become a graduated project.
2. Review: TPC-SIG leaders and domain committers collectively decide whether to turn the incubating project into a graduated project based on the application issues and related evaluation reports. Decisions are made based on issues first. If there is any undecided item, escalate it to the SIG meeting for review.
3. OpenHarmony architecture review: Three TPC-SIG representatives (from TPC-SIG leaders, domain committers, and project committers respectively) state the reasons for the project becoming an OpenHarmony graduated project at the OpenHarmony architecture SIG meeting and obtain review comments from the architecture SIG.
4. Repository creation on TPC: For projects that apply for repository creation on OpenHarmony-TPC, the (TODO) project will be established as required.
5. Certification: You will receive a graduation badge certification (TODO) after the project passes the graduation review, which can be used in the project. The project will also be displayed in the TPC graduated project LandScape.
6. Governance: Graduated projects will be displayed on the TPC graduation governance dashboard (TODO) for routine governance.
7. Development: For details, see section 4 "Development" (TODO).
8. Archiving review: TPC-SIG leaders periodically review graduated projects and archive related projects based on archiving evaluation indicators (TODO).

3.3.3 Services

1. Governance guidance for open source projects (TODO)
2. Legal services (TODO)
3. User community link (TODO)
4. Marketing activities (TODO)
5. Compliance and vulnerability security support(TODO)
6. Tool sets (TODO)

4 Development

4.1 Purposes

TODO

4.2 Collaboration Process

TODO

4.3 Services

TODO

5 Publication and Maintenance of the Release Version

5.1 Objectives

Use the release version to continuously iterate the current optimal solution of each technical domain and ensure lifecycle maintenance.

5.2 Collaboration Process

1. Planning: Customize the release version planning (TODO).
2. Application: Create an issue (TODO) and apply for turning a graduated project into a release version based on the template requirements (TODO).
3. Review: TPC-SIG leaders and TAG collectively decide whether to turn the graduated project into a released software based on the application issues and related evaluation reports (TODO).
4. Publication: The software of release version will be displayed in the TPC release LandScape (TODO).
5. Certification: You will receive a release badge certification (TODO) after the project passes the release review, which can be used in the project.
6. Usage and reputation analysis: TODO
7. Vulnerability and virus detection: TODO
8. Maintenance: TODO
9. End of Life (EOL): TPC-SIG leaders develop the EOL strategy based on the release lifecycle management (TODO).

6 Contribution Assessment

6.1 Contribution Volume Assessment

TODO

6.2 Maturity Level Certification

TODO