-
Notifications
You must be signed in to change notification settings - Fork 1
08 FAQ
A Certificate of Collaboration is a formal acknowledgement that a student or collaborator has made a documented and reviewed contribution to a project, task, research activity, or community initiative.
No.
Certificates are issued only upon request and after a review of the available evidence. Participation alone does not guarantee certification.
A student or collaborator may request certification when they believe they have accumulated meaningful contributions that can be supported by project records and other evidence.
Evidence may include:
- Assigned GitHub issues
- Pull requests
- Documentation
- Research notes
- Prototypes
- Testing activities
- Community contributions
- Other project records
Assignments provide a clear record of responsibility and contribution. Work performed without assignment may be difficult to verify and may not be eligible for certification.
No.
The Certificate of Collaboration is an independent recognition of contribution and participation. It is not an accredited educational qualification, degree, or professional licence.
No.
Receiving a certificate does not create an employment contract, internship agreement, contractor relationship, partnership, or any other employment status.
No.
Unless a separate written agreement exists, contributors participate on a voluntary basis and are not employees of CollabBee, Tabu Socials, SACS, Orilonova, or related projects.
The certification programme itself does not provide compensation.
Contributions recognised through certification are generally voluntary unless a separate funding, employment, internship, grant, or project agreement explicitly states otherwise.
Yes.
Certificates may be revoked if they were issued in error, obtained through misrepresentation, or can no longer be supported by the available evidence.
Certificates issued before the formalisation of the Certification of Collaboration programme may be classified as legacy certificates.
Legacy certificates are not automatically revoked, but they may not be verifiable through the current registry system.
Certificates can be verified using the Certificate ID and the public registry. Where applicable, cryptographic signatures and supporting project records may also be used to confirm authenticity.
The final decision to issue, deny, or revoke a certificate rests with the founder of the Certification of Collaboration programme.