Changes

20 bytes added ,  06: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.                 
252

edits