Changes

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC i.e., 3:30 A.M. IST. It's too much for any South Asian contributor to join at that time regularly.

One of the major problem for lack of participation in the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC i.e., 3:30 A.M. IST. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.  

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.