273
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: + + + + + + + + + + + + + +
Development Team/Project Ideas (view source)
Revision as of 16:08, 13 March 2009
, 16:08, 13 March 2009→About
* See http://wiki.laptop.org/go/Category:GSoC_proposals for last years' OLPC applications to GSoC. A quick scan indicates that around 80-90% of these would have been appropriate Sugarlabs applications if Sugarlabs had existed at the time. The other 10-20% would still be OLPC applications, because they involve either software for the XS (school server) or something specific about the XO hardware.
* See http://wiki.laptop.org/go/Category:GSoC_proposals for last years' OLPC applications to GSoC. A quick scan indicates that around 80-90% of these would have been appropriate Sugarlabs applications if Sugarlabs had existed at the time. The other 10-20% would still be OLPC applications, because they involve either software for the XS (school server) or something specific about the XO hardware.
=== General Priorities ===
There is no absolute ordering of Sugarlabs' priorities. Different members will not agree perfectly on what steps will do more to help our educational mission. So the list below is just one version, and I welcome other comments below.
My first priority is things that will have a strong effect on the long-term rate of development of Sugar. I'd put just 4 things in that category: the ability to develop activities in AJAX, ditto for Flash (because of the number of developers who know those tools, especially in the third world); and a structure for sugar unit tests (IMO we will never get good enough software quality for wide adoption, running on multiple distribution without automated testing).
My second priority is things that will improve on sugar's key promises. An easier and better way to handle files: versioned datastore, improvements in creating and using tags for the journal and file picker dialogs. A simpler and safer security model: getting Rainbow working in Sugar and improving it's coverage of the Bitfrost ideals. A simple and discoverable, yet powerful, UI overall: improved accessibility, discoverable keyboard shortcuts. Ubiquitous connectivity and collaboration: multi-pointer sharing, auto-collaborating data structures, viral/peer-to-peer activity distribution, shared journals. Useful in the classroom: a one-click workflow for getting AND turning in homework.
My third priority is activities to cover the core functions. Reading: an improved Read, which handles true ebook formats (PDF is made for printing). Writing: Write is pretty good. Communication: an email activity. Math: a great graphing utility.
My fourth priority is other educational activities. There are hundreds of good ideas out there.
On the other hand, a project is no good if it doesn't get done. The highest priorities on my list are also the hardest. An achievable idea for priority 4 is better than pie in the sky. And if you want to take on a bigger task, ask us in IRC - we will help guide you.
== (relatively) Well-explained ideas (follow template just below) ==
== (relatively) Well-explained ideas (follow template just below) ==