252
edits
Changes
Jump to navigation
Jump to search
Line 18:
Line 18: − + − + Line 35:
Line 35: − It's important to declare that for the purpose of simplifying bureaucracy and actually pilot the model, I (laura_vargas) have unanimously formulated the initial Open Badges list [Published on March 3, 2017] and the Open Badges names.+ − + − Once the pilot starts returning feedback, the sustainability of the program will depend on our capacity to facilitate new active contributors identification and if and when necessary, friendly and open democratic process for selecting and/or nominating badges and badge holders.+ − While I did it to the best of my knowledge as an organizational engineer, please forgive the limited list. I reformulated the model taking into consideration all great feedback from members received in IAEP and their feelings towards the flow of resources.+ + + + + − + − + Line 49:
Line 53: − + − − For piloting the model during 2017, we have the following active contributors '''(List B)''' of self defined as in need of financial resources: − # Sugar Network Project Leader: Laura Vargas − # ... − − For piloting the model during 2017, we have the following active contributors '''(List A)''' of self defined as '''not''' in need of financial resources: − # Infrastructure Hero 1: Samuel Cantero − # ...Therefore '''only active edition of the above Wiki text by each wiki user''' will change the name from '''List A''' to '''List B'''. − Everyone not listed in either lists after a defined deadline, will be added to List A +
no edit summary
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.
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.
=== 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 will have a nominal 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 an Open Badge. All Badges will have a nominal monthly stipend of US$ 500 attached.
=== Piloting the model during 2017 ===
=== Piloting the model during 2017 ===
# Open Badges Samurai: Ignacio Rodriguez
# Open Badges Samurai: Ignacio Rodriguez
'''List B:''' For piloting the model during 2017, we have the following active contributors list of self defined individuals "in need of financial resources":
# Sugar Network Project Leader: Laura Vargas
# ...
'''List A:''' For piloting the model during 2017, we have the following active contributors of self defined individuals " '''not''' in need of financial resources" '''(List A)''':
# Infrastructure Hero: Samuel Cantero
# Translation Community Manager: Chris Leonard
# ...
'''The model is based on autoevaluation, then only active edition of the above Wiki text by each wiki user''' will change any name from '''List A''' to '''List B'''.
'''Open Badges Program and Stipends'''
'''Pilot Program Guidelines'''
- Reasonable periods of time should be given for Community members to nominate themselves or another member as a Badge nominee.
- Reasonable periods of time should be given for Community members to nominate themselves or another member as a Badge nominee in upcoming rounds.
- For each round, Badge nominees will have a reasonable period of time to identify them selves as "yes, I am in need of financial resources" or as "no, I am not in need of financial resources", before submitting each years Budget to the Sugar Labs Oversgight Board.
- For each round, Badge nominees will have a reasonable period of time to identify them selves as "yes, I am in need of financial resources" or as "no, I am not in need of financial resources", before submitting each years Budget to the Sugar Labs Oversgight Board.
- By default all nominated active contributors are considered as '''not''' in need of financial resources (List A).
- By default all nominated active contributors are considered as '''not''' in need of financial resources (List A).
For piloting the model during 2017, the April 7 SLOBs meeting is proposed as the Pilot
- For the purpose of simplifying bureaucracy for the pilot, I (laura_vargas) as an organizational engineer to the best of my knowledge and eliminating every possible conflict of interest attached to the proposal, have formulated the initial Sugar Labs Open Badges list as published on March 3, 2017.
Once the pilot starts returning feedback to the community, the sustainability of the program will depend on our capacity to facilitate new active contributors identification and if and when necessary, friendly and open democratic process for selecting and/or nominating badges and badge holders.
The deadline to such edition it could be one day before the following Oversight Board meeting. I (laura_vargas) have added Samuel in List A only as an example, as he has already stated at IAEP.
The deadline to such edition it could be one day before the following Oversight Board meeting. I (laura_vargas) have added Samuel in List A only as an example, as he has already stated at IAEP.