Changes

Jump to navigation Jump to search
no edit summary
Line 66: Line 66:     
'''Mid-term Evaluation'''
 
'''Mid-term Evaluation'''
:By this time, I plan to have finished writing polyglot for sugar and sugar-toolkit-gtk3
+
:By this time, I plan to have finished writing polyglot for sugar and sugar-toolkit-gtk3 and have an automatic cross version testing setup in both of these.
    
'''June 23 - August 11(Second half of the official coding period)'''
 
'''June 23 - August 11(Second half of the official coding period)'''
Line 72: Line 72:  
* Week 2: Write documentation on maintaining sugar core and sugar toolkit under the new setup to ease future development.  
 
* Week 2: Write documentation on maintaining sugar core and sugar toolkit under the new setup to ease future development.  
 
* Week 3: If the mentor(s) and the core developers are satisfied with the code and think that the codebase is solid, try and port sugar-build in the same way.
 
* Week 3: If the mentor(s) and the core developers are satisfied with the code and think that the codebase is solid, try and port sugar-build in the same way.
  −
         
'''Deliverables at the end of GSoC'''
 
'''Deliverables at the end of GSoC'''
 
* Automated tests across python versions for sugar and sugar-toolkit-gtk3
 
* Automated tests across python versions for sugar and sugar-toolkit-gtk3
* Fully python 3 compatible polyglot codebases of sugar and sugar-toolkit-gtk3  
+
* Fully Python 3 compatible polyglot codebases of sugar and sugar-toolkit-gtk3  
 
* Python 3 compatible sugar-build (optionally)  
 
* Python 3 compatible sugar-build (optionally)  
    
Post GSoC, I would be available to help port activities and sugar-buildbot to python 3.x and also write a porting guide for activities for developers.
 
Post GSoC, I would be available to help port activities and sugar-buildbot to python 3.x and also write a porting guide for activities for developers.
    +
'''Why I think I can complete this project successfully'''
 
I believe in the cliche about actions speaking louder than words, so I plan on porting [https://github.com/PabloCastellano/telepathy-python telepathy-python] to python3 in the coming week, So I can show that I'm committed and capable of undertaking this project. I strongly feel for Sugar and want to contribute to it one way or another, so much so I would be interested in doing so regardless of whether I get into GSoC.
 
I believe in the cliche about actions speaking louder than words, so I plan on porting [https://github.com/PabloCastellano/telepathy-python telepathy-python] to python3 in the coming week, So I can show that I'm committed and capable of undertaking this project. I strongly feel for Sugar and want to contribute to it one way or another, so much so I would be interested in doing so regardless of whether I get into GSoC.
    
===Me and the community===
 
===Me and the community===
 
'''Impact of the project'''
 
'''Impact of the project'''
   
At the end of my project, the testing on the sugar toolkit and the sugar core would have improved greatly and I strongly believe that a robust set of unit tests is a must for every project as it eases development. Python 3 has better unicode support and I think a lot of activities based around text would greatly benefit from porting to python 3.  
 
At the end of my project, the testing on the sugar toolkit and the sugar core would have improved greatly and I strongly believe that a robust set of unit tests is a must for every project as it eases development. Python 3 has better unicode support and I think a lot of activities based around text would greatly benefit from porting to python 3.  
   Line 93: Line 91:       −
* What will you do if you get stuck on your project and your mentor isn't around?
+
'''In case of getting stuck on the project in the absence of my mentor'''
Find help on the mailing list or the IRC, or if that doesn't work out, work on a different part of the project until my mentor is available.
+
First there's the sugarlabs community, I'm sure there will always be someone around on the mailing list or the IRC who are willing to help. Then there's always the internet, which is an amazing resource. So much so that I could say that half the things I've learnt in my life have been through the Internet. Sites like stackoverflow has a very diverse community always willing to offer help. If none of it work out, works out , I would try working on a different part of the project until my mentor is available or I find a proper solution.
 +
 
   −
* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?
+
'''Keeping the Community informed'''
I plan to write a report every week on my [http://upman.github.io blog] and also discuss with people regularly  over the mailing list or the IRC channel.
+
I plan on writing a report every week on my [http://upman.github.io blog] and also discuss with people regularly  over the mailing list or the IRC channel.
 +
I might also write articles about six and the approaches I use to write polyglot so I can keep the developers in the know of what I'm doing. This could also serve as documentation for when somebody is looking to add to the sugar core or make a bug fix in the future.
    
===Miscellaneous===
 
===Miscellaneous===
   −
I've been able to setup the development environment and here's the screenshot of it with the suggested modification.
+
I've been able to setup the development environment and here's the screenshot of it with the suggested modification of my email replacing the "logout" text.
 
[[File:Sugar_running_scrshot.png|600px]]
 
[[File:Sugar_running_scrshot.png|600px]]
  
26

edits

Navigation menu