19
edits
Changes
Jump to navigation
Jump to search
Line 70:
Line 70: − +
→You and the community
* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
In my opinion, completing this project will result in a more uniform codebase across the activities available for Sugar. This will make it easier for new Sugar Labs contributors to pick up existing activities and upgrade them further in the future without having to deal with deprecated code or technologies and will provide a more consistent design across the activities (by replacing deprecated widgets, for example). I also consider that having as many activities as possible upgraded to the latest version of the technology stack is important because it makes them more reliable and compatible with newer versions of different underlying components of Sugar and their enhancing future features.
In my opinion, completing this project is important because it will offer the possibility to have a larger number of activities available on Sugar after GTK+2 will not be available anymore on Linux, when its security updates support ends I also believe that this project will help the community by modelling a more uniform codebase across the activities available for Sugar. This will make it easier for new Sugar Labs contributors to pick up existing activities and upgrade them further in the future without having to deal with deprecated code or technologies and will provide a more consistent design across the activities (by replacing deprecated widgets, for example). I also consider that having as many activities as possible upgraded to the latest version of the technology stack is important because it makes them more reliable and compatible with newer versions of different underlying components of Sugar and their enhancing future features.
* What will you do if you get stuck on your project and your mentor isn't around?
* What will you do if you get stuck on your project and your mentor isn't around?