技术规范贡献的完整流程：从准备文件到检查审核，四个步骤保障贡献者权益
All technical contributors must sign the Contributor License Agreement (CLA) that specifies the clauses of intellectual property rights authorization.
CLA is a core legal document that protects the rights and interests of both the community and contributors. All organizations participating in the development of community technical specifications and group standards must sign the CLA before making contributions.
Prepare the Contribution File
Sign the Contribution Agreement
Submit the Contribution File and Agreement
Check the Contribution File
Follow the four steps below to complete the contribution of technical specifications, ensuring the rights and interests of both the community and contributors.
Primary contributor: Obtain the CLA and prepare the contribution file and associated attachments to be submitted. There are two types of CLAs: type A and type B. Type A includes copyright and patent grants, while type B includes only copyright grants. Type A is recommended.
Non-primary contributors who have made contributions: Sign and submit the CLA along with the contribution file and associated attachments to be submitted. The CLA type must be consistent with that of the primary contributor.
The CLA shall be signed by a contributor, either by affixing the official seal (the entity using the seal must be the same as the name of the member unit) or by the signature of the authorized signatory of the member unit. The CLA must be filled in with complete information about the contribution file and the date to protect the rights of the contributor.
If there is no primary contributor, or the primary contributor has not signed the CLA, the CLA of type B shall be used by default. Alternatively, after all contributors discuss and determine the agreement type, a contributor may be elected as the primary contributor to sign the CLA.
The CLA and its corresponding contribution file and associated attachments can be uploaded by the contributor to the community database (to be enabled) or submitted to the Secretariat. The Secretariat will then store them in the technical contribution database on the community website or upload them to the AllianceHub community database.
The database on the community website is open to the public, while the AllianceHub community database is accessible only to members. If the contributor requests the contribution file to be open only within the Alliance, this must be specified when submitting the files.
The program or project owner shall review the contribution file and associated attachments, and organize discussions on whether they can be used as input for existing projects or as the basis for new projects. Newly initiated projects must be approved by the Technology Steering Committee.
If the owner has suggestions or supplements to the contribution content, the contributor can modify the files based on the suggestions and resubmit them. When resubmitting, the contributor must include the files required in step 1.
