Task #2638

Badges for the community

Added by Sophie Gautier 7 months ago. Updated 4 days ago.

In Progress
Target version:
Team - Q2/2019
Start date:
Due date:
% Done:


Estimated time:


This task is to follow-up the setting of badges and OpenBadges for the community. Attached is a document explaining what we want to achieve using Fedora badges and OpenBadges technologies.

OpenBadgesForLO.odt (474 KB) OpenBadgesForLO.odt Sophie Gautier, 2018-08-14 13:24
openbadges_test.png (290 KB) openbadges_test.png Mike Saunders, 2018-08-16 16:23
BadgeSystemDesignLibreOffice.ods (24.8 KB) BadgeSystemDesignLibreOffice.ods last version as of 2019-03-20 Sophie Gautier, 2019-03-20 18:03

Related issues

Related to Marketing - Feature #689: BadgesNew


#1 Updated by Mike Saunders 7 months ago

So to get the ball rolling on this, I've followed the steps in the New Issuers Guide - I've tested this on There are three important files for defining a specific badge:

So those three files are static and make us ready to issue badges. To actually issue a badge, we create a .json file for each recipient, like this example which awards a badge to me (Mike). The UID must be unique. The main challenge here is generating these automatically, eg when someone performs a specific task in the LibreOffice project. But the files are quite simple.

With that .json file, we can use to "bake" the data into an image. This generates a PNG file which contains all the useful metadata that we defined before - the recipient, the issuer, and so forth. Badge recipients can then display the badges on their websites/social media, and upload them to a "badge backpack" at to view details about them (see openbadges_test.png, attached to this ticket, as an example).

Next steps

Creating badges is fairly simple - that's good. What we need to do now is:

  • Work out how to create .json files for awarded badges, with unique IDs (eg with a PHP script)
  • Then link that script to our project services (Git/Gerrit, wiki, Pootle etc.) so that badges can be generated automatically
  • Find out if using the Open Badges site is OK (I think so), or it'd be better if we hosted "backpacks" ourselves, like Fedora does

#2 Updated by Florian Effenberger 7 months ago

  • Target version set to Q4/2018

Who's gonna take the lead on this, Sophie or Mike? :)

#3 Updated by Mike Saunders 6 months ago

Florian Effenberger wrote:

Who's gonna take the lead on this, Sophie or Mike? :)

Let's discuss this at LibOCon, and then make some concrete plans going forward. It'd be a good thing to bring up at the Community Meeting on Tuesday, and I personally won't have much time to work in it before then anyway. I'm happy to take on the technical tasks after, of course...

#4 Updated by Sophie Gautier 3 months ago

#5 Updated by Mike Saunders about 1 month ago

So, current status:

  • Guilhem has created some JSON queries to get stats from the wiki, so that we can add badges accordingly
  • Sophie is going to define and collect the minimum criteria to open a badge from the different projects and see how we can implement a first set
  • Mike is working with the design community on some shiny badge ideas

#6 Updated by Florian Effenberger 19 days ago

  • Target version changed from Q4/2018 to Q2/2019

#7 Updated by Sophie Gautier 18 days ago

  • File BadgeSystemDesignLibreOffice.ods added

Adding the badge system design in progress here

#8 Updated by Sophie Gautier 4 days ago

  • File deleted (BadgeSystemDesignLibreOffice.ods)

Also available in: Atom PDF