GSLKThe club library

Open Badges — portable, verifiable credentials

You led a hundred people for two years and it fits on your CV as one line nobody can check. The badge you get here can be checked: an employer opens it and sees who issued it, to whom, and what for.

← The whole library

Mozilla Foundation → 1EdTech Consortium (formerly IMS Global) · 2011

How it works

A line in a club spreadsheet travels nowhere and nobody can check it. A badge carries who issued it, to whom, for what, against which criteria and how to verify it — so a third party confirms it without asking us.

Issuerthe club whose reputation is the badge's actual value

Recipientthe student who still owns it after they graduate

Achievement and criteriawhat had to be done before the badge could be given

Evidencethe project and a peer's confirmation attached to it

Verificationa cryptographic proof in 3.0; in 2.0 usually just a live URL

You can now say which part of a badge the signature checks, and which part rests on your club's reputation alone.

What you do first

Pick one genuinely finished piece of work and collect its evidence: what was done, when, and who can confirm it. Without that third part a badge is just a picture.

Who thought of it

Mozilla Foundation → 1EdTech Consortium (formerly IMS Global)

2011

The idea came out of the 2010 Mozilla Festival in Barcelona, among people at the Mozilla Foundation and the MacArthur Foundation; Mozilla announced it in 2011, and the public beta of the Open Badges Infrastructure appeared in October 2012. Open Badges 1.0 launched in 2013. Stewardship passed to the Badge Alliance in 2014 and, from 1 January 2017, to IMS Global Learning Consortium, which renamed itself 1EdTech Consortium in 2022. Version lineage: 1.0 (2013) → 1.1 → 2.0 (2018) → 2.1 (2020) → 3.0, whose final release was published on 29 May 2024 and which has been revised in place since (there is no separate 3.1).

The full biography is on the public version →

No freely licensed likeness of this person exists, so this is a generated emblem. It is not a portrait.

Why this matters

gslk answers a very specific pain: "I led a hundred people for two years and still cannot get a job." For that, a peer-confirmed result has to leave the club — onto LinkedIn, onto a CV, in front of an employer — and the recipient has to be able to check it without contacting us. That is exactly what an open standard does, and exactly why an internal "gslk badge" would not do: a closed badge is worth only as much as the lifespan of the platform that issued it.

Where this runs in the platform

These screens carry out this specific work. Every published work in the library also has at least an exercise — it is at the foot of this page.

NOT IMPLEMENTED YET. gslk does not issue Open Badges — no badge has been issued and there is no integration with the standard in the code.
The groundwork is in place, though not the groundwork originally designed: a badge in gslk is a member achievement, and competency points are earned from recorded activity and finished objectives with proof. The evidence list and a teammate's endorsement on a project hold the evidence itself. There is no self-assessment and no 360° review anywhere in that chain. That is the chain a badge will rest on.
The project register (/admin/projects) — where a competency becomes evidence; without it a badge would have nothing to attest to.

Source

1EdTech Consortium. Open Badges Specification, Version 3.0 (IMS Final Release, 29 May 2024; document revised since). Originally developed by the Mozilla Foundation with MacArthur Foundation funding, 2011–2013.