From 2197ec3a58b59164ea44f728af218a9763a31dcf Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Thu, 11 Apr 2013 06:08:06 +0000
Subject: [PATCH] Advanced Cap Types

[Imported from Trac: page GSoCIdeas, version 13]
---
 GSoCIdeas.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/GSoCIdeas.md b/GSoCIdeas.md
index 92660c0..52bd0ec 100644
--- a/GSoCIdeas.md
+++ b/GSoCIdeas.md
@@ -17,7 +17,8 @@ You might end up working on one of the projects below even after going through t
 |---|---|---|
 |*Project*|*Tickets*|*Difficulty*|
 |[#ShareRebalancingandRepair Share rebalancing and repair]|#699, #232|tricky|
-|[#UploadStrategyOfHappiness Upload Strategy Of Happiness]|#610, #1124, #1130, #1293, #1382, #1814|tricky|
+|[#UploadStrategyOfHappiness Upload Strategy Of Happiness]|#610, #1124, #1130, #1293, #1382, #1814|subtle|
+|[#AdvancedCapTypes Advanced Cap Types]|#795, #796, #954, #958|inconceivable|
 
 
 ## Share Rebalancing and Repair
@@ -28,4 +29,8 @@ A Summer of Code project might tackle repair and rebalancing, ensuring that serv
 
 ## Upload Strategy Of Happiness
 
-The *Servers of Happiness* criterion is already in place for deciding whether a given distribution of shares over servers satisfies the user's requirements for fault-tolerant distribution. However, the algorithm that decides what shares to upload to which servers is not optimized to always satisfy the Servers of Happiness criterion. [Kevan Carstensen's master's thesis](https://zooko.com/uri/URI%3ADIR2-RO%3Aoljrwy5i2t3dhcx5mzrksegehe%3Axtac4ubcnr5eqo6d7h4wyj5sm522olj4mthizz2i3lfw2b5nla6q/Latest/compsci/Carstensen-2011-Robust_Resource_Allocation_In_Distributed_Filesystem.pdf) explains the context in great details and proposes an *Upload Strategy of Happiness* algorithm for allocating shares to servers. Implementing the *Upload Strategy of Happiness* should close the following tickets: #610, #1124, #1130, #1293, #1382, #1814.
\ No newline at end of file
+The *Servers of Happiness* criterion is already in place for deciding whether a given distribution of shares over servers satisfies the user's requirements for fault-tolerant distribution. However, the algorithm that decides what shares to upload to which servers is not optimized to always satisfy the Servers of Happiness criterion. [Kevan Carstensen's master's thesis](https://zooko.com/uri/URI%3ADIR2-RO%3Aoljrwy5i2t3dhcx5mzrksegehe%3Axtac4ubcnr5eqo6d7h4wyj5sm522olj4mthizz2i3lfw2b5nla6q/Latest/compsci/Carstensen-2011-Robust_Resource_Allocation_In_Distributed_Filesystem.pdf) explains the context in great details and proposes an *Upload Strategy of Happiness* algorithm for allocating shares to servers. Implementing the *Upload Strategy of Happiness* should close the following tickets: #610, #1124, #1130, #1293, #1382, #1814.
+
+## Advanced Cap Types
+
+The current set of cap types is described on [Capabilities](Capabilities). There are several proposals for extended semantics: revocable write-caps (#945), a secure "301 Moved Permanently" redirect (#958), add-only sets (#795), write-only caps (#796).
\ No newline at end of file