252
edits
Changes
Jump to navigation
Jump to search
mLine 14:
Line 14: − +
→Why use Open Badges at Sugar Labs
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 community. 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 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.