Open Badges: Difference between revisions

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.

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, ~~Sugarizer~~, 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 Web, Sugar Network, 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.

Line 24:

=== 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 a 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]

~~Still, the model requires each Badge holder nominee to~~ clearly state it's decision to accept it ~~or not before a set~~ deadline.

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 March, 30 of 2017.

=== Piloting the model during 2017 ===

~~For the purpose of simplifying bureaucracy for the pilot~~, ~~I (laura_vargas)~~ have formulated the ~~initial~~ Sugar Labs Open Badges list.

I, Laura Vargas, have formulated the Sugar Labs Open Badges list for piloting the model during 2017.

So far, 9 Open Badges are drafted for the 2017 Pilot:

# Infrastructure Hero: Samuel Cantero

# Infrastructure Hero: Samuel Cantero (no to the Stipend, thanks!)

# Infrastructure Hero: Sebastian Silva

# Marketing Intern: Samson Goddy

# Sugar Network Project Leader: Laura Vargas (yes to Stipend, thanks!)

# Sugar Network Project Leader: Laura Vargas (yes to the Stipend, thanks!)

# Sugarizer Project Leader: Lionel Laske

# Social Help Project Leader: Sam Parkinson

# Translation Community Manager: Chris Leonard

# Translation Community Manager: Chris Leonard (no to the Stipend, thanks!)

# Open Badges Samurai: Ignacio Rodriguez

# Sugar Labs Badge of Honor: Walter Bender

The decision of receiving the Stipend is completely personal and each active contributor nominated will need to state it's decision in the list above. If no decision is stated, it would be equivalent to say no to the Stipend.

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.

For the 2017 Pilot the deadline is set on March, 30 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 prefer not to receive the stipend please write (no to the Stipend, thanks!) at the end of your name.

~~'''Important Note: Active edition of~~ the ~~above~~ list ~~is expected~~ to be ~~made by each user on each line only.'''~~

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 any SLOB member before March 30, 2017 as only SLOBs members are welcome to add nominees and only until March 30, 2017 for this Pilot round.

~~Deadline~~ for ~~adding 2017~~ Open Badges nominees~~~~

~~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 any SLOB member before March 30, 2017 as only SLOBs members are welcome to add nominees and~~ only ~~until March 30, 2017 for this Pilot round~~.

'''Important Note: Active edition of the above list is expected to be made by each user on each line only.'''

Budget for 2017 Open Badges

@@ 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.
-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, Sugarizer, 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 Web, Sugar Network, 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.
@@ Line 24: / Line 24: @@
 === 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 a 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]
-Still, the model requires each Badge holder nominee to clearly state it's decision to accept it or not before a set deadline.
+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 March, 30 of 2017.
 === Piloting the model during 2017 ===
-For the purpose of simplifying bureaucracy for the pilot, I (laura_vargas) have formulated the initial Sugar Labs Open Badges list.
+I, Laura Vargas, have formulated the Sugar Labs Open Badges list for piloting the model during 2017.
 So far, 9 Open Badges are drafted for the 2017 Pilot:
-# Infrastructure Hero: Samuel Cantero
+# Infrastructure Hero: Samuel Cantero (no to the Stipend, thanks!)
 # Infrastructure Hero: Sebastian Silva
 # Marketing Intern: Samson Goddy
-# Sugar Network Project Leader: Laura Vargas (yes to Stipend, thanks!)
+# Sugar Network Project Leader: Laura Vargas (yes to the Stipend, thanks!)
 # Sugarizer Project Leader: Lionel Laske
 # Social Help Project Leader: Sam Parkinson
-# Translation Community Manager: Chris Leonard
+# Translation Community Manager: Chris Leonard (no to the Stipend, thanks!)
 # Open Badges Samurai: Ignacio Rodriguez
 # Sugar Labs Badge of Honor: Walter Bender
+The decision of receiving the Stipend is completely personal and each active contributor nominated will need to state it's decision in the list above. If no decision is stated, it would be equivalent to say no to the Stipend.
-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.
+For the 2017 Pilot the deadline is set on March, 30 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 prefer not to receive the stipend please write (no to the Stipend, thanks!) at the end of your name.
-'''Important Note: Active edition of the above list is expected to be made by each user on each line only.'''
+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 any SLOB member before March 30, 2017 as only SLOBs members are welcome to add nominees and only until March 30, 2017 for this Pilot round.
-<u>Deadline for adding 2017 Open Badges nominees</u>
-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 any SLOB member before March 30, 2017 as only SLOBs members are welcome to add nominees and only until March 30, 2017 for this Pilot round.<u></u>
+'''Important Note: Active edition of the above list is expected to be made by each user on each line only.'''<u></u>
 <u>Budget for 2017 Open Badges</u>