Summer of Code/Zeeshan Khan: Difference between revisions

 
(One intermediate revision by the same user not shown)
Line 104: Line 104:
=== Days TASK ===
=== Days TASK ===
10 May to 19 May
10 May to 19 May
* Go through the Gnome.developer
* Go through the Gnome.developer webpage and figure out the differences between GTK2 and GTK3 commands, imports and calling methods.
webpage and figure out the
differences between GTK2 and GTK3
commands, imports and calling
methods.
* Get my hand over the differences
* Get my hand over the differences
between GST0.10 and GST1.0
between GST0.10 and GST1.0
* Get my concepts clear over migration
* Get my concepts clear over migration from GTK2 to GTK3.
from GTK2 to GTK3.


20 May to 27 May
20 May to 27 May
* Go through the codebase of major
* Go through the codebase of major sugar activities like turtle, chat, calculate ​and record.
sugar activities like turtle, chat,
calculate ​and record.


28 May to 3 June
28 May to 3 June
* Start changing the codes of a major
* Start changing the codes of a major activity, turtleart ​where GTK2 is used, according to the way described in the project features.
activity, turtleart ​where GTK2 is
used, according to the way described
in the project features.


4 June to 5 June
4 June to 5 June
* Test the activity and send the patches
* Test the activity and send the patches to the community for review and make necessary changes.
to the community for review and make
necessary changes.


6 June to 12 June
6 June to 12 June
* Start changing the codes of record
* Start changing the codes of record activity according to the basic migration steps and features proposed.
activity according to the basic
migration steps and features
proposed.


13 June to 14 June
13 June to 14 June
* Test the activity and send the patches
* Test the activity and send the patches to the community for review and make necessary changes.
to the community for review and make
necessary changes.


15 June to 21 June
15 June to 21 June
* Start changing the codes of chat
* Start changing the codes of chat activity according to the basic migration steps and features proposed.
activity according to the basic
migration steps and features
proposed.


22 June to 23 June
22 June to 23 June
* Test the activity and send the patches
* Test the activity and send the patches to the community for review and make necessary changes.
to the community for review and make
necessary changes.


24 June to 25 June
24 June to 25 June
* Discuss about the changes, problems
* Discuss about the changes, problems and working of these 3 major activities with the mentors and make necessary changes .
and working of these 3 major
activities with the mentors and make
necessary changes .


26 June
26 June
* Prepare for the mid-term evaluation
* Prepare for the mid-term evaluation and re evaluate the submitted patches.
and re evaluate the submitted
patches.


27 June to 29 June
27 June to 29 June
Line 167: Line 140:


30 June to 5 July
30 June to 5 July
* Start changing the codes of calculate
* Start changing the codes of calculate activity according to the basic migration steps and features proposed.
activity according to the basic
migration steps and features
proposed.


6 July to 7 July
6 July to 7 July
* Test the activity and send the patches
* Test the activity and send the patches to the community for review and make necessary changes.
to the community for review and make
necessary changes.


8 July to 17 July
8 July to 17 July
* Taking two minor activities, Colors
* Taking two minor activities, Colors and Stopwatch ​ and changing their codes according to the basic migration steps and features proposed.
and Stopwatch ​ and changing their
codes according to the basic
migration steps and features
proposed.


18 July to 26 July
18 July to 26 July
* Changing the codes of two minor
* Changing the codes of two minor activities, Dots and Boxes​ and Slider-puzzle-branch​ according to the basic migration steps and features proposed.
activities, Dots and Boxes​ and
Slider-puzzle-branch​ according to
the basic migration steps and features
proposed.


27 July to 28 July
27 July to 28 July
* Test the 4 activities and send the
* Test the 4 activities and send the patches to the community for review and make necessary changes.
patches to the community for review
and make necessary changes.


29 July to 7 August
29 July to 7 August
* Changing the codes of two minor
* Changing the codes of two minor activities, Classroom broadcast ​and Convert ​according to the basic migration steps and features proposed.
activities, Classroom broadcast ​and
Convert ​according to the basic
migration steps and features
proposed.


8 August to 16 August
8 August to 16 August
* Changing the codes of two minor
* Changing the codes of two minor activities, Arithmetic​ and Pukllanapac ​and according to the basic migration steps and features proposed.
activities, Arithmetic​ and
Pukllanapac ​and according to the
basic migration steps and features
proposed.


17 August to 18 August
17 August to 18 August
* Test the 4 activities and send the
* Test the 4 activities and send the patches to the community for review and make necessary changes.
patches to the community for review
and make necessary changes.


19 August to 23 August
19 August to 23 August
* Improve the code efficiency
* Improve the code efficiency
* A last test of all the activities
* A last test of all the activities refactored and make sure that each activity is running perfectly and faster.
refactored and make sure that each
activity is running perfectly and faster.


24 August to 27 August
24 August to 27 August
* Bug fixes
* Bug fixes
* Documentation of features that are
* Documentation of features that are implemented, on wiki pages.
implemented, on wiki pages.


28 August to 30 August
28 August to 30 August
Line 292: Line 237:
We want to make sure that you can set up a ​development environment​ before the summer
We want to make sure that you can set up a ​development environment​ before the summer
starts. Please do ​one​ of the following:
starts. Please do ​one​ of the following:
* Send us a link to a screenshot of your Sugar development environment with the
* Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout".
following modification: when you hover over the XO-person icon in the middle of
* Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug.
Home view, the drop-down text should have your email in place of "logout".
* Send us a link to a pull request or merge request you have made on a Sugar or
Sugar activity bug.
  https://github.com/sugarlabs/reflect/pull/10
  https://github.com/sugarlabs/reflect/pull/10
  [reflect] added a collapse button to close the overlay area.
  [reflect] added a collapse button to close the overlay area.