Changes

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. 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.   

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, 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.   

=== Stipends for Badge Holders  ===

=== 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 have by default a monthly stipend of US$ 500 attached.     

Open Badges proposal contemplates to open channels for resources to flow to active contributors that have been awarded with a yearly Open Badge. All Badges have by default a monthly stipend of US$ 500 attached.     

Still, the model requires each Badge holder interested in receiving the Stipend to clearly state it's decision whether it's '''A''' to receive the monthly stipends as a donation or '''B''' not to receive the monthly stipends.       

Still, the model requires each Badge holder interested in receiving the Stipend to clearly state it's decision on time for financial planning of each round.       

=== Piloting the model during 2017 ===

=== Piloting the model during 2017 ===