Changes

Here, in Bucharest, is a group of young computer science specialists and students called [http://www.rosedu.org/ ROSEdu (Romanian Open Source Education)]. As an aspiring member of this organization I have created content in the form of questions related to the Introduction to Operating Systems course (a course about how Linux based operating systems work) which have been used on the online competition-quiz platform developed by ROSEdu called World of USO (USO roughly translates to Introduction to Operating Systems in Romanian) which is accessible to students at my University during the first semester of the year, when the course takes place (here is a snippet from an email on the ROSEdu mailing list stating my participation https://pastebin.com/UsUqf1tY).  

Here, in Bucharest, is a group of young computer science specialists and students called [http://www.rosedu.org/ ROSEdu (Romanian Open Source Education)]. As an aspiring member of this organization I have created content in the form of questions related to the Introduction to Operating Systems course (a course about how Linux based operating systems work) which have been used on the online competition-quiz platform developed by ROSEdu called World of USO (USO roughly translates to Introduction to Operating Systems in Romanian) which is accessible to students at my University during the first semester of the year, when the course takes place (here is a snippet from an email on the ROSEdu mailing list stating my participation https://pastebin.com/UsUqf1tY).  

I would love to work on an open-source project this summer because I believe that I can learn a lot of relevant information and improve my software developing skills. I also believe that the atmosphere of an open-source organization is one of the best for working and learning because of its passion-driven members.

I would love to work on an open-source project this summer because I believe that I can learn a lot of relevant information and improve my software developing skills. I also believe that the atmosphere of an open-source organization is one of the best for working and learning thanks to its passion-driven members.

===About your project===

===About your project===

|-

|-

|22

|22

|[https://github.com/sugarlabs/amazonas-activity Amazonas] v

|[https://github.com/sugarlabs/amazonas-activity Amazonas]  

|-

|-

|23

|23

|[https://github.com/sugarlabs/supertux-activity SuperTux] v

|[https://github.com/sugarlabs/supertux-activity SuperTux]  

|-

|-

|24

|24

|[https://github.com/sugarlabs/Lemonade Lemonade] v

|[https://github.com/sugarlabs/Lemonade Lemonade]  

|-

|-

|25

|25

|[https://github.com/sugarlabs/iknowEditor iknowEditor] v

|[https://github.com/sugarlabs/iknowEditor iknowEditor]  

|}

|}

* What is the timeline for development of your project? The Summer of Code work period is from mid-May  to mid-August; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (end of June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

* What is the timeline for development of your project? The Summer of Code work period is from mid-May  to mid-August; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (end of June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

| -

| -

|23-04 -> 14-05

|23-04 -> 14-05

|Community bonding: attend as many IRC meetings as possible in order to get up to date with what the Sugar Labs community is currently working on and create a small database of all the original and highly involved contributors to the activities that I will port so in case that I need some specific information about a particular activity that I cannot find otherwise, I can try to get in touch with them.

|Community bonding: attend as many IRC meetings as possible in order to get up to date with what the Sugar Labs community is currently working on  

and create a small database of all the original and highly involved contributors to the activities that I will port so in case that I need some specific information  

 

about a particular activity that I cannot find otherwise, I can try to get in touch with them.

Ask for advice on how my workflow should look like.

Ask for advice on how my workflow should look like.

|-

|-

|-

|-

| 6 || 18-06 -> 24-06 || Port activities 3 - 6.

| 6 || 18-06 -> 24-06 || Port activities 3 - 6.

Start working on creating a small activity on my own in order to further improve my skills. Use the "Make your own sugar activities" FLOSS manual as a starting point.

Start working on creating a small activity on my own in order to further improve my skills.  

 

Use the "Make your own sugar activities" FLOSS manual as a starting point.

|-

|-

| 7 || 25-06 -> 01-07 || Port activities 7 - 10.

| 7 || 25-06 -> 01-07 || Port activities 7 - 10.

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.

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?