Changes between Version 68 and Version 69 of GSoCIdeas2010
- Timestamp:
- 2010-03-12T06:24:03Z (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSoCIdeas2010
v68 v69 4 4 [http://code.google.com/soc Google Summer of Code] 5 5 6 The [http://www.python.org/psf Python Software Foundation], a GSoC umbrella organization, will sponsor Tahoe. 7 8 Students: you don't have to use one of the following Ideas. You can come up with your own Ideas, either inspired by these or your own Blue Sky idea. The most important thing is to e-mail the Mentor team (listed at the bottom of this page) ''immediately'' saying that you are interested. 9 10 See also the [http://wiki.python.org/moin/SummerOfCode/2009 PSF Ideas page], which includes a subset of these ideas, and a lot of other Python-but-not-Tahoe ideas. 11 12 Please read this page on the PSF wiki about [http://wiki.python.org/moin/SummerOfCode/Expectations what will be expected of you]. 6 Students: you don't have to use one of the following Ideas. You can come up with your own Ideas, either inspired by these or your own Blue Sky idea. The most important thing is to e-mail the Mentor team (listed at the bottom of this page) saying that you are interested. 13 7 14 8 = Ideas = … … 22 16 * HTTP proxy approach 23 17 * Special scheme handling in browser add-ons 24 * [http://code.google.com/p/google-caja Caja] approach: Require all Javascript to pass the Caja verifier in the Tahoe web frontend, then create an interface to the tahoe webapi which matches the intended capability semantics.25 * Tahoe Cryptography:18 * [http://code.google.com/p/google-caja Caja] approach: Require all Javascript to pass the Caja verifier in the Tahoe-LAFS web frontend, then create an interface to the tahoe webapi which matches the intended capability semantics. 19 * Tahoe-LAFS Cryptography: 26 20 * Help us author a paper proving the security of the crypto that will be used to implement new shorter caps (such as the [NewCaps/WhatCouldGoWrong Elk Point protocol] or the "Semi-Private Key" construction from http://allmydata.org/~zooko/lafs.pdf ). [http://allmydata.org/trac/tahoe-lafs/query?status=!closed&order=priority&keywords=~newcaps Tickets labelled 'newcaps'] 27 21 … … 29 23 * Make the [http://allmydata.org/trac/tahoe-w32-client Windows client] use only free open-source software. (Implementing WebDAV is an alternative that would achieve a similar effect.) 30 24 31 == Connecting Tahoe To Other Things ==25 == Connecting Tahoe-LAFS To Other Things == 32 26 * Filesystem access: 33 27 * improve the FUSE frontend ([source:contrib/fuse source code]). [http://allmydata.org/trac/tahoe-lafs/query?status=!closed&order=priority&keywords=~fuse Tickets labelled 'fuse'] 34 28 * support WebDAV for access from Windows and various filesystem browsers. [http://allmydata.org/trac/tahoe-lafs/query?status=!closed&order=priority&keywords=~webdav Tickets labelled 'webdav'] 35 * Explore running a Tahoe grid over [https://torproject.org Tor] or [https://i2p2.de I2P] to provide anonymity to servers and/or clients. 29 * integrate Tahoe-LAFS with the GVFS Gnome virtual filesystem 30 * Explore running a Tahoe-LAFS grid over [https://torproject.org Tor] or [https://i2p2.de I2P] to provide anonymity to servers and/or clients. 36 31 * Rescue the neglected C client library [http://allmydata.org/trac/libtahoeclient_webapi libtahoeclient_webapi]. 37 32 … … 41 36 * Use Zeroconf or similar so nodes can find each other on a local network to enable quick local share migration. 42 37 * Deal with unreliable nodes and connections in general, getting away from allmydata.com's assumption that the grid is a big collection of reliable machines in a colo under a single administrative jurisdiction. [http://allmydata.org/trac/tahoe-lafs/query?status=!closed&order=priority&keywords=~availability Tickets labelled 'availability'] 43 * Abstract out the server selection part of Tahoe so that the projects in this category of "grid membership and server selection" can be mostly independent of the rest of Tahoe. See also [http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#2009-02-06 this note about standardization of LAFS].38 * Abstract out the server selection part of Tahoe-LAFS so that the projects in this category of "grid membership and server selection" can be mostly independent of the rest of Tahoe-LAFS. See also [http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#2009-02-06 this note about standardization of LAFS]. 44 39 * Write a GUI to visualize and manipulate the set of servers connected and the set holding shares of files. 45 40 … … 53 48 * an interactive tree browser web frontend in !JavaScript (Nathan has written most of one -- what can it grow into?) 54 49 * Extend and improve the {{{tiddly_on_tahoe}}} implementation. 55 * Port another light-weight open source web app to Tahoe +javascript (calendar, photo album, [https://bespin.mozilla.com Bespin]).50 * Port another light-weight open source web app to Tahoe-LAFS+javascript (calendar, photo album, [https://bespin.mozilla.com Bespin]). 56 51 57 52 = Mentors =