Difference between revisions of "Open Badges"
Laura Vargas (talk | contribs) (progress) |
Laura Vargas (talk | contribs) (more text) |
||
| Line 6: | Line 6: | ||
Open Badges is the name of a group of specifications and open technical standards originally developed by the Mozilla Foundation with funding from the MacArthur Foundation. The Open Badges standard describes a method for packaging information about accomplishments, embedding it into portable image files as a digital badge, and establishing an infrastructure for badge validation. The standard was originally maintained by the Badge Alliance Standard Working Group, but transitioned officially to the IMS Global Learning Consortium as of January 1, 2017. [1] | Open Badges is the name of a group of specifications and open technical standards originally developed by the Mozilla Foundation with funding from the MacArthur Foundation. The Open Badges standard describes a method for packaging information about accomplishments, embedding it into portable image files as a digital badge, and establishing an infrastructure for badge validation. The standard was originally maintained by the Badge Alliance Standard Working Group, but transitioned officially to the IMS Global Learning Consortium as of January 1, 2017. [1] | ||
| − | Open Badges represent a more detailed picture than a CV or résumé as they can be presented in ever-changing combinations, creating a constantly evolving picture of a person’s lifelong learning. | + | Open Badges represent a more detailed picture than a CV or résumé as they can be presented in ever-changing combinations, creating a constantly evolving picture of a person’s lifelong learning. |
=== Why use Open Badges at Sugar Labs === | === Why use Open Badges at Sugar Labs === | ||
| − | As part of our Funding and Marketing plan, taking care of internal relationships needs to be a priority for Sugar Labs. | + | As part of our Funding and Marketing plan, taking care of internal relationships needs to be a priority for Sugar Labs. [2] |
| − | We at Sugar Labs have articulated many talented active contributors. Still, historically we have failed to retain many of them. With the implementation of alternative programs like the Open Badges, we | + | We at Sugar Labs have articulated many talented active contributors. Still, historically we have failed to retain many of them. With the implementation of alternative programs like the Open Badges, we could try to revert this trend. |
| − | Open Badges has the intention of reflecting openly | + | The Open Badges program at Sugar Labs has the intention of reflecting openly individual or collective expertise over a specific project, team or task. Reflection is one of the main principles embedded on Sugar's DNA, so reflecting collective and individual accomplishments is a logical step for Sugar Labs community. For the implementation team, main challenge and opportunity may be the fact that there is several graphical work inherently attached to the creation and maintenance of the Badges. Also possible integrations with Sugar, Sugarizer, Sugar Network, etc. |
| − | Open Badges were originally formulated to recognize the value of the infrastructure team and key project team leaders. Thanks to infrastructure team | + | Open Badges were originally formulated to recognize the value of the infrastructure team and key project team leaders. Thanks to infrastructure team there is a level of service that allows us to be constantly in the air to interact with each other, with the code and with our users. Thanks to our key project team leaders, Sugar adapts and evolves to specific cases of use. This interaction and close support can only enrich our upstream main project. |
Still, Sugar labs is a dynamic entity and should avoid labor relationships. Instead, the adoption of "retributions by merit" and/or "awards" policies are more suitable. | Still, Sugar labs is a dynamic entity and should avoid labor relationships. Instead, the adoption of "retributions by merit" and/or "awards" policies are more suitable. | ||
| Line 22: | Line 22: | ||
=== Stipends for Badge Holders === | === Stipends for Badge Holders === | ||
| − | Open Badges | + | Open Badges proposal contemplates to open channels for resources to flow to active contributors that have been awarded with an Open Badge. All Badges will have a nominal monthly stipend of US$ 500 attached. |
| − | The | + | The beneficiaries or "badge holders" can choose to accept our "donation" or if not in need can also choose to give it back to the General Funds account. |
| − | For piloting the model | + | For piloting the model, we have defined 10 Open Badges: |
| − | + | Infrastructure Hero 1: Samuel Cantero | |
| + | |||
| + | Infrastructure Hero 2: Sebastian Silva | ||
| + | |||
| + | Infrastructure Hero 3: Bernie Innocenti | ||
| + | |||
| + | If you consider there are more Badges and/or Badge holders that should be considered for the first year, please feel free to nominate someone else or yourself and give a name to the Badge. | ||
| + | |||
| + | Under this model and for the first year (03/2017 - 03/2018), each badge could have a US$500/month stipend attached, for a total of US$3,500 per month, totalling US$ 36,000 per year in stipends [2] to Active contributors. | ||
Members and non members of Sugar Labs have recommended the following reading to understand more about the subject of sustainability in Open Source: | Members and non members of Sugar Labs have recommended the following reading to understand more about the subject of sustainability in Open Source: | ||
| Line 38: | Line 46: | ||
Please share your thoughts on the discussion page. | Please share your thoughts on the discussion page. | ||
| − | |||
| − | |||
| − | |||
| − | |||
See relevant report: | See relevant report: | ||
| Line 53: | Line 57: | ||
References | References | ||
* [1] https://en.wikipedia.org/wiki/Mozilla_Open_Badges | * [1] https://en.wikipedia.org/wiki/Mozilla_Open_Badges | ||
| − | * [2] https://en.wikipedia.org/wiki/Stipend | + | * [2] [[Marketing Team]] |
| + | * [3] https://en.wikipedia.org/wiki/Stipend | ||
Revision as of 23:19, 2 March 2017
|
NOTICE: This page is a draft in active flux... Please contribute to these contents and discuss issues on the discussion page. |
Open Badges is the name of a group of specifications and open technical standards originally developed by the Mozilla Foundation with funding from the MacArthur Foundation. The Open Badges standard describes a method for packaging information about accomplishments, embedding it into portable image files as a digital badge, and establishing an infrastructure for badge validation. The standard was originally maintained by the Badge Alliance Standard Working Group, but transitioned officially to the IMS Global Learning Consortium as of January 1, 2017. [1]
Open Badges represent a more detailed picture than a CV or résumé as they can be presented in ever-changing combinations, creating a constantly evolving picture of a person’s lifelong learning.
Why use Open Badges at Sugar Labs
As part of our Funding and Marketing plan, taking care of internal relationships needs to be a priority for Sugar Labs. [2]
We at Sugar Labs have articulated many talented active contributors. Still, historically we have failed to retain many of them. With the implementation of alternative programs like the Open Badges, we could try to revert this trend.
The Open Badges program at Sugar Labs has the intention of reflecting openly individual or collective expertise over a specific project, team or task. Reflection is one of the main principles embedded on Sugar's DNA, so reflecting collective and individual accomplishments is a logical step for Sugar Labs community. For the implementation team, main challenge and opportunity may be the fact that there is several graphical work inherently attached to the creation and maintenance of the Badges. Also possible integrations with Sugar, Sugarizer, Sugar Network, etc.
Open Badges were originally formulated to recognize the value of the infrastructure team and key project team leaders. Thanks to infrastructure team there is a level of service that allows us to be constantly in the air to interact with each other, with the code and with our users. Thanks to our key project team leaders, Sugar adapts and evolves to specific cases of use. This interaction and close support can only enrich our upstream main project.
Still, Sugar labs is a dynamic entity and should avoid labor relationships. Instead, the adoption of "retributions by merit" and/or "awards" policies are more suitable.
Stipends for Badge Holders
Open Badges proposal contemplates to open channels for resources to flow to active contributors that have been awarded with an Open Badge. All Badges will have a nominal monthly stipend of US$ 500 attached.
The beneficiaries or "badge holders" can choose to accept our "donation" or if not in need can also choose to give it back to the General Funds account.
For piloting the model, we have defined 10 Open Badges:
Infrastructure Hero 1: Samuel Cantero
Infrastructure Hero 2: Sebastian Silva
Infrastructure Hero 3: Bernie Innocenti
If you consider there are more Badges and/or Badge holders that should be considered for the first year, please feel free to nominate someone else or yourself and give a name to the Badge.
Under this model and for the first year (03/2017 - 03/2018), each badge could have a US$500/month stipend attached, for a total of US$3,500 per month, totalling US$ 36,000 per year in stipends [2] to Active contributors.
Members and non members of Sugar Labs have recommended the following reading to understand more about the subject of sustainability in Open Source:
"Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure" by Nadia Eghbal.
2017 Open Badges Pilot
Please share your thoughts on the discussion page.
See relevant report:
Self Exclusion
Here is a way to register for exclusion. Add your name to the list if you identify as an active contributors
may be paid by other organisations, or may have to reject any badge because of conflict of interest.
References