= Related Projects = There are several projects in various states of maturity to extend Tahoe or integrate it with other tools. (These are in various states of maturity and maintenance -- please update this wiki and post to tahoe-dev if you play with any of these.) * François Deppierraz's Tahoe plugin for duplicity * {{{tiddly_on_tahoe}}} -- Zooko's plugin for !TiddlyWiki so it can save itself to Tahoe * Shawn Willden's ambitious new backup tool project (interesting vaporware) * {{{tahoewapijs}}} -- Nathan Wilcox's Tahoe !JavaScript library (unannounced) * {{{blackmatch}}} -- Rob Kinninmont's FUSE implementation * {{{src/allmydata/gui/macapp.py}}} -- Rob Kinninmont's Macintosh GUI * {{{contrib/fuse}}} -- three different FUSE implementations by three different authors * {{{tahoe-w32-client}}} -- a complete Windows product with filesystem integration (a virtual drive) and a GUI, written by allmydata.com and open-sourced, but not documented or announced = Spin-off Projects = These are projects that are currently primarily maintained by Tahoe developers. * foolscap * zfec * pycryptopp = Dependencies = We are fortunate to have a vast library of high quality Free Software that we can re-use to build Tahoe. We contribute patches and bug reports back to these projects. The following list is incomplete -- see also [source:_auto_deps.py]. * Python * Twisted * gcc * Nevow * setuptools = Other Projects = These projects have no specific relationship with our project, but they are similar in some ways and so may be of interest. We sometimes exchange ideas with the designers of some of these projects, especially on the [http://lists.zooko.com/mailman/listinfo/p2p-hackers p2p-hackers mailing list]. * [http://ceph.newdream.net/about ceph] is a distributed filesystem intended to be scalable and robust. It includes kernel code to be loaded into a Linux kernel. There are several peer-reviewed papers about the design. licence: LGPL * [http://flud.org flud backup] is an ambitious decentralized backup system. flud has the distinction of being one of few decentralized storage projects with a sense of humor. licence: GPLv3 * [http://cleversafe.org cleversafe] is a company that makes a distributed data storage grid. Some of the company's projects are released under GPLv2. * [http://irods.org iRODS] is an open source grid technology building on top of 10 years of work on SRB (storage resource broker). Development of the core iRODS data grid system is funded by the National Science Foundation and the National Archives and Records Administration. license: BSD * [http://gnunet.org GNUnet] is an anonymous, censorship-resistant, file-sharing network. licence: GPLv2+ * [http://hadoop.apache.org/core/ Hadoop] is open source, inspired by the Google File System, written in Java, supported by Yahoo, and seems to have broad acceptance among programmers (at least compared to the alternatives). licence: Apache Software Licence v2.0 * [http://kosmosfs.sourceforge.net CloudStore] formerly known as "Kosmos Distributed File System" -- is open source, inspired by the Google File System, written in C++, and recently announced some sort of compatibility with Hadoop. licence: Apache Software Licence v2.0 * [http://www.danga.com/mogilefs/ mogilefs] is open source, inspired by the Google File System, written in Perl and uses MySQL. It was written by the folks who made [http://livejournal.com LiveJournal]. The name is an anagram for "OMG files". licence: some combination of BSD and GPL and Artistic. * [http://fluidinfo.com/ fluidinfo] is a stealth-mode startup that is apparently doing something creative in the realm of knowledge management. The founder, Terry Jones, is or was a researcher in the field of artificial life and genetic algorithms. Here's [http://www.cs.unm.edu/~forrest/dissertations-and-proposals/terry.pdf his PhD thesis]. He also contributes to the Twisted Python project. fluidinfo hasn't released any source code. (interesting vaporware) == See Also == Our [wiki:Dev Dev page], especially the [wiki:Extensions developing Extensions page] Our [wiki:Bibliography Bibliography page].