24
edits
Changes
Summer of Code/2014/Port to Python3 (view source)
Revision as of 16:27, 20 March 2014
, 16:27, 20 March 2014→You and the community
===You and the community===
===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.
Kamaljeet Kaur: It's going to be an important project. Porting to a newer version is beneficial in long-term as the whole working will be enhanced with new features. It's the right time to make the required changes and because there are many developers who are contributing, sugar will not restrict them to use only previous versions of technologies.
There are several reasons why this project is important to Sugar Labs: (1) we need to keep pace with the projects we depend upon upstream -- Python 3 is being to become de rigour -- and (2) Python 3 has much better support for i18n and unicode -- critical to the global nature of our project. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 13:38, 20 March 2014 (EDT)
There are several reasons why this project is important to Sugar Labs: (1) we need to keep pace with the projects we depend upon upstream -- Python 3 is being to become de rigour -- and (2) Python 3 has much better support for i18n and unicode -- critical to the global nature of our project. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 13:38, 20 March 2014 (EDT)
Getting stuck means I have already put my efforts to solve some problem. Yes, the mentors are there to guide us, but in such a case, rather than keep waiting, without hesitating, I'll ask out the problem on IRC, mailing list of this sweet community. And if it's a technical problem, can be put on some other relevant places to get out of there.
Getting stuck means I have already put my efforts to solve some problem. Yes, the mentors are there to guide us, but in such a case, rather than keep waiting, without hesitating, I'll ask out the problem on IRC, mailing list of this sweet community. And if it's a technical problem, can be put on some other relevant places to get out of there.
* 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?
* 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?
The first strategy will be regular mails and interaction on IRC regarding questions and the progress both. The second will be use of git which will keep the community informed. Thirdly everything will be there on my blog regularly.
The first strategy will be regular mails and interaction on IRC regarding questions and the progress both.
The second will be use of git which will keep the community informed.
Thirdly everything will be there on my blog regularly as I already have such an experience.
===Miscellaneous===
===Miscellaneous===