Line 84: |
Line 84: |
| * 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. |
| | | |
− | With the completion of this project, Sugar Labs will have a documented procedure to port and deploy applications that are part of the KDE Education Project. This will include about twenty applications, and others that are built using Qt but are not part of KDEEdu. This will save Sugar activity developers from having to write applications that may already exist but are not built for Sugar or that don't use GTK+. | + | With the completion of this project, Sugar Labs will have a documented procedure to port and deploy applications that are part of the KDE Education Project. This will include about twenty applications, and others that are built using Qt but are not part of KDEEdu. This will save Sugar activity developers from having to write applications that may already exist but are not built for Sugar or don't use GTK+. |
| | | |
| From homunq: KDEEdu is one of the most important set of open source educational programs. Having a demonstrated way to get those working in Sugar would help fill a number of important holes in our activity line-up, and would also help with making impressive demos. | | From homunq: KDEEdu is one of the most important set of open source educational programs. Having a demonstrated way to get those working in Sugar would help fill a number of important holes in our activity line-up, and would also help with making impressive demos. |
Line 94: |
Line 94: |
| * 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? |
| | | |
− | I would look for answers with other developers. This project is a crossroads of many greater projects (Sugar, KDE, Qt, GTK+) and so I will attempt to get answers any way I can. That includes the fundamental Google search, followed by contacting developers on IRC and mailing lists. This task of inter-compatibility between graphical toolkits is so important to open source development that there should be some great advice available. | + | I will look for answers with other developers. This project is a crossroads of many greater projects (Sugar, KDE, Qt, GTK+) and so I will attempt to get answers any way I can. That includes the fundamental Google search, followed by contacting developers on IRC and mailing lists. This task of inter-compatibility between graphical toolkits is so important to open source development that there will be some great advice available. |
| | | |
| * 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? |