273
edits
Changes
Development Team/Project Ideas (view source)
Revision as of 10:52, 27 March 2009
, 10:52, 27 March 2009→Stand-alone activities
==== KDEEdu ====
==== KDEEdu ====
Sugarize any [http://edu.kde.org/ KDEEdu] activity, especially the ones which have no corresponding Sugar activity. This probably means recoding the C to use GTK instead of QT and to use Sugar conventions. It is doubtful that this process could be automated, so you'd probably just do one activity.
Sugarize any [http://edu.kde.org/ KDEEdu] activity, especially the ones which have no corresponding Sugar activity. The issue is that Kdeedu uses qt, while sugar uses gtk; the student would propose a reasonable solution to this issue. It is doubtful that the whole sugarization process could be automated, so you'd probably just do one activity.
*Priority for Sugar: High
*Priority for Sugar: High
*Skills needed: Python, Glade, GTK. the Sugar collaboration framework
*Skills needed: Python, Glade, GTK. the Sugar collaboration framework
==== Bug report activity ====
[http://dev.sugarlabs.org/ticket/340 activity for bug reports]
*Priority for Sugar: High
*Difficulty: Easy
*Skills needed: Python, GTK, maybe some simple web forms from both client and server side (ie, PHP or similar)
==== Etc., Etc. ====
==== Etc., Etc. ====