tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

add Jack Lloyd's notes on Cloud Apps 

[Imported from Trac: page GSoCIdeas2010, version 79]
zooko 2010-03-16 16:30:20 +00:00
parent af51082923
commit 0462e585df
1 changed files with 20 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
GSoCIdeas2010.md

@ -10,12 +10,12 @@ We encourage you to come up with your own suggestions, if you cannot find a suit
Deadlines and directions for students' applications to the Google Summer-of-Code can be found on [the Google pages](http://code.google.com/soc/). Deadlines and directions for students' applications to the Google Summer-of-Code can be found on [the Google pages](http://code.google.com/soc/).
| | | | | | |
|---|---| |---|---|---|
|*Project*|*Difficulty*| |*Project*|*Difficulty*|*Contact*|
|[#RedundantArrayofIndependentClouds Redundant Array of Independent Clouds]|Medium| |[#RedundantArrayofIndependentClouds Redundant Array of Independent Clouds]|Medium|[Zooko Wilcox-O'Hearn]mailto:zooko@zooko.com|
|[#ShareMigration Share Migration]|Medium| |[#ShareMigration Share Migration]|Medium|any mentor|
|[#CloudApps Cloud Apps]|Easy–Hard|
---- ----
@ -61,6 +61,20 @@ file health and accounting, so prospective students would do well to explore
those open issues, too. A good accounting jumping-off point is #666. A good those open issues, too. A good accounting jumping-off point is #666. A good
jumping-off point for health is #778. jumping-off point for health is #778.
# Cloud Apps
Difficulty: easy to hard, depending on project choice and how far you want to push it
There are a lot of applications that could potentially make good use of Tahoe-LAFS replacing the typical centralized storage of flat files or SQL databases. Currently supported projects include [TiddlyWiki](http://www.tiddlywiki.com/) (one of the Tahoe-LAFS developers hosts his blog using [TiddlyWiki stored in Tahoe-LAFS](http://allmydata.org/trac/tiddly_on_tahoe)), [Hadoop](http://hadoop.apache.org/), and [a number of others](RelatedProjects).
There are still many useful and interesting things that have yet to be built using Tahoe-LAFS. Perhaps the most promising is in the area of web applications; what applications can you think of that could make use of a highly reliable filesystem accessible from both desktops and [handheld devices](http://github.com/ctrlaltdel/TahoeLAFS-android)? Keep in mind that Tahoe-LAFS's architecture allows sharing and delegation opportunities that are difficult or impossible to implement using other backends. Some ideas people have suggested include a calender or photo album, or porting Mozilla's [Bespin](https://bespin.mozilla.com) editor).
Nathan Wilcox wrote most of interactive tree browser frontend in JavaScript (see [RelatedProjects](RelatedProjects) [RelatedProjects page]the); Toby Murray wrote [a front-end in Cajita](http://allmydata.org/pipermail/tahoe-dev/2010-March/004137.html); what interesting ways might this be extended?
This is in some ways the most interesting area for development as it combines security and distributed systems problems with providing a user interface that lets a person who isn't particularly security minded operate safely by default. This is a hard problem, but offers great rewards in terms of learning, and even the ability to break new ground in safe-by-default interface design.
Required skills: HTML and JavaScript for web applications. For other tie-ins, will depend on the base project (for instance porting the git DVCS to run on Tahoe would good C-fu, with git experience helpful).
---- ----
# Mentors # Mentors
*Who is willing to spend about five hours a week (estimated) helping a student do it right?* *Who is willing to spend about five hours a week (estimated) helping a student do it right?*