<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Laura,</p>
<p>Well, designing the badge structure, you have to think about a
few things. I'm giving you a detailed list here because I think it
will save you time later on in the designing process (there is no
official manual on how to do this, but I find these are relevant
items to consider early on):<br>
</p>
<p>* Think about the official authority who will be confirming the
assignment of these badges. It could be decentralized (with IPv6
URLs for example) but somehow a badge only has value if some kind
of superior "authority" (or group of people) confirms it.
Otherwise anyone could auto-assign him/herself as many badges as
they want. Each OpenBadge comes with a URI to confirm its
authenticity. At the moment it's very dependent on some kind of
authority and a permanent URI (no blockchain or other kind of
decentralized recognition has crossed the OpenBadges path yet, I
think).<br>
</p>
<p>* OpenBadges currently do not offer a possibility for
"hierarchical" badges, so there's no use in thinking about several
badges generating a "super-badge" or something like that. If you
want to represent hierarchies, your OpenBadges-issuing application
will have to deal with that, as the OpenBadges standard itself
won't.</p>
<p>* (linked to the previous one): Think about the structure you
want to use. Some badges will fall into an easy category (one
specific application, for example), but other badges might be
about contributing to a forum or helping others. In this case, you
might want to also keep a way to group together all badges about
contributing on a forum for different applications. Tags should
help better than a strict tree categorization, in this case.<br>
</p>
<p>* (again linked to the previous point): Before anything else, you
should think about what type of achievements you want to represent
with badges. Is it "learning this stuff" or is it "contributing to
this thing", etc? This will give you achievement "types" (like you
described below about Fedora) and help you avoid mixing
everything. In particular when designing the badges visually, you
want to use the same color, for example, for the same type of
achievement</p>
<p>* Think whether you want badges to be eternal or have an expiry
date. For example, "Answering more than 100 posts" on a forum is
permanent (in most cases). However "Having the skills to
administer a Linux server" is a changing target. You can either
decide that the badge is valid for only 2 years since achieving
it, or say that it works only for "Ubuntu 16.04", so that it
automatically becomes worthless as time and versions live and die.</p>
<p>* It's good to try and find a library of icons that you will use
for all the (visual) badges. It ensures a coherent collection of
badges in the end. The Mozilla OpenBadges-badgekit uses 2
different libraries (don't remember which):
<a class="moz-txt-link-freetext" href="https://github.com/mozilla/openbadges-badgekit">https://github.com/mozilla/openbadges-badgekit</a>. You can also use
<a class="moz-txt-link-freetext" href="https://www.openbadges.me">https://www.openbadges.me</a>, although I find the fact that it's not
Open Source (or not clearly so) a bit of an obstacle for me. A few
good free icons libraries are glyphicon and font-awesome.<br>
</p>
<p>* If an achievement will be part of a sub-collection (like, I
don't know, all the achievements linked to one sugar app), then
you should also think about a common design for that specific
sub-collection. In our case, we've modified a bit the badgekit to
allow us to build badges with a different "tab" attached to the
border of the tag, representing the logo of Chamilo. This is great
because the badge's background represents the app, while the
badge's central icon represents the achievement itself - in this
case, however, the badgekit depended on an SVG background which is
a bit difficult to modify (in the end we edited the badge
background's SVG source manually because editing it through
Inkscape modified the ID of the element and the badgekit's
JavaScript code got lost).</p>
<p>* Mozilla provides an open source badges "backpack" repository,
which I believe is written in Python (good for you, I suppose).
They also provide a central repository which you can use freely.
It uses Mozilla's "Persona" for authentication, which is to be
abandonned on the 30th of November (in a few days), but I'm sure
you'll be able to enter with normal credentials after that. By
"Central" repository I mean anyone can store all the OpenBadges he
gets from different sources there (SL, Chamilo, etc) and maintain
their personal badges repository there (and then link them from
LinkedIn, for example, although LinkedIn's support for OpenBadges
is inexistent).<br>
</p>
<p>* Finally, know that OpenBadges files (images) can also *store*
metadata in the PNG file. This is a property of PNG which comes in
beautifully in OpenBadges, because you can actually "save the
image" of a PNG badge and that image contains the verification
URI, the issueing authority, etc. So you can depend on that to
ensure transportability of the badges in a disconnected
environment (these PNG can later be read by an OpenBadges reader
and show you the data). In this case, you design a "template" PNG
file which is later modified by your OpenBadges-compatible
application to add the "achiever's data". So a badge is just an
image until it is "issued" to someone. Then it becomes an image
with metadata.<br>
</p>
<p>In general, Stack Overflow's strategy to reward contribution is a
good example of what you could do for a forum. At some point,
Ubuntu had also launched an achievements strategy in its forums
and on launchpad, which somehow died or stopped progressing. I
think maybe Fedora's inspiration came from there... not sure. In
light of these projects, it really make sense to not only think
about a library of badges, but also of an open standard to
exchange them, so it can survive the test of time.<br>
</p>
<p>Regards and blessings from locked-down Lima (because of the
APEC),<br>
</p>
<p>Yannick<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Le 19/11/16 à 14:50, Laura Vargas a
écrit :<br>
</div>
<blockquote
cite="mid:CAHbZrxrhiH_Qf422pCF-cD=0ehhN4wH97DG73dE0F4K0a9a8+g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Thank you Yannick!<br>
<br>
</div>
I guess that us (SL) working on <b>designing the badges
structure </b>will be the next step.<br>
<br>
</div>
<div>Any specific instruction on this?<br>
</div>
<div><br>
</div>
<div>Regards and blessings from the Amazon :D<br>
<br>
</div>
<div>Laura V<br>
</div>
<div>
<div>
<div>
<div>
<div><br>
<div>
<div>
<div class="gmail_quote"><br>
---------- Mensaje reenviado ----------<br>
From: Yannick Warnier <<a
moz-do-not-send="true"
href="mailto:yannick.warnier@beeznest.com">yannick.warnier@beeznest.com</a>><br>
To: <a moz-do-not-send="true"
href="mailto:sugar-sur@lists.sugarlabs.org">sugar-sur@lists.sugarlabs.org</a><br>
Cc: <br>
Date: Sat, 19 Nov 2016 10:03:55 -0500<br>
Subject: Re: [sugar-sur] [IAEP] Open Badges<br>
Hi folks,<br>
<br>
Just so you know (I'm not engaging my team in
any way through this) Chamilo is an GPL
(PHP/MySQL) e-learning platform that implements
badges in a relatively easy way and allows you
to design your badges (with an embedded widget
developed by Mozilla) very easily.<br>
<br>
I am available to explain one (or several) of
you guys and girls how to build courses or
specific items that will let you earn badges.
I'm just not sure Chamilo will be what you need
(I haven't read the whole thread).<br>
<br>
In my experience, the most challenging part is
designing the badges structure, but the tool is
there to manage them afterwards, in the long
run. Chamilo can serve as a central point where
those badges are generated and can be verified
(OpenBadges can use a unique URI to verify the
origin of the badge issue).<br>
<br>
-- <br>
<br>
Regards,<br>
<br>
Yannick Warnier<br>
Founder & Leader<br>
Chamilo<br>
<br>
<br>
Le 19/11/16 à 09:29, Laura Vargas a écrit :<br>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"
class="gmail_quote">
Hello and thanks to everyone interested on the
subject,<br>
<br>
I wasn't aware of this efforts in progress of
the Rochester Institute of<br>
Technology and the Teaching Open Source. I
will read in detail.<br>
<br>
Still, with the Fedora example my idea was to
submit to community<br>
consideration an strategic implementation of
open badges for community<br>
building, like Fedora.<br>
<br>
For example, Fedora uses:<br>
<br>
- Content Badges: For contributions made in
the form of documentation<br>
<br>
- Development Badges: For contributions made
to the code(s)<br>
<br>
- Quality Badge: Equivalent could be a *Sugar
Testing Badge*... (we<br>
could start with this one?)<br>
<br>
<br>
Of course this is a larger project and would
require strong support from<br>
Sugar Labs.<br>
<br>
<br>
If the Fedora folks could do it, I feel almost
ashamed we haven't... :D<br>
<br>
Regards<br>
<br>
2016-11-19 7:54 GMT-05:00 Stephen Jacobs <<a
moz-do-not-send="true" target="_blank"
href="mailto:sj@magic.rit.edu">sj@magic.rit.edu</a><br>
<mailto:<a moz-do-not-send="true"
target="_blank"
href="mailto:sj@magic.rit.edu">sj@magic.rit.edu</a>>>:<br>
<br>
We've got a small group in the class this
coming semester. If the<br>
skill set isn't in the class we can look
at other avenues as well.<br>
<br>
Class, etc won't start til end of
January. SL community should<br>
certainly dive in to the previous work to
figure out what's needed.<br>
Might be enough has been done in the past
it can be moved forward<br>
before classes start. If not, they should
at least generate a wish<br>
list for what needs to be done<br>
<br>
Sent from my iPhone<br>
<br>
On Nov 19, 2016, at 2:26 AM, Remy
DeCausemaker <<a moz-do-not-send="true"
target="_blank"
href="mailto:decause@gmail.com">decause@gmail.com</a><br>
<mailto:<a moz-do-not-send="true"
target="_blank"
href="mailto:decause@gmail.com">decause@gmail.com</a>>>
wrote:<br>
<br>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"
class="gmail_quote">
/me emerges from a long lurking state<br>
<br>
Once upon a time, the folks in the RIT
HFOSS program built an<br>
activity for viewing open badges locally
on the XO called Sash:<br>
<br>
GitHub.com/fossrit/sash <<a
moz-do-not-send="true" target="_blank"
rel="noreferrer"
href="http://GitHub.com/fossrit/sash">http://GitHub.com/fossrit/sas<wbr>h</a>><br>
<br>
They also built open badges into 2
games, lemonade stand and skytime:<br>
<br>
GitHub.com/fossrit/lemonade-st<wbr>and<br>
<<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="http://GitHub.com/fossrit/lemonade-stand">http://GitHub.com/fossrit/lem<wbr>onade-stand</a>><br>
<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="https://github.com/FOSSRIT/SkyTime">https://github.com/FOSSRIT/Sky<wbr>Time</a><br>
<<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="https://github.com/FOSSRIT/SkyTime">https://github.com/FOSSRIT/Sk<wbr>yTime</a>><br>
<br>
dzho is the current professor, but it's
been a few years since<br>
those code paths were run.<br>
<br>
The Fedora badges dashboard is called
tahrir, and source can be<br>
found here:<br>
<br>
GitHub.com/Fedora-infra/tahrir <<a
moz-do-not-send="true" target="_blank"
rel="noreferrer"
href="http://GitHub.com/Fedora-infra/tahrir">http://GitHub.com/Fedora-infr<wbr>a/tahrir</a>><br>
<br>
Hope this helps,<br>
--RemyD.<br>
<br>
On Nov 19, 2016 02:06, "Samson Goddy"
<<a moz-do-not-send="true"
target="_blank"
href="mailto:samsongoddy@sugarlabs.org">samsongoddy@sugarlabs.org</a><br>
<mailto:<a moz-do-not-send="true"
target="_blank"
href="mailto:samsongoddy@sugarlabs.org">samsongoddy@sugarlabs.<wbr>org</a>>>
wrote:<br>
<br>
sounds like a good idea!<br>
<br>
<br>
Samson Goddy<br>
<br>
On Sat, Nov 19, 2016 at 4:23 AM,
Laura Vargas<br>
<<a moz-do-not-send="true"
target="_blank"
href="mailto:laura@somosazucar.org">laura@somosazucar.org</a>
<mailto:<a moz-do-not-send="true"
target="_blank"
href="mailto:laura@somosazucar.org">laura@somosazucar.org</a>><wbr>>
wrote:<br>
<br>
<br>
Here is a link to Fedora's Open
Badge dashboard:<br>
<br>
<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="https://badges.fedoraproject.org/">https://badges.fedoraproject.o<wbr>rg/</a><br>
<<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="https://badges.fedoraproject.org/">https://badges.fedoraproject.<wbr>org/</a>><br>
<br>
Should SL consider to adopt a
similar strategy?<br>
<br>
<br>
--<br>
Laura V.<br>
I&D SomosAZUCAR.Org <<a
moz-do-not-send="true" target="_blank"
rel="noreferrer"
href="http://SomosAZUCAR.Org">http://SomosAZUCAR.Org</a>><br>
<br>
Happy Learning!<br>
<br>
<br>
______________________________<wbr>_________________<br>
IAEP -- It's An Education
Project (not a laptop project!)<br>
<a moz-do-not-send="true"
target="_blank"
href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a>
<mailto:<a moz-do-not-send="true"
target="_blank"
href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.o<wbr>rg</a>><br>
<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="http://lists.sugarlabs.org/listinfo/iaep">http://lists.sugarlabs.org/lis<wbr>tinfo/iaep</a><br>
<<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="http://lists.sugarlabs.org/listinfo/iaep">http://lists.sugarlabs.org/li<wbr>stinfo/iaep</a>><br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
IAEP -- It's An Education Project
(not a laptop project!)<br>
<a moz-do-not-send="true"
target="_blank"
href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a>
<mailto:<a moz-do-not-send="true"
target="_blank"
href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.o<wbr>rg</a>><br>
<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="http://lists.sugarlabs.org/listinfo/iaep">http://lists.sugarlabs.org/lis<wbr>tinfo/iaep</a><br>
<<a moz-do-not-send="true"
target="_blank" rel="noreferrer"
href="http://lists.sugarlabs.org/listinfo/iaep">http://lists.sugarlabs.org/li<wbr>stinfo/iaep</a>><br>
<br>
</blockquote>
<br>
<br>
<br>
--<br>
Laura V.<br>
I&D SomosAZUCAR.Org<br>
<br>
Identi.ca/Skype acaire<br>
IRC kaametza<br>
<br>
Happy Learning!<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
sugar-sur mailing list<br>
<a moz-do-not-send="true" target="_blank"
href="mailto:sugar-sur@lists.sugarlabs.org">sugar-sur@lists.sugarlabs.org</a><br>
<a moz-do-not-send="true" target="_blank"
rel="noreferrer"
href="http://lists.sugarlabs.org/listinfo/sugar-sur">http://lists.sugarlabs.org/lis<wbr>tinfo/sugar-sur</a><br>
<br>
</blockquote>
<br>
<br>
---------- Mensaje reenviado ----------<br>
From: <a moz-do-not-send="true"
href="mailto:sugar-sur-request@lists.sugarlabs.org">sugar-sur-request@lists.sugarlabs.org</a><br>
To: <br>
Cc: <br>
Date: Sat, 19 Nov 2016 10:05:28 -0500<br>
Subject: confirm
9399489e2999893ef531a7b249a3d37c7c8895a6<br>
Si responde a este mensaje manteniendo la
cabecera Subject: (Asunto)<br>
intacta, Mailman descartará el mensaje retenido.
Haga esto si el<br>
mensaje es spam. Si responde a este mensaje
incluyendo una cabecera<br>
Approved: con la contraseña de la lista en ella,
se aprobará el<br>
mensaje para que se entregue a la lista. La
cabecera Approved: puede<br>
aparecer también en la primera línea del cuerpo
de la respuesta.<br>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature">Laura V.<br>
I&D SomosAZUCAR.Org<br>
<br>
Identi.ca/Skype acaire<br>
IRC kaametza<br>
<br>
Happy Learning!<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>