Open Badges - Revision history

Laura Vargas: /* Why use Open Badges at Sugar Labs */

2017-06-23T11:18:06Z

Why use Open Badges at Sugar Labs

← Older revision		Revision as of 07:18, 23 June 2017
Line 18:		Line 18:
	For the Open Badges 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, Sugar Network, Sugarizer, Sugar Blend, etc.		For the Open Badges 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, Sugar Network, Sugarizer, Sugar Blend, etc.

	Open Badges are here 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.		Open Badges are here formulated to recognize the value of the infrastructure team and promote the work of 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.

Laura Vargas: /* Why use Open Badges at Sugar Labs */

2017-04-07T04:00:17Z

Why use Open Badges at Sugar Labs

← Older revision		Revision as of 00:00, 7 April 2017
Line 14:		Line 14:
	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 will try to revert this trend.		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 will 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.		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 design, so reflecting collective and individual accomplishments is a logical step for Sugar Labs.

	For the Open Badges 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, Sugar Network, Sugarizer, Sugar Blend, etc.		For the Open Badges 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, Sugar Network, Sugarizer, Sugar Blend, etc.

Laura Vargas: /* References */

2017-04-07T03:59:21Z

References

← Older revision		Revision as of 23:59, 6 April 2017
Line 57:		Line 57:
	Members and non members of Sugar Labs have recommended the following reading about sustainability in Open Source:		Members and non members of Sugar Labs have recommended the following reading about sustainability in Open Source:

	[https://fordfoundcontentthemes.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf "Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure"] by Nadia Eghbal ~~[3]~~.		[https://fordfoundcontentthemes.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf "Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure"] by Nadia Eghbal.

	Please share your thoughts on the discussion page.		Please share your thoughts on the discussion page.

Laura Vargas: /* References */

2017-04-07T03:59:06Z

References

← Older revision		Revision as of 23:59, 6 April 2017
Line 4:		Line 4:


	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]~~		[https://en.wikipedia.org/wiki/Mozilla_Open_Badges 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.

	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.
Line 24:		Line 24:
	=== Stipends for Badge Holders ===		=== Stipends for Badge Holders ===

	Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ _____ attached. ~~[2]~~		Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly [https://en.wikipedia.org/wiki/Stipend stipend] of US$ _____ attached.

	Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot the deadline to state personal decisions to accept the stipend is _______ of 2017.		Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot the deadline to state personal decisions to accept the stipend is _______ of 2017.
Line 57:		Line 57:
	Members and non members of Sugar Labs have recommended the following reading about sustainability in Open Source:		Members and non members of Sugar Labs have recommended the following reading about sustainability in Open Source:

	~~"Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure" by Nadia Eghbal [3].~~		[https://fordfoundcontentthemes.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf "Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure"] by Nadia Eghbal [3].
	* [1] https://en.wikipedia.org/wiki/Mozilla_Open_Badges
	* [2] https://en.wikipedia.org/wiki/Stipend
	* [https://fordfoundcontentthemes.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf ~~<nowiki>~~[3]~~</nowiki>] https://fordfoundcontentthemes.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure~~.~~pdf~~

	Please share your thoughts on the discussion page.		Please share your thoughts on the discussion page.

Laura Vargas: /* Stipends for Badge Holders */

2017-04-07T03:46:21Z

Stipends for Badge Holders

← Older revision		Revision as of 23:46, 6 April 2017
Line 26:		Line 26:
	Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ _____ attached. [2]		Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ _____ attached. [2]

	Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot ~~such~~ deadline to state personal decisions to accept the stipend is _______ of 2017.		Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot the deadline to state personal decisions to accept the stipend is _______ of 2017.

	=== Piloting the model during 2017 ===		=== Piloting the model during 2017 ===

Laura Vargas: /* Stipends for Badge Holders */

2017-04-07T03:45:15Z

Stipends for Badge Holders

← Older revision		Revision as of 23:45, 6 April 2017
Line 24:		Line 24:
	=== Stipends for Badge Holders ===		=== Stipends for Badge Holders ===

	Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ ~~500~~ attached. [2]		Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ _____ attached. [2]

	Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot such deadline to state personal decisions to accept the stipend is _______ of 2017.		Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot such deadline to state personal decisions to accept the stipend is _______ of 2017.

Laura Vargas: /* Piloting the model during 2017 */

2017-04-07T03:44:30Z

Piloting the model during 2017

← Older revision		Revision as of 23:44, 6 April 2017
Line 34:		Line 34:
	# Infrastructure Hero: Sebastian Silva		# Infrastructure Hero: Sebastian Silva
	# Marketing Intern: Samson Goddy		# Marketing Intern: Samson Goddy
	# Sugar Network Project Leader: Laura Vargas ~~(yes to the Stipend, thanks!)~~		# Sugar Network Project Leader: Laura Vargas
	# Sugarizer Project Leader: Lionel Laske		# Sugarizer Project Leader: Lionel Laske
	# Social Help Project Leader: Sam Parkinson		# Social Help Project Leader: Sam Parkinson

Laura Vargas: /* Piloting the model during 2017 */

2017-04-07T03:44:04Z

Piloting the model during 2017

← Older revision		Revision as of 23:44, 6 April 2017
Line 39:		Line 39:
	# Open Badges Samurai: Ignacio Rodriguez		# Open Badges Samurai: Ignacio Rodriguez
	# Sugar Labs Badge of Honor: Walter Bender		# Sugar Labs Badge of Honor: Walter Bender
	The decision of receiving the ~~Stipend~~ is completely personal and optional; each active contributor nominated shall state it's decision in the list nominees before the set deadline. If no decision is stated by the set deadline, for the model that would be equivalent to say no to the ~~Stipend~~ on each round.		The decision of receiving the stipend is completely personal and optional; each active contributor nominated shall state it's decision in the list of nominees before the set deadline. If no decision is stated by the set deadline, for the model that would be equivalent to say no to the stipend on each round.

	- If you are on the list and you would appreciate to receive the stipend please write (yes to the Stipend, thanks!) at the end of your name.		- If you are on the list and you would appreciate to receive the stipend please write (yes to the Stipend, thanks!) at the end of your name.
Line 53:		Line 53:
	'''Budget for this proposal is expected to come out of Sugar Labs general funds and therefore the Budget is subject to SLOBs approval. Required Budget will be calculated according to the information registered in this page by _______ of 2017. A formal motion will be presented to the Sugar Labs Oversight board.'''		'''Budget for this proposal is expected to come out of Sugar Labs general funds and therefore the Budget is subject to SLOBs approval. Required Budget will be calculated according to the information registered in this page by _______ of 2017. A formal motion will be presented to the Sugar Labs Oversight board.'''

	If you are on the nominees list, please remember to evaluate your needs to continue contributing to the SL project and state soon your decision about receiving or not receiving the Stipend. '''If nothing is stated by the nominee, it will be assumed there is no intention to accept the Stipend offered by Sugar Labs to that nominee.'''		If you are on the nominees list, please remember to evaluate your needs to continue contributing to the Sugar Labs project and state soon your decision about receiving or not receiving the Stipend. '''If nothing is stated by the nominee, it will be assumed there is no intention to accept the Stipend offered by Sugar Labs to that nominee.'''

	~~Required Budget to run this pilot will be calculated on ______ of 2017, giving a reasonable period of time for Badge nominees to state their decisions.~~

	=== References ===		=== References ===
	Members and non members of Sugar Labs have recommended the following reading about sustainability in Open Source:		Members and non members of Sugar Labs have recommended the following reading about sustainability in Open Source:

Laura Vargas: /* Stipends for Badge Holders */

2017-04-07T03:40:53Z

Stipends for Badge Holders

← Older revision		Revision as of 23:40, 6 April 2017
Line 26:		Line 26:
	Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ 500 attached. [2]		Open Badges proposal contemplates to open channels for resources to flow to active contributors in need that have been awarded with a yearly Open Badge. All Badges have by default an optional monthly stipend of US$ 500 attached. [2]

	Each active contributor nominated will need clearly state it's decision to accept it, ~~here~~ in the ~~wiki~~. For the 2017 pilot such deadline is _______ of 2017.		Each active contributor nominated will need to clearly state it's decision to accept the stipend by writing "yes to the Stipend, thanks!", after their name in the following list. For the 2017 pilot such deadline to state personal decisions to accept the stipend is _______ of 2017.

	=== Piloting the model during 2017 ===		=== Piloting the model during 2017 ===
Line 40:		Line 40:
	# Sugar Labs Badge of Honor: Walter Bender		# Sugar Labs Badge of Honor: Walter Bender
	The decision of receiving the Stipend is completely personal and optional; each active contributor nominated shall state it's decision in the list nominees before the set deadline. If no decision is stated by the set deadline, for the model that would be equivalent to say no to the Stipend on each round.		The decision of receiving the Stipend is completely personal and optional; each active contributor nominated shall state it's decision in the list nominees before the set deadline. If no decision is stated by the set deadline, for the model that would be equivalent to say no to the Stipend on each round.

	~~For the 2017 Pilot round the deadline is set on ________ of 2017.~~

	- If you are on the list and you would appreciate to receive the stipend please write (yes to the Stipend, thanks!) at the end of your name.		- If you are on the list and you would appreciate to receive the stipend please write (yes to the Stipend, thanks!) at the end of your name.
Line 47:		Line 45:
	- If you are on the list and you would prefer not to receive the stipend please don't write anything at the end of your name		- If you are on the list and you would prefer not to receive the stipend please don't write anything at the end of your name

	- If you are not in the list but consider you are an active contributor and would like to be nominated for the Pilot round of Open Badges for 2017, please contact the Sugar Labs Oversight Board members ~~before ________ of 2017~~ as only SLOBs members are welcome to add nominees and only until _______ of 2017 for this Pilot round.		- If you are not in the list but consider you are an active contributor and would like to be nominated for the Pilot round of Open Badges for 2017, please contact the Sugar Labs Oversight Board members as only SLOBs members are welcome to add nominees and only until _______ of 2017 for this Pilot round.

	'''Important Note: Active edition of the above nominee list is expected to be made by each user on his/her line only.'''<u></u>		'''Important Note: Active edition of the above nominee list is expected to be made by each user on his/her line only.'''<u></u>

Laura Vargas: /* Why use Open Badges at Sugar Labs */

2017-04-07T03:35:21Z

Why use Open Badges at Sugar Labs

← Older revision		Revision as of 23:35, 6 April 2017
Line 16:		Line 16:
	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.		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.

	For the Open Badges 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, Sugar ~~Web~~, ~~Sugar Network~~, Sugar Blend, etc.		For the Open Badges 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, Sugar Network, Sugarizer, Sugar Blend, etc.

	Open Badges are here 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.		Open Badges are here 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.