Difference between revisions of "Open Badges"
Laura Vargas (talk | contribs) |
Laura Vargas (talk | contribs) |
||
| Line 10: | Line 10: | ||
=== Why use Open Badges at Sugar Labs === | === Why use Open Badges at Sugar Labs === | ||
| − | We at Sugar Labs have many talented active contributors. Still, historically we have failed to retain them. | + | We at Sugar Labs have many talented active contributors. Still, historically we have failed to retain them. With the implementation of alternative programs like the Open Badges, we hope to revert this trend. |
| − | + | As part of our Funding and Marketing plan, taking care of internal relationships seems like a priority for Sugar Labs. Open Badges has the intention of reflecting openly an individual or collective expertise over a specific project, team or task. | |
| − | + | The reflection is one of the main principles embedded on Sugar's DNA, so reflecting collective and individual accomplishments is a logical match. The fact that there is graphical work inherently attached to the creation and maintenance of the Badges, makes that the Badges implementation itself to be considered a collective work of art. | |
| − | + | Open Badges were originally formulated to recognize the value of the infrastructure team and key project team leaders. | |
| − | + | Thanks to infrastructure team members 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. | |
| − | Sugar | + | 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. |
| − | + | Another consideration is that Sugar labs as a dynamic entity should avoid labor relationships. Instead, the adoption of "retributions by merit" and/or "awards" policies are more suitable and easy to implement. | |
| − | + | === Open Badges with Stipends === | |
| − | + | Open Badges may be one way to open channels for resources to flow to active contributors. For piloting the first round (year 2017) and according to financial viability, up to | |
| − | + | The beneficiary or "badge holder" can choose to accept our "donation" or if not in need can also declare self exclusion. | |
| − | + | it on to any active contributor in need or to give it back to the General Funds account. I volunteer myself to co-manage payments and logistics with Adam and SFC and Ignacio has volunteer to lead the development of the Badges. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
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 47: | Line 37: | ||
2017 Open Badges Pilot | 2017 Open Badges Pilot | ||
| − | + | # | |
| − | |||
| − | |||
| − | # | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Please share your thoughts on the discussion page. | Please share your thoughts on the discussion page. | ||
| Line 71: | Line 44: | ||
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. | 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. | ||
| + | |||
| + | See relevant report: | ||
| + | |||
| + | https://fordfoundcontentthemes.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf | ||
= Self Exclusion = | = Self Exclusion = | ||
Revision as of 19:45, 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
We at Sugar Labs have many talented active contributors. Still, historically we have failed to retain them. With the implementation of alternative programs like the Open Badges, we hope to revert this trend.
As part of our Funding and Marketing plan, taking care of internal relationships seems like a priority for Sugar Labs. Open Badges has the intention of reflecting openly an individual or collective expertise over a specific project, team or task.
The reflection is one of the main principles embedded on Sugar's DNA, so reflecting collective and individual accomplishments is a logical match. The fact that there is graphical work inherently attached to the creation and maintenance of the Badges, makes that the Badges implementation itself to be considered a collective work of art.
Open Badges were originally formulated to recognize the value of the infrastructure team and key project team leaders.
Thanks to infrastructure team members 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.
Another consideration is that Sugar labs as a dynamic entity should avoid labor relationships. Instead, the adoption of "retributions by merit" and/or "awards" policies are more suitable and easy to implement.
Open Badges with Stipends
Open Badges may be one way to open channels for resources to flow to active contributors. For piloting the first round (year 2017) and according to financial viability, up to
The beneficiary or "badge holder" can choose to accept our "donation" or if not in need can also declare self exclusion.
it on to any active contributor in need or to give it back to the General Funds account. I volunteer myself to co-manage payments and logistics with Adam and SFC and Ignacio has volunteer to lead the development of the Badges.
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.
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.
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