Development Team/Project Ideas: Difference between revisions
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
* See http://wiki.laptop.org/go/Category:GSoC_proposals for last years' applications to OLPC. 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 applications to OLPC, 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' applications to OLPC. 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 applications to OLPC, because they involve either software for the XS (school server) or something specific about the XO hardware. | ||
== Well-explained ideas == | == (relatively) Well-explained ideas (follow template just below) == | ||
==== Template ==== | ==== Template ==== | ||
Line 144: | Line 144: | ||
*Difficulty (as a GSoC project): medium-hard | *Difficulty (as a GSoC project): medium-hard | ||
*Skills needed: | *Skills needed: intermediate ability with Python and communications | ||
== Brainstorm / unexplained ideas == | == Brainstorm / unexplained ideas == | ||
Line 150: | Line 150: | ||
* Accessibility Support: Sugar currently doesn't have anything available for the visually impaired. | * Accessibility Support: Sugar currently doesn't have anything available for the visually impaired. | ||
* [[DevelopmentTeam/DatastoreRewrite#Versioned_entries_.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[DevelopmentTeam/Almanac/sugar.datastore.datastore|DataStore]]: create a new version for each (automatic or manual) Keep with the same name / tags, create a branch if metadata was changed. Allow the user to access "older" versions (Keeping and "old" version will create a branch) and view ancestry (tree of branches). See also [http://wiki.laptop.org/go/Olpcfs Olpcfs]. | |||
==== Research projects: code exists, but more-or-less unpolished, and it would be awesome to get one of these really working well == | |||
* [[DevelopmentTeam/DatastoreRewrite#Versioned_entries_.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[DevelopmentTeam/Almanac/sugar.datastore.datastore|DataStore]]: create a new version for each (automatic or manual) Keep with the same name / tags, create a branch if metadata was changed. Allow the user to access "older" versions (Keeping and "old" version will create a branch) and view ancestry (tree of branches). See also (old) [http://wiki.laptop.org/go/Olpcfs Olpcfs] and (newer; less-documented; based on an RCS backend and a relatively small amount of fuse magic) [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2]. | |||
* There is also [http://wiki.laptop.org/go/Journal%2C_reloaded Journal, reloaded]], another research project with real code behind it that is promising but languishing. In this case, the idea is to make the journal "tagging" view transparently compatible with a traditional hierarchical directory structure. | |||
* bemasc's [http://dev.laptop.org/git/users/bemasc/groupthink/ groupthink], expanded: The idea is to have a data structure which keeps itself in sync across many laptops "behind the scenes", thus providing drop-in collaboration as long as the structure in question provides the needed functionality. The problem is that the existing code is unpolished, and only supports some pretty limited data structures. I have some ideas of [[how groupthink could be more general]]. [[User:Homunq|Homunq]] 00:43, 11 March 2009 (UTC) | |||
==== Java ==== | ==== Java ==== |