-
Notifications
You must be signed in to change notification settings - Fork 1
06 Certificate Standards
Hèlen Grives aka edited this page Sep 19, 2026
·
2 revisions
Certificates of Collaboration are awarded on the basis of documented and verifiable contribution.
Certification is not based solely on participation, project membership, attendance, or time spent. The founder evaluates the quality, traceability, and significance of contributions against the standards below.
- Contributions must be linked to assigned work.
- Contributions must be documented.
- Evidence must be available for review.
- Work must follow established project procedures and templates.
- Contributions must have been carried out in consultation with the project team.
- Activities must align with the goals and values of the project.
The founder may consider:
- Quality of work
- Consistency of participation
- Initiative and responsibility
- Collaboration and communication
- Technical and non-technical contributions
- Impact on the project or community
Certification may be declined when:
- Contributions cannot be verified.
- Evidence is missing or incomplete.
- Work was performed outside agreed project processes.
- GitHub assignments, issues, or pull requests do not adequately support the claimed contribution.
- The claimed contribution is substantially different from the documented contribution.
The certification decision rests with the founder.
Issuance of a certificate confirms that the available evidence has been reviewed and that the contribution meets the standards of the Certification of Collaboration programme.